Testing a program not currently executing

To test a program not currently executing, specify on the TEST or TESTAUTH command the data set name containing the program to be executed and any other applicable operands.

You can load and execute a program under the control of the TEST command processor if it is either:

A link-edited member of a partitioned data set or extended partitioned data set (PDSE).
An object module in a sequential or partitioned data set or PDSE.

You can load and execute a program under the control of the TESTAUTH command processor if it is a link-edited member of an APF-authorized library.

Issue the TEST or TESTAUTH command followed by the program name and the operands of the command that either define the program or are necessary to its operation. For example:

For the TEST command, the keyword LOAD or OBJECT depending on whether the program is a load or an object module. The TESTAUTH command does not support the OBJECT keyword. LOAD is the default.
The keyword CP, TP, or NOCP, depending on whether the program to be tested is a command processor, an APPC/MVS transaction program, or is another type of program that is not a command processor or a transaction program. NOCP is the default.
Note: You only need to specify the TP keyword if you are testing an inbound APPC/MVS transaction program (see Testing an APPC/MVS Transaction Program). You can test outbound transaction programs as ordinary programs.
Additional parameters necessary for the program being tested.

If the program you are testing is a command processor, specify the keyword CP. The CP keyword causes the test routine to create a command processor parameter list (CPPL), and place its address into register 1 before loading the program. If you do not explicitly specify the CP operand, any parameters that you specify in the TEST or TESTAUTH command are passed to the named program as a standard operating system parameter list. That is, when the program under TEST or TESTAUTH receives control, register 1 contains a pointer to a list of addresses that point to the parameters.

To test an inbound APPC/MVS transaction program, specify the TP operand.

Use the LU or BASELU keyword to specify the LU on which to test the transaction program. These operands are valid only when you use the TP keyword operand. BASELU is the default.
Use the keyword KEEPTP to specify that TEST or TESTAUTH should not clean up the transaction program and its conversations when TEST ends. If you do not specify this keyword, the TSO/E TEST command cleans up the transaction program and its conversations.