VERIFY subcommand syntax options

You can repeat the VERIFY subcommand within the same MODIFY statement. However, you cannot mix it with DELETE, INSERT, or UPDATE subcommands in the same MODIFY statement.

The following figure shows the VERIFY subcommand syntax options. 

Related topics

MODIFY-command

Overview-of-BMC-AMI-Copy-commands

VERIFY subcommand syntax diagram

GUID-01EBD7AB-3B4E-46A0-8115-4DE57FC66234-low.png

Use VERIFY to:

  • Detect when image copies in SYSCOPY or BMCXCOPY are not in the ICF catalog and (if not in the catalog) either delete the entry or issue a warning message
  • Verify the recoverability of the specified table or index space and (if the space is unrecoverable) either issue a warning message or make a copy of the space
  • Verify that there is a minimum number of copies registered in SYSCOPY or BMCXCOPY, and if not, either issue a warning or make a copy of the space
  • Verify that the elapsed time since the last copy was made is not greater than a specified number of days, and if it is greater, either issue a warning or make a copy of the space
  • Verify the number of log data sets made since the last copy was made is not greater than a specified number, and if it is greater, either issue a warning or make a copy of the space

These analyses can be performed for the local site, the recovery site, or both.

Important

The VERIFY function places unrecoverable objects in COPY-pending status when you specify ON NOTRECOVERABLE WARN (the default) unless you specify the NOCOPYPEND option.

VERIFY subcommand options 

Option

Description

MINIMUM COPIES integer

Use MINIMUM COPIES to verify that there is a minimum number of copies of any type registered in SYSCOPY or BMCXCOPY.

  • Use MINIMUM COPIES 0, the default, to specify no verification.
  • Use MINIMUM COPIES integer where integer is in the range of 1 through 65535 to verify that at least integer copies of any type are registered in SYSCOPY or BMCXCOPY.

The minimum number of copies of any type is satisfied by counting primary copies for the site type being analyzed. MODIFY counts any copy, even if there is an unrecoverable event between that copy and the current time.

If verification of MINIMUM COPIES fails, you can make a copy of the space.

MINIMUM FULLCOPIES integer

Use MINIMUM FULLCOPIES to verify that there is a minimum number of full copies registered in SYSCOPY or BMCXCOPY.

  • Use MINIMUM FULLCOPIES 0, the default, to specify no verification.
  • Use MINIMUM FULLCOPIES integer to verify that at least integer full copies are registered in SYSCOPY or BMCXCOPY where integer is in the range of 1 through 65535.

The minimum number of full copies is satisfied by counting primary full copies for the site type being analyzed. MODIFY counts a full copy, even if there is an unrecoverable event between that copy and the current time.

If verification of MINIMUM FULLCOPIES fails, you can make a full copy of the space.

MAXIMUM DAYS integer

Use MAXIMUM DAYS to verify that no more than a specified number of days have elapsed since the last image copy was made.

  • Use MAXIMUM DAYS 0, the default, to specify no verification.
  • Use MAXIMUM DAYS integer to specify a finite number of days. The valid range for integer is 1 through 65535.

If verification of MAXIMUM DAYS fails, you can make a copy of the space.

Important

SYSLGRNX YES (see SYSLGRNX) can be used in conjunction with MAXIMUM DAYS, so the condition triggers if more than the specified number of days have elapsed since the last image copy and the object has been updated since that copy was made.

MAXIMUM LOGS integer

Use MAXIMUM LOGS to verify that not more than a specified number of log data sets were created since the last image copy.

Important

For data sharing, all subsystems are checked, and the condition is true if any subsystem has more than the specified number of logs.

  • Use MAXIMUM LOGS 0, the default, to specify no verification.
  • Use MAXIMUM LOGS integer to specify a finite number of logs. The valid range for integer is 1 through 65535.

If verification of MAXIMUM LOGS fails, you can make a copy of the space.

Important

SYSLGRNX YES (see SYSLGRNX) can be used in conjunction with MAXIMUM LOGS so that this condition triggers if more than the specified number of log data sets were created and the object has been updated since that copy was made. The count of logs begins with the log containing the first update (log range) after the copy was made.

NOCOPYPEND

Specify NOCOPYPEND to indicate that you do not want to have COPY-pending status set if a space is not recoverable.

When you use the NOCOPYPEND option with a version of Db2 that has a versioning feature, old version numbers will not be freed. If you need to reuse the version numbers, you will have to run the MODIFY command without the NOCOPYPEND option.

Important

The VERIFY function places unrecoverable objects in COPY-pending status when you specify ON NOTRECOVERABLE WARN (the default) unless you specify the NOCOPYPEND option.

Warning

Use this option with care. A space that normally would be placed in COPY-pending status is left with its status unchanged.

OFFSITE

Use the OFFSITE option to specify what ICBACKUP type to use as offsite copies. VERIFY analysis for the recovery site uses only the copy type specified by OFFSITE.

Values of OFFSITE

Value

Description

OFFSITE LB

OFFSITE LB specifies the local site backup copy for use in VERIFY analysis.

OFFSITE RP

(Default) OFFSITE RP specifies the recovery site's primary copy for use in VERIFY analysis.

ON DSNOTFOUND

Use ON DSNOTFOUND to tell MODIFY what action to take when a cataloged image copy in SYSCOPY or BMCXCOPY is not found in the ICF catalog.

Values of ON DSNOTFOUND

Value

Description

ON DSNOTFOUND WARN

(Default) Use WARN to issue a warning message and return code 4.

ON DSNOTFOUND DELETE

Use DELETE to delete the SYSCOPY or BMCXCOPY row.

ON NOTRECOVERABLE

Use ON NOTRECOVERABLE to specify that MODIFY is to verify the recoverability (to current) of the space. ON NOTRECOVERABLE can also be used to specify the action to take when an unrecoverable space is found or to specify the action to take when MINIMUM COPIES, MAXIMUM DAYS, or MAXIMUM LOGS specifications are not met.


Values of ON NOTRECOVERABLE

Value

Description

ON NOTRECOVERABLE WARN

(Default) Use WARN to issue a warning and return code 4.

ON NOTRECOVERABLE COPY

Use COPY to create an image copy of the space.

You can specify the name of a copy template after the keywords USING TEMPLATE.

Important

You must specify ON NOTRECOVERABLE COPY if MODIFY is to conditionally invoke BMC AMI Copy to make an image copy.

SITETYPE

Optionally use SITETYPE to specify the site type for the recoverability analysis.


Values of SITETYPE

Value

Description

SITETYPE LOCAL

Use SITETYPE LOCAL to limit analysis to the local site.

SITETYPE RECOVERY

Use SITETYPE RECOVERY to limit analysis to the recovery site.

SITETYPE BOTH

Use SITETYPE BOTH to perform analysis for both local and recovery sites.

SITETYPE zParmsSiteType

(Default) zParmsSiteType is the current Db2 designation of site type in the ZPARMS.

SYSLGRNX

Use SYSLGRNX to indicate whether or not an analysis of the log ranges should be considered when MAXIMUM DAYS or MAXIMUM LOGS or both are specified.


Values of SYSLGRNX

Value

Description

SYSLGRNX NO

(Default) SYSLGRNX NO specifies that no log range information is accessed or analyzed.

SYSLGRNX YES

SYSLGRNX YES specifies that the MODIFY VERIFY command will analyze the log ranges because the last copy to determine if the object has been updated. If no updates have been made since the last copy, neither MAXIMUM DAYS nor MAXIMUM LOGS will trigger regardless of the limits specified.

USING TEMPLATE

Use USING TEMPLATE to specify the name of a copy template to be used when you specify ON NOTRECOVERABLE COPY and an unrecoverable space or out-of-user-defined-limits condition are found by MODIFY. The default is TEMPLATE DEFAULT.

Important

The keyword TEMPLATE is optional and might be omitted from the specification.

The following rules apply when you use USING TEMPLATE:

  • Omit USING TEMPLATE when you want to use the default copy template.

  • Use USING TEMPLATE name when you want to name a template other than the default. The name variable is an eight-character name.

    USING TEMPLATE name requires a TEMPLATE command in SYSIN to provide the syntax for BMC AMI Copy to make the copy. The copy is scheduled after the completion of any other work indicated in SYSIN. For more information, see TEMPLATE-command.

    Important

    You must use the TEMPLATE command (see TEMPLATE-command) to specify either TEMPLATE name or TEMPLATE DEFAULT when you specify ON NOTRECOVERABLE COPY.

 

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