Hang detection functionality
TXSeries® for Multiplatforms 11.1 provides a hang detection tool that detects potential hangs and collects the required problem determination documents automatically. The tool also provides a capability to FORCEPURGE the transaction after a set period of time.
This hang detection functionality allows you to collect the process information to determine the transaction hang scenario. To enable this facility, you need to define TranMonitorAction and TramMonitorInterval parameters in Transaction Definition stanza. The TranMonitorAction attribute should be set to either process_dump or tran_dump and TranMonitorInterval to a non zero value (in seconds) to collect the process stack or transaction dump information to find process or transaction state to determine whether this transaction is hung or not.
By default, this facility is enabled for all the defined transactions and the default values are process_dump and 300 seconds.
The terminal conversational transactions will not do the action defined in TranMonitorAction parameter and this value will be set to none internally by TXSeries and a warning message will be logged in the CSMT file.
The functionality uses the Transaction Monitoring facility introduced in TXSeries for Multiplatforms 11.1, to take an action defined for the transactions in the TD stanza depending on the values set for the attributes TranMonitorAction and TranMonitorInterval. If any action (other then none) is defined in the TranMonitorAction and the timeout value set in the TranMonitorInterval (other then zero) then the transaction expiring at TranMonitorInterval will perform the action specified in TranMonitorAction.
The action process_dump will be dumping the process stack information using showProcInfo utility for that process the transaction runs. The transaction would continue to run.
The action tran_dump will be generating a file with the transaction dump.
If none is specified to TranMonitorAction along with other options, the other options are ignored.
If the transactions are conversational type, then TranMonitorAction will be set to none (no action will be taken) internally. A message will be logged in CSMT file regarding this change.