You can use the TEST and TESTAUTH commands to test APPC/MVS transaction programs. You can use the commands with inbound transaction programs—those that are initiated in response to inbound conversation requests from their partner transaction programs. When testing an APPC/MVS transaction program:

• There must not be a transaction program existing in the TSO/E user's address space when the TSO/E TEST or TESTAUTH command is invoked to test an APPC/MVS transaction program. You should log on with a logon procedure that does not allocate APPC/MVS conversations if an APPC/MVS transaction program is to be tested. After TSO/E TEST has been invoked with the TP keyword, you can allocate DFM data sets. However, if you want to invoke TEST again, you may have to log off and then log on again.
• You cannot use the TSO/E TEST or the TESTAUTH command to completely test multi-trans (multiple transaction) transaction programs. You can, however, use TSO/E TEST to partially test an APPC/MVS multi-trans transaction program up to the point when the transaction program attempts to get the next transaction.
• The user-level transaction program profile for the LUs that are to be used for transaction program testing must be defined at installation time. To define a user-level transaction program profile, the LUADD statement in PARMLIB member APPCPMxx must include the TPLEVEL(USER) keyword.
• If you press the attention key while waiting for the inbound allocate request, and enter anything other than a null line, TSO/E cancels the test request.
• If you press the attention key twice to end the TSO/E TEST or TESTAUTH command, and enter anything other than a null line, TSO/E cancels the command. The TSO/E TEST or TESTAUTH command cleans up the transaction program you are testing unless the KEEPTP keyword is specified.