Skip to Content

Pacing Interval between Checkpoints — Checkpoint elapsed time

Use this option to control whether 

AR/CTL

 uses the time between checkpoints for determining the pacing interval between checkpoints.

If you want to control pacing by checkpoint time, you must define the minimum amount of time required between checkpoints. When the application program issues a checkpoint call, AR/CTL allows checkpoint processing to occur only if the elapsed time since the last actual checkpoint is greater than the value of this option.

You may want to set a low checkpoint elapsed time (30 to 60 seconds) for periods of online activity. During batch processing, you can increase the elapsed time to several minutes if online access to the data is not an issue.

Panel field

Pacing Interval between Checkpoints—Checkpoint elapsed time

Values

Set one of the following values:

N

Do not use the checkpoint elapsed time for determining the pacing interval between checkpoints.

mmmm:ss.th

Use the checkpoint elapsed time for determining the pacing interval between Checkpoints. Starting with the time that 

AR/CTL

 last allowed checkpoint processing to occur, this number of minutes (0 through 1440), seconds (0 through 59), and hundredths of a second (0 through 99) must elapse before 

AR/CTL

 allows checkpoint processing to occur. A value of 0000:00.00 causes 

AR/CTL

 to allow checkpoint processing for every checkpoint call if the Pacing Interval between Checkpoints—Condition option is set to ANY.

Default

N


Related topic

Using-the-Checkpoint-Pacing-Class-Options-panel


 

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

BMC AMI Application Restart Control for Db2, IMS and VSAM 4.2