Figure 4

(Page

3

of

3).

 

Changes to RACF Commands

 

 

 

 

 

 

Command

Description

 

 

 

 

 

 

 

 

 

 

 

 

 

Support

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

TARGET

The

new

 

keyword

 

WDSQUAL

is

 

added

to

theOW24966

 

 

 

RACF TARGET command to indicate that the

 

 

 

 

 

variable that follows will be used

by RRSF

as

the

 

middle

qualifier

 

for

the

work

space

data

set

names

 

of

the

 

INMSG

and

OUTMSG

queues

for

the

local

 

 

 

RRSF node defined by the TARGET command.

 

 

 

 

 

WDSQUAL

cannot

be

used

for

a

remote

node.

 

 

 

 

The format for the qualifier name is

 

 

 

 

 

 

prefix.wdsqual.ds_identity. wdsqual can

be

from

1

 

 

 

 

to 8 characters long beginning with an alphabetic

 

character.

Initial

numerals

are

not

accepted.

The

 

formation of the workspace data set names can be

 

changed until the data sets are allocated. This

 

normally occurs when a DORMANT or OPERATIVE

 

 

 

 

 

keyword is processed. After that keyword is

 

 

 

processed, the data set names cannot be changed.

 

Concerning

TARGET

nodename

OPERATIVE

 

 

 

 

 

 

 

 

WDSQUAL(xxx) , RACF processes the

 

 

 

 

 

 

 

OPERATIVE keyword after the WDQUAL

keyword,

 

 

 

 

even though the user specified them in the reverse

 

order.

The

keyword

WDSQUAL

 

works until

RACF

 

 

 

 

has processed a TARGET command specifying

 

 

 

 

 

DORMANT or

OPERATIVE

for

that

node.

 

 

 

 

 

 

 

This

enhancement

allows

operators

to

set

one

or

 

 

 

more work space data sets for

local

node

names,

 

which can be used when they are working with

 

 

 

multisystem RRSF nodes, especially in a sysplex

 

 

 

environment.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

If you have any TARGET commands in your

 

 

 

 

 

IRROPTxx RACF parameter library member that

 

 

 

 

specify

the

WORKSPACE

 

keyword

abbreviated to a

 

 

 

W,

you

 

need

to

increase

the

length

of

that

keyword

 

to at least WO so it is not

mistaken

for

the

new

 

WDSQUAL

keyword

which

is now

represented

as

 

 

 

W.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

If WDSQUAL is not specified, the previously used format for the data set names is used. This is prefix.sysname.INMSG and

prefix.sysname.OUTMSG.

For more information on the TARGET command, seeOS/390 Security Server (RACF) Command Language Reference.

Data Areas

Figure 5 lists changed product-sensitive programming interface (PSPI) data for RACF.

Chapter 3. Summary of Changes to RACF Components for OS/390 15Release 4

Page 34 Page 36
Page 35
Image 35
IBM OS/390 manual Data Areas
Page 34 Page 36

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.
Top Page Image Contents