IBM OS/390 manual Customization Considerations, Customer Additions to the Router Table and the CDT

Page 49

Chapter 6. Customization Considerations

This chapter identifies customization considerations for OS/390 Release Server (RACF).

For additional information,OS/390seeSecurity Server (RACF) System

Programmer's Guide.

Customer Additions to the Router Table and the CDT

Installations must verify that classes they have added to the route descriptor table (CDT) do not conflict with new classes shipped with duplicate table entries are detected, the following error messages time:

ŸFor a duplicate router table entry, RACF issues this message and processing:ICH527I RACF DETECTED AN ERROR IN THE INSTALLATION ROUTER￿

TABLE, ENTRY class_name, ERROR CODE 1.

ŸFor a duplicate CDT entry, RACF issues this message and enters fa

ICH564A RACF DETECTED AN ERROR IN THE INSTALLATION CLASS ￿DESCRIPTOR TABLE, ENTRY class_name, ERROR CODE 7.

If a conflict in class names occurs, you must delete the profiles installation-defined class with the conflicting name, delete the CDT ent class, add a CDT entry with a different name, and redefine the pr

Do not assemble the user-defined CDT (ICHRRCDE) on OS/390 Release 4 a attempt to use it on a system running RACF at a lower level than RACF Release 2.

RACF/DB2 External Security Module Customization

If you have both this release of RACF and Version 5 of DB2, you protect DB2 objects. Migrating to this can be done one object at example, all DB2 tables can be protected by RACF while other DB2 o RACF-protected. If an object is not protected by RACF, the RACF/DB2 security module defers to DB2 for authority checking.

The following is an overview of the steps involved in customizing RACF/D external security module. For OS/390details,Securitysee Server (RACF) System Programmer's Guide andOS/390 Security Server (RACF) Security Administrator's Guide

ŸConcerned staff members, such as the security administrator, syste

programmer, DB2 system programmer, and database administrator, need

decide

whether to

use

the

RACF/DB2

external

security

module.

 

Ÿ Staff members

need

to

decide which

of the options (such as cla

name options) offered by the RACF/DB2

external

security

module

the

use. This can be as simple as using

the defaults, which is reco

defaults

are

used,

no

new

classes are needed.

 

 

Copyright IBM Corp. 1994, 1997

29

Image 49
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 PublicationsFTP Servers 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.SAMPLIBGID Class Descriptor Table CDTUID Command Language Reference CommandsPermit NoclauthParmlib Data Areas ICHRFX03 ExitsICHRFX04 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 RootTarget Node SyscallTask Name VerificationProfile SetsCics TSO/E How to Get Your Racf CDPage See IndexLsqa See alsoexits IRR@XACS 19 Ispf panelsPlpa 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.