Chapter 7. Administration Considerations

This chapter summarizes the changes to administration procedures that administrator should be aware of. For more OS/390information,Securitysee

Server (RACF) Security Administrator's. Guide

The TMEADMIN Class

The

new TMEADMIN class is used to associate a TME

administrator

with

a

MVS

identity

on

any MVS system that

is

part

of

a Tivoli management

re

The

TMEADMIN

class

contains a profile

for

each

TME

administrator

who

is

perform RACF user management tasks. The name of this profile is the T administrator string name. For example:

admin-login-name@TME-region-name

The hex code for @ is x'7C'. You need to use the key on your key provides that hex value. Sharing of a single RACF user ID by multiple administrators is not recommended. It is preferable that each TME ad map to a unique RACF user ID.

In

the

following

example, the

TME

administrator root

in

the

Tivoli

TMR r

pok01 would have a RACF user ID

of

CSMITH.

The APPLDATA

field of

this

contains

the

RACF

MVS userid.

Only

a

RACF

administrator

with

SPECIAL

autho

can

issue

this

command:

 

 

 

 

 

 

 

 

 

RDEFINE

TMEADMIN root@pokð1 APPLDATA('CSMITH')

 

 

 

 

 

 

For more information on the TMEADMIN

class,

see

“Tivoli

Management

 

Environment

(TME)

10

Global Enterprise

Management User Administration Service

on

page 8.

 

 

 

 

 

 

 

 

 

 

 

Password History Changes

When

an administrator

resets a password for

a user, the

old

passwor

the password history list. This is done with the use of

one

of th

commands:

 

 

 

 

ALTUSER (userid ...) PASSWORD

 

 

 

ALTUSER (userid ...) PASSWORD(password)

 

 

 

PASSWORD USER(userid ...)

 

 

 

 

For

more information,

see “Password History

Enhancements” on

page 7.

Program Control by System ID

Program control by system ID limits a user's access to a particular specified system. It improves system management and usability of pro products in the sysplex environment. In addition, it eliminates error-p procedures, eliminates the need to keep DASD that is not shared, an the possibility of license exposures.

Copyright IBM Corp. 1994, 1997

31

Page 51
Image 51
IBM OS/390 manual Administration Considerations, Tmeadmin Class, Password History Changes

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.