Using the TSO/E TEST Command to Test an Assembler Language TP

The TSO/E TEST command offers interactive test facilities that allow you to test TPs written in assembler language. TSO/E TEST automatically calls the Register_Test and Accept_Test services, and loads the module for the TP to be tested. When the test ends, TSO/E TEST automatically cleans up the TP to be tested and its conversations if the KEEPTP parameter is not specified on the command.

Follow these steps when using TSO/E TEST to test an assembler TP:

Logon to TSO/E with a logon procedure that does not allocate APPC/MVS conversations when an APPC/MVS TP is to be tested.
Catalog the data set that contains the load module for the TP to be tested.
Allocate all required data sets to the TSO/E address space where the TP is to run, including a data set for the TP message log. See the section on logging transaction program processing in z/OS MVS Planning: APPC/MVS Management.
Ensure that no active APPC conversations are in progress in the TSO/E address space where the TP is to run.
Establish the required environment for the test shell TP, as described in Test Shell Characteristics.
Ensure that the TP under test belongs to an APPC/MVS local LU that allows user-level TP profiles. (Although you are not required to have a user-level TP profile when testing a TP under a TSO/E user ID, the associated LU still must be enabled for user-level TP profiles.) See Enabling an LU for User-Level TP Profiles.
Figure 1 shows a terminal screen that represents the sequence of events for steps 7 through 9, which follow. In the figure, capitalized text indicates a response from the system, and mixed-case text indicates a user command:
Figure 1. TSO/E Terminal Screen
```
         READY

 7      test 'user.appc.load(testtp)' tp('TESTTP') lu('LUA')

               IKJ57522I YOU CAN ALLOCATE THE TP NOW

 8      +++ the user starts a program that allocates
                the TP to be tested +++

         TEST

 9      +++ the user can now test the TP as if it
                is an ordinary program +++

         TEST

 10      end

         READY
```
Enter the TEST command, where "user.appc.load(testtp)" is the load module for the TP to be tested, TESTTP is the TP name under which the load module is to be tested, and LUA is the LU on which the TP is to be tested. If you do not enter the LU keyword, the default value is the system base LU. The system loads and invokes the TP.
After the system issues message IKJ57522I, start an outbound TP that allocates an APPC/MVS conversation with the TP to be tested. The outbound TP should specify the following values when calling the Allocate service to allocate the conversation:
- The user ID under which the TP under test (the inbound TP) is running
- A Security_type of security_pgm or security_same.
See APPC/MVS TP Conversation Callable Services for a complete description of the parameters that are required on an Allocate call from an outbound TP. The system displays a TEST mode message.
Enter TEST subcommands to test the TP (see z/OS TSO/E Command Reference for information about TEST subcomands). When the test completes, the system returns another TEST mode message, and waits for the user's next command.
Enter the end subcommand to end test processing. TEST returns to READY mode.

For complete information about how to use the TSO/E TEST command, see z/OS TSO/E Command Reference and z/OS TSO/E Programming Guide.