ISSUE PREPARE
Issue the first flow of a syncpoint request on an APPC mapped conversation.
Description
ISSUE PREPARE applies only to distributed transaction processing over APPC links. It enables a syncpoint initiator to prepare a syncpoint worker for syncpointing by sending only the first flow (prepare-to-commit) of the syncpoint exchange. Depending on the reply from the syncpoint worker, the initiator can proceed with the syncpoint by issuing a SYNCPOINT command, or initiate back-out by issuing a SYNCPOINT ROLLBACK command.
Options
- CONVID(name)
- identifies
the conversation to which the command relates. The 4-character name
identifies either the token returned by a previously executed ALLOCATE
command in EIBRSRCE in the EIB, or the token representing the principal
facility (returned by a previously executed ASSIGN command).
For compatibility with earlier releases, SESSION is accepted as a synonym for CONVID. New programs should use CONVID.
If both CONVID and SESSION are omitted, the principal facility is assumed.
- STATE(cvda)
- gets
the state of the current conversation. The cvda values returned by CICS® are:
- ALLOCATED
- CONFFREE
- CONFRECEIVE
- CONFSEND
- FREE
- PENDFREE
- PENDRECEIVE
- RECEIVE
- ROLLBACK
- SEND
- SYNCFREE
- SYNCRECEIVE
- SYNCSEND
Conditions
- 16 INVREQ
- RESP2
values:
- 200
- A distributed program link server application specified the function-shipping session (its principal facility) on the CONVID option.
also occurs (RESP2 not set) in any of the following situations:- The conversation is not an APPC mapped conversation.
- The conversation state is not valid for the request.
- The sync level of the conversation is not 2.
Default action: terminate the task abnormally.
- 61 NOTALLOC
- occurs
if the CONVID value in the command does not relate to a conversation
that is owned by the application.
Default action: terminate the task abnormally.
- 81 TERMERR
- occurs
for a session-related error. Any action on that conversation other
than a FREE causes an ATCV abend.
A CANCEL TASK request by a user node error program (NEP) may cause this condition if the task has an outstanding terminal control request active when the node abnormal condition program handles the session error.
Default action: terminate the task abnormally with abend code ATNI.