Table 9 (Page

2 of 2). Overview of POWER JECL Statements

 

 

 

POWER

Function

JES2 or MVS Equivalent

Statement

 

 

 

 

 

* $$ FLS

Indicates that a VSE/POWER job

/*PURGE if INTRDR

 

should be terminated by

 

 

internal flushing.

 

 

 

 

* $$ JOB

Indicates the beginning of a

// JOB

 

VSE/POWER job and specifies

 

 

the routing of jobs, output, and

 

 

notify messages.

 

 

 

 

* $$ LST

Provides handling information

// OUTPUT, /*OUTPUT, or // DD

 

for printer output; routes list

SYSOUT=x, DEST=destination

 

output to a node.

 

 

 

 

* $$ PUN

Provides handling information

// OUTPUT, /*OUTPUT, or // DD

 

for punched output; routes

SYSOUT=x, DEST=destination

 

punch output to a node.

 

 

 

 

* $$ RDR

Inserts a diskette file into the

No equivalent in OS/390.

 

input stream.

 

 

 

 

* $$ SLI

Inserts data from an accessible

// INCLUDE

 

library.

 

 

 

 

* $$ /*

Indicates the end of a VSE job

No equivalent in OS/390.

 

step (used with the SLI

 

 

statement only).

 

 

 

 

* $$ /&

Indicates the end of a VSE job

No equivalent in OS/390.

 

(used with the SLI statement

 

 

only).

 

 

 

 

/*$SLI

Indicates end of input data for

No equivalent in OS/390.

 

an SLI member.

 

 

 

 

4.4.3 Summary of JES2 JECL - A Table

Table 10 (Page 1 of 2). JES2 Control Statements

Statement

Purpose

Comments

 

 

 

/*$command

Enters JES2 operator

 

 

commands through the input

 

 

stream.

 

 

 

 

/*JOBPARM

Specifies certain job-related

Use parameters on the // JOB

 

parameters at input time.

statement instead.

 

 

 

/*MESSAGE

Sends messages to the

Seldom used.

 

operator via the operator

 

 

console.

 

 

 

 

/*NETACCT

Specifies an account number

Seldom used.

 

for a network job.

 

 

 

 

/*NOTIFY

Specifies the destination of

Use NOTIFY on the // JOB or //

 

notification messages.

OUTPUT statements.

 

 

 

/*OUTPUT

Specifies processing options for

Use the // OUTPUT JCL

 

SYSOUT data set(s).

statement instead.

 

 

 

/*PRIORITY

Assigns a job queue selection

Use PRTY= on the // JOB

 

priority.

statement instead.

 

 

 

/*ROUTE XEQ

Specifies the execution node

Use the /*XMIT statement as

 

for the job.

an alternative.

 

 

 

90VSE to OS/390 Migration Workbook

Page 114
Image 114
IBM OS/390 manual Summary of JES2 Jecl a Table, 1 of 2. JES2 Control Statements, Statement Purpose Comments

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.