Submitting a compile request from TSO Client in batch mode

Use the pbb parameterized build request to submit a COBOL program to the z/OS® system for compiling. This command runs the parameterized build request in batch mode.

Before you begin

Before you can submit parameterized build requests in batch mode, an administrator needs to modify the following files. Changes to be made to these files are shown in boldface with underscoring.

Member TSCBATCH of hlq.version.JCL

//TSCBATCH JOB ,USERID,NOTIFY=&SYSUID, 
// USER=&SYSUID,CLASS=F,MSGCLASS=H,TIME=50 
//******************************************************************** 
//*                                                                  * 
//*     CLEARCASE OS/390 CONNECTORS                                  * 
//*                                                                  * 
//*         JOB TO SUBMIT THE BATCH PARAMETERIZED BUILD              * 
//*                                                                  * 
//*     BEFORE SUBMITTING:                                           * 
//*                                                                  * 
//*         1. MODIFY THE SUBSTITUTION PARAMETERS TO MEET YOUR       * 
//*            SITE REQUIREMENTS.                                    * 
//*         2. MODIFY THE LAST STATEMENT WITH CORRECT HLQ            * 
//RSERVER PROC HLQ='RCC.#version'            <== HLQ
//************************************************** 
//* ISPF BATCH AUFRUF 
//************************************************** 
//TSOBAT   EXEC PGM=IKJEFT01,DYNAMNBR=1000 
//SYSTSPRT DD SYSOUT=* 
//SYSOUT   DD SYSOUT=* 
//SYSPRINT DD SYSOUT=* 
//SYSEXEC  DD DISP=SHR,DSN=&HLQ..TSCRX
//STEPLIB  DD DISP=SHR,DSN=&HLQ..TSCLOAD
//         PEND 
//RSERVER  EXEC RSERVER 
//SYSTSIN  DD * 
EXEC 'RCC.#version.TSCRX(EXCMDP)' 'MAP0'

Member EXCMDP of hlq.version.TSCRX

/* Rexx */
/****************************************************************/
/*    Licensed Materials - Property of IBM                      */
/*                                                              */
/*    (C) Copyright IBM Corp. 2005, 2011                        */
/*                                                              */
/*     Change "RCC.version" to the appropriate high-level       */
/*     qualifier.  The high-level qualifier must match the      */
/*     specification for the HLQ parameters in the allocation   */
/*     job, RCC01ALO.                                           */
/*                                                              */
/****************************************************************/
Parse Arg input
Parse Var input mapParm batchjob fileNames
HLQ = 'RCC.version'
USERID = Sysvar('Sysuid')
/* LOG3 = LOGnn, such as LOG01, LOG02, */
LOG3 = 'LOG'batchjob
CMDFILE = USERID'.TSC.CMD'
CMDFILEP = USERID'.TSC.CMDP'
/* get file name and assign env variable' */
pg. = ' '
Parse var fileNames pg.1 pg.2 pg.3 pg.4 pg.5
 noFile = 5
 listinx  = ' '
 ProgNames = ' '
 Do i = 1 to noFile
   if pg.i /= ' ' Then Do
    listinx = 'PBB_'i'='pg.i
    ProgNames = ProgNames' 'listinx
   End
 End
Address Tso
x = MSG('OFF')
Address Tso
 "FREE DD(RCCPROC RCCPARMS RCCMAP STDOUT STDERR RCCLOG EDCENV )"
 "FREE DD(SYSUDUMP)"
x = MSG('ON')
"ALLOC FI(RCCPROC)  DA('"USERID".TSC.JCLP')      SHR "
"ALLOC FI(RCCPARMS) DA('"USERID".TSC.CMDP(CCCMDP)') SHR "
"ALLOC FI(RCCRC) DA('"USERID".TSC.CMDP(OUTRCP)') SHR "
"ALLOC FI(RCCMAP)   DA('"USERID".TSC.JCLP("mapParm")')   SHR "
"ALLOC FI(STDOUT)   SYSOUT(A)                         "
"ALLOC FI(STDERR)   SYSOUT(A)                         "
"ALLOC FI(RCCLOG)   DUMMY                             "
"Call '"HLQ".TSCLOAD(RCCTSOC)' '"ProgNames" > ''"USERID".PBB."LOG3"''' asis"

Address Tso
x = MSG('OFF')
 "FREE DD(RCCPROC RCCPARMS RCCMAP STDOUT STDERR RCCLOG EDCENV )"
 "FREE DD(SYSUDUMP CEEDUMP )"
x = MSG('ON')
return;

About this task

The pbb parameterized build request compiles and links a COBOL source program. Your ClearCase® administrator can modify the parameterized build scripts to make build available for any language file your site supports. The pbb command is not valid for view private files.

Procedure

To submit a pbb request, do these steps.
  1. On the option line of the TSO Client Main Menu, type 4.
  2. On the left side of the Dataset Action panel, under DSLIST, type s beside one or more of the data sets in the list to select a data set.
  3. On the left side of the View File List panel, under the ClearCase file name, do one of the following actions:
    • Type pbb next to the file name. The build request is submitted.
    • Type s next to the file name and press Enter. The File Actions panel displays. Type pbb on the option line, press Enter, and press PF3 END to return to the View File List panel. The build request is submitted.
    You will be notified when the batch job is completed. The details of step by step build processing are recorded in a log file located in USERID.PBB.LOGnn, a separate log file used only for the batch parameterized build.

Results

Assuming that the sample build script is modified as shown below, the output listing file is saved to a preallocated PDS named USERID.TSC.LIST(PBTEST1).

//SYSPRINT DD DSN=$mfid.TSC.LIST($mem),DISP=SHR
You can view the output listing from panel 4 if a profile mapping statement has been specified. The output object file is located in PDS USERID.XOBJLIB on the z/OS system. The output link control file is located in PDS USERID.XLOADLIB on the z/OS system. The BCL scripts generated by the build process are located under /VOB/userid directory, where VOB is the path of the VOB and userid is your TSO user ID. The following BCLs are generated and send to the mainframe to execute the build request during the compilation. In these file names, sourcefile is the name of the file for which the parameterized build command is issued, such as s1alloc_pbtest1.bcl.
s1delete.jcl
Deletes the temporary PDS.
s1alloc_sourceFile.jcl
Allocates a PDS and uploads the COBOL source from ClearCase.
compile_sourceFile.jcl
Compiles COBOL program.
devprint_sourceFile.jcl
Generates the link load file used for link edit.
lnkbatch_sourceFile.jcl
Performs the link edit.
The following output files generated by the build process are located in the VOB directory.
userid_sourceFile_compile.log
The log file for compiling. In this file name, yourfile.cbl is the name of the file for which you submitted the Compile request.
userid_sourceFile_rccbuild.log
The remote build log file.
Assuming USER1 is the TSO login ID used to form the PDS name, the following are the files uploaded to the host and the output files generated after a successful build. The name of the PDS for the output load module is specified in the variable $loadlib defined by the attribute ZCCENV.
USER1.SOURCE(YOURFILE)
The COBOL source program.
USER1.XOBJLIB(YOURFILE)
The output object file, where YOURFILE is the name of the source file submitted for compile.
USER1.XLOADLIB(YOURFILE)
The output link control file, where YOURFILE is the name of the source file submitted for compile.
USER1.CA.PARMBLD.LOAD(YOURFILE)
The output load module, where YOURFILE is the name of the source file submitted for compile.

An error message is issued under the following conditions:

  • The file selected is not on a Windows® platform.
  • The PARMBUILD_SCRIPTS environment variable is not specified in the profile.
  • The file selected is a view private file.