Write checkpoints to IMS log


This option applies only to application programs that use IMS.

It is ignored when you use AR/CTL for Db2 and/or AR/CTL for VSAM without AR/CTL for IMS. If you have AR/CTL for IMS but the IMS region control module (DFSRRC00) is not present, AR/CTL ignores this option.

For application programs that use IMS, you can control whether AR/CTL calls IMS to write the checkpoint (X'18') records to the IMS log after AR/CTL writes the checkpoint records to the checkpoint data set. Writing the records to the log allows IMS to handle the restart if a problem occurs with AR/CTL restart. BMC Software recommends that you choose this action. If an extremely high volume of checkpoints requires you to reduce the size of the IMS log, you can choose not to write the X'18' records to the log.

Warning

Note

Instead of bypassing the logging of checkpoints to IMS, a better approach to reducing the size of the IMS logs is to use checkpoint pacing. For details, see Using-checkpoint-pacing-and-the-current-shift-identifier.

Panel field

Write checkpoints to IMS log

Keyword

LOGTOIMS

Values

Set one of the following values:

Y

Write the checkpoint records to the IMS log after writing them to the restart data set. BMC Software recommends that you use this value in most situations.

N

Write the checkpoint records to the restart data set only. AR/CTL must be used to restart the job (if necessary) because the X'18' records needed by the IMS restart procedure are not on the IMS log.

Default

Y


 

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