4.4.2 ID group definition (client services)
- Organization of this subsection
(1) Creating the ID group definition file
To create an ID group from the distribution-destination system in the ID group definition file, define the ID group to which the local system belongs, and register the file to the desired relay system. This file cannot be used when defining to an ID group registered from the managing server.
(a) File name of the ID group definition file
When the distribution-destination system registers the ID group definition file to an upper-level relay system, the group consists of one layer if the registration destination relay system does not register to that ID group. The group consists of two layers if the registration destination relay system registers to that ID group.
Use the file names shown in Table 4-3 to create the ID group definition file.
|
ID group definition registration method |
Type |
File name |
|---|---|---|
|
When registering to another relay system |
Other than HP-UX |
/NETMRDS/rdsprm/DMWIDUPM |
|
HP-UX |
/etc/opt/NETMDMW/rdsprm/DMWIDUPM |
- #
-
In a relay system directly connected to the managing server, this file is always used because registration to the upper-level relay system is not possible.
If the ID group definition file shown in Table 4-3 has already been created when JP1/IT Desktop Management 2 - Agent is started, the ID group is registered according to the contents of the file. Therefore, if an ID group definition file has been created at installation, the set contents will be valid until recreated. When the ID group is correctly registered, the extension of the ID group definition file is labeled .bak. If registration fails, it will be labeled .err.
(b) Creation format of the ID group definition file
Use a text editor to create the ID group definition file. The following shows the format of the ID group definition file.
[LOCAL-ID] *ID-group-1 : *ID-group-n |
- [LOCAL-ID]
-
Specifies the start of the ID group definition. Enter from the first column, and enclose in brackets [ ]. After [LOCAL-ID], do not specify space characters or tabs.
- *ID-group ~ <alphanumeric characters>((1-8 characters))
-
Enter * in the first column, and after the *, specify the ID group that the local UNIX machine belongs to. You cannot enter anything between * and the ID group. Do not specify space characters or tabs after the ID group.
You can specify multiple ID groups.
Create ID group definition files according to the rules below.
-
When # is specified on the first column, that line is regarded as a comment.
-
If the recreated ID group definition file is registered, the previous ID group definition file will become invalid. Because of this, enter all ID groups to be defined when changing the definition of the ID group, not just the ID group that is to be added.
(2) ID group definition file registration
There are two ways to register the ID group definition file to the relay system.
-
Restarting the system
If you restart the system to register the file, the job corresponding to the defined ID group is executed automatically if the job is stored in the temporary job storehouse.
-
Executing the rdsiddefine -s command
If you use the rdsiddefine -s command to register the file, the defined ID group is simply registered to the relay system. Therefore, even if a corresponding job is stored in the temporary job storehouse, it will not be executed automatically. To execute the job, execute the rdsidexec command.
If the ID group definition file cannot be registered due to a transmission error, or other problems, the ID group definition file is stored as is. Correct the cause of the error, and then try again.
If registration cannot be performed due to a syntax error of the ID group definition file, the file name is changed to a name with the extension .err. Correct the definition of the ID group definition file, and then execute again.
You can reference the contents of the registered file by executing the following command.
-
rdsiddefine -ll (to reference the ID group defined by the local UNIX machine)