Submitting the COBOL build request
About this task
rccbuild -h servername@portno -b cobcomp -ft cobcomp.jcl -k IBM-850 -r IBM-037 -it
banner.cbl -dt banner.led -v MBR=BANNER cobcomp=cobol__lib LERUN=langevn_lib
HLQ=hlqname -V -V -V
The –v option
in the sample rccbuild command supplies values
for user-defined variables that are declared in the build script cobcomp.jcl.
The variables are highlighted in the following example. //COBC EXEC PGM=IGYCRCTL
...
//SYSLIN DD DISP=SHR,DSN=&HLQ..&SYSTEM..OBJ(&MBR)
...
//LKED EXEC PGM=IEWL,COND=(5,LT,COBC),REGION=4096K
...
//SYSLIB DD DISP=SHR,DSN=&COBCOMP
// DD DISP=SHR,DSN=&LERUN
//OBJLIB DD DISP=SHR,DSN=&HLQ..&SYSTEM..OBJ(&MBR)
...
//SYSLMOD DD DISP=SHR,DSN=&HLQ..&SYSTEM..LOAD(&MBR)
...
Procedure
To submit a build request for the sample COBOL files,
do these steps:
- Edit the rccbuild command in cobcomp.bat.
- To run the batch file on the client, do these steps
Results
The build server returns two output files whose names are
derived from information in the COBCOMP BCL:
- COBC.SYSPRINT contains COBOL compiler messages. COBC is the step name on the EXEC statement that calls the COBOL compiler.
- LKED.SYSPRINT contains Linkage Editor messages. LKED is the step name on the EXEC statement that calls the Linkage Editor.
These files are returned to the client because COBCOMP BCL also has SYSPRINT DD statements that include the extension parameter RCCEXT=RCCOUT.