Application programming interface problems
For problems with a program written using the CICSPlex SM application programming interface (API), first rule out potential sources of problems. Then check for error messages and abends, and collect the relevant information before contacting your IBM® Support Center.
The first step is to rule out the following potential sources of
problems:
- Coding errors in the program itself.
- Incompatibilities between the program and the environment where
it runs.
- 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 correctly and that it was link-edited with the appropriate API stub for the environment in which the program runs. The API stub for a CICS® environment is EYU9AMSI. The API stub for a non-CICS environment is EYU9ABSI.
- 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.
- Collect the following documentation:
- Program source
- Program listing (for compiled or assembled programs)
- Linkage editor map (for compiled or assembled programs)
- AUXTRACE data set for the CMAS, if available
- Formatted EYU_TRACE output (for REXX programs).
- System console log
- Appropriate job logs
- System or transaction dump, if any