The batch utility program TUBATEST allows the functions available via the Com-plete Batch interface to be tested individually.
Sample job control can be found in the Com-plete distribution source library in member JCLTUBAT, and looks as follows:
- z/OS:
//JOBTUBA JOB.... JOB CARD INFORMATION .. //* //* THIS IS A SAMPLE JOB TO RUN THE TUBATEST UTILITY //* TO PERFORM TEST FUNCTIONS FOR COMPLETE BATCH FUNCTIONS. //* //* THE FOLLOWING CHANGES HAVE TO BE PERFORMED BEFORE RUNNING THIS JOB:- //* //* 1. INSERT A VALID JOBCARD. //* 2. CHECK THE STEPLIB DATASET NAMES. //* //* NOTE:- //* THE FOLLOWING ONLY REQUIRED IF YOU REQUIRE TO OVERRIDE ACSTAB //* OR IF AN ACSTAB MODULE DOES NOT EXIST IN THE USER.LOAD DATASET. //* //* 3. CHANGE nnnn AND sss TO THE ACCESS NODE-ID AND ADABAS ROUTER SVC //* IDENTIFYING THE TARGET SYSTEM. //* //BATCH PROC //BATCH EXEC PGM=TUBATEST //STEPLIB DD DSN=COM.LOAD,DISP=SHR // DD DSN=COM.USER.LOAD,DISP=SHR <- FOR ACSTAB // DD DSN=ADABAS.LOAD,DISP=SHR <- FOR ADALNK //SYSPRINT DD SYSOUT=* //SYSABEND DD SYSOUT=* //*COMBTCH DD DSN=NODEnnnn.SVCsss,DISP=(NEW,DELETE),UNIT=SYSDA, //* SPACE=(TRK,(1,0,0)) // PEND //T1 EXEC BATCH //BATCH.SYSIN DD * < control cards > /*- z/VSE:
* $$ JOB JNM=JOBTUBA,DISP=D,CLASS=0 * $$ LST DISP=D,CLASS=A //JOB TUBATEST JOB.... JOB CARD INFORMATION .. /* /* THIS IS A SAMPLE JOB TO RUN THE TUBATEST UTILITY /* TO PERFORM TEST FUNCTIONS FOR COMPLETE BATCH FUNCTIONS. /* /* THE FOLLOWING CHANGES HAVE TO BE PERFORMED BEFORE RUNNING THIS JOB:- /* /* 1. INSERT A VALID JOBCARD. /* 2. CHECK THE LIBDEF STATEMENTS. /* /* NOTE:- /* THE FOLLOWING ONLY REQUIRED IF YOU REQUIRE TO OVERRIDE ACSTAB /* OR IF AN ACSTAB MODULE DOES NOT EXIST IN THE USER.LOAD DATASET. /* /* 3. CHANGE nnnn AND sss TO THE ACCESS NODE-ID AND ADABAS ROUTER SVC /* IDENTIFYING THE TARGET SYSTEM. /* // ASSGN SYS003,SYSLST // LIBDEF *,SEARCH=(SAGLIB.COMUSER,SAGLIB.COMvrs,SAGLIB.ADAvrs) /* DLBL COMBTCH,'NODEnnnn.SVCsss' // EXEC PGM=TUBATEST GETCHR /* /& * $$ EOJ
The control statements used as input from the SYSIN file determine which functions TUBATEST performs.
The control statement cards are free format . However, the whole of an individual statement must fit onto one 80 character input string.
The general format of the control cards is as follows:
<function> <operand1> <operand2> .... <operandn>
The number of operands which can be supplied is dependent on the function to be performed. A description of the functions and operands supported is given below:
- ABEND
The batch job is terminated with a S007 abend, the online transaction in the target Com-plete is terminated normally.
- CAPTUR
- GETCHR
- EOJ
The online transaction in the target Com-plete is terminated normally, the batch job continues, and if other input cards are available, the requested functions are performed.
Note:
If the TUBATEST is terminated without issuing an EOJ, the on-line transaction will remain in session in the target Com-plete until other action is taken (e.g. Autologoff or operator action).- MESGSW <destination> <message text>
Default destination is VIRTP1. Only one destination can be specified. Text length is 80 bytes. Default text is blanks. Message class is always 1.
You can enter the U= notation if the destination is a userid, otherwise it is taken for a printer name.
- PSOPEN <destination>
Default destination is VIRTP1. Only one destination can be specified. Listname is always ZUBATEST Form is always blanks. Length is always 81.
- PSPUT <printout text>
Text length is 80 bytes. Carriage control is ' '.
- PSCLOS
- RJE <option> <jcl card text>
Use option H for hold, any other value will release the JCL to the internal reader.
- SDOPEN <SD file name>
Default SD filename is ZUBATEST Tibname is always SHR. Number of records is 100. Record length is always 6 Kbytes.
- SDCLOS
SD filename is ZUBATEST. Tibname is always SHR.
- SDDEL
SD filename is ZUBATEST. Tibname is always SHR.
- SDWRT <record text>
SD filename is ZUBATEST. Tibname is always SHR. The SD file is written sequentially.
- SDREAD
SD filename is ZUBATEST. Tibname is always SHR. The SD file is read sequentially from the beginning.
After calling the Batch function TUBATEST will, where appropriate, print a display of any relevant control blocks and/or data areas and also display the response code returned from the batch interface routine.