Configuration option names

The following options are read from the //BCDIN JCL file. The name, description, and example of the option are provided.

bcd.applicationLanguage=language

Names the language of the application to be launched, where language is one of the following values:

COBOL: indicates the program is written in COBOL; although this parameter is supported, the LE parameter is recommended
JAVA: indicates the program is written in Java™
LE: indicates the program is written in either COBOL or PL/I.
XJCL: indicates the program is XJCL that is provided by the user; the xJCL is read using the //BCDXJCL DD statement.

Default

None; the statement is required.

Example

bcd.applicationLanguage=JAVA

bcd.applicationName=application-name

Names the fully qualified PL/I, COBOL or Java class program name of the application, where application-name is the name of the application.

For PL/I or COBOL applications, application-name is a 1-8 character module name. The z/OS Batch Runtime uses the typical z/OS® LNKLST/STEPLIB search order for locating the COBOL application.

For Java applications, application-name is the fully qualified class name. The z/OS Batch Runtime uses the CLASSPATH environment variable to locate the main() method of the specified classname.

Default

None

Example

bcd.applicationName=XMPCOBJX

bcd.applicationArgs.n=argument

Names an argument to be passed to the application, where n=argument specifies the suffix number of the argument position.

For Java applications, each argument is passed as an element of the argument array that is passed to the main method.

For PL/I or COBOL applications, you can specify only one argument. The argument can contain a maximum of 100 characters and is passed using the same convention as the PARM= keyword of the // EXEC JCL statement.

Default

None

Example

bcd.applicationArgs.1=java arg1

bcd.supportClass.n=support-class-name

Names a support class to be used with z/OS Batch Runtime, where n=support-class-name specifies a suffix number that indicates the order in which the support class is invoked.

Default

None, but at least one support class is required.

Example

bcd.supportClass.1=com.ibm.db2.jcc.t2zos.T2zosBatchRuntimeSupport

Note: For DB2®, the following support class is provided by the JDBC driver. To use it, you must uncomment the following statement provided in the sample BCDBATCH job.

com.ibm.db2.jcc.t2zos.T2zosBatchRuntimeSupport

bcd.verbose=value

Specifies the verbose mode for the batch runtime, where value is either TRUE or FALSE. z/OS Batch Runtime generates additional diagnostics when you specify TRUE for verbose mode and can affect performance.

Default: FALSE
Example: bcd.verbose=true

bcd.supportPropertiesDDName.n=ddname

References a ddname defining a properties file containing initialization statements for the support class. The properties are in keyword=value format suitable for a Java Properties object.

This statement maps one-to-one with the bcd.supportClass.n statements that define the support class.

In the case of the DB2 JDBC driver, the properties read from this file are the same as those referenced by the info parameter of the DriverManager.getConnection method. Reading the properties from the file is an alternative to specifying them as -D options when invoking Java.

This statement is optional. If not provided for a support class, an initialization file is not read.

bcd.xJCLEncoding=encoding-name

where encoding-name names an encoding to be used when reading the xJCL defined by the /BCDXJCL DD statement. This statement is optional and defaults to the JVM file.encoding value.

bcd.xJCLRestartEnabled=boolean

Specifies whether the xJCL defined job is restartable. When restart is enabled, the Batch Runtime will update its persistence files upon each checkpoint. If the job subsequently abnormally terminates and is in the restartable state, the job can be restarted and will use the state saved since the last checkpoint. The state includes positioning information for each batch data stream.

true: When restart is enabled, the Batch Runtime creates checkpoint files in the file system. By default, the files are created under the user home directory. The directory can be changed using the bcd.xJCLRestartHome option.

false: When restart is not enabled, the job cannot be restarted using the Batch Runtime restart facility if it abnormally terminates.

This statement is optional and defaults to false.

bcd.xJCLRestartHome=path

Names the home directory where restart control files will be placed in the XJCL environment when restart is enabled.

The directory must exist. The files will be deleted when the job terminated successfully.

The default is the working directory for the job as returned by the Java System.getProperty(“user.dir”) method.

bcd.xJCLRestartJobId=jobid

Names a previously failed xJCL defined job to be restarted. The job must be in the restartable state.

When an xJCL job is submitted, the job Id assigned to the job is recorded in message BCD0310I. Use this jobid as the value of the bcd.xJCLRestartJobId statement when restarting the job.