JCL differences (VSE and MVS) (continued) VSE Job Control statements

ASSGN statement 83 CAT= on DLBL 83 conditional JCL 84 DLBL and EXTENT 83 EXEC statement 82 JOB statement 82 MTC statement 83 RESET statement 83 TLBL statement 82

JCL high level similarities JCL statement & job layout

conditional JCL 73 continuation cards 72 EXEC (job step) 72 file definitions 72 imbedded JCL 72 instream data 73 JOB statement (job) 72 nesting procedures 72 return codes 73 variables 73

spooling

internal reader 73 JECL 89

Data statement - * $$ DATA 89 LIST card - * $$ LST 89 POWER versus JES2 JECL 89 summary of JES2 JECL 90

JES2 21

additional job scheduling functions 214 checkpoint 210

CICS interface 151 command equivalences 231 commands 450

control cards 453

detailed comparisons with POWER 225 devices 449

diagnosis 475

equivalent POWER parameters 225 functional comparison with POWER 211 implementation 209

initialization parameters 211 installation exits 211 introduction 207

JECL summary 90 JES2 procedure 211 job log 395

job scheduling 213 major differences

end-of-page sensing 209 FCB incompatibilities 209

KEEP disposition for pre-execution jobs 207 other differences 209

printer forms alignment via PSETUP 208 separator page difference 208

tape spooling 208

time event scheduling for jobs 208

JES2 (continued)

major JES2-POWER differences 207 NJE 221

operator commands 211 operator commands JES2 211 other differences JES2-POWER 209 output service 215

patching facility 231

PLINE mapping to LINE parameters 227 POWER command equivalences 231 POWER JECL comparison 89

POWER parameter mapping 225 procedure 211

resource setup 209

RJE operations 220, 452 SMF accounting records 223 spool volumes 210

start 210 starting 210 stopping 448 system data sets 395 system messages 395 tailoring 211

testing techniques 225 JES2/POWER functional comparison 211

accounting comparisons

JES2 SMF accounting records 223 job accounting 223

NJE accounting 224 application interfaces

job information services 222 other Interfaces 222 output retrieval 222 programmable spool interfaces 221 spool space allocation 221

input service

interactive user interfaces (ICCF/CMS/TSO) JES2 testing techniques

Poly-JES 225 job scheduling

additional job scheduling functions with MVS/JES2 214

job stream disposition 213 OS/390 solution 213 serializing job execution 214 time event scheduling 214

network job entry NJE definitions 221 NJE exits 221

NJE management 221 NJE operations 221

output service

end-of-page sensing 217 FCB naming differences 217 FCB prefixes 217

FCB specification 218 output disposition 217 output segmentation 216

printer forms alignment via PSETUP 217

604VSE to OS/390 Migration Workbook

Page 628
Image 628
IBM OS/390 manual JES2

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.