4.4 JECL

JECL is very important in VSE and is commonly used. The difficulty from a conversion standpoint is to determine where the job is due to having two different job cards in JCL. The JECL statement is a POWER job, the DOS Job or VSE Job is the // JOB. The POWER job is like the MVS JOB. This is where the class and priority information is specified. It exists at the beginning of a job stream.

JES control statements are not recommended for new applications. You should use the new JCL statements such as // OUTPUT instead of the /*OUTPUT, /*ROUTE JECL statements. Today most JECL functions can be accomplished through standard JCL statements.

See Table 10 on page 90 for a list of recommendations.

4.4.1.1 LIST Card - * $$ LST

The LIST card in VSE is the equivalent of both // DD SYSOUT statement and

OUTPUT statement in MVS.

Defaults, list and punch destinations can be put on the VSE JOB card as well as the LST card. Both are merged into the OUTPUT statement in MVS.

There is a difference between the scope of a LST statement and an equivalent

DDstatement. In MVS a DD statement is only viable for one step. In VSE, a * $$ LST statement is in effect from the time it is processed by POWER until EOJ or another LST statement for the same device address is processed. As soon as the effect of a given LST statement ends then the output is available for printing.

4.4.1.2 Data Statement - * $$ DATA

The data statement in VSE is a way for an include in SLI to specify the point where some data external to that include statement should be processed. It is similar to sending overrides in JECL but not as cumbersome in the space with the line number. The data statement allows you to pass data to a step. The step could be in the middle of an include statement. This is a commonly used method. The MVS equivalent is either a DD DATA override or a DD that points to a PDS member or a sequential data set.

4.4.2 Comparison of POWER and JES2 JECL - A Summary

Table 9 (Page

1 of 2). Overview of POWER JECL Statements

 

 

 

POWER

Function

JES2 or MVS Equivalent

Statement

 

 

 

 

 

* $$ CTL

Assigns a new default input

$T RDR(nn),Class=class

 

class to VSE/POWER jobs.

 

 

 

 

* $$ DATA

Inserts data from the reader

// DD * or

 

queue into a library member

// DD DATA

 

after this member was

 

 

retrieved for inclusion into a

 

 

VSE/POWER job.

 

 

 

 

* $$ EOJ

Indicates the end of a

//

 

VSE/POWER job.

 

 

 

 

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

Page 113
Image 113
IBM OS/390 manual Comparison of Power and JES2 Jecl a Summary, List Card * $$ LST, Data Statement * $$ Data

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.