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
About this task
Procedure
Results
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!