New global user exit points

Table 26 shows the new global user-exit points.

Table 26. New global user-exit points
Module or domain Exit name When invoked
EXEC interface program XPCERES

XPCERES is invoked by the EXEC interface program, on the target region, before CICS® processes either of the following kinds of dynamically-routed link request:

  • A distributed program link (DPL) call
  • A Link3270 bridge request

It is described in the CICS Customization Guide.

File control domain XFCFRIN

For an introduction to XFCRIN see XFCFRIN and XFCFROUT global user exits

XFCFRIN allows you to:

  • Monitor file control requests and allow them to continue, to be processed by CICS file control
  • Intercept file control requests and bypass CICS file control processing altogether
  • Redirect the request to a remote region.

For details of these global user exit points see the CICS Customization Guide.

XFCFROUT

For an introduction to XFCROUT see XFCFRIN and XFCFROUT global user exits

On completion of requests in the remote region, you can use XFCFROUT, which allows you to monitor the results of completed file control requests.

For details of these global user exit points see the CICS Customization Guide.

Interval control program XICERES

XICERES is invoked by the interval control program, before CICS processes a non-terminal-related EXEC CICS START request that has been dynamically routed to this region.

It is described in the CICS Customization Guide.

Security manager domain XSNEX

Introduced to enable you to restore the same behavior for EXEC CICS SIGNON and SIGNOFF commands as in releases of CICS before CICS TS 2.1 (see Change of rules for EXEC CICS SIGNON and SIGNOFF for details of the changed behavior).

The intention behind XSNEX, and its supporting sample programs is to provide a short term migration aid, to give you time to modify affected application programs to work with the new behavior described in Change of rules for EXEC CICS SIGNON and SIGNOFF.

XFCFRIN and XFCFROUT global user exits

There are changes to file control to permit a CICS system file to be defined as a remote file. For example, the EJB directory data set and the EJB object store data set must both be shared by all the AORs in a logical EJB server. The changes to CICS file control enable this sharing to be managed by a CICS file-owning region (FOR). However, the restructuring of file control to enable this enhancement to CICS remote file support can affect the invocation of the file control EXEC interface API global user exits, XFCREQ and XFCREQC:

If you are affected by this change, and still need to intercept the file control request in the file-owning region, you can use the new file control exit, XFCFRIN, which allows you to:

On completion of requests in the remote region, you can use XFCFROUT, which allows you to monitor the results of completed file control requests.

For details of these global user exit points see the CICS Customization Guide.

[[ Contents Previous Page | Next Page Index ]]