10.1.1.2 Time Event Scheduling for Jobs

POWER supports the scheduling of job submission based on a one-time or repetitive schedule such as daily, weekly on a given day and time, and so on.

JES2 has a primitive ²automatic command scheduling² facility, but you will probably need an automated job scheduling package in OS/390 to do the same things you were doing with POWER.

10.1.1.3 Tape Spooling

Spooling to tape is usually done for very large SYSOUT data sets where there is limited spool space or where the data is to be archived. JES2 does not provide direct spooling to tape.

For very large output files, or to archive critical output, you can use the JES2 Spool Offload facility or some spool archiving package such as RMDS or R/DARS.

For data exchange to offline devices or programs, use the IBM supplied external writer (XWTR procedure) to write spooled data to tape.

Another possible solution in MVS to accomplish tape spooling is instead of allocating a file to SYSOUT, you can specify a unit on the DD statement to direct it to tape (for example, UNIT = TAPE). Then use the MVS utility IEBGENER to print the tape with the SYSUT2 DD statement specifying the address of the desired printer (for example, UNIT=00E). Note: The printer has to be ²drained² from JES2 before it can be allocated to the IEBGENER utility program.

Use of the above procedure retains (KEEPs) the output on tape as long as the installation has a retention requirement.

10.1.1.4 Printer Forms Alignment via PSETUP

The POWER ²PSETUP² function allowed the operator to print a couple of pages of X¢s in order for the operator to line up the form. JES2 does not provide this same function. Here are some alternatives:

With JES2, you can start the printing, and if an alignment adjustment is

needed, interrupt the printer, do the alignment, and then issue the JES2 Backspace command. ²$B PRTnnnn,D² (where nnnn is the printer number)

will logically backspace to the beginning of the data set. Printing resumes at the beginning of the data set. (This assumes the data set being restarted is large enough not to be completely printed before it is backspaced.)

Another technique is to have some dummy reports kept on spool for each form that needs alignment. Release the dummy output group and cause it to be selected first so you can line up the printer.

10.1.1.5 Separator Page Difference

Operators may be using the VSE separator pages to separate individual copies of reports. JES2 handles separator pages differently than VSE. Under VSE, when a printout has multiple copies, separator pages are printed between each copy. With JES2, you can use ªoutput groupº separator pages (one at the beginning and one at the end) ªdata setº separators, and ªdata set copyº separators between each copy.

For output group separators, specify SEP=YES on the JES2 PRT(nnn) initialization statement. You can use the IBM-supplied separator pages, or you

208VSE to OS/390 Migration Workbook

Page 232
Image 232
IBM OS/390 Time Event Scheduling for Jobs, Tape Spooling, Printer Forms Alignment via Psetup, Separator Page Difference

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.