SNAX/APC Application Programming Manual

Application Prototype Simulator
SNAX/APC Application Programming Manual—138786
4-36
REQUEST-TO-SEND (F6)
is mapped or not). SNAX/APC requires this two-byte length field. Note that the
length must be entered in hexadecimal. The data does not have to end on a logical
record boundary unless it is the last or only data to be sent.
The data must be in a format recognizable to the partner TP. For example, if a CICS
application is to receive the data, the data must be in EBCDIC. Use the hexadecimal
editor to enter EBCDIC data (in hexadecimal).
Length
specifies the number of bytes of data being sent with this SEND-DATA verb. This is
the buffer size and is not necessarily the same as the length of the logical record.
Reply Fields
IPC Return Code
displays the value of HEADER-RETURN-CODE returned in the IPC header reply.
IPC Return Code Detail
displays the value of HEADER-RETURN-CODE-DETAIL returned in the IPC
header reply.
UOWs In
displays the number of UOWs in this IPC message (always 1 for APS).
UOWs Out
for APS, this value is always 1. UOWs Out indicates the number of reply UOWs
contained in the reply from SNAX/APC.
Header Return Code
displays the value of REP-RETURN-CODE returned in the reply UOW.
Request to Send Ind
indicates whether the partner TP issued a REQUEST-TO-SEND verb. The value Y
indicates that REQUEST-TO-SEND notification was received from the partner TP,
which requests the local TP (APS) to enter the Receive state. The value N indicates
that the partner TP did not issue a REQUEST-TO-SEND verb.