Setting up checkpoint pacing
AR/CTL can pace checkpoints for an application program--allow checkpoint processing to occur or return control to the application program without performing checkpoint processing, depending on whether the checkpoint meets the checkpoint conditions you have defined. Checkpoint pacing is defined and performed externally to the application program. AR/CTL makes the pacing decision dynamically, based on real-time factors such as the characteristics of the program execution, the number of calls, and the time between checkpoints. Checkpoint pacing criteria can change dynamically while the program is executing.
Checkpoint pacing allows the application program to issue checkpoints each time the program reaches a logical point during processing, without concern for operational issues such as checkpoint overhead.
To invoke checkpoint pacing during application program execution, change (or verify) the values in the most specific processing option record that applies to the job step. Set the Use Checkpoint Pacing option to Y and set the Pacing Class Name option to the name of the pacing class record you will create. Then create a checkpoint pacing record, which contains pacing options to define the pacing conditions to use.
To create a checkpoint pacing record
Note
For details about this task, see Reference.
- Access the BMC AMI APPLICATION RESTART CONTROL primary menu, and select option 3 (Checkpoint pacing options).
- On the List Records panel, enter the ADD command.
- On the Add Record panel, enter the name of the pacing class you want to define.
- For each option field on the Pacing Class Options panel, type the values you want to use. Field-level help with ? is not available on these panels.
- Press Enter to validate the information. To continue to the next page, enter the
DOWNcommand. Enter the END command to save the record and exit from the panel.
Related topic
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.