The Synchronize Data Group File Entry (SYNCDGFE) command synchronizes database files associated with a data group by data group file entries.
Active data group required: Because the SYNCDGFE command runs through a database apply job, the data group must be active when the command is used.
Choice of what to synchronize: The Sending mode (METHOD) parameter provides granularity in specifying what is synchronized. Table 74 describes the choices.
|
*DATA |
This is the default value. Only the physical file data is replicated using MIMIX Copy Active File processing. File attributes are not replicated using this method. If the file exists on the target system, MIMIX refreshes its contents. If the file format is different on the target system, the synchronization will fail. If the file does not exist on the target system, MIMIX uses save and restore operations to create the file on the target system and then uses copy active file processing to fill it with data from the file on the source system. |
|
*ATR |
Only the physical file attributes are replicated and synchronized. |
|
*AUT |
Only the authorities for the physical file are replicated and synchronized. |
|
*SAVRST |
The content and attributes are replicated using the IBM i save and restore commands. This method allows save-while-active operations. This method also has the capability to save associated logical files. |
Files with triggers: The SYNCDGFE command provides the ability to optionally disable triggers during synchronization processing and enable them again when processing is complete. The Disable triggers on file (DSBTRG) parameter specifies whether the database apply process (used for synchronization) disables triggers when processing a file.
The default value *DGFE uses data group file entry to determine whether triggers should be disabled. The value *YES will disable triggers on the target system during synchronization.
If configuration options for the data group, or optionally for a data group file entry, allow MIMIX to replicate trigger-generated entries and disable the triggers, when synchronizing a file with triggers you must specify *DATA as the sending mode.
Including logical files: The Include logical files (INCLF) parameter allows you to include any attached logical files in the synchronization request. Logical files that are explicitly excluded from replication are not sent. This parameter is only valid when *SAVRST is specified for the Sending mode prompt.
Physical files with referential constraints: Physical files with referential constraints require a field in another physical file to be valid. When synchronizing physical files with referential constraints, ensure all files in the referential constraint structure are synchronized concurrently during a time of minimal activity on the source system. Doing so will ensure the integrity of synchronization points.
Including related files: You can optionally choose whether the synchronization request will include files related to the file specified by specifying *YES for the Include related (RELATED) parameter. Related files are those physical files which have a relationship with the selected physical file by means of one or more join logical files. Join logical files are logical files attached to fields in two or more physical files.
The Include related (RELATED) parameter defaults to *NO. In some environments, specifying *YES could result in a high number of files being synchronized and could potentially strain available communications and take a significant amount of time to complete.
A physical file being synchronized cannot be name mapped if it has logical files associated with it. Logical files may be name mapped by using object entries.
Files with permissions or masks: When the SYNCDGFE command is invoked from a command line or by a program other than MIMIX and specifies the sending mode as METHOD(*DATA) when synchronizing a file that is protected by enabled permissions or masks, the command will temporarily change the user profile of the job to the MIMIXOWN user profile while processing the file. The user profile of the job is changed back to its original value before the job ends.
Temporal tables and history tables with a versioned relationship: When the SYNCDGFE command is invoked from a command line or by a program other than MIMIX and specifies the sending mode as METHOD(*DATA) when synchronizing a system-period temporal table or a history table for which a versioned relationship exists, the command will temporarily change the user profile of the job to the MIMIXOWN user profile while processing the file. The user profile of the job is changed back to its original value before the job ends.
Ignored attribute processing: The Ignored attribute processing (IGNATR) parameter specifies how to process any attributes of the object being synchronized that are configured to be ignored by audits. Attributes that are configured to be ignored streamline distributing data in non-switchable data groups and in data groups whose target node is a replicate node of an application group. The default value, *KEEP, does not synchronize the ignored attributes and keeps the current values on each system in the data group. The value *REPLACE allows you to synchronize the ignored attributes using values from the source system objects. For more information, see Ignoring attribute differences in distributed environ-ments.