gtpp1m0b | Program Development Support Reference |
You can run the PTV utility in the following modes (also known as testing levels). To decide which mode to use you must determine the status of program development at your installation and the degree of testing complexity required. A description of each mode follows here.
In this mode, more than 1 test unit can be included on a test unit tape (TUT). A test unit can also span more than 1 TUT.
The PTV utility starts automatically when running in this mode. During each test unit and after each test unit is complete, you can enter live input if you specified live input on the RUNID card.
No driver is permitted in this mode. Also, the application program interfaces for processing messages in the test unit must be established. After the PTV utility has created the environment, PTV initiates the test by passing your first message to the control program, simulating an input message arriving on a communication line.
Messages are handled in single or multithread environments, and in burst or asynchronous mode:
In this mode, only 1 test unit can be included on a TUT. However, this test unit can span more than 1 TUT. You start and control the PTV utility in this mode by entering the ZSTVS commands. You can enter live input during the unit test.
In this mode, a full scale system is tested. Messages are handled in a multithread environment. Data and programs must have been loaded with standard system facilities. Data and programs are not allowed on the TUT. In this mode, messages are handled as in the phase 3 (package test) mode, except that the testing mode is specified through a PTV command.
This mode stops the PTV utility and returns control to the TPF system.
See TPF Operations for more information about PTV commands and for procedures you can use to run the PTV utility.