security program for the system. The

 

batch

job

 

 

 

 

 

 

 

 

 

 

 

 

 

 

owner is specified on the

 

USER

parameterV

on

 

the

 

 

 

 

 

 

 

 

 

 

 

 

 

 

JOB

statement

 

or

inherited

 

from

the

submitter

 

of

the

 

identification and

.verification

 

job.

This

user

ID

identifies

a

RACF

 

verification .

Seeuser

 

 

user

profile.

 

 

 

 

 

 

 

 

 

 

 

 

Ÿ

OMVS

user

ID:

 

A

 

numeric

value

 

between

0

 

andVERIFY

 

request

 

.

 

The

issuing

of

the

RACROUTE

 

 

2147483647, called a UID (or sometimes macrouserwith

REQUEST=VERIFY

specified.

A

VERIFY

 

number), that identifies a user to OpenEditionrequest is

used to verify the authority of a use

 

services. These numbers appear in the RACFworkuserinto the system. The

VERIFY

request replaces t

 

profile

for

the

user.

 

 

 

 

 

 

 

 

RACINIT

function.

 

 

 

 

 

 

 

 

 

 

A

user ID

is

equivalent

to

 

an

account

 

on a UNIX-type

.

The

issuing

of

the

RACROUTE

 

system.

(4) A

symbol

identifying

a

 

system

 

VERIFYX

request

 

 

 

 

 

user.

 

with

REQUEST=VERIFYX specified.

A

VERIFYX

(5) Synonymous

with

 

user

identification.

 

 

 

macro

 

 

 

 

request verifies a user and builds

a

UTOKEN, and

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

user

name .

(1) In

RACF,

one

to

20

 

 

 

 

handles

the

propagation

of

submitter

ID.

 

alphanumeric

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

characters

that

represent

a

RACF-defined

 

user.

(2) In

 

 

 

 

 

 

 

 

 

 

 

 

 

OpenEdition

MVS,

a

 

string

that

is

used

to

VM . A licensed program that controls “virtual

 

 

identify

a

and runs on two main command

languages,

user.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

machines”

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CP

and

CMS.

 

Can be

VM/SP,

VM/HPO,

VM/XA,

or

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

user

profile .

 

A

description

of

 

 

 

 

 

 

 

VM/ESA.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

a RACF-defined user

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

that includes the user ID, user

name,

 

default

group

 

 

 

 

 

 

 

 

 

 

 

 

 

name,

password,

profile

owner,

user

attributes,

and

 

 

 

 

 

 

 

 

 

 

 

 

 

other information. A user profile

can

 

 

 

W

information

 

 

 

 

 

 

 

 

 

 

 

 

include

 

 

 

 

 

 

 

 

 

 

 

 

for

subsystems

such

as

 

TSO

and

TSODFP.

See

 

workspace

 

data

sets

.

VSAM

data sets

used

by

RACF

segment

andDFP

segment .

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

for

queuing

requests

sent

to

and

received

from targ

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

nodes

 

in

an

RRSF

environment.

 

 

 

 

 

 

46 OS/390 V2R4.0 Security Server (RACF) Planning: Installation and Migration

Page 65 Page 67
Page 66
Image 66
IBM OS/390 manual Verification, Name, Profile, Sets
Page 65 Page 67

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