Testing Applications › Common Testing Errors

Common Testing Errors

The following is a list of some of the common errors that are made during testing.

• All load module components that are needed for the test must be generated and installed. When testing the flow between two procedure steps, be sure that both procedure steps were installed.
• If you attempt to access a load module that was not generated, the test fails. If the attempt is from within the Application Test Facility, the error message is:

  CSV0031 REQUESTED MODULE module_name NOT FOUND
  

• Press End, as defined in the testing environment for your application, to return to a clear screen.
• To test any part of a multi-step procedure, always generate the first procedure step and the procedure steps you intend to test. This is because the first procedure step provides the access to all other procedure steps in the procedure.
• You can only use the Debug Trace Facility with those components for which you generated debug support. You can test components without using the Debug Trace Facility.
• All load module components must be generated before the load module can be installed.
• The install fails when any component was not generated. The link-edit step has unresolved references when the application was statically linked. The application fails execution with U4038 abends when the application uses the Dynamically Link option.
• A load module must be installed before it can be tested. Ensure that it is installed using the correct installation parameters.
  • For the Application Test Facility, be sure to specify IEFAE as your target environment, or on the Host, select the Target TSO test facility option.
  • For CICS, specify CICS as your target environment. When a component marked for Compatibility is unavailable at execution time, the application attempting to dynamically call the Compatibility module abends with U03999. CA Gen writes a message to the CEEMSG DD indicating the name of the missing module.
• When testing a load module within the Application Test Facility that uses an external action block that contains IMS/CICS environment calls or DL/I calls, be sure to stub out the IMS, CICS, or DL/I calls within the external action block or the external action block itself. Failure to do so, causes the test to abend with a System 0C1 or 0C4.
• For Application Test Facility testing, ensure your ISPF logon CLIST points to a table library with the TIAECMDS command table. Failure to do so causes the PF3 End command to fail.
• CA Gen includes the TIAECMDS. The library in which it is stored is determined during CA Gen installation.

  Note: For information about installation, see the z/OS Installation Guide.

• If you experience problems allocating the TRANMAP file, verify that it exists and check the contents. If the file seems corrupted, delete it and start the testing facility again. CA Gen generates a new TRANMAP file for each user ID when one does not exist.