Batch Operational Manual


An operational manual for batch processing.


The status of all deferred batch jobs will be visible at all times.

Example(s):  An example of a batch job in a queue is shown below: 

Step 1:

Example of ssturn-3

Step 2:
Example of ...ssturn-3b batch



Example of ...ssturn-3f request number


Step 3:

Example of ..load batch


Step 4:

Example of ..open queue


Step 5:
Example of ..open queue commit


Step 6:
its_man_img/om_db_snappa-3comp2.jpg


Step 7:
its_man_img/om_db_snappa-3comp1.jpg


Step 8:
Example of ..complete


Step 9:
Example of ..complete 2





To Schedule a job in Deferred Batch (with Dependents) :

Step 1: Create a Batch Request for the Master Batch Job (The job that has to run first)

Run the main (parent) job via Batch processing ...

om_defbatch_ds1i1.jpg



Select the Deferred mode, complete the printer and printer form if required and press the Proceed button ... the new Batch Request Number is provided.



om_defbatch_ds1i2.jpg


Step 2: Create a Batch Request for the Dependent Batch Job (Only applicable if dependent jobs are to be scheduled along with the Master Batch Job)

Run the dependent (child) job via Batch processing ...



om_defbatch_ds2i1.jpg


Select the Deferred mode, complete the printer and printer form if required as well as the Dependent Request Number as that of the Parent ... and press the Proceed button ... the new Batch Request Number is provided.


its_man_img/om_defbatch_ds2i2.jpg


Step 3: {BATCH-14} - Query Batch Requests ... (displays all requests by any user)

Query the Parent (Deferred) request ...


its_man_img/om_defbatch_ds3i2.jpg




Step 4: Schedule the Master Batch Job

Go to {BATCH-8} - Schedule Programs

Only the 'Root' parent request can be scheduled.

Note 1: Only when the parent request completes processing, the child/children request/s will commence processing.

Note 2: When more than one request is on the same level, all those on the same level will start executing at the same time ... as soon as the previous level completes.

Note 3: Only the 'Root' parent can be scheduled. Children cannot be saved in {BATCH-14b2}.
A 'chain' of requests is created in the background of all the children dependent on a specific parent.

Note 4: A 'chain' cannot be broken, meaning that a Parent request within a 'Root' Parent cannot be scheduled. See example below ...


its_man_img/om_defbatch_ds4i4.jpg



Note 5:
Care needs to be taken when requesting and/or scheduling any request. for example: if a Posting program for the same sub-system is scheduled to run concurrently, it will cause chaos!







Additional notes related to any and all requests:


{BATCH-9} - Background Processes

Make sure that g31proc is running at all times:

its_man_img/om_defbatch_ds4i5.jpg


Whilst a request is saved in {BATCH-14b2} - Query Batch Requests - 2nd tab - Batch Request Description, it cannot be deleted except by the person that saved the request ... not even via {BATCH-6} - Delete Old Requests.



Whether {BATCH-6} - Delete Old Requests, is executed 'manually' via the menu or via the CRON, the same rules apply:
Refer to {BATCH-6} for the rules for deletion and the exceptions.


It is advised that g31uni is executed via the CRON every night.
g31uni does:
  1. Remove old requests {BATCH-6}, based on the value in {BATCH-1b1} - System Parameters, field "Nr of Days after which completed/Cancelled Requests will be Deleted".
  2. Activate all the queues and process requests in the queue if any.
  3. Close the queues based on the value in {BATCH-1b2} - System Parameters - Queue Maintenance, field "Must the Queue Terminate and Close if there is no more Jobs".


{BATCH-1b1} - System Parameters


its_man_img/om_defbatch_ds4i6.jpg



{BATCH-1b2} - System Parameters - Queue Maintenance

Ensure that all queues are defined optimally ...


its_man_img/om_defbatch_ds4i7.jpg




If iEnabler is utilized, the 'W1' queue must be defined as 'OPEN' at all times and have 'N' o in the "Must the Queue Terminate and Close if there is no more Jobs" field.


its_man_img/om_defbatch_ds4i8.jpg




All other queues should be defined as 'CLOSED' with a 'Y'es in the "Must the Queue Terminate and Close if there is no more Jobs" field.



its_man_img/om_defbatch_ds4i9.jpg



History Of Changes

Date System Version By Whom Job Description
11-Jan-2007 v01.0.0.0 Charlene van der Schyff t12345 New manual format.
23-Sep-2009 v01.0.0.1 Charlene van der Schyff t161944 Insert links.
16-Aug-2010 v01.0.0.2 Goodman Kabini t168948 Add the part for scheduling jobs with dependencies.
24-Nov-2010 v02.0.0.0 Dinong Sereko t160972 Add link to BATCH-8
29-Jul-2011 v02.0.0.1 Frans Pelser T170877 Add anchor for BATCH-8 link
26-Aug-2014 v03.0.0.0 Su de Kock T188745 Enhance manual
28-Aug-2014 v03.0.0.0 Dinong Sereko T188745 System owner proof read.
05-Sep-2018
v04.0.0.1
Tshidiso Dennis
T230535
Manual Update, new images