Skip to content

Online and Batch Execution Modes

Several ChangeMan ZMF functions offer you a choice between execution online in ISPF or in a batch job:

  • Checkout

  • Stage From Development (including Mass Stage)

  • Stage from the Stage: package Components panel (the "package list")

  • Recompile Source

  • Library Scan

  • Compare

    You choose between O (online) or B (batch) execution by setting Mode field on an ISPF panel, as shown on this Library Scan Utility (CMNSCN01) panel:

CMNSCN01                    Library Scan Utility
Command ===>_______________________________________________________

Package . . . . . . . . . TEST001852
Application . . . . . . . ____      (Blank for list)
Library type . . . . . .  JCL_      (Blank for list)
Scan mode . . . . . . . . 1_        (1-Online, 2-Batch, 3-Alt Batch)
Records to select . . . . 0_        (0 = all)

Enter "/" to select option
  __ List member names only
  __ Scan for dependencies
  __ Case sensitive

From . . . 0 (0=all)                To . . . . . 0 (max=80)
Components to scan:                 (Blank for all components)
Begin . . . ____________________    End . . . . __________________
Data strings:
cobol                                    OR_ (and/or)

In general, batch mode builds JCL and submits a batch job to execute a ChangeMan ZMF process that would otherwise be executed in your ISPF address space. There are two potential advantages to batch mode:

  • Your terminal can be freed as soon as the batch job is submitted, allowing you to perform other ZMF tasks while the batch job executes.

  • Output is available in JES.

These advantages can be illustrated with a Library Scan example:

  • Online Scan - Your terminal is locked while the scan runs in your address space. When the scan is complete, the results are only available on a scrollable ISPF panel.

  • Batch Scan - Your terminal is locked only for as long as it takes for ISPF file tailoring to build JCL for a batch scan job and to submit the job. When the batch scan job is complete, the results are available in SDSF or whatever tool you use to view JES job output.

When you checkout a component, stage a component that is not like-source, or execute the compare component function, the online and batch modes operate like the library scan example.

Online and batch mode work somewhat differently when you stage or recompile a like- source component. These build functions always execute in a batch job. The ISPF file tailoring that creates the build job JCL is always performed outside of your address space in a special started task initiated by the stage or recompile process. The difference between online and batch mode is in the initiation of the file tailoring started task:

  • Online Stage or Recompile - The file tailoring started task is initiated from your ISPF address space.

  • Batch Stage or Recompile - ZMF submits a batch job that initiates the file tailoring started task.


Whether batch mode releases your terminal faster than online mode depends on:

  • Which function is being executed

  • How many components are being processed

  • How your z/OS resources are allocated Sometimes it may take longer to build JCL and submit a batch job than it takes to execute the function in your ISPF address space.