SYNCPOINT in response to SYNCPOINT
In an APPC mapped conversation , a transaction issues a SYNCPOINT command and its partner responds with a SYNCPOINT command.
Figure 1
,
Figure 2
,
and
Figure 3
illustrate the effect of SEND, SEND
INVITE, or SEND LAST preceding SYNCPOINT on an APPC mapped conversation.
The figures also show the conversation state
before
each command and the state and EIB fields set after each command.
Figure 1. SYNCPOINT (in response to SEND followed by SYNCPOINT) on an
APPC mapped
conversation. 
In this figure, transaction A is communicating
with transaction B using an APPC mapped conversation. Initially,
transaction
A's conversation with B is in
send state
, and transaction B's
conversation with A is in
receive state
.
- Transaction A issues a SEND command; its conversation remains in send state .
- Transaction B issues a RECEIVE command; it is suspended until data is received from transaction A.
- Transaction A issues a SYNCPOINT command; outstanding data, and the syncpoint request, are transmitted. The transaction is suspended until the syncpoint response is received from transaction B.
- Transaction B's RECEIVE command completes; EIBSYNC and EIBRECV are set, and its conversation is in syncreceive state .
- Transaction B issues a SYNCPOINT command; the response is transmitted, and its conversation is in receive state .
- Transaction A's SYNCPOINT command completes, and its conversation is in send state .

Figure 2. SYNCPOINT (in response to SEND INVITE followed
by SYNCPOINT) on an APPC mapped conversation. 
In this figure,
transaction A is communicating with transaction B using an APPC mapped
conversation.
Initially, transaction A's conversation with B is in
send state
,
and transaction B's conversation with A is in
receive state
.
- Transaction A issues a SEND INVITE command; its conversation is now in pendreceive state .
- Transaction B issues a RECEIVE command; it is suspended until data is received from transaction A.
- Transaction A issues a SYNCPOINT command; outstanding data, the INVITE flag, and the syncpoint request, are transmitted. The transaction is suspended until the syncpoint response is received from transaction B.
- Transaction B's RECEIVE command completes; EIBSYNC is set, and its conversation is in syncsend state .
- Transaction B issues a SYNCPOINT command; the response is transmitted, and its conversation is in send state .
- Transaction A's SYNCPOINT command completes, and its conversation is in receive state .

Figure 3. SYNCPOINT (in response to SEND LAST followed
by SYNCPOINT) on an APPC mapped conversation. 
In this figure,
transaction A is communicating with transaction B using an APPC mapped
conversation.
Initially, transaction A's conversation with B is in
send state
,
and transaction B's conversation with A is in
receive state
.
- Transaction A issues a SEND LAST command; its conversation is now in pendfree state .
- Transaction B issues a RECEIVE command; it is suspended until data is received from transaction A.
- Transaction A issues a SYNCPOINT command; outstanding data, the LAST flag, and the syncpoint request, are transmitted. The transaction is suspended until the syncpoint response is received from transaction B.
- Transaction B's RECEIVE command completes; EIBSYNC and EIBFREE are set, and its conversation is in syncfree state .
- Transaction B issues a SYNCPOINT command; the response is transmitted, and its conversation is in free state .
- Transaction A's SYNCPOINT command completes, and its conversation is in free state .
