4.2.1.7 Instream Data

Both operating systems allow Instream Data in the middle of the JCL. This is data that will be processed by the executing program.

4.2.1.8 Variables

The JCL in both operating systems will accept variables. These variables are set with the // SET statement in MVS, or SETPARM in VSE.

4.2.1.9 Conditional JCL

Conditional JCL exists in both environments and allows performing IF and GOTO statements. Loops are prohibited. In MVS, the IF statements are all processed at converter time. Although the mechanics are very different, functionally, the IFs are the same in both environments.

4.2.1.10 Return Codes

Return codes from previous steps can also be tested during execution in both environments. Program steps can be bypassed based on the result of testing for a condition (a return code or a parameter value). For example, if in a statement, the return code was more than zero, then bypass the next statement. In MVS, this is handled by the COND parameter on the // EXEC statement.

See also 4.3.11.3, ªMVS Conditional JCLº on page 84.

4.2.2 Spooling

Spooling exists in both environments. POWER for VSE and JES for OS/390. POWER and JES provide similar input and output capabilities and a similar system of classes and priorities.

4.2.2.1 Internal Reader

The internal reader facility exists in both environments. An application program can pass jobs to the spool, right into the input queue, just by writing to a pseudo punch device. RJE and NJE also exist in both environments.

Further discussion of spooling can be found in Chapter 10, ªPOWER and JES2º on page 207.

4.3 JCL Differences Between VSE and MVS

In part because of the differences in philosophy discussed in 4.1, ªThe Philosophy of JCL in System/390º on page 69, there are differences in the processing of JCL that lead to Job Control Language differences between the two environments.

4.3.1 Job Input

In VSE systems, job input consisting of JCL statements and instream data, whether spooled through the POWER spooling system or directly read in a partition, is processed in a strictly sequential process. That is, a program can only read one input statement at any one time, and this is a sequential process. A programming or JCL error in VSE can cause the VSE Job Control program to read a user data statement, or a user program to read a JCL statement, with unpredictable results.

Chapter 4. Job Control Language (JCL) Differences and Considerations 73

Page 97
Image 97
IBM OS/390 manual Spooling, JCL Differences Between VSE and MVS, Job Input

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.