Chapter 8. Auditing Considerations

This section summarizes the changes to auditing procedures for SMF re

SMF Records

Figure 12 summarizes changes to SMF records created by RACF for OS/39 Release 4. These changes are general-use programming interfaces (GUPI

Figure

12. Changes to SMF Records

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Record

 

 

Record

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Type

 

 

Field

 

Description

of

Change

 

 

 

 

 

Support

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

80

 

 

SMF80DTA

 

When

program

control

through

 

systemProgram

control

 

 

 

 

 

 

ID

is

operating,

a

new bit

isthroughdefinedsystemin

 

 

 

 

 

 

an

 

existing

relocate section

 

forID SMF

 

 

 

 

 

 

 

 

 

TYPE80 records written by the

 

 

 

 

 

 

 

 

 

 

PERMIT

command. The

relocate

 

 

 

 

 

 

 

 

 

 

 

section

is

data

type

39 (X'27'), and

the

 

 

 

 

 

 

new bit indicates that the conditional

 

 

 

 

 

 

 

entity

type

is

SYSID.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

80

 

 

SMF80DA2

 

This

 

record

with a ck_priv

eventOpenEditioncode

 

 

 

 

 

 

is

written

when

an

 

authorizationauditingcheck

 

of

 

 

 

 

 

 

is

done

for

a

superuser.

The superuserrecord

use

 

 

 

 

 

 

contains the audit function code to

 

 

 

 

 

 

 

 

indicate that the ck_priv callable

 

 

 

 

 

 

 

 

 

service was called from spawn

 

 

 

 

 

 

 

 

 

(IRRSPK00).

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

For

more

information on SMF records,OS/390seeS curity

Server

(RACF) Macros

and

Interfaces.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The

RACF/DB2 external

security

module

 

can

be

used

to

protect DB2 ob

RACF profiles. If your installation chooses to use this

function, RACF

records

can be used to audit access attempts to DB2 data and re

information on auditing for the

RACF/DB2 external securityOS/390 module, see

Security

Server

(RACF)

Auditor's.

Guide

 

 

 

 

 

 

 

 

 

Copyright IBM Corp. 1994, 1997

33

Page 53
Image 53
IBM OS/390 manual Auditing Considerations, SMF Records, Auditors Guide, Sysid, IRRSPK00

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.