Before mapping server groups to remote servers, it may be necessary to create and map a new service info code if an appropriate one doesn’t already exist. For example, in the Server Group Mapping section, the server group DIALUP is mapped to the server SERVER1. This information is stored in a service info code called SRVSHELL. In this example, we can see that this service info code has already been configured in the ServicesàService Info Codes section with the description "Shell Server".
Service Info Codes
If we wanted to store this information in a different service info code, we would have to configure it here. For more specific information on how to configure a service info code, refer to the Reference Manual. After the service info code is created, it should be mapped to specific services.
Once service info codes are configured, they should be mapped to specific services. As seen below we can see that the service info code SRVSHELL is mapped to the service type FLAT.
Service Info Code Mapping
This causes the server information, more specifically the server description to be stored in the SRVSHELL info code for the specific service when a FLAT service is opened. The example below shows how the FLAT service opened for a customer stores the SRVSHELL information.
New FLAT service
This corresponds to the description of the server SERVER1 as configured in the Server Control à Servers section.
Server Description
|
|
Because the Server Description is used when storing the server information into a service info code, if the description of the server is changed, the server control may not be able to locate the service for modification. Server descriptions should be chosen carefully, so that changes will not be necessary. |
