If
you are having problems with a program written using the CICSPlex® SM application programming interface (API), the
first step is to rule out:
- Coding errors in the program itself.
- Incompatibilities between the program and the environment where it is
running. Specifically:
- If the API program is a REXX exec, ensure that the API function package (module
EYU9AR00 with the aliases of EYU9AR01 and IRXFUSER) is in an authorized
library that is in the MVS™ linklist or allocated to the STEPLIB DD in the
address space in which the REXX exec is running.
- If the API program is an assembled or compiled program, verify that
the program assembled or compiled properly and that it was link-edited
with the proper API stub for the environment in which the program will run.
The API stub for a CICS® environment is EYU9AMSI. The API stub for a
non-CICS environment is EYU9ABSI.
If you have ruled out these potential sources of problems and the program
still does not run successfully, you should do the following:
- Check for error messages and abends.
Such messages could be issued
by:
- The CMAS to which the API processing thread is connected.
- The MAS or user address space where the program is running.
If the program is running under MVS as a batch, TSO, or NetView® program,
error messages are written to the MVS console. If the program is running under
CICS, error messages are written to the CICS message log.
- Collect the following documentation:
- Program source
- Program listing (for compiled or assembled programs)
- Linkage editor map (for compiled or assembled programs)
In addition, collect as much of the following as possible:
- AUXTRACE data set for the CMAS, if available
- Formatted EYU_TRACE output (for REXX programs). Refer to the CICSPlex System Manager Application Programming Guide book for details on EYU_TRACE.
- System console log
- Appropriate job logs
- System or transaction dump, if any
When you have all the relevant information, contact your IBM® Support Center.
[[ Contents Previous Page | Next Page Index ]]