Table 23.

POWER Exit to JES2 Exits

 

 

 

 

 

 

POWER

Description

JES2 Exit

Comment

Exit

 

 

 

 

 

 

 

JOBEXIT

Job input - Scan JCL & JECL

EXIT(2)

JOB statement scan

 

(POWER exits allow access to

EXIT(3)

JOB accounting field

 

SYSOUT data.)

EXIT(4)

Other JCL & JECL

 

 

 

(No access to SYSIN data.)

 

 

 

 

NETEXIT

Input from NJE node

EXIT(47)

NJE Headers Received

 

 

 

(No access to SYSIN or

 

 

 

SYSOUT data.)

 

 

 

 

OUTEXIT

Output to printer or punch

EXIT(1)

Job Separator

 

(POWER exits allow access to

EXIT(15)

Data Set Separator

 

SYSOUT data.)

 

(No access to SYSIN or

 

 

 

SYSOUT data.)

 

 

 

 

XMTEXIT

Output to an NJE node

EXIT(46)

NJE Headers Transmitted

 

 

 

(No access to SYSIN or

 

 

 

SYSOUT data.)

 

 

 

 

10.4.2.1 Source Code Modifications

Most JES2 modules are distributed in source form and can be modified to meet specific customer needs, though this is not recommended by IBM. It is sometimes easier to modify the JES2 source code than accomplish the same thing through exits.

10.4.2.2 The JES2 Patching Facility

Patch and AMASPZAP statements can be used to make minor and temporary modifications to the JES2 object code until JES2 is restarted by directly replacing the changed code. The JES2 Patching Facility changes only the memory copy of data; the copy residing on DASD (for example, LPA) cannot be replaced.

For details and precautions, see the section entitled ²The JES2 Patching Facility² in Chapter 1 of the JES2 Initialization and Tuning Guide.

10.4.3 POWER-JES2 Command Equivalences

There are major differences between JES2 and POWER. This section will compare the products from a different perspective, that of the central operator. Through the migration, the functional role of the operator will remain the same. Therefore the most often asked questions by the central operator will be the following,

1.How do I do a certain function?

2.In POWER, I used ¢xyz¢ command. What command do I use in JES2?

The following figure gives an overview of POWER commands and the JES2 equivalent. See OS/390 JES2 Commands and VSE/POWER Administration and Operation for details.

Chapter 10. POWER and JES2 231

Page 255
Image 255
IBM OS/390 POWER-JES2 Command Equivalences, Source Code Modifications, JES2 Patching Facility, Power Exit to JES2 Exits

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.