gtps2m25 | ACF/SNA Data Communications Reference |
Use the PIU trace facility to display the NLPs that are sent between the
TPF system and remote RTP endpoints. See Appendix D, Using the Path Information Unit (PIU) Trace Facility for more information about the PIU trace facility.
When the TPF system breaks an RTP connection for a reason that is not
architected, an implementation-specific sense code is sent in the connection
fault (CF) segment to indicate the reason for the failure. The
following are the sense codes and reasons why the TPF system sends them:
- X'A001EE01'
- The TPF operator issued a ZNRTP INACT command causing the connection to be
unconditionally broken.
- X'A001EE02'
- The TPF system is asked to retransmit a message, but the HPRMT is not
defined; therefore, no saved message exists.
- X'A001EE03'
- The TPF system is asked to retransmit a message, but the message was not
found in the HPRMT.
- X'A001EE04'
- The number of items on the RTP output queue for this RTP connection is too
large.
- X'A001EE05'
- The number of items on the RTP input queue for this RTP connection is too
large.
- X'A001EE06'
- The TPF system asked for data to be retransmitted, but the remote RTP
endpoint did not retransmit that data.
- X'A001EE07'
- Two NLPs marked as start-of-message (SOM) were received without an
end-of-message (EOM) between them.
- X'A001EE08'
- An NLP marked as middle-of-message was received without a start-of-message
(SOM) being received first.
- X'A001EE09'
- An NLP marked as end-of-message (EOM) was received without an NLP marked
as start-of-message (SOM) having been received first.
- X'A001EE0A'
- The TPF system sent a COB request to end the RTP connection, but a COB
response was not received.