Job Management Partner 1/Software Distribution Client Description and User's Guide
This section describes the rules that apply to the settings files for the client services and distributor tools.
- Organization of this subsection
- (1) Creating a new settings file
- (2) Format of settings files
- (3) Rules for creating a settings file
- (4) Specifying host names
- (5) Changing the settings file
- (6) Actions to be taken for data migration from JP1/Software Distribution Client
(1) Creating a new settings file
Use a text editor to create the settings files. The following shows the names of the settings files.
- Settings file for the client services
- For systems other than HP-UX: /NETMRDS/rdsprm/RDSSETFL
- For HP-UX: /etc/opt/NETMDMW/rdsprm/RDSSETFL
- Settings file for the distributor tools
- For systems other than HP-UX: /NETMAF/dmprm/RDMSET
- For HP-UX: /etc/opt/NETMAF/dmprm/RDMSET
If a settings file has been created upon startup, JP1/Software Distribution Client configures the operating environment according to the settings file.
- When the operating environment has been successfully set
Extension .bak is added to the end of the settings file name.
- When the operating environment cannot be set
Extension .err is added to the end of the settings file name.
When the settings file is created, the specified contents will be valid until the settings file is changed. For details on how to change the settings file, see (5) Changing the settings file.
You can assign any file name to the settings file for the distributor tools by specifying the -f option in the rdsafenv command.
Create settings files in the following format:
attribute-namevalueWhere, indicates a tab code and indicates that you should press the Enter key.
- attribute-name
- In attribute-name, specify an item you want to set in the settings file.
- value
- In value, specify the value of attribute-name you want to set for the UNIX machine.
The details to specify in a settings file differ depending on the facility that is being used. For details about the settings files, see 6.4.2 through 6.4.5. For the packager settings, use the same settings as for the individual UNIX machines.
(3) Rules for creating a settings file
- You can enter a space instead of a tab ().
- If you enter a pound sign (#) in the first column, the line is assumed to be a comment.
- Each line in a settings file can contain up to 256 bytes including the code () for the pressed Enter key.
- If you specify the same attribute name more than once, only the last one specified takes effect. All the other attributes specified before the last one are ignored.
- When you do not specify an item, the following values take effect.
- The first time the settings file is created: Default
- When the contents of the settings file have been changed: The specified value of the settings file before it was changed
- Specify the host name according to (4) Specifying host names.
(4) Specifying host names
The host names you specify in the ManagingHost attribute in settings files and in hostname of each workstation must also be specified in the /etc/hosts file. You cannot specify aliases. The /etc/hosts files of the nodes in the same network must have the same Internet address and host name definition. The following shows the relationship between the host name of /etc/hosts and its alias names:
Internet-address host-name aliasFor details on Internet addresses, host names, and their aliases, see the appropriate manual for each operating system.
(5) Changing the settings file
Follow the procedures below when changing the settings file. In addition, when the distribution status server facility is running, stop it using the rdsdlvse -p command before changing anything. After completing changes, use the rdsdlvse command to restart the distribution status server facility.
- To change the ManagingHost value or the ConnectionKind value, execute the rdssys -u command to delete the value from the system configuration information. Also delete the following files:
Before changing the value of WorkstationType, make sure that all jobs addressed to the system to be changed have been completed.
- For systems other than HP-UX: /NETMRDS/rdsprm/.myname
- For HP-UX: /var/opt/NETMDMW/rdsprm/.myname
- Stop processes in the following order:
- Execute one of the following commands to stop the process for reporting the results:
- For a relay system: rdssnd -q
- For a client workstation: rdsrf -q
- For an end workstation: /NETMRDS/COM/rdssnde -q (/opt/NETMDMW/lbin/rdssnde -q for HP-UX)
- Execute the following command to stop the resident process:
- For systems other than HP-UX: /NETMRDS/COM/rdskillsrv
- For HP-UX: /opt/NETMDMW/lbin/rdskillsrv
- Delete .bak from the settings file name to resume the original name.
- Change the contents of the settings file. If JP1/Software Distribution Client is installed on a machine on which JP1/Software Distribution SubManager Version 8 or earlier, JP1/Software Distribution Client Version 8 or earlier, or JP1/Software Distribution Workstation has been installed, the settings file of the earlier version can be inherited and used.
- Either restart the system or start the process by executing the following command:
For systems other than HP-UX: /NETMRDS/COM/rdsstart
For HP-UX: /opt/NETMDMW/lbin/rdsstart
You can also change the settings file for the distributor tools in the Environment Settings window of the distributor tools GUI. The Environment Settings window can be displayed from any mode of the Software Distribution Client window.
Specify the workstation type for JP1/Software Distribution Client in WorkstationType of the settings file. To change the workstation type in connection with a network configuration change, the following steps are necessary in addition to the procedure described above:
- Before making the change, ensure that all jobs addressed to the system have been completed.
- Ensure that the prerequisite programs have been installed.
- Change the workstation type in WorkstationType of the settings file. Also reassess other settings according to the workstation type change.
(6) Actions to be taken for data migration from JP1/Software Distribution Client
When you replace machines and migrate the data from JP1/Software Distribution Client, you need to back up the settings file and some other files.
You can migrate JP1/Software Distribution Client data only when the migration-source system and the migration-destination system use the same OS. The version of JP1/Software Distribution Client must also be the same.
The following files need to be backed up:
- Settings file
- Temporary collection storehouse#1
- For systems other than HP-UX
- /NETMRDS/rdsprm/NS000000#2
- /NETMRDS/rdsprm/.myname#2
- /NETMRDS/.uap/uplistd#2
- /NETMRDS/rdsprm/.delvadrs#2
- /NETMRDS/rdsprm/.delvadrs.ex#2
- /NETMRDS/rdsprm/.delvadrs.opt#2
- For HP-UX
- /var/opt/NETMDMW/rdsprm/NS000000#2
- /var/opt/NETMDMW/rdsprm/.myname#2
- /var/opt/NETMDMW/.uap/uplistd#2
- /var/opt/NETMDMW/rdsprm/.delvadrs#2
- /var/opt/NETMDMW/rdsprm/.delvadrs.ex#2
- /var/opt/NETMDMW/rdsprm/.delvadrs.opt#2
- #1
- If the settings file contains either of the following, a backup is required:
- HOST is set in ConnectionKind.
- END is set in WorkstationType.
- #2
- When you pre-install JP1/Software Distribution Client, for example, in cases where you copy the hard disk containing JP1/Software Distribution Client to install JP1/Software Distribution Client, delete these files after you install JP1/Software Distribution Client.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.