If you want to call
a COBOL module from a Java batch plain old Java object (POJO) in the
batch environment, you must first create a COBOL call stub Java class.
You can compile
COBOL call stubs with the marshal.jar and ilcontainer.jar files
on the classpath. The marshal.jar and ilcontainer.jar files
are included with the COBOL call stub generator tool.
Invoke a COBOL call stub Java class.
Invoke
the Java call stub from your batch application. Read the COBOL call
stub Java class usage example topic for more information.
You can dynamically update a COBOL
module without having to restart the application server.
Subtopics:
Creating a COBOL call stub Java class
If you want to call a COBOL module from a Java batch plain old Java object (POJO) in the
batch environment, you must first create a COBOL call stub Java class.
Compiling COBOL call stub Java classes
COBOL call stub Java classes
must be compiled with the marshal.jar and ilcontainer.jar files
on the class path. The marshal.jar and ilcontainer.jar files
are included with the COBOL call stub generator tool.
COBOL call stub Java class usage example
The COBOL call stub Java class
usage example shows how a batch application can invoke a COBOL procedure
using the COBOL container.
COBOL RETURNING, RETURN-CODE, getReturnValue, and getReturnCode parameters
If the COBOL module specifies a RETURNING parameter, it
can be retrieved from the stub using the stub.getReturnValue() method.
The method returns the Java object
representation of the RETURNING parameter, which is the data bindings
class generated by the COBOL call stub generator tool.
COBOL container for batch troubleshooting
If you encounter problems when using COBOL container for
batch troubleshooting, there are a number of options that are available
to you.
Last updated: April 18, 2014 05:01 AM CDT http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=tgrid_cobol_container_developing File name: tgrid_cobol_container_developing.html