Before you can rename the host, you must terminate JP1/Software Distribution and Embedded RDB.

To rename the OS host after operation has started:

1. Terminate Remote Installation Manager.
2. From Control Panel, choose Administrative Tools, then Services, and then stop the Remote Install Server service.
3. Terminate the programs that are accessing the JP1/Software Distribution database.
   For example, if JP1/Asset Information Manager is being used to access the JP1/Software Distribution database, stop all JP1/Asset Information Manager services, commands, and tasks.
   
4. Execute the netmdb_stop.bat command, located in the JP1/Software Distribution Manager installation target directory \BIN, to stop the database.
5. Use a text editor to open the pdsys file that is stored in JP1/Software-Distribution-installation-directory\NETMDB\conf.
6. Change host-name-before-change in pdunit -x host-name-before-change -u unt1 -d "JP1/Software-Distribution-installation-directory\NETMDB".^{#1, #2}
7. Use a text editor to open the pdutsys file that is stored in JP1/Software-Distribution-installation-directory\NETMDB\conf.
8. If the setting set pd_hostname = host-name-before-change is specified, make the appropriate change to host-name-before-change.^{#1, #3}
9. Use a text editor to open the following five files that are stored in JP1/Software-Distribution-installation-directory\NETMDB\conf\emb:
   
   • HiRDB.ini file
   • reload.bat file
   • reorganization_al.bat file
   • reorganization_tb.bat file
   • unload.bat file
10. Change host-name-before-change in PDHOST=host-name-before-change.^#2
11. Rename the OS host.
12. Restart the OS.

#1

The maximum length of a single definition line is 80 characters. If a definition exceeds 80 characters, divide it into multiple lines, and specify the continuation symbol \ at the end of each line being continued.

Example:

pdunit -x jp1sdmanager.domain -u unt1 \
-d "C:\Program Files\Hitachi\NETMDM\NETMDB"

#2

To use the failover function of JP1/Software Distribution in a cluster system environment, specify the logical host name.

#3

To use the failover function of JP1/Software Distribution in a cluster system environment, specify the physical host name.

Note

The following notes apply when hosts are renamed after operations have begun:

• For details about how to specify host names, see 8.1.2 Assigning host names in a JP1/Software Distribution system.
• If any of the following types of jobs exist, delete such jobs, make sure that the jobs have been deleted, and then rename the host:
  Job whose execution status is anything other than normal termination or error
  Send package, allow client to choose job
  Jobs that acquire inventory information periodically
  If you rename the host without deleting such jobs, currently executing jobs may stop or deletion of lower systems' jobs may become impossible.
  

This subsection describes how to suppress output of unneeded messages from the messages that are output to the event log by Embedded RDB. For details about the Embedded RDB messages, see the manual HiRDB Version 8 Messages.

Before you set suppression of message output, terminate JP1/Software Distribution and Embedded RDB.

Suppress only information messages (messages with an ID that ends with I). It may become difficult to resolve errors if you suppress output of warning or error messages (messages with an ID that ends with W or E).

To suppress message output to the event log:

1. Terminate the Remote Installation Manager.
2. Open the Control Panel and choose Administrative Tools, then Services to stop the Remote Install Server service.
3. Terminate the product that is accessing the JP1/Software Distribution database.
   For example, if JP1/Asset Information Manager is accessing the JP1/Software Distribution database, stop all the services, commands, and tasks of JP1/Asset Information Manager.
   
4. Execute the netmdb_stop.bat command, located in the JP1/Software Distribution Manager installation target directory \BIN, to stop the database.
5. Use a text editor to open the pdsys file that is stored in JP1/Software-Distribution-installation-directory\NETMDB\conf.
6. Add to the line pdmlgput -s N -m message-ID,message-ID,message-ID the IDs of the messages whose output is to be suppressed.
   Do not include in message-ID the message severity code that follows the hyphen (-). To specify multiple message IDs, use a comma to separate the IDs. If the specification exceeds 80 columns, enter \ at the end of the line to be continued to set a linefeed.
   The following example adds message IDs to the existing settings in order to suppress output of the KFPS00010-I, KFPS00011-I, KFSP00012-I, and KFSP00013-I messages:
   

   

7. Execute the netmdb_start.bat command, located in the JP1/Software Distribution Manager installation target directory \BIN, to start the database.
8. Open the Control Panel and choose Administrative Tools, then Services to start the Remote Install Server service.

While you are executing one of the following commands to manipulate the database, if an error (such as a communication error or disk error) occurs, the command might not respond.

• Reorganizing the database (netmdb_reorganization.bat command)
• Backing up the database (netmdb_unload.bat command)
• Releasing the area for operation logs that were deleted (netmdb_reclaim.bat command)

If you cannot forcibly terminate a command that does not respond because, for example, the command was executed automatically by the Windows task feature or by JP1/AJS, perform the following steps to set an execution timeout for the command.

Terminate JP1/Software Distribution and Embedded RDB before you set the execution timeout.

1. Stop Remote Installation Manager.
2. Stop the Remote Install Server service through the Service of Administrative Tools of Control Panel.
3. Stop all the programs that are accessing the database of JP1/Software Distribution.
   For example, when JP1/Asset Information Manager is accessing the database of JP1/Software Distribution, stop all the commands and tasks for JP1/Asset Information Manager.
   
4. Execute the netmdb_stop.bat command that is stored in JP1/Software-Distribution-Manager-installation-directory\BIN to stop the database.
5. Use a text editor to open the pdsys file that is stored in JP1/Software-Distribution-installation-directory\NETMDB\conf.
6. Add a line for set pd_utl_exec_time = command execution timeout in the pdsys file. ^#1
7. Execute the netmdb_start.bat command that is stored in JP1/Software-Distribution-Manager-installation-directory\BIN to start the database.
8. Start the Remote Install Server service through the Service of Administrative Tools of Control Panel.

#1

pd_utl_exec_time = command execution timeout

Specify a command execution timeout in the range from 0 to 35791394 (minutes) for the following commands that manipulate the database. If you do not specify a value, or specify 0, the command execution timeout will not be set.

• Upgrading the database
• Reorganizing the database (netmdb_reorganization.bat command)
• Backing up the database (netmdb_unload.bat command)
• Restoring the database (netmdb_reload.bat command)
• Releasing the area for operation logs that were deleted (netmdb_reclaim.bat command)

If the command does not complete after the time specified for the execution timeout has elapsed, the command being executed will be abnormally terminated.

For this operand, specify a value that allows for some extra time compared to the actual time that the command requires for execution.

For example, if upgrading the database requires a maximum of approximately 90 minutes, and reorganizing the database requires a maximum of approximately 60 minutes, specify pd_utl_exec_time=120 for the timeout, just in case. This is because if a process that normally finishes in 90 minutes has not responded after 120 minutes, we can assume that an error causing the command not to respond has occurred. Also, we recommend that you specify 0 for the execution timeout when you execute the following commands:

• Upgrading the database
• Restoring the database (netmdb_reload.bat command)

Sample

#
#------------------------------------------------------------------
# set form 
#
:
 
:
set pd_utl_exec_time = 120
#
#------------------------------------------------------------------
# putenv form 
#