can write your own using JES2 exit 1. (For PSF controlled printers, use PSF exits APSUX01 and APSUX02.)

For separators between individual data sets or data set copies, you must specify SEPDS=YES on the PRT(nnnn) statement and provide a JES2 Exit 15 for JES2 controlled printers. (For PSF controlled printers, use PSF exit APSUX03.)

10.1.1.6 End-of-page Sensing

POWER, by storing a carriage control tape image, allows a program to ²sense² channel 12 or end-of-page. This is not supported in JES2. Line count logic must be substituted. You can change the application to count lines under VSE prior to the MVS conversion.

10.1.1.7 FCB Incompatibilities

POWER permits the ²channel one² position to be on any line of the page. JES2 requires Channel 1 to be on Line 1 for all printers controlled by JES2.

This restriction is in place because JES2 uses a skip-to-channel-1 to reposition the printer to the top of forms when it goes through device setup.

Also see 10.3.4.8, ªFCB Naming Differencesº on page 217.

10.1.1.8 Other Differences

Incompatibilities such as JCL and Operator Commands are covered in other chapters:

Chapter 4, ªJob Control Language (JCL) Differences and Considerationsº on page 69

Chapter 28, ªOrientation to OS/390 Console Operationº on page 443

10.2Implementing JES2

This section describes the significant migration and conversion activities to implement JES2 for the first-time user.

10.2.1 Setting Up the Required Resources

Both POWER and JES2 require DASD files to spool the jobs and their output, and queues to manage them. The following figure describes the various types of spool and control files of VSE/POWER and their equivalent file types in JES2.

Chapter 10. POWER and JES2 209

Page 233
Image 233
IBM OS/390 manual Implementing JES2, Setting Up the Required Resources, End-of-page Sensing, FCB Incompatibilities

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.