SNAX/APC Configuration and Management Manual
Trace Analysis Program
SNAX/APC Configuration and Management Manual—138787
5-20
Normal Version (Log Format)
On this side, the conversation also starts with a TP-READY verb issued by the 
remote TP. 
Remember that the names local and remote are relative (within the context of verb 
parameters), for example, the local LU is the one that is local to this side of the 
conversation.
The parameters of the verb indicate:
•
The local LU name is lup01.
•
The local TP name is progp01a001.
•
No, the attach is not local—which means this TP will not be initiating the 
conversation and therefore will start in a Receive state.
•
No, the TP is not dispatched.
All reply and return codes have the value zero, a normal completion. Because all the 
other verbs issued by this TP complete normally, those subsequent responses have 
been edited out from the example—with the exception of the RECEIVE-AND-
WAIT verbs.
The RECEIVE-AND-WAIT verb is issued by the remote TP when it is ready to 
receive data or control information from the local TP.
The parameters of the verb indicate:
•
The record type is Logical.
•
The number of bytes that can be received is 400.
Successful completion of the RECEIVE-AND-WAIT verb occurs when the TP 
receives data or control information from the other TP. The WHAT-RECEIVED 
indicator informs the TP of the type of information received.  In this case the data 
type is 1, which indicates that the TP received a complete logical record or the last 
remaining portion of a logical record—the entire data string.
A TP in Receive state issues RECEIVE-AND-WAIT verbs until the value in WHAT-
RECEIVED indicates a transition from Receive state. This occurs with the second 
issuance of the RECEIVE-AND-WAIT verb.  The received data type is 4, which 
indicates that the local TP issued a CONFIRM verb. The remote TP enters the 
Confirm state and can respond by issuing either CONFIRMED or SEND-ERROR. 
No data is received in this reply.
The remote TP uses the CONFIRMED request to acknowledge receipt of data (or 
completion of a function).
The remote TP again issues a RECEIVE-AND-WAIT. This time the response 
contains no data, but the UOW header return code contains the value 1005. This 
indicates an RC-DEALLOCATE-NORMAL request.  The local TP requested 
conversation deallocation. The remote TP should now issue DEALLOCATE 
(LOCAL). The conversation is now in Deallocate state. This is a normal return 
code—it is not an error.
1
2
3
4
5










