Ensuring that System REXX is set up and active
For full functionality, the Incident Log task requires that the System REXX (SYSREXX) component be set-up and active on your z/OS® system.
This topic contains the following information:
Ensuring that System REXX is set-up properly
Observe the following considerations regarding
System REXX set-up:
- Ensure that you have an AXRnn JCL member in PROCLIB, similar to the AXRnn member in SYS1.IBM.PROCLIB.
- If you have an AXRnn member in SYS1.IBM.PROCLIB, ensure that SYS1.IBM.PROCLIB is in the MSTJCLxx IEFPDSI DD concatenation.
- Ensure that the user ID specified for AXRUSER in AXRnn has the correct permissions.
For more information about setting up System REXX, see the
following documents:
Ensuring that System REXX is active
SYSREXX is started automatically during IPL. If your installation has stopped SYSREXX, it is recommended that you restart it.
If you choose to defer this step, the Incident Log task runs with limited functionality.
How to check if this step is done
If the AXR address space is active on the z/OS system, the System REXX component
is active. To determine whether the AXR address space is active, enter
the following command:
D A,AXR
Figure 1 shows the
expected result:
Starting the SYSREXX address space
To start the SYSREXX component, enter the following command from the operator console:
START AXRPSTRT
For information about configuring System REXX on your system, see z/OS Program Directory.