+

Search Tips   |   Advanced Search

COBOL container for batch troubleshooting

If we 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:

When activated, the trace prints the following line to the job log after each COBOL invocation:

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


Common errors

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 we encounter
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 WAS 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 WAS 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 WAS SR user ID.


Related concepts

  • COBOL container overview


    Related tasks

  • Develop COBOL container batch applications
  • Create a COBOL call stub Java class
  • Compiling COBOL call stub Java classes
  • Generating COBOL call stubs

  • COBOL call stub Java class usage example
  • COBOL RETURNING, RETURN-CODE, getReturnValue, and getReturnCode parameters