gtpo1mhv | Operations |
The following information describes the different control cards that are required by the system test compiler and the SMDU.
The correct sequence of the control cards is as follows, assuming that the system test compiler was linked and stored in a JOBLIB as STC:
//STCRUN JOB (Accounting Info),MSGLEVEL=1 //JOBLIB DD DSN=ACP.LINK.RELvv.ssid,DISP=SHR //STEPNAME EXEC PGM=STC,PARM='SALVER=ss,SALSIZ=nnnnnn' //SYSOUT DD SYSOUT=A //ISMDD DD SYSOUT=A //LIST DD SYSOUT=A //SYSPRINT DD SYSOUT=A //SYSUDUMP DD SYSOUT=A //STCDD DD DSN=ACP.OBJ.RELvv.ssid,DISP=SHR //SALTB DD DSN=ACP.SALTBL.RELvv.ssid,DISP=SHR //TAPE0 DD DSN=SDMF,UNIT=(TAPE,,DEFER),LABEL=(,BLP) // DISP=OLD,VOL=SER=userK0 //TAPE1 DD DSN=NEWTUT,UNIT=(TAPE,,DEFER),LABEL=(1,SL), // DISP=(,PASS),VOL=SER=userK1 //TAPE2 DD DSN=NEWSDMF,UNIT=(TAPE,,DEFER),LABEL=(,NL), DISP=(,PASS),VOL=SER=userK2 //TAPE3 DD DSN=DRIL,UNIT=(TAPE,,DEFER),LABEL=(,NL), // DISP=OLD,VOL=SER=userK3 //DISK01 DD DSN=PARSRCDS,VOL=SER=userd1 // UNIT=device,DISP=OLD, //CARDIN DD * system test compiler control cards /* //
Where:
The SDMF and the DRIL can reside on the same tape. In this case, the TAPE3 DD statement must contain the appropriate data set sequence number.
The system test compiler control cards can reside on tape. In this case, the CARDIN DD statement must contain the appropriate information.
When programs are being loaded to the TUT tape, the system test compiler requires that certain information is passed using the PARM= parameter in the EXEC statement. The PARM= parameter provides the version number (SALVER=vv) and the size (SALSIZ=nnnnnn) of the system allocator table.
The following control cards are necessary for a system test compiler run.
The control cards that define the pilot tape or the TUT tape must be preceded by one or more disk allocation cards and 1 disk type card. The last card of the input must be followed by an END STC card.
Each disk allocation card defines a set of disk tracks that were formatted
with either 381- or 1055-byte records on the SDMF/DRIL work disk. As
many as 20 disk allocation cards for large records and as many as 20 disk
allocation cards for small records can be used in one system test compiler
run.
Column | Content | Description |
---|---|---|
1 | (blank) |
|
2-5 | LOAD |
|
6 | (blank) |
|
7-15 | ADDRESSES |
|
16 | (blank) |
|
17-20 | xxxx | 4-digit hexadecimal address (cylinder number and head number) of the first track of this set. |
21 | (blank) |
|
22-23 | TO |
|
24 | (blank) |
|
25-28 | yyyy | 4-digit hexadecimal address (cylinder number and head number) of the last track of this set. |
29 | (blank) |
|
30 | Y or N | Specify Y if this set of tracks on the system test compiler work disk was formatted for duplicate records (primary or secondary). |
31 | (blank) |
|
32-35 |
1055 or 381 | Size of records on this set of tracks |
36-40 | (blank) |
|
41 | 1 | The disk allocation card that contains the first set of large (1055) addresses must contain a 1 in column 41. This card must be the first large address card on all subsequent runs. |
42-80 | (blank) |
|
One disk type card must be included to indicate to the system test compiler
the type of disk pack available for use as a work pack.
Column | Content | Description |
---|---|---|
1 | (blank) |
|
2-4 | STC | Identify the type of run. |
5-9 | (blank) |
|
10-13 | LOAD |
|
14-15 | (blank) |
|
16-23 | DISKFILE |
|
24-35 | (blank) |
|
36-39 |
dddd | Identify the device type of the system test compiler unit test disk; for example, 3390. (See TPF Migration Guide: Program Update Tapes for a list of supported devices.) |
40 | (blank) |
|
41 | L or (blank) | This column must contain an L if the SDMF and the DRIL are loaded to the system test compiler unit test disk from a tape. A blank column indicates to the system test compiler that the SDMF and the DRIL already reside on the system test compiler unit test disk. |
42-80 | (blank) |
|
This card must follow the last test unit. It indicates the end of
the run.
Column | Content | Description |
---|---|---|
1 | (blank) |
|
2-4 | END |
|
5 | (blank) |
|
6-8 | STC | Identify the type of run. |
9-80 | (blank) |
|
The following control cards are necessary for an SDMU run.
The disk allocation cards that are necessary for an SDMU run have the same format as the disk allocation cards that are used for a system test compiler run.
One disk type card must be included to indicate to the system test compiler
the type of disk pack available for use as a work pack.
Column | Content | Description |
---|---|---|
1 | (blank) |
|
2-5 | SDMU |
|
6-9 | (blank) |
|
10-13 | LOAD |
|
14-15 | (blank) |
|
16-23 | DISKFILE |
|
24-35 | (blank) |
|
36-39 |
dddd | Identify the device type of the system test compiler unit test disk; for example, 3390. (See TPF Migration Guide: Program Update Tapes for a list of supported devices.) |
40 | (blank) |
|
41 | L or (blank) | This column must contain an L if the SDMF and the DRIL are loaded to the system test compiler unit test disk from a tape. A blank column indicates to the SMDU that the SDMF and the DRIL already reside on the system test compiler unit test disk. |
42-80 | (blank) |
|
The SDMU END card follows the SDMU generation cards. It creates a
new SDMF tape and ends the job. Any new records that were added to the
SDMF are dumped to the printer.
Column | Content | Description |
---|---|---|
1 | (blank) |
|
2-5 | SDMU | Identify type of run. |
6-9 | (blank) |
|
10-12 | END |
|
13-80 |
|
|