Functions provided by the CPI component

Table 23 summarizes the external subroutine interfaces provided by the CPI component. It shows the subroutine call formats, the level-1 trace point IDs of the modules providing the functions for these formats, and the functions provided.

Table 23. CPI component’s subroutine interfaces
Format Trace Function
CPIN
AP 0C01
AP 0C02
START_INIT
COMPLETE_INIT
CPSP
AP 0CD0
AP 0CD1
SYNCPOINT_REQUEST

CPIN format, START_INIT function

The START_INIT function of the CPIN format is used to attach a CICS® task to perform initialization of the CPI component.

Input parameters

None.

Output parameters

RESPONSE
is the subroutine’s response to the call. It can have any of these values:
OK|DISASTER|KERNERROR
[REASON]
is returned when RESPONSE is DISASTER. Possible values are:
RESPONSE Possible REASON values
DISASTER
GETMAIN_FAILED
ADD_SUSPEND_FAILED

CPIN format, COMPLETE_INIT function

The COMPLETE_INIT function of the CPIN format is used to wait for the initialization task attached by the START_INIT function to complete processing.

Input parameters

None.

Output parameters

RESPONSE
is the subroutine’s response to the call. It can have any of these values:
OK|DISASTER|KERNERROR
[REASON]
is returned when RESPONSE is DISASTER. It has this value:
INIT_TASK_FAILED

CPSP format, SYNCPOINT_REQUEST function

The SYNCPOINT_REQUEST function of the CPSP format is used to send LU6.2 syncpoint flows on recoverable conversations using the SAA Communications interface, and to update the conversation state as required.

Input parameters

CPC_ADDRESS
is the address of the SAA Communications conversation control block (CPC).
LUC_ADDRESS
is the address of the DFHLUC parameter list.

Output parameters

RESPONSE
is the subroutine’s response to the call. It can have either of these values:
OK|KERNERROR
[[ Contents Previous Page | Next Page Index ]]