dfhe5_exit_intro.html |
Last updated: Saturday, 15 June 2019CICS® Transaction Server for z/OS®, Version 5 Release 2 has changes to some existing programming interface. Check your existing global user exit programs against the changes summarized here.
The CICS global user exit programming interface is product-sensitive, and depends on the facilities that are set up in your CICS system. It is advisable to reassemble global user exit programs for each CICS release, because changes to CICS internals might affect structures used by the CICS global user exit programming interface, even if there are no changes to the externals of the programming interface.
In CICS TS for z/OS, Version 5.1, there were changes to the parameter list structure for functions on the KEDS gate. If you have global user exit programs that use the kernel domain XPI functions, which are the DFHKEDSX calls START_PURGE_PROTECTION and STOP_PURGE_PROTECTION, then you must reassemble those exit programs.
For other areas of the XPI, check the changes to externals that are summarized in this section, and modify your global user exit programs to allow for changes to relevant parameters. After you complete your program changes, reassemble the affected global user exit programs against the CICS Transaction Server for z/OS, Version 5 Release 2 libraries.
A global user exit or task-related user exit might be assembled using CICS libraries from one CICS release and make an XPI call on a system that runs a different CICS release. In this situation, whether or not control is successfully transferred from the exit to the correct CICS module to handle that XPI call depends on the combination of CICS releases, and whether the XPI call is a release-sensitive call. For the user exit to succeed, you must also check other factors, for example whether XPI parameters have changed between releases.
If a user exit fails, an error message is issued and the transaction that called the exit might abend.
The following table summarizes the effect of different CICS releases on user exits. Release-sensitive XPI calls are not available in releases before CICS TS 4.1.
| CICS release of the libraries used to assemble the XPI call | Release-sensitive XPI call? | CICS system that the XPI call is made on | Result |
|---|---|---|---|
| CICS TS 5.2, CICS TS 5.1, CICS TS 4.2, or CICS TS 4.1 | Yes | All currently supported CICS releases | Control transfers to the correct CICS module for the XPI call |
| CICS TS 5.2, CICS TS 5.1 or CICS TS 4.2 | No | CICS TS 5.2, CICS TS 5.1 or CICS TS 4.2 | Control transfers to the correct CICS module for the XPI call |
| CICS TS 5.2, CICS TS 5.1 or CICS TS 4.2 | No | CICS TS 4.1, CICS TS 3.2, and CICS TS 3.1 | Unpredictable result |
| CICS TS 4.1 | No | CICS TS 5.2, CICS TS 5.1, CICS TS 4.2, or CICS TS 4.1 | Control transfers to the correct CICS module for the XPI call |
| CICS TS 4.1 | No | CICS TS 3.2 and CICS TS 3.1 | Unpredictable result |
| CICS TS 3.2 or CICS TS 3.1 | No | CICS TS 5.2, CICS TS 5.1, CICS TS 4.2, or CICS TS 4.1 | Back level XPI call detected, and user exit fails |
| CICS TS 3.2 | No | CICS TS 3.2 | Control transfers to the correct CICS module for the XPI call |
| CICS TS 3.2 | No | CICS TS 3.1 | Unpredictable result |
| CICS TS 3.1 | No | CICS TS 3.2 or CICS TS 3.1 | Control transfers to the correct CICS module for the XPI call |
Last updated: Saturday, 15 June 2019