IMTRLIFE did not generate messages until after IMS had abdumped offending transaction
Article ID: 202887
Updated On:
Products
Issue/Introduction
An IMS transaction was hung for a couple hours.
We have several Sysview thresholds for IMTRLIFE that should have generated messages but didn't.
After a couple hours, the transaction was identified and abdumped by support.
Following the abdump, many IMTRLIFE 'PROBLEM' messages were finally generated on that transaction as well as others.
The other odd thing was that multiple messages came out for the same transactions, but with different times for the value - like they had been held up somehow.
We'd like to know how that happened and if using the API to OPSMVS instead of a MESSAGE being generated would have made any difference in getting the information.
Environment
Release : 15.0
Component : SYSVIEW
Resolution
The IMTRLIFE Threshold you have will only be triggered after the transaction is complete.
This is unlike the dynamic CICS Thresholds that are used in SYSVIEW to perform transaction KILL's.
The IMTRLIFE will only produce the messages after the transaction has ended, and if something is hanging in the IMS region, that could delay the transaction from ending and eventually triggering the message.
Feedback
