Command scope in Db2 data sharing
Many commands that are used in a data sharing environment affect only the member for which they are issued.
The breadth of a command's impact is called the scope of that command. For example, a STOP DB2 command stops only the member identified by the command prefix. Such commands have member scope.
Other commands have group scope because they affect an object in such a way that all members of the group are affected. For example, a STOP DATABASE command, issued from any member of the group, stops that database for all members of the group.
Commands with group scope
The following commands have group scope:
| Commands | Commands |
|---|---|
Commands with specified scope
The following commands have either group or member scope, depending on the options that you specify in the command. The specific command options used to specify the scope vary for different commands command.
| Commands | Commands |
|---|---|
Most other commands have member scope. For information about the specific data sharing scope of each command, see the Environment
sections in the description of each command in Db2 commands.
- Trace information for data sharing members
- When this command with group scope is issued in a Db2 data sharing member, it also runs on all other active members. IFICID 090 trace records for other group members can show that the same command was issued by the SYSOPR authorization ID from the 016.TLPKN5F correlation ID, in addition to the trace records from the member where the original command was issued.
