7.4 Submitting Jobs for Batch Execution

ICCF allows users to submit jobs for batch execution through the SUBMIT procedure and an ICCF supplied program, DTSSUBMT. Tailoring of the SUBMIT procedure allows the ICCF System Administrator to provide system standards for execution and list and punch output. Listed output from the batch execution may be viewed at the terminal using the /LISTP command provided that the output is dispatchable and is not presently being printed by VSE/POWER. ICCF also provides three procedures, GETL, GETP, and GETR, to retrieve list, punch or reader queue data and store this data as ICCF members. You may use the /DQ command of ICCF to view the VSE/POWER reader, list, and punch queue directories, and the ICCF supplied program, DTSDA, can be used to display the status of the DOS/VSE partitions.

In TSO/E, you can submit jobs for batch processing if your installation authorizes you to do so. This authorization, specified as JCL, is stored in RACF or UADS with your user attributes. If you have this authorization, the system lets you use the four commands (SUBMIT, STATUS, CANCEL, and OUTPUT) that control the processing of batch jobs. You can use these commands to submit a batch job, to display the status of a batch job, to cancel a batch job, and to control the output of a batch job. You may also use ISPF facilities to perform this work rather than the commands TSO/E supplies. Many JES2 customers also use the facilities provided by the System Display and Search Facility (SDSF) to control and work with the output from batch jobs. SDSF provides a more complete

full-screen interface to batch jobs, and gives functions similar to the /CTLP and /DQ facilities of ICCF.

When you enter the SUBMIT command, you must give the name of a data set (or data sets) containing the batch job (or jobs). Each job consists of job control language (JCL) statements and of program instructions and data. If you do not specify the NONOTIFY operand, you will be notified when your batch job terminates. TSO/E provides for system standards on submitted jobs through the coding of a SUBMIT command exit. Through this exit, an installation can approve, reject, or modify the JCL statements being submitted.

Any time after you submit a background job you can use the STATUS command to have its status displayed. The display will tell you whether the job is awaiting execution, is currently executing, or has executed but is still on the output queue. The display will also indicate whether a job is in hold status. The STATUS command is similar to the /STATUSP command of ICCF.

The CANCEL command cancels execution of a batch job. This command can only be used on jobs that follow the naming convention of job names beginning with the TSO/E user ID. There is no equivalent to this command in ICCF.

The OUTPUT command may be used to manipulate all held output, regardless of whether the output is produced during the current LOGON session, a previous LOGON session, or by a batch job submitted from any source.

162VSE to OS/390 Migration Workbook

Page 186
Image 186
IBM OS/390 manual Submitting Jobs for Batch Execution

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.