5.6.1 Operations that result in changes to the common definition information on the primary node and how to apply the settings to the secondary node

(1) When common definition information is added or changed

When additions or changes are made to the common definition information by one of the operations listed in Table 5-4, you need to make the common definition information consistent on the primary and secondary nodes. If several of the operations in Table 5-4 are executed in succession, you only need to perform this procedure once to apply all the changes to the common definition information on the secondary node.

1. On the primary node, back up the common definition information by executing the jbsgetcnf command.

   Execute the command as follows:

   jbsgetcnf -h logical-host-name > backup-file-name

   Note that the logical host name must be correctly specified with lower or upper case as specified when the logical host was set up.

2. Copy the backup file to the secondary node.

3. Execute the jbssetcnf command on the secondary node with the backup file specified as a command argument.

   Execute the command as follows:

   jbssetcnf backup-file-name

To Page Top

(2) When user mapping information is deleted

If you used the jbsmkumap or jbsrmumap command or the JP1/Base Environment Settings dialog box (Windows only) to delete user mapping information, use the following procedure to make the common definition consistent between the primary and secondary nodes:

1. On the primary node, execute the jbsgetumap command to back up the user mapping information.

   Execute the command as follows:

   jbsgetumap -h logical-host-name > backup-file-name

2. Copy the backup file to the secondary node.

3. Execute the jbsmkumap command on the secondary node with the backup file specified as a command argument.

   Execute the command as follows:

   jbsmkumap -h logical-host-name -f backup-file-name

To Page Top

(3) When OS user password information is deleted (Windows only)

If you used the jbsmkpass, jbsrmumappass, or jbspassmgr command or the JP1/Base Environment Settings dialog box to delete password information for OS users, use the procedures below to make the common definition consistent on the primary and secondary nodes. Note that the way in which you apply the changes to the common definition information on the secondary node differs for each command.

To Page Top

(4) When jp1hosts information is deleted

If you used the jbshostsimport command to delete jp1hosts information, use the following procedure to make the common definition consistent between the primary and secondary nodes:

1. On the primary node, back up the jp1hosts information by executing the jbshostsexport command.

   Execute the command as follows:

   jbshostsexport -h logical-host-name > backup-file-name

2. Copy the backup file to the secondary node.

3. Execute the jbshostsimport command on the secondary node with the backup file specified as a command argument.

   Execute the command as follows:

   jbshostsimport -h logical-host-name -r backup-file-name

Note

In an environment in which jp1hosts2 information is registered, also specify the -f option when executing the jbshostsimport command. For details on the jbshostsimport command, see jbshostsimport in 15. Commands.

To Page Top

(5) When a host or host group is deleted in the command execution environment

If you use the jcocmddef command to set up the command execution environment and then specify the command with the -group option to delete a host or host group, use the following procedure to make the common definition consistent between the primary and secondary nodes:

1. Copy the host group definition file from the primary node to the secondary node.

2. Execute the jcocmddef command on the secondary node with the host group definition file specified as a command argument.

   Execute the command as follows:

   jcocmddef -host logical-host-name -group host-group-definition-file

To Page Top

(6) When authentication server is deleted

If you used the jbssetusrsrv (UNIX only), or jbssetupsrv (Windows only) command or the JP1/Base Environment Settings dialog box (Windows only) to delete authentication server, use the procedures below to make the common definition consistent on the primary and secondary nodes.

To Page Top