gtps4m1ySystem Generation

Program Test Vehicle

The program test vehicle (PTV) is capable of executing two different test phases under the control of TPF. These are package and system test and they are referred to by phase III and system test vehicle (STV) modes. With PTV, a user's application programs can be executed at various levels of testing while executing in a real-time TPF environment. Additional information about PTV testing may be found in TPF Program Development Support Reference.

The generation of a system with PTV support requires the user to code the PTV keyword on the CORREQ macro. Three choices are available:

NO
There will be no PTV support (the default).

YES
PTV support for both levels of testing.

STV
PTV support, but only for system test mode.
Note:
The specification of either YES or STV will also cause an indication in keypoint record 'A' (CTKA) that the system is in test mode. This same indication is also set on via the specification of VM=YES on the CONFIG macro.

In addition to the SIP generation requirement for PTV, the user must also perform other tasks for the proper generation of PTV support. These tables are related to the type of communications support that the user is employing (see Data Communications Support).

For 3705 EP communications support, the user must define the 3705 EP lines which are to be used by the application programmers when coding test unit input for PTV phase III and STV modes via the system test compiler (STC).

  1. PTV high-speed input may be from ALC, BSC, 3270 local, and/or SLC pseudo lines. The changes and generation considerations necessary for PTV 3705 EP support are also required for ALC lines supported by ACF and NEF, but NEF input also requires PTV/SNA generation requirements (see PTV considerations below).
  2. The user chooses whether to use real lines or to define for PTV a completely simulated 3705 EP communications network for its use. The difference is that if real lines are used, there can be no real input from those lines when executing PTV. If the choice is to use a simulated network, then the PTV user must generate that network all the way down to the terminal level (see Communications Record Generation) as if it really existed. Note, extreme care must be exercised by the system operators not to try to actually activate the simulated lines.
  3. Prior to executing SIP, the user must physically update a PTV segment to define these lines:
    1. ACP.SRCE.OL.RELvv PDS member NPTV, which is copied by CP segment CCUTIL and assembled by SIP, contains the simulated line number table that is located at label 'BRSHST'. Each is a two-byte entry where the first byte contains bit indications about the line and the second byte contains the actual symbolic line number (SLN) to be used. The listing commentary of NPTV explains how to code the bit indications. Entries not in use must be coded as a X'00FF'.
    2. The released version of NPTV contains entries for the "TPF Development" database and must either be physically updated prior to SIP Stage II or the entries patched into CCUTIL prior to execution. For PSEUDO SLC lines, the line number and the associated link must be defined in NPTV so that PTV can make use of that line.
    3. Line X'01', which represents prime and RO CRAS, should not be put into these tables. Input from the prime CRAS (LNIATA of X'010000') via STC may be coded without this table entry. Note that input of commands via STC from other than the prime CRAS can also be accomplished by coding input from a simulated alternate CRAS terminal which has been defined in the database and/or entered via the ZACRS command prior to PTV execution.
    4. At least one entry must be in each of the two tables.
  4. In addition to the updates required for PTV itself, users of PTV/STV mode and 3705 EP communications must also enter all of the simulated terminal addresses being used into tables located within the PDS member BMP0 of the post processor (see Diagnostic Output Formatter). This is required to perform terminal simulation by the offline formatter.