Procedure for modifying the BCDIN JCL

The following list summarizes the BCDIN JCL statements to use for configuring the Batch Runtime options:

1 Specify the option that corresponds to the language of the application.
For example, in PL/I or COBOL:
```
bcd.applicationLanguage=LE
```
For example, in Java™:
```
bcd.applicationLanguage=JAVA
```
2 Specify the program name or fully qualified Java class name of the application, where MYPGMNAM or yourpackagename is the name of the application.
For example, in COBOL:
```
bcd.applicationName=MYPGMNAM
```
For example, in Java:
```
bcd.applicationName=com.xyz.yourpackagename.classname
```
3 Specify the program arguments that you want to pass to the program. Java and COBOL each have there own format.
For Java applications, you can use any number of arguments. Each argument is passed as an element of the initial arguments array passed to the main method. For example:
```
bcd.applicationArgs.1=java arg1
bcd.applicationArgs.2=java arg2
bcd.applicationArgs.3=java arg3
```
For COBOL applications, you can use a single argument with a maximum length of 100 characters. For example:
```
bcd.applicationArgs.1=COBOL single argument up to 100 characters
```
The COBOL single argument... value corresponds to the PARM='string <=100 chars' value of an //EXECPGM EXEC PGM=Cobol_Main,PARM= JCL statement.
4 Specify the name of the support class used to manage the transaction. For example, the following statement for the DB2® JDBC driver should be uncommented from Figure 1.
```
bcd.supportClass.1=com.ibm.db2.jcc.t2zos.T2zosBatchRuntimeSupport
```
5 Specify the verbose mode, using true or false.
If you want diagnostic information, use the following statement:
```
bcd.verbose=true
```
If you do not want verbose mode, use the following:
```
bcd.verbose=false
```