SYNCPT Verb Issued Locally
This section provides an example verb sequence with a verb issued locally.
SYNCPT verb issued locally.
The transaction program issues a SEND_DATA or MC_SEND_DATAverb depending on whether a basic or mapped conversation is being used.
The SEND_DATA or MC_SEND_DATA VCB is passed transparently through the vendor API to Host Integration Server. When the verb completes, the return code from Host Integration Server is returned to the transaction program.
The transaction program issues a SYNCPT verb to the vendor API.
The vendor API creates a PREPARE PS header and transmits it by issuing a SEND_DATA or MC_SEND_DATA verb. For a mapped conversation, the data_type field of the MC_SEND_DATA VCB must be set to AP_PS_HEADER.
On completion of the SEND_DATA or MC_SEND_DATA verb, the vendor API issues a RECEIVE_AND_WAIT or MC_RECEIVE_AND_WAIT verb.
The RECEIVE_AND_WAIT or MC_RECEIVE_AND_WAIT verb completes with the what_rcvd field of the VCB with a value of AP_PS_HEADER. The data buffer is filled with the received REQUEST_COMMIT PS header.
Another RECEIVE_AND_WAIT or MC_RECEIVE_AND_WAIT verb is issued to get send direction. Note that the vendor API can combine these two verbs into a single request by setting the rtn_status field of the VCB to AP_YES in order to receive status with data on the first RECEIVE_AND_WAIT or MC_RECEIVE_AND_WAIT.
A COMMITTED PS header is then transmitted using a SEND_DATA or MC_SEND_DATA verb.
The Vendor API issues a RECEIVE_AND_WAIT or MC_RECEIVE_AND_WAIT verb to receive the FORGET PS header from the remote TP.
Another RECEIVE_AND_WAIT or MC_RECEIVE_AND_WAIT verb is issued with the what_rcvd field of the VCB set to AP_SEND to get send direction (again the rtn_status RECEIVE_AND_WAIT field of the VCB can be set to AP_YES to combine these two verbs).
When send indication is received, the vendor API returns the SYNCPT verb to the local transaction program with an OK return code.