IBM OS/390 manual Syscall, Target Node, Task

Page 65

supervisor

.

 

The

part

of

a

control

program

thatexternal

format,

allowing

a caller to access individ

coordinates

 

the

use

of

resources

and

maintainsfieldsthe withinflow

the

UTOKEN.

 

 

 

 

 

of processing unit operations. Synonymsupervisoryfor

 

TOKENXTR

request

 

 

.

The issuing of the RACROUTE

routine.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

macro

 

with

REQUEST=TOKENXTR

specified.

A

 

supervisory

routine

 

.

 

A

routine,

 

usually

part

of TOKENXTRan

request

extracts

a

UTOKEN

from

the

operating system, that controls the executioncurrentofotheraddress space,

task,

or

a

caller-specified

routines and regulates the flow of work in a data

 

 

 

 

 

 

 

 

 

 

 

processing

system.

Synonymous supervisorwith .

 

 

transaction

program

(TP)

. A

program used

for

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

cooperative transaction processing within an SNA

syscall .

In

OpenEdition

MVS,

 

deprecated

term

networkfor.

For

APPC/MVS,

any

program

on

MVS

 

that

callable

service.

 

 

 

 

 

 

 

 

 

 

 

 

issues

 

APPC/MVS

or CPI Communication calls, or is

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

scheduled by the APPC/MVS transaction scheduler.

sysplex . A set of MVS systems communicating and

 

 

 

 

 

 

 

 

 

 

 

 

 

cooperating

 

with

each other through multisystemTSO segment

 

.

The

portion of a RACF profile

hardware elements and software services to

containingprocess TSO

logon

information.

 

 

 

 

customer

workloads.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

sysplex

communication

 

 

.

An

optional

RACF

function

U

 

 

 

 

 

 

 

 

 

 

 

 

 

that

allows

 

the

system

to

use

XCF

services

and

 

 

 

 

 

 

 

 

 

 

 

 

 

communicate

with

other

systems

that

are

also

UACC .

 

Seeuniversal

access

authority.

 

 

enabled

 

 

 

 

 

 

 

 

 

 

for sysplex

communication.

 

 

 

 

 

 

 

 

UID .

 

Seeuser

identifier.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

system

authorization

facility

(SAF)

 

.

 

An

MVS

 

 

 

universal

 

access

authority

(UACC)

.

The

default

component

that

provides

a

central point

of

 

 

control

 

for

 

 

 

 

 

 

 

 

 

 

security

decisions.

It

either

processes

 

access authority that applies to a resource if

requests

directly

 

 

permitted

access to the

or works

with

RACF

or

 

another

security

 

 

group

 

is not

specifically

 

product to

 

 

The universal access authority can be a

process

them.

 

 

 

 

 

 

 

 

 

 

 

 

 

resource.

 

 

 

 

 

 

 

 

 

 

 

 

 

the

access

authorities.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

system call . In OpenEdition MVS, synonym for callable service.

user . A person who requires the services of a computing system.

T

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

user

 

ID .

 

A

string

of

characters

that

 

uniquely

iden

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

a user to a system. A user ID is 1 to 8 alpha

target

node .

 

 

An

RRSF

node

that

a

given

 

RRSF

 

characters.

 

On

TSO,

user

 

IDs

cannot

exceed

7

 

 

 

 

node

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

is

logically

 

connected

to as

a

result

 

of

a

characters

and

must

begin

with

an

alphabetic,

#,

$

 

 

 

TARGET

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

command.

The

 

local node

 

is

a

 

 

 

 

 

 

 

 

@

 

character.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

target node of itself, and

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

all of its remote nodes

are

targetlocalnodes.

 

See also

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

node, remote

 

 

node.

 

 

 

 

 

 

 

 

 

 

 

 

 

user

 

identification

 

and

verification

 

 

.

The

acts

of

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

identifying

and

verifying a RACF-defined user to th

task .

(1) A

 

basic

unit

of

work

to

be

 

 

 

system

during

a

logon

or

batch

job

processing.

 

RACF

 

 

accomplished by

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

identifies the user by the user ID and verifie

computer. The task is usually specified to a control

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

program

in

a

multiprogramming

or

multiprocessing

 

by

the password or operator identification card

environment.

(2) A basic

unit

of

work

to

be

 

during

logon

processing

or

the

password

 

supplied

on

performed.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Some examples

include

a

 

user

task,

 

a

server

batch

JOB

statement.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

task,

and

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

a

processor

 

task.

(3) A

process

and

the

procedures

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

that

run

the

process.

(4) In

a

 

 

 

 

 

 

 

user

 

identifier

(UID)

 

.

(1) A

unique

string

of

character

multiprogramming

 

or

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

multiprocessing

environment,

one

or

more

 

 

 

 

that identifies

an

operator

to

the

system. This

s

sequences

 

of

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

instructions

 

treated

by

a

control

program

as

characters limits the functions and information the

 

 

an

element

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

of work to be accomplished by

a

 

computer.

operator

can

 

use. (2) A

non-negative

integer,

which

 

(5) The

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

basic

unit

 

of

work

for

the

MVS

system.

 

 

can

be contained in an objectuid_oft,hattypeis used

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

to

 

identify a system user. When the identity of

TOKENBLD

request

 

 

 

.

The

issuing

of

the

 

 

 

 

is

 

associated

 

with

a

process,

a

user

ID

value

 

 

 

 

RACROUTE

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

macro

with

 

REQUEST=TOKENBLD

 

specified.

A

 

 

 

 

to

 

as

a

real

 

user

ID,

 

an

effective

 

user

ID,

o

TOKENBLD

request

builds

a

UTOKEN.

 

 

 

 

 

 

 

(optional)

saved

 

set-user-ID.

(3) The

identification

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

associated

with

a

user

or

job.

 

The

 

two types

o

TOKENMAP

request

 

 

 

.

The

issuing

of

the

 

RACROUTEare:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

macro

with

 

REQUEST=TOKENMAP

specified.

A

 

 

 

 

 

Ÿ

 

RACF

user

ID:

 

 

A

string

of characters

that

uniquel

TOKENMAP

request

maps

a

token

in

either

internal

 

 

 

or

 

 

 

 

a

RACF user

or

a

batch

job

owner

t

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

identifies

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Glossary

 

45

 

 

 

Image 65
Contents IBM Page IBM IBM Fourth Edition, SeptemberContents Considerations RacfGet IndexRacf PspiPage USA IBMUSA Page Trademarks Page About This Book How to Use ThisWho Should Use This Book BookOS/390 Security Server Racf Information , PackageSK2T-2180 Where to Find More InformationServer Racf Information , Package see OS/390 CollectionIBM Systems Center Publications Security Other Sources of InformationRacf home RACF-L discussion list Sample codeFTP Servers PublicationsFtp Page OS/390 Version PresentedRACF Planning inInstallationPage Migration Migration Planning ConsiderationsAdministration Considerations Installation ConsiderationsCustomization Considerations PSPApplication Development Considerations Auditing ConsiderationsGeneral User Considerations Data Areas OS/390 Security ServerPage New and Enhanced Support Release OverviewUID Enhancements to Support for OpenEdition ServicesPassword History Enhancements Run-Time Library ServicesGID Gggg needsALL ProgramOW24966 Enhancements to New FmidAccess Enable/Disable ChangesGuide OW26237 EnhancementsNew Callable Services Callable ServicesRelease SYS1.SAMPLIBUID Class Descriptor Table CDTGID Command Language Reference CommandsParmlib NoclauthPermit Data Areas ICHRFX04 ExitsICHRFX03 Messages MacrosNew Messages Changed MessagesPanels Deleted MessagesICHP242A ICHP241CICHH241C MemberChanges to the Racf Publications Library Publications LibraryOS/390 Security Server Data Areas This No longer Licensed Publication Its New FormMigration Strategy Planning ConsiderationsRacf Migration and Planning for Racf 1.9.2GC23-3045 Hardware RequirementsOpenEdition MVS CompatibilityProgram Control by System ID RELEASE=2.4 Keyword onPage Racf Storage Considerations Installation ConsiderationsVirtual Storage Racf Estimated Storage UsageHow ICB System Programmers GuidePage Customer Additions to the Router Table and the CDT Customization ConsiderationsRACF/DB2 External Security Module Customization RACF/DB2For OS/390 Version Installation Administration Guide Volume , SC26Exit Processing OS/390 Security Server Racf System Programmers. GuideTmeadmin Class Administration ConsiderationsPassword History Changes Server Racf Security Administrators. GuideRacroute REQUEST=LIST Enhancements of Global Access CheckingSMF Records Auditing ConsiderationsAuditors Guide SysidPage Programming Interfaces Application Development ConsiderationsFastauth Changes Racroute IcheintyPage Security Server Racf General Users. Guide General User ConsiderationsPage Glossary UpdateMVS AuditFacility DirectionData DirectoryGID EntityFile HFSRequest PasswordNode UnitProcess PositPads UtilityVerifyx ClassificationFile System RootTask SyscallTarget Node Name VerificationProfile SetsCics TSO/E How to Get Your Racf CDPage See IndexPlpa See alsoexits IRR@XACS 19 Ispf panelsLsqa See alsoRRSF router table SMF80DTARaclist SmfidPage Readers Comments Wed Like to Hear from You Readers Comments Wed Like to Hear from You IBMPage 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.