IBM OS/390 manual Verification, Name, Profile, Sets

Page 66

 

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
Image 66
Page 65 Page 67
Contents IBM Page IBM Fourth Edition, September IBMContents Get RacfConsiderations IndexPspi RacfPage IBM USAUSA Page Trademarks Page Who Should Use This Book How to Use ThisAbout This Book BookServer Racf Information , Package see Where to Find More InformationOS/390 Security Server Racf Information , PackageSK2T-2180 OS/390 CollectionIBM Systems Center Publications Racf home RACF-L discussion list Other Sources of InformationSecurity Sample codePublications FtpFTP Servers Page PresentedRACF Planning inInstallation OS/390 VersionPage Migration Planning Considerations MigrationCustomization Considerations Installation ConsiderationsAdministration Considerations PSPGeneral User Considerations Auditing ConsiderationsApplication Development Considerations Data Areas OS/390 Security ServerPage Release Overview New and Enhanced SupportEnhancements to Support for OpenEdition Services UIDGID Run-Time Library ServicesPassword History Enhancements Gggg needsProgram ALLNew Fmid OW24966 Enhancements toGuide Enable/Disable ChangesAccess OW26237 EnhancementsRelease Callable ServicesNew Callable Services SYS1.SAMPLIBClass Descriptor Table CDT GIDUID Commands Command Language ReferenceNoclauth PermitParmlib Data Areas Exits ICHRFX03ICHRFX04 New Messages MacrosMessages Changed MessagesDeleted Messages PanelsICHH241C ICHP241CICHP242A MemberOS/390 Security Server Publications LibraryChanges to the Racf Publications Library Data Areas This No longer Licensed Publication Its New FormPlanning Considerations Migration StrategyHardware Requirements Racf Migration and Planning for Racf 1.9.2GC23-3045Program Control by System ID CompatibilityOpenEdition MVS RELEASE=2.4 Keyword onPage Virtual Storage Installation ConsiderationsRacf Storage Considerations Racf Estimated Storage UsageHow System Programmers Guide ICBPage RACF/DB2 External Security Module Customization Customization ConsiderationsCustomer Additions to the Router Table and the CDT RACF/DB2Exit Processing Administration Guide Volume , SC26For OS/390 Version Installation OS/390 Security Server Racf System Programmers. GuidePassword History Changes Administration ConsiderationsTmeadmin Class Server Racf Security Administrators. GuideEnhancements of Global Access Checking Racroute REQUEST=LISTAuditors Guide Auditing ConsiderationsSMF Records SysidPage Fastauth Changes Application Development ConsiderationsProgramming Interfaces Racroute IcheintyPage General User Considerations Security Server Racf General Users. GuidePage MVS UpdateGlossary AuditData DirectionFacility DirectoryFile EntityGID HFSNode PasswordRequest UnitPads PositProcess UtilityFile System ClassificationVerifyx RootSyscall Target NodeTask Profile VerificationName SetsHow to Get Your Racf CD Cics TSO/EPage Index SeeSee alsoexits IRR@XACS 19 Ispf panels LsqaPlpa Raclist SMF80DTASee alsoRRSF router table SmfidPage Readers Comments Wed Like to Hear from You IBM Readers Comments Wed Like to Hear from YouPage IBM
Related manuals
Manual 673 pages 53.75 Kb

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