Filter
Top Products
v Otherwise, use the EXEC CICS ENABLE command to enable the user exit
program.
If you enable a global user exit program before it has been installed and
LPA=YES is specified as a system initialization parameter, CICS scans the LPA
for the program. If message DFHLD0109I is issued, it means that CICS was
unable to find the program in the LPA and is using the version in DFHRPL or a
dynamic LIBRARY.
4. When you have finished using the exit program, you can disable it using the
EXEC CICS DISABLE command.
For examples of how to enable and disable global user exit programs, see the
sample programs listed in “Sample global user exit programs” on page 15.
Viewing active global user exits
You can use the Web User Interface to view all of the global user exit programs that
are running in your CICS regions.
You must have CICSPlex SM installed and configured to perform this task.
1. Log on to the Web User Interface.
2. Select Operations views > Exit operations views > Global user exits. The
global user exits view displays details for all of the programs that are using
global user exit points in your CICS regions.
3. Select the name of the global user exit program that you are interested in to
view the details of the program definition.
Using this view you can perform additional tasks such as enabling and disabling
global user exit programs.
Invoking more than one exit program at a single exit
You can invoke more than one exit program from a single global user exit point.
Although such programs can work independently, you should note the following
points:
v An exit program is only called at an exit if it has been made available for
execution with the START option of the EXEC CICS ENABLE command. The order
of invocation, when more than one exit program has been started at an exit
point, is the order in which the programs were activated (that is, the order in
which the EXEC CICS ENABLE commands associated them with the exit point).
When programs work on the same data area, you should consider the order in
which they are invoked. For example, in a terminal control output exit, an exit
program might manipulate the same message in different ways, depending on
the way an earlier exit program acted.
v Return code management is more complicated than it is for single programs.
Each exit program sets a return code in register 15 as usual. The second and
subsequent programs invoked from a single exit point can access the return code
value set by the preceding program (the “current return code”) using the
parameter UEPCRCA of DFHUEPAR.
The following rules apply to return codes if a second user exit program sets a
different return code value from that selected by the previous program:
– If the new program supplies the same return code value as the current return
code (addressed by UEPCRCA), then CICS acts on that value.
Chapter 1. Global user exit programs 13