Java Batch ILC sample

About this task

The following key phrases are associated with this sample: java batch, pojo, plain old java object, ilc, cobol, parallel, pjm, parallel job manager

Procedure

Setting up your environment

1. Start the appropriate application servers and any supporting management processes.
2. Configure your job scheduler. For instructions on performing this task, see the "Configuring the job scheduler" article in the WebSphere Application Server Information Center
.

Note:If you have already performed this step in your environment, this step can be skipped

Installing the ILC sample

1. In the administrative console, click Applications > New application > New Enterprise Application.
2. Specify the full path of the sample.

   For example:

   <unzipped_sample_dir>/installableApps/ILCSample.ear

3. Complete the steps using the wizard.
   1. Select Detailed - Show all installation options and parameters.
   2. Expand the list for Choose to generate default bindings and mappings. Select Generate Default Bindings, and click Next.
   3. In Step 2, select the endpoint server or cluster.
   4. Accept the defaults for the rest of the values.
   5. Click Finish.
4. If you plan to install additional sample applications, do so now.
5. Restart the application server or start the application.

   If this time is the first time that you are installing an application, restart the server. Otherwise, you can start the application when you navigate to the Applications > Application Types > WebSphere enterprise applications panel.

Build the Cobol modules

1. Extract the cobol modules from the application jar file. The cobol files are located under the cobol/ dir. All the cobol files along with the makefile are in ebcdic.
2. Ensure the cobol compiler is referenced in the STEPLIB and cob2 is available on your PATH
3. Run the make file
4. Ensure the resulting COBOL DLLs are in a location on the SR's LIBPATH (server_region_libpath)

For reference, the following list maps which batch steps require which cobol modules:

1. ILCEmpProcessor requires COBEMP.
2. ILCDataTypes requires PRIMITVE, NATLTEST, HELLO1, HELLO2, SIMPLE.
3. ILCHoldableCursorBDS requires HOLDCURS (see Building HOLDCURS).

Additional preparation

1. If using ILCSampletxt2txtxJCL, copy sample input file (provided in app) to /tmp/input-emp.txt.
2. If using ILCSamplejdbc2jdbcxJCL:
1. Create ILCEMP table in DB2 (see CreateILCSampleTablesDB2zOS).
2. Create the JDBC datasource (see "Creating JDBC Datasource").
3. If using ILCSamplecurs2cursxJCL:
1. Create ILCEMP table in DB2 (see CreateILCSampleTablesDB2zOS).
2. Create the JDBC datasource (see "Creating JDBC Datasource").
3. Build HOLDCURS (see "Building HOLDCURS").
4. If using ILCSampleDataTypesxJCL.xml, no further config required.

Running the ILC sample

Save config, restart the appserver, and submit the xJCL.

Building HOLDCURS

1. Extract the cobol files from the app jar. The cobol files are located under the cobol/ dir. All the cobol files along with the makefile and MAKEHC JCL are in ebcdic.
2. Copy HOLDCURS.cbl and ILCEMP.cpy to a dataset.
3. Customize MAKEHC JCL to fit your system.
1. Adjust dataset locations for COBOL compiler, DB2 binaries, etc.
2. Define output datasets for object files and DBRMs.
3. Specify dataset containing HOLDCURS and ILCEMP.
4. Submit MAKEHC.
   
   MAKEHC has 3 steps:
   1. compile cobol. Creates HOLDCURS obj file, DBRM for SQL statements.
   2. linkedit cobol
   3. binds the DBRM to a DB2 package.
5. Copy the resulting DLL (HOLDCURS) to the SR's LIBPATH (server_region_libpath). Ensure that the DLL is executable by the SR.
6. Grant the servantID EXECUTE authority on the DB2 package. See GrantILCSampleDBRMPackageDB2zOS.

NOTE: If binding into a package other than NULLID, then you may have to add the package name to the pkList property of the JDBC datasource.

Creating JDBC Datasource

1. Create datasource for ILC EMP table, using jndi-name of: jdbc/ilcds
2. Disable connection pooling and sharing
1. Data sources --> {select data source} --> Cusom properties -> Add/set property: disableWASConnectionPooling=true
2. Data sources --> {select data source} --> Connection pool properties --> Connection pool custom properties --> Add/set property: globalConnectionTypeOverride=unshared

Other files

1. CreateILCSampleTablesDB2zOS: DDL for creating and populating ILC EMP table in DB2
2. GrantILCSampleDBRMPackageDB2zOS: SQL for granting EXECUTE priv on DB2 package.
3. input-emp.txt: sample input file contains EMP data.
4. csg.xml: for use with RAD/CSG, for generating the cobol call stubs.
5. csg.properties: for use with CSG.
6. pgcbatchpackager.sh: for use with pgcbatchpackager.jar, for packaging the app