6.6.2 Defining jp1hosts2 information
JP1/Base can keep its own set of hosts information, allowing it to perform name resolution independently of the OS.
- Note
-
When you define jp1hosts2 information, JP1/Base does not reference the definitions in the hosts file and DNS for the host names and IP addresses defined in the jp1hosts2 information.
- Example:
-
jp1hosts2 information:
hostA 100.0.0.10, 200.0.0.10
hosts file:
100.0.0.10 hostA hostB 200.0.0.10 hostC
With these definitions, the hosts file is not referenced for hostA and the IP addresses 100.0.0.10, and 200.0.0.10.
To register jp1hosts2 information:
-
Edit the jp1hosts2 definition file.
A jp1hosts2 definition file (jp1hosts2.conf) is provided by default. If you create your own jp1hosts2 definition file, store it in the same folder as the default jp1hosts2.conf file. For details on the format of the jp1hosts2 definition file, see jp1hosts2 definition file in 16. Definition Files.
-
Execute the jbshosts2import command to register the file.
Execute the command as follows:
jbshosts2import {-o|-r} [jp1hosts2-definition-file-name] [-h logical-host-name]
Use the jbshosts2export command to check the jp1hosts2 information you registered. For details on the commands used in this section, see 15. Commands.
- Note
-
In products that reference jp1hosts2 information, such as JP1/IM - Manager and JP1/AJS3 - Manager, if you define jp1hosts2 information in an environment where jp1hosts information is already defined, the existing jp1hosts information becomes invalid. If you delete the jp1hosts2 information (by executing the jbshosts2import command with the -d option specified), the jp1hosts information becomes valid again.
However, this does not apply to products that do not reference jp1hosts2 information, in which case definition of jp1hosts information will not become invalid.