Starting the batch container manually

This task contains the steps that are required to start a batch container manually from the console.

Before you begin

You need to ensure that you have sufficient access privileges to run the CBCH transaction. For more information on CICS® security, see Security for CICS-supplied transactions, or contact your System Administrator

About this task

These commands must be run from a CICS 3270 terminal.

Procedure

  1. Run transaction CBCH. The transaction completes with message: Batch container initiated. Check JVM logs for startup progress
    Note: If you are not running CBCH in the default JVM server, you must start the CBCH transaction with the JVMSever name as a parameter. For example, CBCH MYJVMSRV.
  2. The CBCH transaction links to a program in the JVM server. The program loads the batch container configuration file, initializes the environment, and registers with the Job Scheduler. A scheduled task periodically publishes available job steps to the Job Scheduler.

Results

Results can be seen by looking in the batch container log files on zFS.

Example

On calling CBCH:
CBCH CICSUSER <DATE/TIME> <JVMSERVER> Batch Container initiation requested
When startup has successfully completed:
CBCH CICSUSER <DATE/TIME> <JVMSERVER> DFHBATJS Batch Container initiation completed
When the batch container is stopped with the CBCS transaction:
CBCH CICSUSER <DATE/TIME> <JVMSERVER> Batch Container stopped
When CBCH is running but the JVM server is disabled or unavailable:
CBCH CICSUSER <DATE/TIME> <JVMSERVER> Batch Container waiting for JVM server
When CBCH is running but the DB2Connection is not connected:
CBCH CICSUSER <DATE/TIME> <JVMSERVER> DFHBATJS Batch Container waiting for DB2

If you have specified a logging detail level of "INFO" or greater in the batch container configuration file, then other messages are also written to the batch container logs: For example:

When the batch container has started successfully:
<DATE/TIME> INFO com.ibm.cics.batch.impl.BatchStartup <init> Batch Container Successfully Initiated
When the batch container is stopped with the CBCS transaction:
<DATE/TIME> 530 INFO com.ibm.cics.batch.impl.BatchStartup main Batch Container Stopping

In addition log messages are written to the WebSphere® Application Server SystemOut.log, for example

When the batch container registers with the Job Scheduler:
Compute Grid Portable Endpoint: 
<CICSHOST>/<CICSAPPLID> registered successfully!


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