system. This support provides a solution

to

many

customers

that find

such

a

situation.

 

 

 

 

 

 

 

 

 

 

 

The PERMIT command has a

new keyword to add users and groups to the

conditional access list, WHEN(SYSID(...)). This keyword is

allowed

only

PROGRAM class. WHEN(SYSID(...)) is similar to the existing keywords

 

 

WHEN(TERMINAL(...)), WHEN(PROGRAM(...)), and WHEN(JESINPUT(...)). No

 

 

class

is

associated

with

SYSID. In addition, no check is made

to d

the

value specified

for

SYSID

is

valid.

 

 

 

 

 

 

A new error message is

issued

if

WHEN(SYSID(...))

is specified

 

for

than

PROGRAM.

When copying

a conditional

access list

from

a PROGRAM

pro

to a non-PROGRAM profile, WHEN(SYSID(...)) entries are not copied. No

messages

are

issued

if

this is the case. This applies

to ADDSD

FRO

FROM,

RACROUTE

REQUEST=DEFINE

with

modeling,

and

PERMIT

FROM.

 

 

 

New FMID

OS/390

Release

4

Security

Server

(RACF)

has

a

new

FMID,

HRF2240.

Altho

RACF, as a component of the OS/390

 

Security

Server,

no

longer

has

a

ve

release, and

modification

level

of

its

own,

for compatibility

with

pr

and

releases

of

RACF

the

new

FMID

is treated as if it represented

The RCVT contains the value 2040 to

identify the RACF level. The ICHEI

ICHEACTN, and ICHETEST macros

accept

the

keyword

RELEASE=2.4,

although

 

 

they

support

no

new

keywords

that

would require

the

RELEASE=2.4

keywor

OW24966 Enhancements to

TARGET

Command

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The RACF TARGET command now accepts the new keyword WDSQUAL

to

allow

 

allocation of the work space data sets when the system name starts

character. This keyword indicates that the variable that follows is

qualifier

used

by

RRSF

for

the

workspace

 

data set

qualifier

names

 

and OUTMSG queues for the local RRSF

node

defined

by the

TARGET comm

WDSQUAL

cannot

be used

for

a remote

node.

 

 

 

 

 

 

 

The format for the qualifiedprefixname.wdsqualis .

ds_.identitywdsqual

can

be

 

 

 

from 1 to 8 characters

long beginning with an alphabetic

character.

 

are

not

 

accepted.

The

formation of the workspace data

set

names

c

until the data sets are allocated. Specifying WDSQUAL

on

another

TARGET

command after its node has become dormant or operative is not allowe

Specifying of

 

WDSQUAL

on

the same command is allowed.

 

 

 

 

 

If you have any TARGET

commands in your IRROPTxx RACF parameter

libra

member that specify the WORKSPACE keyword abbreviated to

a

W,

you

n

increase

the

length

 

of

that

keyword

to at

least

WO

so

it

is

not

m

WDSQUAL

keyword

which

is

now represented as W. It is

recommended

t

use

of

 

abbreviations

be avoided

in

clists,

REXX

execs,

and parmlib

If WDSQUAL is not specified, the previously used format for the d used. Thisprefixis .sysname.INMSG and prefix.sysname.OUTMSG.

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

Chapter 2. Release Overview9

Page 29
Image 29
IBM OS/390 manual New Fmid, OW24966 Enhancements to

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.