NetBatch Manual

Job Planning, Submission, and Management
NetBatch Manual—522460-004
4-7
Creating a Job Input File
Creating a Job Input File
A job’s input file contains the statements executed by the job’s executor program. (For
example, if a TACL process is the executor program, the file contains TACL
commands; if the COBOL compiler is the executor program, the file contains the
program source code.) The syntax of the statements in the file must follow the syntax
rules of the executor program.
Figure 4-4 shows sample TACL input files for two of the jobs (TLOG-A and TLOG-B)
planned earlier.
Using Completion Codes to Test Process Termination Status
Every process that executes returns a completion code to its ancestor in its ABEND,
STOP, or PROCESS_STOP_ system message. The code indicates whether the
process terminated normally or otherwise.
Completion codes are integers in the range -32768 to 32767. These considerations
apply to their use:
Figure 4-4. Sample Input File
Completion Codes Comments
-32768 to -1 Reserved for HP use. Only a privileged caller can have a negative
completion code returned to its ancestor.
0 to 999 Reserved for shared use by HP and its customers.
1000 to 32767 Reserved for customer use. Not used by HP.
TACL input file for job TLOG ?A:
#SET #INFORMAT TACL
RUN A
[#IF (:_COMPLETION:MESSAGECODE = -5 AND
:_COMPLETION:COMPLETIONCODE = 7)
COMMENT Stop myself if A stops with completion code 7
|THEN|
#STOP /COMPLETIONCODE 7/ [#PROCESSINFO /PROCESSID/]
COMMENT Release A’s dependent jobs if A runs successfully
|ELSE|
ZBAT:RELEASE $ZBAT *
]
TACL input file for job TLOG ?B:
BACKUP $TAPE1, $DATA1.DAYLOGS.TODAYS, LISTALL, OPEN, &
AUDITED, VERIFYREEL
ZBAT:RELEASE $ZBAT TLOG-G
VST118.vsd