The following example outlines the required steps for testing an
APPC/MVS transaction program with the TSO/E TEST command:
READY
(1) test (myprog) tp(’MAIL’) keeptp
(2) IKJ57522I YOU CAN ALLOCATE THE TP NOW
+++ the user starts a program that allocates the TP to be tested +++
(3) TEST
+++ the user can now test the TP as if it is an ordinary program +++
(4) TEST
(5) end
(6) READY
- Prefix.LOAD(myprog) contains the load module
for the transaction program to be tested. MAIL is the transaction
program name under which the load module is to be tested. The inbound
allocate request will try to allocate MAIL.
- Wait for TSO/E TEST to prompt you to allocate the transaction
program to be tested. The message IKJ57522I indicates that it is
your turn to start a program that allocates an APPC/MVS conversation
with the transaction program to be tested.
- TEST displays a TEST mode message, indicating
that it is your turn to enter TEST subcommands to control TEST's processing.
- TEST returns control to the terminal with another mode message.
- To terminate TEST processing, use the END subcommand.
- TEST returns to READY mode.
Because the LU keyword is not specified in this example, TSO/E
TEST uses the base LU for testing (BASELU is the default keyword).
Also, the transaction program and its remaining conversations are
not cleaned up by the TEST command because the KEEPTP keyword is specified.