How to access CA Jobtrac Job Management from IBM's Unix System Services?
CA Jobtrac release 11.0 includes an utility to allow use of the CA Jobtrac's @Jobtrac commands to access CA Jobtrac from within the IBM's Unix System Services (USS). @Jobtrac is the command facility that the GJTRABTR batch utility and the CA GSS ADDRESS Jobtrac facility both use to read, update and add jobs to the CA Jobtrac Checkpoint dataset. The new USS command, jtuss (remember that USS is sensitive), provides the same functionality in the USS environment. While jtuss can be issued directly from a telnet session, the command will be most useful in Unix shell scripts.
Below is a sample script for a process named fileppr that runs in USS and needs to have an MVS job, PROCFILE, run after it completes.
# Sample USS script
fileppr
jtuss 'mod job(PROCFILE) dep(-m)' >jtuss.outif . ?> '0' .;
thenecho "error returned from JTUSS - check jtuss.out "fiexit
In the script above, after the fileppr command is run, the jtuss command will remove the M dependency from the CA Jobtrac job PROCFILE to allow it to run (assuming it has no other predecessors or dependencies). The output of the command is redirected (>) to a file named jtuss.out.
If the jtuss command is unsuccessful, the message "error returned from JTUSS - check jtuss.out" will be written to stdout. The command output and any error messages will be in the jtuss.out file.
In the example the M dependency was remove from the job, but it could have just as easily added a job by using this command instead.
jtuss 'add job(PROCFILE)' >jtuss.out
Any of the standard @Jobtrac commands and parameters can be specified in the jtuss command. This allows you to specify all the standard job parameters such as jobtype, start and target time, dependency codes and resource codes. For more information on using the jtuss command refer to "Accessing from Unix System Services (USS)" in the CA Jobtrac Extended Scheduling Services Guide.