OPTI-AUDIT highlights 521 OPTI-AUDIT product details 521 option setting recommendations 363 optional features for release 4 416 options

mapping 354 specific to DOS 343

specific to DOS compiler 335 specific to MVS 344 specific to MVS compiler 336

order and install the OS/390 software 405 ordinal day of year definition 576 orientation for utilities

DFSMSdss 456 IDCAMS 455 IEBCOPY 455 IEBGENER 455 IEBxxx or IEHxxx 455

orienting ICCF users to TSO/ISPF 437 OS/390

automated operations tools 510 base elements 19

building initial test system 430 bypass label processing facility 106 catalog management 114 catalogs 110

classes 535 COBOL 131

console operation 443 controlling the system 447 cross-system shareoptions 129 DASD sharing definitions 129 data set naming 99

devices supported 402 DFSMSdss 397 DFSMSdss functions 398 documentation resources 39 entitled installation methods 406 fee-based installation 405 guest considerations 430 hardcopy processing 393 indexed VTOC considerations 109 initial operations 518 installation methods 406

ISPF overview 390

Job Control philosophy 70 job stream disposition 213 label processing bypass 106 Language Environment migration

considerations 352 library maintenance 431 library management 391

maintaining libraries and SMP/E zones 431 maintenance environment 431

master catalog 114 migrating VSE RPG II 329 migration considerations 250 MPF 25

OS/390 (continued) NCP 192

NJE connection 415 operating environment 19 operating hardware consoles 443 optional features 20

order and install software 405 other elements 416

output descriptor macro 242 printing SYSLOG 394 product content 19

shared DASD between test systems 432 shared DASD between VSE and OS/390 433 shareoptions 129

SQL/DS to DB2 migration 178 staff requirements 38

standards and naming conventions 497 storage management 100 synchronizing VSE applications 430 SYSLOG 394

System Automation 467 system control 447 system-related products 23 terminal access 414

test logical partition 431 test system building 430

test systems (vs. cloned DASD) 432 user catalogs 115

verifying new system 413 VS FORTRAN 349 VSAM backup/restore 387 VTAM 189

VTAMLST 190 XCF 189

OS/390 components/products/subsystems operating environment

base elements 19

MVS subsystem & component terminology 21 optional features 20

product content 19 supporting products 23

subsystem level comparison/affinity 24 OS/390 customization

MVS BCP

MVS exits 415

SYS1.PARMLIB Parameters 415 tailoring other components 416

new OS/390 system

applying preventive service 414 NetView FTP access 415

NJE connection to OS/390 415 terminal access to OS/390 414 verifying new OS/390 system 413

other OS/390 elements

Independent Software Vendor products 417 Release 4 base elements 416

Release 4 optional features 416

Index 609

Page 633
Image 633
IBM manual OS/390 NCP, Vtamlst 190 XCF, Mvs Bcp

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.