Interactive versus batch processing

Objects can be processed quickly and efficiently either interactively or in batch mode.

The interactive method makes use of the convenience of the online interface. The batch method is more powerful and often faster. Extremely large object sets (those containing more than a few hundred objects) should always be processed in batch mode.

Related topics

Generating-batch-recovery-JCL-interactively

Generating-a-backup-job-in-batch

Generating-recovery-JCL-in-batch

Key-concepts

Interactive versus batch object set creation

You can create application object sets either interactively or in batch mode. For performance reasons, you should create object sets that will contain extremely large numbers of objects in batch mode.

For information about creating object sets interactively, see Creating-and-working-with-object-sets. For information about building application object sets in batch mode, see ARMBGRP—Object set creation and maintenance.

Interactive versus batch revalidation of recoverability

You can revalidate the recoverability of object sets one at a time using the online interface.

You can revalidate the recoverability of many object sets concurrently when you use batch revalidation. For performance reasons, you should revalidate extremely large object sets (those containing more than a few hundred objects) in batch mode.

For information about revalidating the recoverability of an object set interactively, see Object-set-recovery-revalidation-and-reporting. For information about batch revalidation, see ARMBGPV—Object set recovery revalidation.

Interactive versus batch JCL generation

You can generate backup or recovery JCL using the online interface.

You can specify recovery points, and recovery options at the object set level, revalidate the recoverability of an object set, and specify such things as alternate recovery points for individual objects when necessary in a single TSO session. Apart from providing a job statement for the generated backup or recovery job, you are not required to code any JCL.

You can also use the TSO session to generate backup and recovery JCL in batch mode, although you can also completely avoid using a TSO session if you code your own JCL and use the ARMBGEN program to generate the backup and recovery jobs. In addition to releasing the BMC AMI Recovery Manager online interface for other work, ARMBGEN provides better automation for point-in-time recovery following an application failure and more automation for disaster recovery preparation.

Important

You can set object set backup and recovery options that will remain in effect only for the duration of the JCL generation by using the UPDATE option of the ARMBGEN program. You can permanently change object set backup or recovery options prior to JCL generation by using the ARMBGRP program.

 

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