The getUMAP and getGMAP services

also look for default values. If ge

given a

 

UID

as

input

 

and

the

corresponding

USER

profile

has

 

no

OMVS

the

caller

of the

getUMAP

service

receives

the

default.

If

no

de

RACF

return

code

8,

reason

code 4

are

returned

by

 

the

getUMAP

ser

is

passed

to

getUMAP,

then

it

returns

a

user ID,

which

is

likely t

of

the

 

default

user.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Similarly,

if

getGMAP

is

given

a

GID

as

input

and

the

corresponding

GR

has

no

OMVS

segment,

the

caller

of the getGMAP service receives the

no default value is found, RACF

return code 8, reason code 4 are r

getGMAP

service.

If

a

 

GID

is

passed

to

getGMAP,

it

returns

a

group

is

likely

to

return

the

group

name

of

the

default

group.

 

 

 

 

The default OMVS segments reside in a USER profile and a GROUP prof installation selects the names of these profiles, using a profile in class. The name of the FACILITY class profile is BPX.DEFAULT.USER. The application data field contains the user ID and the group name. The the user ID specified contains the UID, and the group profile f specified contains the GID.

In order to use this default USER/GROUP support, the following need

Ÿ Make the FACILITY class active.

ŸDefine BPX.DEFAULT.USER with APPLDATA(' uuuu/gggg') whereuuuu

specifies a

default user ID of 1gggg-8 charactersspecifie anddefault group

name of 1-8

characters.

The

USERuuuu profileneeds

to

have

an

OMVS

segment with

the default UID, HOME,

and

PROGRAM.

The

GROUP profile

gggg needs

to have an

OMVS

segment

giving

the

default

GID.

Ÿ If only default user information is needed,uuuuuse'). APPLDATA ('

The processing of the default OMVS segments for the user and the c connection group are independent of each other. The OMVS segment of specified on the initUSP may be used to obtain the UID, and the from the group ID specified in the FACILITY class profile. Similarly, default UID found through the user ID specified in the FACILITY used, the GID may come from the user's current connect group. Also specified in the FACILITY class profile does not need to be a mem specified in that profile. These values are used independently.

Run-Time Library Services

The Run-Time Library Services (RTLS) of OS/390 introduce new contents supervisor support to facilitate the binding of applications to a spe run-time environment defined on an installation basis. System programmers use FACILITY class profiles and RACF's program control when there is a control access to run-time libraries and the programs that use the r

Password History Enhancements

The

password

history

enhancement

makes it easier for installations to

users

from circumventing

password

history security policy. The old

pas

saved

in the

password

history

list when a password is reset by an

The

following

commands

have been

modified to

save the

old password

w

the

password

is reset:

 

 

 

 

 

 

 

 

 

 

 

Chapter

2. Release

Overview7

 

Page 26 Page 28
Page 27
Image 27
IBM OS/390 manual Run-Time Library Services, Password History Enhancements, Gid, Gggg needs
Page 26 Page 28

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