Skip to Content

Batch job deployment architecture and workflow

You can redirect batch job SQL requests to a remote DB2 subsystem, redirect IMS DL/I calls issued by batch jobs to a remote IMS subsystem, or perform the job steps on the remote LPAR where the subsystem resides.

The following example describes the process for DB2 batch job requests and requires a license for Subzero for DB2. The process for IMS batch job requests is similar, but requires a license for Subzero for IMS.

  1. You use the APPLICATION RESTART CONTROL for DB2 (AR/CTL) product to define that you want to redirect the SQL requests to a DB2 subsystem on a remote LPAR or alternatively perform the job on the remote LPAR in order to reduce latency.
  2. AR/CTL calls Subzero.
  3. According to the action that you selected in AR/CTL, Subzero takes one of the following actions:
    • Redirects the SQL requests to the remote DB2 subsystem
    • Calls MainView Batch Optimizer–Advanced, which performs the job steps consecutively on the remote LPAR

This deployment uses capabilities that APPLICATION RESTART CONTROL for DB2 and MainView Batch Optimizer provide. For more information, see Setting-up-IMS-or-DB2-batch-job-redirection.

 

GUID-59B80A61-F6B6-4D7F-8617-501CF679E0E5-low.png 

 

 

GUID-A0360CBC-A1FA-489A-8D3D-EB1B7101CE13-low.png 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Subsystem Optimizer 3.0