Extracting Detailed Scheduling and Conversation Information

With the Extract_Information service, APPC/MVS transaction programs can extract detailed information about their own conversations and scheduling. If in supervisor state or PSW key 0-7, they can extract conversation information about other TPs.

You can call the Extract_Information service from a TP to extract scheduling information such as the transaction scheduler, the transaction initiator class, and the TP schedule type under which the TP is running. You can also extract conversation information, such as the total number of conversations in which the TP is involved, the number of sends and receives it has performed, the unit of recovery identifier (URID) for a protected conversation, and the total amount of data sent and received.

TPs can save this extracted information in a data set for later analysis or use it dynamically. For example, a TP can use the Extract_Information service to check whether it is scheduled with the multi-trans schedule type and, if so, call the Get_Transaction service to accept new conversation requests in sequence.

As input to the Extract_Information service, specify the type of information you want to extract (scheduler, summary conversation, or specific conversation), the TP or conversation involved (the caller's or, if the caller is authorized, the TP_ID or Conv_ID of another TP or conversation whose information you want), and a buffer for the output. The buffer can be ALET-qualified, subject to the limits described in Support for Data Spaces.