CICS Transaction Server for z/OS Feature Pack for Modern Batch V1.0

The CICS® Modern Batch Feature Pack provides functions that allow batch jobs to run and share resources concurrently with online transactions.

This feature pack processes batch jobs inside a CICS JVM server and enables the jobs to share access to resources with online transactional work, thereby reducing or eliminating the need for a batch window. The feature pack provides a batch container that executes inside the JVM server to start and manage the batch jobs. The batch container is compatible with the WebSphere® Application Server (WAS) batch container and includes a common set of Java™ APIs for developing batch jobs.

CICS batch jobs are scheduled using a Job scheduler in WAS, which can then route the job to CICS over HTTP, where it runs inside the CICS batch container and can access CICS resources via the JCICS API.

The Modern Batch Feature Pack version v1.0 is developed for CICS TS for z/OS®, Version 4.2 or later.

The following diagram illustrates the Modern Batch architecture.
Diagram showing the overall architecture of the Modern Batch feature.

Benefits of a batch container

A batch container provides the following capabilities:
  • Manages the lifecycle of a batch job, as described in the job definition.
  • Records the history of a job’s execution in a job log, including standard stream output from the batch job steps.
  • Collects performance and usage metrics so that you can manage work load management and accounting.
  • Provides a powerful job failover model, based on checkpoint/restart semantics.

Websphere Application Server batch components

The components of a batch application are:
  • Batch job step
  • Batch job controller
  • Checkpoint algorithm
  • Results algorithm

For more information, see Components of a batch application.