Changes to CICS XPI
Reassembling global user exit programs
The CICS global user exit programming interface is sensitive to both the release of CICS and settings in CICS. Even if there are no changes to the externals of the programming interface, changes to the internal workings of CICS can affect structures that are used by the CICS global user exit programming interface. As a consequence, you should reassemble global user exit programs for each CICS release.
Effect of multiple releases on user exits
A global user exit or task-related user exit might be assembled by using CICS libraries from one CICS release and make an XPI call on a system that runs a different CICS release. In this situation, successful transfer of control from the exit to the correct CICS module to handle that XPI call depends on the combination of CICS releases that are used to assemble the call and to make the call, and on whether the XPI call itself is release-sensitive. Release-sensitive XPI calls are available only from Version 4.1.
Table 1 shows the effect of different combinations of CICS release and the release-sensitivity of the call.
| CICS release of the libraries that are used to assemble the XPI call | Release-sensitive XPI call? (from V4.1 only) | CICS system that the XPI call is made on | Result |
|---|---|---|---|
| 5.2, 5.1, 4.2, or 4.1 | Yes | Any supported CICS release | Control transfers to the correct CICS module for the XPI call |
| 5.2, 5.1, 4.2 | No | 5.2, 5.1, 4.2 | Control transfers to the correct CICS module for the XPI call |
| 5.2, 5.1, 4.2 | No | 4.1, 3.2, 3.1 | Unpredictable result |
| 4.1 | No | 5.2, 5.1, 4.2, or 4.1 | Control transfers to the correct CICS module for the XPI call |
| 4.1 | No | 3.2 or 3.1 | Unpredictable result |
| 3.2 or 3.1 | No | 5.2, 5.1, 4.2, or 4.1 | Back-level XPI call detected, and user exit fails |
| 3.2 | No | 3.2 | Control transfers to the correct CICS module for the XPI call |
| 3.2 | No | 3.1 | Unpredictable result |
| 3.1 | No | 3.2 or 3.1 | Control transfers to the correct CICS module for the XPI call |
Changes to the XPI functions
| Functional area | V4.1 | V4.2 | V5.1 | V5.2 | V5.3 | V5.4 |
|---|---|---|---|---|---|---|
| All | CHANGED: By replacing the CALL XPI parameter with the RELSENSCALL XPI parameter, an XPI call assembled by using the CICS TS 4.1 libraries can execute successfully on all currently supported CICS releases. | |||||
| Bind channel | NEW: DFHPGCHX - to bind a channel to a task. | |||||
| Business application manager | NEW: INQUIRE_ACTIVATION call | |||||
| Enqueue | CHANGED: New ENQUEUE_TYPE option is added to ENQUEUE and DEQUEUE | |||||
| Loader | CHANGED:
|
|||||
| Kernel domain | CHANGED: Changes to the parameter list structure for functions on the KEDS gate. You must reassemble any exit programs that use START_PURGE_PROTECTION and STOP_PURGE_PROTECTION. | |||||
| Monitoring | NEW and CHANGED: New INQUIRE_APP_CONTEXT call now returns the current application context for the most recent application that was set onto the task | |||||
| Program management | CHANGED: REQUIRED_AMODE option of the SET_PROGRAM call specifies the
addressing mode of non-LE AMODE(64) assembler programs. SPECIFIED_AMODE option of the GET_NEXT_PROGRAM and INQUIRE_PROGRAM calls, and the CURRENT_AMODE option of the INQUIRE_CURRENT_PROGRAM call, now return the addressing mode of non-Language Environment (LE) AMODE(64) assembler programs |
CHANGED: New options on the INQUIRE_PROGRAM and START_BROWSE_PROGRAM calls to inquire on private programs for applications that are deployed on platforms. | ||||
| Set tracking data | NEW: DFHMNTDX - to set the transaction tracking origin data tag for the issuing task. | |||||
| State data access | CHANGED: DSA option of the INQ_APPLICATION_DATA call now returns the address of the head of the dynamic storage chain as a 64-bit address. | |||||
| Storage control |