Syncpoints
If the server program was started by a LINK command that specified the SYNCONRETURN option, it is able to issue a syncpoint.
If it does, this does not commit changes made by the client program. For changes to be committed across the distributed unit of work, the client program must issue the syncpoint. The client program can also backout changes across the distributed unit of work, provided that the server program has not already committed its changes.
The server program can find out how it was started, and therefore
whether
it is allowed to issue independent syncpoint requests, by issuing the
ASSIGN
STARTCODE command. This command returns the following values relevant to
a DPL server program:
- 'D' if the program was started by a LINK request without the SYNCONRETURN option, and cannot therefore issue SYNCPOINT requests.
- 'DS' if the program was started by a LINK request with the SYNCONRETURN option, and can therefore issue SYNCPOINT requests. However, the server program need not issue a syncpoint request explicitly, because CICS takes a syncpoint as soon as the server program issues the RETURN command.
- Values other than 'D' and 'DS' if the program was not started by a remote LINK request.