File Management - IBM

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
object. This is true unless the user is a member of a group profile and has
OWNER(*GRPPRF) specified for the profile.
If you specify OWNER(*GRPPRF), the group profile becomes the owner of the
to-file. In this case, if the user profile running the copy command does not have
authority to add a member or write data to the new file, the copy command fails.
The created to-file does not maintain the file capabilities of the from-file. The to-file
allows update, delete, read, and write operations, regardless of whether the
from-file allowed these operations. Following are special considerations for the
new to-file:
v If the number of records copied into a member is greater than the maximum size
of the created to-file, the to-file is extended without intervention by the system
operator.
v If the from-file is an SQL table, view, or index, the created to-file will be a
physical file that is not an SQL table. However, when the from-file contains
LOBs, datalinks, or user-defined types, the created to-file is an SQL table.
v If the from-file has a trigger program associated with it, the CPYF and
CPYFRMQRYF commands do not copy the trigger information to the to-file
when the CRTFILE parameter is used.
v If you create a new file (CRTFILE(*YES)) from a file with constraints, the
constraint definitions do not copy to the new file.
v If you create a new file (CRTFILE(*YES)) from a file with user-defined functions,
the user-defined functions do not copy to the new file.
Adding, replacing, and updating records (MBROPT parameter)
84 File Management V4R5
On the CPYF, CPYFRMDKT, CPYFRMQRYF, CPYFRMTAP, or CPYSRCF
commands, you can add or replace existing data in the to-file by specifying
different attributes on the MBROPT parameter. The CPYF command also allows
you to update duplicate key records and add non-duplicate key records to a to-file
member. You can do these tasks by specifying *REPLACE, specifying *ADD, or
specifying *UPDATE on the MBROPT parameter (see page Specifying *REPLACE
when copying files).
Specifying *REPLACE when copying files
By specifying *REPLACE, you essentially clear the member. The copied records are
the only records in the member when the operation completes. You must have
authority to clear the member in order to specify MBROPT(*REPLACE).
For copy commands other than the CPYFRMQRYF command, when you specify
*REPLACE, copy command processing fails if the from-file does not contain any
records. When you specify *REPLACE on the CPYFRMQRYF command, the to-file
member will be cleared even if the open query file contains no records.
*REPLACE is the default value for the CPYSRCF command. All other copy
commands have the default value of *NONE; however, *NONE is valid only for
copying to a device file.