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.

Debug trace

To enable tracing of the COBOL container code, add the following to the Java™ trace specification:
com.ibm.ws.batch.ilc.*=all
com.ibm.websphere.batch.ilc.*=all

Performance trace

To monitor performance of COBOL container invocations, activate the following Java trace specification:
com.ibm.ws.batch.ilc.impl.LEChildEnvironment.invokeProcedure=all
When activated, the trace prints the following line to the job log after each COBOL invocation:
Returned from procedure {name}, duration=1335875 ns, rc=0

The reported duration includes the execution time of the COBOL procedure and of the surrounding container code.

Common errors

Table 1. Common errors and suggested solutions when running the COBOL container. This table lists common errors encountered while running the COBOL container, along with suggested solutions. If you encounter a listed error, try the suggested solution.
Error Suggested solution
com.ibm.websphere.batch.ilc.ILContainerException: mkfifo failed with rc=-1 Ensure that the ${GRID_JOBLOG_ROOT}/joblogs directory exists and is writeable by the WebSphere® Application Server SR user ID.
com.ibm.websphere.batch.ilc.ILContainerException: LEChildEnvironment.create failed (CEEPIPI function:0x5A rc:0x0000006F rsn:0x5B400002) Ensure that PIPIENV is on the LIBPATH (server_region_libpath) and is executable by the WebSphere Application Server SR user ID.
java.lang.UnsatisfiedLinkError: LECENV (Not found in java.library.path) Ensure that libLECENV.so is on the LIBPATH (server_region_libpath) and is executable by the WebSphere Application Server SR user ID.

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: March 5, 2017 17:54
File name: rgrid_cobol_container_troubleshooting.html