Testing Applications › Application Test Facility Considerations

Application Test Facility Considerations

The TSOAE environment used by the Application Test Facility was implemented as a 31-bit, LE compliant application. The use of 24-bit storage was changed to be limited to those TSO and I/O functions that require being addressed below the 16-MB line. This version of TSOAE provides virtual storage constraint relief for testing and implementing large CA Gen applications within TSO and batch.

The Application Test Facility does not support external subroutine logic such as DL/I calls, IMS calls, or CICS calls.

Only DB2 databases can be updated during test executions.

You have two ways to test applications that use DL/I, IMS, or CICS calls:

• Create CA Gen procedure steps without the USE statements that call the external logic. Then generate and test CA Gen load modules. After the load modules have been debugged, add the USE statements to your action diagrams.
• Create CA Gen procedure steps, including the USE statements in your action diagrams. Create stubs for the external routines that do not use DL/I, IMS, or CICS calls. Then generate and test CA Gen load modules. After the load modules have been debugged, add the DL/I, IMS, or CICS calls to the stubs.

When testing batch applications, it is important to consider the amount of test data used. The Application Test Facility executes online, so it is recommended you use a small volume of data when testing batch applications.