4.3.13 Summary of MVS JCL Statements

Table 8. MVS Job Control Statements

JCL Statement

Purpose

 

 

 

//

command

Enters an MVS system operator command

 

 

through the input stream. The command

 

 

statement is used primarily by the operator. Use

 

 

the COMMAND statement instead of the JCL

 

 

command statement.

 

 

 

//

COMMAND

Specifies an MVS or JES command that the

 

 

system issues when the JCL is converted. Use

 

 

the COMMAND statement instead of the JCL

 

 

command statement.

 

 

 

//*

comment

Contains comments. The comment statement is

 

 

used primarily to document a program and its

 

 

resource requirements.

 

 

// CNTL

Marks the beginning of one or more program

 

 

control statements.

 

 

 

//

DD

Identifies and describes a data set. Indicates the

 

 

end of data placed in the input stream. Note: Any

 

 

two characters can be designated by the user to

 

 

be the delimiter.

 

 

 

//

ENDCNTL

Marks the end of one or more program control

 

 

statements.

 

 

 

//

EXEC

Marks the beginning of a job step; assigns a

 

 

name to the step; identifies the program or the

 

 

cataloged or in-stream procedure to be executed

 

 

in this step.

 

 

 

//

IF/THEN/ELSE/ENDIF

Specifies conditional execution of job steps within

 

 

a job.

 

 

 

//

INCLUDE

Identifies a member of a partitioned data set

 

 

(PDS) or partitioned data set extended (PDSE)

 

 

that contains JCL statements to be included in

 

 

the job stream.

 

 

 

//

JCLLIB

Identifies the libraries that the system will search

 

 

for INCLUDE groups and Procedures named in

 

 

EXEC statements.

 

 

 

//

JOB

Marks the beginning of a job; assigns a name to

 

 

the job.

 

 

 

//

 

Marks the end of a job.

 

 

 

//

OUTPUT

Specifies the processing options that the job

 

 

entry subsystem is to use for printing a SYSOUT

 

 

data set.

 

 

 

//

PEND

Marks the end of an in-stream or cataloged

 

 

procedure.

 

 

 

//

PROC

Marks the beginning of an in-stream procedure

 

 

and may mark the beginning of a cataloged

 

 

procedure; assigns default values to parameters

 

 

defined in the procedure.

 

 

 

//

SET

Defines and assigns initial values to symbolic

 

 

parameters used when processing JCL

 

 

statements. Changes or nullifies the values

 

 

assigned to symbolic parameters.

 

 

 

88VSE to OS/390 Migration Workbook

Page 112
Image 112
IBM OS/390 manual Summary of MVS JCL Statements, MVS Job Control Statements, JCL Statement Purpose

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.