Figure

11 (Page

2

of

3).

RACF Estimated Storage Usage

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Storage

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Subpool

 

Usage

 

 

 

 

 

 

 

 

 

 

 

How

to

Estimate

Size

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ESQA

 

RACF

data

sharing

control

area

 

300 (when enabled for sysplex communication)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Class

descriptor

table

(CNSX)

 

(number_of_IBM-defined_classes×28) +

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(number_of_IBM-defined_entries_in_router×30)_table+

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(number_of_customer_defined_classes× 58) + 26

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

For Security Server (RACF), there are 145 IBM-defined

 

 

 

 

 

 

 

 

 

 

 

 

 

 

classes and 167 IBM-defined

entries in

the

router

table, s

 

 

 

 

 

 

 

 

 

 

 

 

 

 

the size of the CNSX is 9096 +

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(number_of_customer_defined_classes× 58).

If

you

install a

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PTF that adds entries, you will need

to

recalculate

this

 

 

 

 

 

 

 

 

 

 

 

 

 

 

number.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

LSQA

 

ACEE and

related

storage

 

 

 

400 + installation_data_length +

 

 

 

 

 

 

 

 

 

 

Notes:

 

 

 

 

 

 

 

 

 

 

 

terminal_installation_data_length

+

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

application_installation_data +

(52

for

every

78

temporary

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1. Applications

can

place

this

 

stor

ge

 

 

 

up

to

the

next

multiple

of

52)

 

 

 

in

a

different

subpool.

 

datasets, rounded

 

 

 

 

If

the

address space

has

been

dubbed

an

OpenEdition

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2. Applications

can

create

multipleprocess,

then add:

52

+

 

 

 

 

 

 

 

 

 

 

 

 

ACEEs

in

this

and

 

other

storage

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

subpools.

 

 

 

 

 

 

 

 

(number_of_connected_groups_with× GIDs4)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Add 112 bytes if the user

has

CLAUTH

for

a

class with

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

POSIT

value

over

127.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ELSQA

 

Connect

group

table

 

 

 

 

 

64 + (48× number_of_groups_connected)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In-storage

generic

profiles

160 + number_of_generic_profiles× (14 +

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

average_profile_size + average_profile_name_length)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

storage

tracking

table

 

 

3500

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACROUTE

REQUEST=LIST

profiles

2108 + (number_of_profiles_×in_16)class+

 

 

 

 

 

 

 

 

 

Note:

Applications

can

place

 

 

(number_of_unique_generic_profile_prefix× 24)lengths+

 

 

 

 

these

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

profiles

in

a

 

 

 

 

 

(number_of_generic_profiles× 4) +

 

 

 

 

 

 

 

 

 

 

 

 

 

different storage

 

 

 

 

 

 

+

average_profile_size

+

 

 

 

subpool.

 

 

 

 

 

 

 

 

(number_of_resident_profiles× (10

 

 

 

 

 

 

 

 

 

 

 

(1.×5 class_max_profile_name_size))) for each class if

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

GLOBAL=YES

is

not

specified

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CSA

 

RACF

global

access

tables

 

 

3040 + (number_of_user_classes× 24) +× (182 +

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

number_of_entries×

(6

+ ×(1max.5_profile_name_size)))

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

database

control

structures

4600

+

(number_of_BAM_blocks× 6)

+

(364

x

 

 

 

 

 

 

 

(DCB, DEB,

templates)

 

 

 

 

number_of_RACF_primary_data_sets)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

subsystem

 

control

blocks

3500

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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

Page 46
Image 46
IBM OS/390 manual How

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.