MVS (continued) device addresses 80 DFP 21

DISPLAY command 447 execution overrides 149 exits 415

IEFBR14 78 initialization routine 269 JCL - a summary 88 JCL - sample 93

JCL versus VSE JCL 73

JES2 additional job scheduling functions 214 Job Control statements 84

linkage macros 271 Migration System 486 multitasking macros 283 naming standards 408 overlay 345

RACF 149

register conventions 269 specific options 344 storage management 345 system requirements 170 tools testing 508

virtual storage considerations 135 virtual storage macros 289 VSAM macros 290

N

n-way processor support 9 NAME 336

naming considerations 99

conventions - common applications 549 differences 217

guidelines 543 NaviQuest 103 NCP 192

NCP/EP Definition Facility (NDF) 192 nesting procedures 72

NetView FTP access 415 network

configuration 191 definitions 194, 203 management 233 printer definition 236

Network Job Entry 220 new VM users 425

NI status codes 172

NJE

accounting 224 connection to OS/390 415 data transfer 405 definitions 221

exits 221 management 221 nodes definition 230 operations 221, 453

NJE (continued)

operator commands 233

PLINE mapping to JES2 LINE 227 SDSF panels 454

using SDSF panels 454 no labels 105 NOALLOCATION data sets 123 NOFEED 339

NOIMBED option 120

non-LE/VSE run-time environments 354 nonstandard labels 106

not recommended DITTO batch keywords 385 not recommended DITTO functions 383

not supported in MVS 339 NOTAPEMK NOLABEL 340 NOTE macro 299, 309 nucleus load table 137 NUMBER 336

O

object code migration 251

obsolete DITTO batch keywords 384 obsolete DITTO functions 382 OEM product education 536

OMR (Optical Mark Read) 339 online Fast Copy 397

online program conversion 14 online unit testing 512 OPEN allocation 78

OPEN macro 297, 304, 314 operating hardware consoles 443 operating system implementations 98 operational differences 242 operations 16, 173, 190

automated 37 automated tools 50 NJE 221 procedures 411 RJE 220

support staffing 50 operations management 465

automating operational procedures 467 methodology 466

overview 465 tasks 465

operator

commands JES2 211 commands NJE 233 communication interrupts 288 data entry 76

flexibility 76 interfaces 443 intervention 76

OPERLOG 394

printing OPERLOG 394 OPSYS routine 349 OPTI-AUDIT 79, 520

608VSE to OS/390 Migration Workbook

Page 632
Image 632
IBM OS/390 manual MVS device addresses 80 DFP, Nje, Printing Operlog 394 Opsys routine 349 OPTI-AUDIT 79

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.