Chapter 5. Installation Considerations

This chapter describes the following changes of interest to the sys installing OS/390 Release 4 Security Server (RACF):

Ÿ Virtual storage considerations

ŸTemplates

RACF Storage Considerations

This section discusses storage considerations

for RACF.

 

 

Using

the RACF DB2

external security

module

increases the

number

of

the

RACF database.

Therefore, if you

plan

to use the RACF

DB2

ext

module, recalculate the amount of storage that is needed. If there storage, you should increase the size of the RACF database.

Virtual Storage

Figure 11 estimates RACF virtual storage usage for planning purposes.

Figure

11 (Page

1

of

3).

RACF Estimated Storage Usage

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Storage

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Subpool

 

Usage

 

 

 

 

 

 

 

 

 

 

 

How

to

Estimate

Size

 

 

 

 

 

 

 

 

 

 

 

FLPA

 

RACF

service

routines,

if

IMS

or 47CICS000

 

 

 

 

 

is using RACF for authorization

 

 

 

 

 

 

 

 

checking

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACROUTE

REQUEST=FASTAUTH

 

 

 

 

 

Measure

using

AMBLIST

 

 

and

ICHRTX00

exits

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLPA

 

RACF

installation

exits

that

 

are

 

Measure

using

AMBLIST

 

 

AMODE(24)

or

AMODE(ANY)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

RMODE(24)

code

 

 

 

 

 

 

750

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

service

routines,

if

IMS

or 47CICS000

 

 

 

 

 

is not using RACF for authorization

 

 

 

 

 

 

checking,

unless

explicitly

removed

 

 

 

 

 

 

from

SYS1.LPALIB

and

placed

 

 

 

 

 

 

 

 

 

 

elsewhere for use in FLPA

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACROUTE

REQUEST=FASTAUTH

 

 

 

 

 

Measure

using

AMBLIST

 

 

and

ICHRTX00

exits

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

range

table

 

 

 

 

 

 

4 + (number_of_ranges× 45)

 

 

 

 

 

 

 

 

 

 

 

 

EPLPA

 

RACF

installation

exits

that

 

are

Measure

using

AMBLIST

 

 

AMODE(31)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RACF

resident

modules

above

16MB

875

000

 

 

 

 

 

 

 

 

 

 

 

 

 

SQA

 

RACF

communications vector

table

and2800

 

 

 

 

 

 

extension

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Class

descriptor

table

(CNST)

and

7500

+

58 × number_of_customer_defined_classes

 

 

RACF

router

table

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Copyright IBM Corp. 1994, 1997

25

Page 45
Image 45
IBM OS/390 manual Installation Considerations, Racf Storage Considerations, Virtual Storage, Racf Estimated Storage Usage

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.