Other considerations for the parallel job manager

There are other considerations that help we understand how to optimally use the parallel job manager.

Transaction timeouts

We can keep the default value for the TransactionTimeOut property in the top-level job xJCL. We can alternatively adjust it depending on the transaction timeout of the subordinate job.

Job logs

We can view job logs for a subordinate job from the job management console. The PJM retrieves subordinate job logs for its logical job and aggregates them into its top-level job log.

Failover scenarios

If the top-level job and several subordinate jobs are in the restartable state, then restart only the top-level job. If we restart any of the subordinate jobs manually, then the top-level job does not process the logical transaction properly.

Disaster recovery

Use the jobrecovery script when a primary site fails to allow a secondary site to take over.

Related:

Batch jobs and their environment

Parallel job manager APIs

jobrecovery.bat|.sh batch script