Submitting a Job

There are a number of different ways that you can submit your job on systems running MVS.

The easiest way of submitting ad hoc jobs that you may have just created using the ISPF editor is to type submit (which you can abbreviate to just sub) in the primary command field of the editor while you have the editor open displaying the job that you want to run. Another way with ISPF is to go into option 3.4 (Dataset List Utility) and display the list of jobs contained in you job library. You can enter the submit (or sub) command next to the job that you want to submit from there.

That's all very well for ad hoc jobs in your testing environment but greater control is required for your production environment. This control is usually achieved by either having separate regions for test and production and not giving access to submit jobs on production or by allocating different job classes to each and restricting which classes individuals can submit to.

Regular production jobs are usually submitted automatically by a job scheduling system such as Control-M, Jobtrac, or OPC. These systems control when jobs are submitted based on time triggers and/or the successful completion of prerequisite jobs and can run your production jobs for you without any operator intervention other than for when there are problems.

Another way to submit ad hoc jobs in your production environment is from CICS applications via the issue send command which can write directly to the job input queue. The safest way to work this is to submit a dummy job that will act as a trigger for a job defined in your job scheduling system.

ISPF itself does not contain any options that will allow you to monitor your batch jobs once they are submitted although there are a number of alternative products that can be added on to ISPF to provide you with the ability to do this. The most common of these is a product called SDSF which allows you to monitor the job input queue, job output queue (where you can also view the reports produced by the program before they are printed), and also can display a list of the jobs currently executing in batch on your system.


This article written by Stephen Chapman, Felgall Pty Ltd.

go to top

FaceBook Follow
Twitter Follow