Skip to content

Invoking the Batch Execution Panel

From the Library Consolidation, Source/Copy Synchronization, or Equivalent JCL Comparison menus, select option 4 (BATCH JOB) to display the Batch Execution panel. The Batch Execution panel, shown below, appears.

SERBATCH ---------------------- BATCH EXECUTION ------------------------------

Enter "/" to select options
       _ Status Report for all members - no Execute/Export actions

      Execute Options                             Export Options
    _ Skip all members
    _ Execute all members                       _ Export members with equal
    _ Skip executed and Exported members          last modification timestamp
    _ Skip executed and Reconciled members      _ Export Reconciled members with
    / Skip Executed members                       Degree of Complexity None
    _ Skip executed but Equal members           _ Export executed Equal members
    _ Do not execute Single members             _ Export Single members
    _ Produce Merge Report for Executed members _ Export just Executed members

    Job Statements
    ===> //USER83F JOB (X170,374),      ,       <=== CHANGE ACCORDINGLY_____
    ===> // MSGCLASS=9,NOTIFY=USER83,TIME=1     <=== CHANGE ACCORDINGLY_____ 
    ===> /*JOBPARM S=ESA5                       <=== CHANGE ACCORDINGLY_____

Press ENTER to submit; Enter END Command to terminate JOB submission.

...

You can choose any number of Execution and/or Export options, as well as opt for producing a Reconciliation Status reports only.

Execute Options

With any of the Execute options, you can request that a detailed MERGE Report is produced for each member to show the differences between the versions. Each block of changes is surrounded by two blocks of common code lines in a fade-in/fade-out fashion. The MERGE report is written to your PRINT data set specified on the Profile Data Sets panel.

You can filter the version members you want to be compared and merged by entering a forward slash (/) symbol on the option fields.

  • The first option, Skip all members, is used to report on the current status of the consolidation. It only produces detailed and summary reports. The report formats are explained below. Another way to produce only a Status Report is to select that option only which is above the Execute and Export options.

  • The second option, Execute all members, is self-explanatory. Note, though, that previous executions and your reconciliations of the same libraries will be lost. To prevent such a loss, you can select a combination of the remaining 5 options:

    • The Skip executed and Exported members option keeps the exported version members intact (that is, those that you consider completed).

    • The Skip executed and Reconciled members option keeps the reconciled version members intact (including those already exported).

    • The Skip Executed members option is useful when you have started the consolidation of several members online and then decided to execute the rest in batch mode.

    • The Skip executed but Equal members option speeds up the re-execution by ignoring members that are the same in all version libraries. A re-execution may be required because of changes in the comparison parameters—like TEXT Type and/or Comparison resolution.

    • The Do not execute Single members option speeds up the execution by ignoring the members that reside in only one version library (i.e., there are no other versions of them). The downside of this option is that you have to manually copy them from the corresponding version libraries to the export library, if you do not select also the Export Single members option.

Export Options

You can filter the members you want to be exported in batch by entering a forward slash (/) symbol on the option fields.

  • The first option, Export members with equal last modification timestamp, saves a lot of time for comparing and merging essentially equal versions; you can export them in batch while other members are executed.

  • The second option, Export Reconciled members with Degree of Complexity None, allows you to export in batch those member versions that have been completely reconciled; that is, all the conflicts have been resolved and single changes validated.

  • The third option, Export executed Equal members, combines the execution of member versions with their export should they be found to be equal.

  • The fourth option, Export Single members, also saves resources by bypassing the execution and directly exporting the members found in only one of the version libraries. Choosing this option automatically selects the corresponding Do not execute Single members execution option.

  • The fifth option, Export just Executed members, works with the profile export option "Export with Conflicts." If this option is set to YES, then every executed member in the batch job run will be exported regardless of whether or not there are unresolved conflicts. If this option is set to NO, only just executed members with zero or low Complexity of Reconciliation will be exported, that is, members without conflicts.

Job Statements

You have to tailor the default job statements provided by M+R to comply with the requirements in your shop. You need to do this once only.

Should the batch job abend due to space problems, increase the REGION value.

By default, M+R requires that the TIME parameter is included in the batch execution jobdeck. To disable this requirement, M+R has to be installed with &CDFTIME set to NO in the )INIT section of the SEROJECT panel.

STEPLIB

You have to let M+R know the fully qualified name of its load library so that the STEPLIB statement is properly set in the generated JCL.

M+R expects to find its load library name from a specific DDNAME, depending on the way M+R is installed in your site:

  • CDFLLIB DD for M+R as a stand alone product.

  • CMNLLIB DD for M+R as an option of ChangeMan ZMF.

  • CPXLLIB DD for M+R as an option of Comparex.

In case such a DDNAME is not defined but your ISPF is 4.1 or higher, M+R will call the QLIBDEF service to find the current LINKLISTed load libraries list and use it in the STEPLIB statement.

If your ISPF is 3.x or earlier, M+R will try to find the load libraries list of the ISPLLIB DDNAME for the task and use it in the STEPLIB statement.

If the above fails, M+R writes the formatted JCL in your WIS library as a @@CDFJOB member and informs you that you can submit the job after filling in the load library name in STEPLIB statement.