With this powerful function, you can have job routing between CPUs based on defined resource names (subsystems like IBM® DB2® or IMS™) and their availability (up or down). You can manage resource availability on each system running IBM Operating System Environment Manager job routing and you can control the routing with JECL statements in the job or by assigning routing control information through the ISPF interface.

This function prevents jobs from being selected until all needed datasets are available.

Using the End User Computing Job Scheduling and Limiting options, you can limit the number of jobs that a user can be running concurrently.

This function can be used to place up to 32 bytes of JOB or STEP accounting information into the catalog record for a newly created VSAM dataset or SMS-managed non-VSAM dataset. Additionally, the user ID of the job is placed into the Owner field of the catalog record. Neither of these fields is overridden if the information has already been provided.

This function helps you migrate to LE/370 and any new version of most program products such as FILE/AID, SAS and others. You can modify or replace existing STEPLIB DD statements or add a new STEPLIB DD based on job class, job name, user ID, step name or program name.

Use this function to calculate an approximate charge for running each step of a job and an approximate total cost of running the job.

Use this function to enforce CPU time limitations. Extend CPU time, JOB wait time and TSO wait time. Control, by job class, the insertion of a missing time parameter, overriding the time specified on the job card. Cancel the job if the job time is greater than the JES2 time value.