Troubleshooting and support

About this task

This problem determination information is specific to running the Modern Batch feature pack in CICS®.

Procedure

  1. Check the following on z/OS®:
    • The CICS resources in CSD group DFHBATCH are enabled.
    • The CICS job log does not contain error messages.
    • There are no error messages in the files <WORK_DIR>*.dfhjvmerr and <WORK_DIR>*.dfhjvmout.
    • If dfhjvmerr shows a Java™ exception with the message SQLCODE = -923, SQLSTATE = 57015 error tokens = ACCESS;00E30301;00000800;DSNJCC, ensure that your DB2® system is installed and customized to allow connections from the IBM® Data Server Driver for JDBC 4.
    • There are no error messages in the JVM system.err or system.out logs. By default, these logs are in files <WORK_DIR>*.dfhjvmerr and <WORK_DIR>*.dfhjvmout, where <WORK_DIR> is the location on zFS defined in the JVM profile.
    • The batch container configuration file is correct. By default, the configuration file is in <JVMPROFILEDIR>/batchcontainer-config.xml, where JVMPROFILEDIR is the location that is specified in the CICS region SIT parameter. Note: The JVM profile property -Dcom.ibm.cics.batch.config overrides the default definition.
    • The CICS system and the Job scheduler system can communicate with each other using HTTP.
  2. Check the following using a web browser:
    • The job output, which is available in the Job Management Console.
    • The WebSphere® Application Server Network Deployment System.out and System.err files do not contain errors.

    You can view these files from the Integrated Solutions Console. Click: Servers > Server Types > WebSphere application servers > your server > Logging and tracing > JVM Logs > Runtime > View.

What to do next

To aid troubleshooting, you can enable trace for the batch container by changing the logging level that is set in the batch containers configuration file. The most detailed trace level is ALL. A change in trace level is picked up during the next batch heartbeat, which is up to 30 seconds after the configuration file is updated.

If you raise a problem with IBM support, use the information in the IBM Support Portal to make sure that you have collected all the required diagnostic information.



troubleshooting.html | Timestamp icon Last updated: Sunday, 4 June 2017