Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Copy for Db2 13.1.

MODIFY global options syntax


This section describes the MODIFY global options syntax and description for the MODIFY command.

Warning

Important

See Multiple-commands-in-the-SYSIN-data-set for rules about repeating and mixing DELETE, INSERT, UPDATE, and VERIFY subcommands in MODIFY statements.

MODIFY global options syntax diagram 

GUID-1E9CC8CE-7EE4-40A6-837A-ED16CED09934-low.png

Option

Description

ANALYZE

The ANALYZE option gives you the choice of performing the MODIFY command or performing analysis only to provide information with no actual maintenance against a space or any of the tables. The ANALYZE option should always be placed after the MODIFY subcommand (DELETE, INSERT, UPDATE, or VERIFY).

Values of ANALYZE

Value

Description

ANALYZE NO

(Default) ANALYZE NO performs the modifications requested by MODIFY command.

ANALYZE YES

When ANALYZE YES is specified, MODIFY performs its analysis but does not take any maintenance action against SYSCOPY, BMCXCOPY, or SYSLGRNX, the ICF catalog, or the space. Informational messages are displayed.

COMMIT integer

Use the COMMIT option to specify how frequently changes are to be committed to the SYSCOPY, SYSLGRNX, or BMCXCOPY table. The default is to commit when all of the work for a particular table space or index space is complete for a DELETE, INSERT, UPDATE, or VERIFY subcommand. Committing more frequently can reduce locking and contention on SYSCOPY, SYSLGRNX, or BMCXCOPY although it can increase elapsed time. The utility attempts to commit after every n row transactions (where n is specified by integer) although it will not divide a unit of work that would leave SYSCOPY, SYSLGRNX, or BMCXCOPY in an inconsistent state. Valid values are 0-32767. Zero indicates to commit when all work for a subcommand is complete.

ON ERROR BADSTATUS

The ON ERROR BADSTATUS option allows you to specify what action MODIFY is to take if a space or partition is in an unacceptable status or has a BMC utility or Db2 utility running against it.

Values of ON ERROR BADSTATUS

Value

Description

ON ERROR BADSTATUS END

(Default) ON ERROR BADSTATUS END indicates MODIFY is to terminate processing with a RC=12.

ON ERROR BADSTATUS SKIP

ON ERROR BADSTATUS SKIP causes MODIFY to issue a message, skip over the space, and continue processing other spaces specified in SYSIN.

If a space is skipped because of ON ERROR BADSTATUS SKIP, the space will not be retried if the job abends and you retry the job with a NEW/RESTART.

ON ERROR NOTSUPPORTED

The ON ERROR NOTSUPPORTED option allows you to specify what action MODIFY is to take if a space or partition is a type that is not supported by MODIFY.

Values of ONERROR NOTSUPPORTED

Value

Description

ON ERROR NOTSUPPORTED END

(Default) ON ERROR NOSUPPORTED END indicates that MODIFY is to terminate processing with a RC=12 if an unsupported type is encountered.

ON ERROR NOTSUPPORTED SKIP

ON ERROR NOTSUPPORTED SKIP causes MODIFY to issue a message, skip over the space, and continue processing other spaces specified in SYSIN.

RECOVERY

The RECOVERY option provides compatibility with the Db2 MODIFY RECOVERY utility. If you do not plan to submit your JCL to the IBM utility, you need not specify this option.

Related topic


 

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

BMC AMI Copy for Db2 12.1