The SET_COORDINATOR call

Associates a link with the current task's unit of work to represent a remote coordinator.

SET_COORDINATOR

Ensure that the object transaction XPI functions for phase 1 (OTTR_PREPARE) and phase 2 (OTTR_COMMIT or OTTR_ROLLBACK) are used to drive the current unit of work through sync point processing, in response to the actions of the remote coordinator. You cannot use the OTTR_COMMIT_ONE_PHASE function if you have used the SET_COORDINATOR function to add information about a coordinator to the unit of work of the current task, and you cannot allow the task to end without using the correct object transaction XPIs to sync point the current unit of work.

DFHOTCOX  [CALL,]
       [CLEAR,]
       [IN,
       FUNCTION(SET_COORDINATOR),
       [IOR_BLOCK,(block-descriptor)]
       [HOST_BLOCK,(block-descriptor)]]
       [OUT,
       COORDINATOR_TOKEN,(name1 | *),
       RESPONSE (name1 | *),
       REASON (name1 | *)]

This command is threadsafe.

HOST_BLOCK (block-descriptor)
A pointer to and length of a character string that represents the identity of the system, which contains the coordinator instance. The maximum supported length of this parameter is 4096 bytes.
IOR_BLOCK (block-descriptor)
A pointer to and length of a character string that represents the coordinator instance in the host system. The maximum supported length of this parameter is 4096 bytes.
COORDINATOR_TOKEN (name1 | *)
A token representing the coordinator.

RESPONSE and REASON values for SET_COORDINATOR

RESPONSE REASON
OK None
EXCEPTION

IOR_TOO LONG
HOST_TOO_LONG
LINK_UNKNOWN
COORDINATOR_NOT_FOUND
COORDINATOR_ALREADY
INVALID_SYNCPOINT_STATE

DISASTER None
INVALID None
KERNERROR None
PURGED None


dfha3_set_coordinator.html | Timestamp icon Last updated: Monday, 5 June 2017