
Processing NetBatch Jobs and Completion Codes
Initiating and Communicating With Processes
5–32
107365 Tandem Computers Incorporated
Processing
Completion
Information
Depending on how you run a process and how the process handles termination, TACL
can access several types of completion information:
TACL supports a STATUS option that stores an indication of why the process
terminated. The possible indications are STOP, ABEND, CPU (CPU failure), and
NET (network failure).
If the process specifies a completion code, you can access the completion code.
Processes can be run as batch jobs under the control of the NetBatch product. The
following paragraphs describe the role and use of TACL as a NetBatch command
interpreter and how to monitor the status of jobs in progress. For detailed information
on scheduling processes as batch jobs, see the NetBatch Manual.
Processing NetBatch Jobs
and Completion Codes
TACL saves completion code information in the variable :_COMPLETION, if it exists.
Tandem code in the standard TACLSEGF defines :_COMPLETION as follows:
[#DEF :_completion STRUCT
BEGIN
INT messagecode;
CRTPID process;
INT headersize VALUE 14;
INT4 cputime;
INT jobid;
INT completioncode;
STRUCT internal;
BEGIN
INT terminationinfo;
SSID subsystem;
END;
STRUCT external REDEFINES internal;
BEGIN
BYTE group;
BYTE user;
CRTPID process;
END;
INT textlength;
CHAR text(0:79);
END;
]
TACL sets this variable whenever you attempt to start a process, whenever you
successfully start a process, and whenever a process you started terminates
(successfully or otherwise). Whenever TACL sets this variable, its previous contents
are lost.
If you define a variable named :_COMPLETION, it should be a STRUCT. Each time
TACL stores data in :_COMPLETION, it resets the STRUCT to default values. If the
STRUCT is shorter than the data to be stored in it, the extra data is discarded. If the
STRUCT is longer than the data to be stored in it, the extra space remains set to default
values.