Procedure for modifying the BCDBATCH job

The following JCL procedure summarizes the key statements to modify in the BCDBATCH job (see Figure 1) that invokes z/OS Batch Runtime.

1 Modify the JOB and EXEC statements to add any parameters required by your installation.
For example in the following statement, BCDPROC is the batch container JCL procedure.
```
//BATCH EXEC BCDPROC,REGION=0M
```
For details and options, including the symbolic to override defaults, see Sample BCDPROC to invoke z/OS Batch Runtime.
2 For the STEPLIB statement, specify any load libraries that the application requires (for example, the data set that contains your COBOL application load modules) for DSN=, where hlq.yourapp.loadlib is the name:
```
//*STEPLIB DD DSN=hlq.yourapp.loadlib,DISP=SHR
//  DD DSN=hlq.jzos.loadlib,DISP=SHR
```
This may include requisite DB2® and COBOL libraries that are not in LNKLST but are loaded during program execution. Note that any COBOL modules that are bound as DLLs should usually be found through the LIBPATH environment variable.

The batch container uses the Java™ SDK JZOS launcher utility. If you installed the Java SDK using SMP/E, JZOS is installed in the LNKLST. However, if you did not use SMP/E, you must install the JZOS launcher into a data set, and add that to your STEPLIB concatenation.

For more information about installing JZOS, see the JZOS Java Launcher and Toolkit Overview at www.ibm.com/systems/z/os/zos/tools/java/
3 Update the installation paths for z/OS Batch Runtime. To tailor the runtime environment, use the //STDENV DD statement in the BCDBATCH JCL to define a shell script. The batch container processes the exported BCD_HOME environment variable referenced by the script as the installation path for z/OS Batch Runtime (default is /usr/lpp/bcp).
4 Update the installation path for Java to the correct level of Java:
```
export JAVA_HOME=/usr/lpp/java/J6.0.1
```
5 Run the z/OS Batch Runtime configuration shell script, bcdconfig, to process the exported environment variables you just defined:
```
. $BCD_HOME/bcdconfig.sh
```
To set up the batch container, you must use the . (dot) command to invoke the bcdconfig.sh.
6 Update the JDBC home directory, jar files, and DLLs:
```
JDBC_HOME=/usr/lpp/db2910_jdbc
```

7 Add additional application jar files to the CLASSPATH:

CLASSPATH="$CLASSPATH":/your/extra/app.jar
#CLASSPATH="$CLASSPATH":/your/extra/app2.jar
#export CLASSPATH="$CLASSPATH"

8 Add your application DLLs to the LIBPATH directories:

LIBPATH="$LIBPATH":/your/extra/lib
LIBPATH="$LIBPATH":/your/extra/lib2
export LIBPATH="$LIBPATH"

9 Enable tracing for z/OS Batch Runtime:

IJO="$IJO -Dcom.ibm.zos.batch.container.BCDTraceConfig.trace=all

10 Add any additional JVM options:
```
IJO="-Xms256m -Xmx512m"
```
You may add, for example, the -Xquickstart option or any other -D or -X JVM runtime option you want to use.
11 Add any additional JDBC options for the DB2 subsystem:
```
IJO="$IJO -Ddb2.jcc.ssid=XXXX -Ddb2.jcc.pkList=NULLID.*,COBOLPKG.*"
```
For more information about the Java Database Connectivity (JDBC) options, see DB2 Application Programming Guide and Reference for Java.

Do not specify -Dfile.encoding in the IBM_JAVA_OPTIONS string. z/OS Batch Runtime only supports the default z/OS® file.encoding of IBM-1047.
12 Export the JVM options:
```
export IBM_JAVA_OPTIONS="$IJO "
```
The IBM_JAVA_OPTIONS string must be set and exported before invoking the bcdconifgend.sh script.
13 Run the following z/OS Batch Runtime completion script:
```
. $BCD_HOME/bcdconfigend.sh
```
Note: This script must always be run last in STDENV.