Copy Options panel
You use the Copy Options panel to set the global (or initial) options used by the Copy utility (3.3). These options are saved in your ISPF profile and persist from one FM/Db2 session to the next.
The
global Copy options are restored at the start of each Copy session
and can be temporarily changed for a copy session by selecting Edit
Copy Options on the Copy To
entry panel.
Panel and field definitions
- Use uncommitted read
- Indicates
whether to enable retrieval of uncommitted data for the Copy session:
- ⁄
- Retrieve data, including data not yet committed by another user
or application program. The resultant SELECT statement used by
FM/Db2 to retrieve table data has the suffix
WITH UR
appended. This allows reading through any locks which might be held on that table. The default is not selected. - (blank)
- Only retrieve committed data from tables without write locks.
Note: If FM/Db2 attempts to retrieve data that has a write lock, an SQL error can result.
- Locking
- FM/Db2
provides options to lock the table to prevent other users from either
updating or reading data. Use these options with caution.
- 1. None
- FM/Db2 does not issue an explicit table lock for the object being copied. Locking of rows and pages within the object is managed by Db2® according to FM/Db2 concurrency options and Db2® installation and object definition options. This is the default setting.
- 2. Share mode
- FM/Db2 issues a LOCK TABLE IN SHARE MODE statement before reading the data from Db2®. This restricts all other users to read-only operations on the object.
- 3. Exclusive mode
- FM/Db2 issues a LOCK TABLE IN EXCLUSIVE MODE statement before reading the data from Db2®. This prevents all other users from accessing the object, unless the other process is running with an isolation level of uncommitted read.
- Duplicate key processing
- You
can specify what action FM/Db2 takes if it encounters a duplicate
key. Set this option to one of the following:
- 1. Ignore
- Existence of duplicate key ignored. This is the default.
- 2. Update
- Updates duplicate rows when Db2® returns a duplicate key error (SQL error code -803) in response to an INSERT SQL statement. When this option is selected, FM/Db2 attempts to update the existing row. All columns of the table that are part of at least one unique index are used to identify the row. No comparison is made between the copied row and the existing row prior to the update operation (that is, the update is done regardless of whether the copied row and existing row are the same). When using this option, it is recommended that a Db2® table name, rather than a view name, be specified. FM/Db2 does not attempt to update existing rows in a view defined on a view.
- For __________ duplicates
- Specifies the maximum number of duplicates permitted. Valid values
are:
- A number in the range 0 to 2147483647. If FM/Db2 detects more than this number of duplicates during the copy process, the copy is canceled and all changes are rolled back.
- ALL. ALL is the default.
- Delete existing rows
- Determines
whether FM/Db2 deletes all existing rows in the table before copying
the data.
- ⁄
- Delete all existing rows.
- (blank)
- Do not delete existing rows. This is the default setting.
- Ignore RI/Constraint errors
- Determines
what processing occurs when the Copy utility encounters an SQLCODE-530
(RI error - no primary key) or SQLCODE-545 (Constraint error).
- ⁄
- The Copy process ignores the error and continues with the next row. The row is not copied or updated and is not included in the copy count.
- (blank)
- Copy utility canceled. This is the default setting.
- Native unicode processing
- Determines
how FM/Db2 processes Unicode encoded data when copying data between
two Unicode encoded tables. When the option is enabled, Unicode encoded
data is copied between Unicode encoded tables without the potential
for character substitution. When the option is not enabled, the option
has no effect; that is, the default processing is used. When either
or both of the FROM or TO tables are not Unicode encoded, the option
has no effect, even if enabled. When this option and the batch execution
options are enabled, "NATIVE= YES" is shown in the generated JCL.
- ⁄
- Process Unicode data natively.
- (blank)
- Do not process Unicode data natively. This is the default setting.
- Create audit trail
- Determines whether audit records are written for the current copy operation. This option may not appear depending on the installation choices made by the product installer. When the option is available, the default is to not write audit records.
Parent panels
Child panels
None.