How to determine why ThruPut Manager is holding a job
Knowledge Article
How to determine why ThruPut Manager is holding a job
When ThruPut Manager Analysis completes successfully (DTM1460I) and the job is requeued for execution
the job may be put in TM-HOLD until conditions are satisfied. Use this procedure to determine why a job is in TM-HOLD.
BMC Compuware ThruPut Manager Standard Edition
All editions of ThruPut Manager.
BMC Compuware ThruPut Manager Standard Edition
All editions of ThruPut Manager.
How to determine why ThruPut Manager is holding a job (TM-HOLD)?
Issue $DJnnnnnn,LONG (where nnnnnn is the job number) from the system where the job is expected to initiate and check the system log (or ULOG from SDSF) for the command output:
This will provide an extended job display for all TM components managing the job (unless custom option UM0029 is ENABLED; issue the TM CUSTOM command to determine which custom options are ENABLED) from the point of view of the JES2 member where the command was issued;
A table of “$HASP890 Rejection Reason Messages ” (RRM) can be found in Appendix B. of the TM Operating Guide (these messages are only displayed when custom option UM0023 is DISABLED).
Although it is not generally recommended, in an emergency situation jobs can be released from a TM HOLD by issuing a RELEASE or ABANDON to the associated TM component that is holding the job:
JBS | JLS | SLM ABANDON nnnnnn – where nnnnnn is the job number;
DCS | JSS | MHS RELEASE nnnnnn – where nnnnnn is the job number;
Note that the job may fail once abandoned, as it may not have the resources it needs to complete successfully.
An SLM job that has not yet been selected due to an RRM code may be started using SLM START nnnnnn – where nnnnnn is the job number.