Sample output from a job built in batch is shown in this
topic.
Refer to the following figure:
Figure 1. Sample output from batch build: Part 1
//TUSERAA JOB TUSER,CLASS=A,NOTIFY=&SYSUID,REGION=0M
//*
//*
//*
//*
//** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//* *
//* Job Generated by IBM Db2 Automation Expert V1R1.01 *
//* *
//* Db2 SSID: SS2 *
//* SQLID: *
//* Profile: TUSER.##V11 TEST *
//* Desc: *
//* User: TUSER *
//* Date: Wednesday, October 23, 2023 *
//* Time: 19:58:59.74 *
//* *
//** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//* *
//** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//* *
//* Step: DAJ @BULD *
//* *
//* Desc: This job will generate the JCL for jobs profile *
//* TUSER.##V11 TEST in a batch mode. *
//* The generated job will be placed in dataset *
//* TUSER.DAJ.TEST(BTCHOUT). *
//* *
//* Return Codes: *
//* *
//* (00) - Job was built successfully with no warnings or errors *
//* *
//* (04) - Job was built with warning messages and the Build Job on *
//* Errors indicator was a "Y" or "W" *
//* *
//* (06) - Job was not built - Exception processing did not flag *
//* any objects to process. *
//* *
//* (08) - Job was built with error messages and the Build Job on *
//* Errors indicator was a "Y" *
//* *
//* (12) - Job was not built - Errors were detected and the Build Job *
//* on Errors indicator was not a "Y" *
//* *
//* Note: Build Job on Errors is an option in the Jobs Profile *
//* Options screen. This option has the following values: *
//* "Yes" - Build job on Errors or Warnings *
//* "No" - Do not build job on Errors or Warnings *
//* "Warnings" - Build job only if highest severity is a *
//* warning message. *
//* *
//** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//* Create temp dataset to bypass enqueue failure in ISPF *
//** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//PROFILE EXEC PGM=IEFBR14
//TEMP DD DSN=&&TEMP,DISP=(NEW,PASS,DELETE),
// UNIT=SYSDA,SPACE=(TRK,(1,1,5)),
// DCB=ISP.SISPTENU
//*
.
.
// Processing DDs
.
.
Figure 2. Sample output from batch build: Part 2
//DAJ #DATA DD *
GENERATE_UTILITY_JOB ( -
DB2 _SUBSYSTEM SS2 -
USER_INDICATOR DAJ -
PROFILE_NAME '##V11 TEST' -
PROFILE_CREATOR TUSER -
EXECUTION_LIB_2 DAJ .WRK0110.LOADLIB -
EXECUTION_LIB_3 FEC.WRK0130.LOADLIB -
EXECUTION_LIB_4 FEC.MNT0130.LOADLIB -
GEN_TO_DATASET TUSER.DAJ.TEST -
DEBUG_MODE OFF -
GEN_TO_MEMBER BTCHOUT -
JOB_CARD_1_1 '//JOBCARD JOB TUSER,CLASS=A,NOTIFY=&SYSU' -
JOB_CARD_1_2 'ID' -
JOB_CARD_2_1 '//*' -
JOB_CARD_3_1 '//*' -
JOB_CARD_4_1 '//*' -
)
//*
**************************** Bottom of Data ****************************
The DAJ #DATA DD contains control cards that are input to the build. The control cards describe the Db2 subsystem, profile source, job cards and member name to be used for output. The DEBUG_MODE parameter is automatically set to OFF. This parameter is used for troubleshooting, and should be changed only upon instruction from IBM® Software Support .