Figure

11 (Page

3

of

3). RACF Estimated Storage Usage

Storage

 

 

 

 

 

 

 

 

 

 

 

Subpool

 

Usage

 

 

 

 

How

to

Estimate

Size

 

 

 

 

 

 

 

 

ECSA

 

RACF

data

set descriptor

table 168and +

(896× number_of_RACF_primary_data_sets)

 

 

extension

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

ICB

(non-shared

DB)

4096

per RACF

database if the database is not shared a

 

 

 

 

 

 

 

not

on

a device marked as shared, 0 otherwise

 

 

 

 

 

 

 

 

 

 

 

 

RACF

program

control

table

28

+

(number_of_program_profiles×

 

 

 

 

 

 

 

average_program_profile_size) +

 

 

 

 

 

 

 

(number_of_controlled_libraries× 50)

 

 

 

 

 

 

 

To find the average_program_profile_size, use the followi

 

 

 

 

 

 

 

formula:

 

 

54+ (average_number_of_access× 9)entries+ (average_number_of _conditional_access× _17)entries+ (average_number_of_libraries× 52)

RACF resident data blocks

For each primary

RACF database: 3248× +

(4136

 

number_of_database_buffers) If using sysplex

 

communication, for

each backup database

add: 3248 + (41

×number_of_database_buffers× 2)

 

 

Dynamic

parse

tables

30

000

 

 

 

SETROPTS

GENLIST

profiles

52

+ (number_of_profiles_×in_16)class+

 

 

 

 

 

(number_of_resident_profiles× (10 + average_profile_size +

 

 

 

 

 

(1.×5 class_max_profile_name_size)))

 

 

 

 

 

 

User

private

RACF transient

storage

16 000 (minimum) while a RACF service is executing

Below

16MB

 

 

 

 

 

 

Templates for RACF on

OS/390 Release

4

 

 

 

 

 

 

 

 

 

 

 

 

 

The

RACF

database

must

have

templates

at

the

Security Server

(RACF)

R

level

in

order

for

RACF

to

function properly.

 

If a Security Server (

system

is

sharing

the

database

with

a

lower-level

system

(RACF

1.9,

 

RACF

1.10,

RACF 2.1, RACF 2.2, Security Server

(RACF)

Release

1,

Secur

Server (RACF) Release 2, or Security Server

(RACF)

Release

3),

the

lo

system

is

able

to

use

the

database

with

the Security Server (RACF)

templates.

Use the IRRMIN00 utility to install

the

 

templates.

 

 

 

For

more

information, OS/390see Security

Server

(RACF)

System

Programmer's

 

 

Guide and

the

program directory

shipped

with

OS/390.

 

 

 

 

Chapter 5. Installation Considerations27

Page 46 Page 48
Page 47
Image 47
IBM OS/390 manual System Programmers Guide, Icb
Page 46 Page 48

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