CL commands: Affect all the pieces of a distributed file with DB2 Multisystem

Some CL commands, when run, affect all the pieces of the distributed file.

When you run these commands on your system, the commands are automatically run on all the nodes within the node group.

This convention allows you to maintain consistency across the node group without having to enter the same command on each system. With authority changes, some inconsistency across the node group might occur. For example, if a user ID is deleted from one system in the node group, the ability to maintain consistency across the node group is lost.

Authority errors are handled individually.

The following commands affect all pieces of the distributed file:

• Add Logical File Member (ADDLFM)
• Add Physical File Constraint (ADDPFCST)
• Add Physical File Member (ADDPFM)
• Add Physical File Trigger (ADDPFTRG)
• Allocate Object (ALCOBJ)
• Change Logical File (CHGLF)
• Change Object Owner (CHGOBJOWN)
• Change Physical File (CHGPF)
• Change Physical File Constraint (CHGPFCST)
• Clear Physical File Member (CLRPFM)
• Copy File (CPYF). See Using the copy file (CPYF) command with distributed files with DB2^® Multisystem for additional information about this command.
• Create Logical File (CRTLF)
• Deallocate Object (DLCOBJ)
• Delete File (DLTF)
• End Journal Physical File (ENDJRNPF). See Journaling considerations with DB2 Multisystem for additional information about this command.
• Grant Object Authority (GRTOBJAUT)
• Remove Physical File Constraint (RMVPFCST)
• Remove Physical File Trigger (RMVPFTRG)
• Rename Object (RNMOBJ)
• Reorganize Physical File Member (RGZPFM)
• Revoke Object Authority (RVKOBJAUT)
• Start Journal Physical File (STRJRNPF). See Journaling considerations with DB2 Multisystem for additional information about this command.

For these commands, if any objects other than the distributed file are referred to, it is your responsibility to create those objects on each system. For example, when using the Add Physical File Trigger (ADDPFTRG) command, you must ensure that the trigger program exists on all of the systems. Otherwise, an error occurs. This same concept applies to the Start Journal Physical File (STRJRNPF) command, where the journal must exist on all of the systems.

If the user profile does not exist on the remote node and you issue the GRTOBJAUT command or the RVKOBJAUT command, the authority is granted or revoked on all the nodes where the profile exists and is ignored on any nodes where the profile does not exist.

• Journaling considerations with DB2 Multisystem
  Although the Start Journal Physical File (STRJRNPF) and End Journal Physical File (ENDJRNPF) commands are distributed to other systems, the actual journaling takes place on each system independently and to each system's own journal receiver.
• Copy File (CPYF) command with distributed files with DB2 Multisystem
  When the Copy File (CPYF) command is issued, the system tries to run the CPYF command as quickly as possible.