IBM OS/390 Compatibility, OpenEdition MVS, Program Control by System ID, RELEASE=2.4 Keyword on

Page 43

Compatibility

This section describes considerations for compatibility between OS/390 Security Server (RACF) and OS/390 Release 3 Security Server (RACF).

OpenEdition MVS

If you are an OpenEdition MVS user, be sure to review carefully th information on possible changes.

For Auditability of Superusers

If you are not already auditing the PROCESS class, you need to dec you want to receive the audit records. If you do decide you w

OpenEdition spawn service, issue SETROPTS LOGOPTIONS(xxxx(PROCESS))

to

obtain the SMF TYPE80 record ck_priv in order to

audit superuser use.

auditing

the

PROCESS class, you do not need to

issue

that

command.

You

need

to

change any programs reporting from

the

unloaded data if

spawn

audit

information.

 

 

 

For Default USER/GROUP OpenEdition Segment

The existing type 317 relocate section appears on any SMF TYPE80 recor written by the RACF callable services for users running with any def OpenEdition information.

You need to change any programs reporting from the unloaded data if support.

Program Control by System ID

If users are already allowed access through the standard access removed from these lists so the conditional access list entry is use program profiles must be refreshed with SETROPTS WHEN(PROGRAM)

REFRESH to activate the updated PROGRAM profiles.

RELEASE=2.4 Keyword on

Macros

 

 

 

 

 

 

 

 

 

 

You

should only

specify

RELEASE=2.4

and

reassemble

if you

intend

to u

new

keywords.

If

you

use

the new keywords,

you

need

to run

the

OS/390 Release

4

system

to

get

the

expected

results.

 

 

Chapter 4. Planning Considerations23

Page 42 Page 44
Image 43
Page 42 Page 44
Contents IBM Page IBM IBM Fourth Edition, SeptemberContents Index RacfConsiderations GetRacf PspiPage USA IBMUSA Page Trademarks Page Book How to Use ThisAbout This Book Who Should Use This BookOS/390 Collection Where to Find More InformationOS/390 Security Server Racf Information , PackageSK2T-2180 Server Racf Information , Package seeIBM Systems Center Publications Sample code Other Sources of InformationSecurity Racf home RACF-L discussion listFtp PublicationsFTP Servers Page OS/390 Version PresentedRACF Planning inInstallationPage Migration Migration Planning ConsiderationsPSP Installation ConsiderationsAdministration Considerations Customization ConsiderationsData Areas OS/390 Security Server Auditing ConsiderationsApplication Development Considerations General User ConsiderationsPage New and Enhanced Support Release OverviewUID Enhancements to Support for OpenEdition ServicesGggg needs Run-Time Library ServicesPassword History Enhancements GIDALL ProgramOW24966 Enhancements to New FmidOW26237 Enhancements Enable/Disable ChangesAccess GuideSYS1.SAMPLIB Callable ServicesNew Callable Services ReleaseGID Class Descriptor Table CDTUID Command Language Reference CommandsPermit NoclauthParmlib Data Areas ICHRFX03 ExitsICHRFX04 Changed Messages MacrosMessages New MessagesPanels Deleted MessagesMember ICHP241CICHP242A ICHH241CData Areas This No longer Licensed Publication Its New Form Publications LibraryChanges to the Racf Publications Library OS/390 Security ServerMigration Strategy Planning ConsiderationsRacf Migration and Planning for Racf 1.9.2GC23-3045 Hardware RequirementsRELEASE=2.4 Keyword on CompatibilityOpenEdition MVS Program Control by System IDPage Racf Estimated Storage Usage Installation ConsiderationsRacf Storage Considerations Virtual StorageHow ICB System Programmers GuidePage RACF/DB2 Customization ConsiderationsCustomer Additions to the Router Table and the CDT RACF/DB2 External Security Module CustomizationOS/390 Security Server Racf System Programmers. Guide Administration Guide Volume , SC26For OS/390 Version Installation Exit ProcessingServer Racf Security Administrators. Guide Administration ConsiderationsTmeadmin Class Password History ChangesRacroute REQUEST=LIST Enhancements of Global Access CheckingSysid Auditing ConsiderationsSMF Records Auditors GuidePage Racroute Icheinty Application Development ConsiderationsProgramming Interfaces Fastauth ChangesPage Security Server Racf General Users. Guide General User ConsiderationsPage Audit UpdateGlossary MVSDirectory DirectionFacility DataHFS EntityGID FileUnit PasswordRequest NodeUtility PositProcess PadsRoot ClassificationVerifyx File SystemTarget Node SyscallTask Sets VerificationName ProfileCics TSO/E How to Get Your Racf CDPage See IndexLsqa See alsoexits IRR@XACS 19 Ispf panelsPlpa Smfid SMF80DTASee alsoRRSF router table RaclistPage 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.
Top Page Image Contents