stand-alone systems 421 standard applications 195 standard labels 78, 103 standard user labels 105 standardized conversion deliverables 51 standards 407

standards, procedures, documentation documentation

hardcopy library 412 printing softcopy books 412 redbooks 412

softcopy library 412 installation standards

DASD and tape volume serials 408 data management standards 407 data sets 408

generation data groups 408 JCL standards 409

MVS naming standards 408 other MVS names 409 related redbooks 408

systems management procedures backing up system 410 change management 411

critical operations procedures setup 411 emergency backup system creation 410 enforcing installation standards 410 implementing system security 410 problems management 411

started task contol 451 starting

&stopping PSF 242 a job 72

JES2 210

the system 447

startup procedures PSF 237 STATEMENT 336 statement compatibility 172 statements not supported 346 status codes 172

STEPCAT statement 117 stopping JES2 448 stopping PSF 242 stopping the system 448 STORAGE 341

storage & space management implementing DFSMS 102 OS/390 considerations 100 system managed storage 100 VSE considerations 100

storage management 100, 345 storage management in PL/I 345

storage management in DOS 345 storage management in MVS 345

strategies 27

structural KSDS errors 477 submitting jobs 439

submitting jobs for batch execution 162 using command procedures 163 subsystem level comparison/affinity 24

Subsystem Storage Protect 508 summary 430, 472

migration tasks 182 of JES2 JECL 90

of MVS JCL statements 88 TSO/E 158

supported linkages 338 supported printers 235 supported to be avoided 340 switchover 517

SYNCHK parameter 121

synchronizing VSE applications with OS/390 versions 430

synopsis 3

syntax correction 76 SYS1.PARMLIB parameters 415 SYSIN/SYSOUT spooling 73 SYSLOG 394

system

access by TSO/E 159 administrator 180 automation for OS/390 467 availability 11

backup 410

data sets for CICS 145

initialization parameters for CICS 140 interface & macros 268

macros 268

managed storage 100 messages 395 operation via SDSF 446 preparation 155 problems diagnosis 473 programmers 46 programming commands 147 requirements MVS 170 security 410

simulation 426 standard labels 78 start 447

status 447 stop 448 testing 513 usage 158 work display 449

system customization 413 System/390 JCL philosophy OS/390′ s job control 70

VSE/ESA′ s Job Control Language 70 systems management 10

overview 457

philosophy & methodology 457 procedures 409

role of automation 460 scope 459

616VSE to OS/390 Migration Workbook

Page 639 Page 641
Page 640
Image 640
IBM manual VSE to OS/390 Migration Workbook
Page 639 Page 641

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