LSD Minor Codes

Previous Topic | Next Topic | Contents | Index
Getting Started Guide | Administration Guide | Reference Guide

LSD Minor Code Values

1102 - MINOR_NO_DIRECT_HOST

This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. This indicates that the LSD was unsuccessful when it attempted to find the direct address of the configured tcp server in the configuration database.

1103 - MINOR_NO_DIRECT_PORT

This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. This indicates that the LSD was unsuccessful when it attempted to find the port number of the configured tcp server in the configuration database.

1104 - MINOR_NO_CS_CONFIG

The LSD raises this exception when the target server is configured to use_comm_server and the LSD can't find any entries in the csmap@load_table entity. This entity is created and updated by the Comm Servers at runtime.

Suggested actions:

• Ensure the Comm Server(s) are running
• Ensure the Comm Server(s) and LSD are using the same configuration database
• Ensure the configuration database is properly secured

1105 - NO_CS_HOST_NAME

This exception is raised when the LSD has found the Comm Server to use, but it could not find the host_name of the Comm Server in the configuration database. This usually indicates that the Comm Server is not properly configured.

An example Comm Server configuration record (also known as entity) might look like this:

    cfgmgt> entity ZC01@comm_server
         port_number            5220
         host_name              oss2.tandem.com
         actual_ip_address      204.160.16.36

To correct this problem, first verify the validity of the Comm Server(s) configuration settings. Next, insure that the Comm Server(s) were correctly initialized and that they are running and able to receive requests. If problems are found, you must fix the configuration and restart the Comm Server server class. This can be done through a PATHCOM session or by stopping the system (using nsdstop), fixing the configuration settings, then restarting the system (using nsdstart).

1106 - NO_CS_PORT_NUMBER

Similar to the NO_CS_HOST_NAME minor code detailed above, this minor code occurs when the LSD has found the Comm Server to use, but it could not find the Comm Server's port_number.

To correct this problem, first verify the validity of the Comm Server(s) configuration settings. Next, insure that the Comm Server(s) were correctly initialized and that they are running and able to receive requests. If problems are found, you must fix the configuration and restart the Comm Server server class. This can be done through a PATHCOM session or by stopping the system (using nsdstop), fixing the configuration settings, then restarting the system (using nsdstart).

1107 - MINOR_NO_PP_CONN

This minor code occurs in the context of an INTERNAL system exception. This indicates that an expected data structure (representing a comm server connection) required by the LSD does not exist.

1108 - MINOR_NO_CLIENT_ADDRESS

This minor code occurs in the context of an INTERNAL system exception. This indicates that the client listed in the csmap@map_table is not valid.

1109 - MINOR_NOT_NSDOM_OBJECT_KEY

This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. This indicates that the LSD was asked to find the location of an object which is not hosted by NonStop DOM. This is not a valid operation.

Previous Topic | Next Topic | Contents | Top
Getting Started Guide | Administration Guide | Reference Guide
Bibliography | Glossary | Index

© Tandem, a division of Compaq. All rights reserved. Legal notices.