# BASEstartm Classic DAS
for OMNItm Software
Installation and User's Guide

Previous | Contents | Index

# Appendix A
Returned Values and Associated Error Messages

This appendix contains returned values and associated error messages for the DAS for OMNI software.

The return values generated by DAS for OMNI software are either standard ILAN$_ values or are from OMNI software. The return values generated by OMNI have the facility code of OMNI_.

To enable message translation of these OMNI_ messages for each process, enter the following command:

    $ SET MESSAGE SYS$MESSAGE:OMNI_CODES_MSG.EXE

For a full list of OMNI errors please refer to the OMNI Application Interface User's Guide. This is a short guide to the most commonly seen errors.

> OMNI-E-INITFAIL, Initiate request failed,

Explanation: Error. An error occurred when attempting to connect to a device.
User Action: Check the device availability.

> OMNI-E-CONNECTERR, Connect Error,

Explanation: Error. An error occurred when attempting to connect to a device.
User Action: Check local and remote ODS configurations. Make sure that you are using the supplied ILAN$SYSTEM_STARTUP.

> OMNI-E-OBJ_UNDEFINED, Service Error Class- Definition: Object Undefined,

Explanation: Error. An error occurred when attempting to read or write to a physical point. In this case, the variable is not defined on the remote device.
User Action: Check that the variable is defined at the remote device.

> OMNI-E-OBJ_ACCESS_DENIED, Service Error Class- Access: Denied,

Explanation: Error. An error occurred when attempting to read or write to a physical point. The device is not allowing access to the variable requested.
User Action: Check the variable address on the device.

> OMNI-E-GETVAL_CNF_ERR, Get Value Confirm Error,

Explanation: Error. An error occurred when attempting to read a physical point.
User Action: Check the network and provider status to further diagnose the problem.

> OMNI-E-PUTVAL_CNF_ERR, Put Value Confirm Error,

Explanation: Error. An error occurred when attempting to write to a physical point.
User Action: Check the network and provider status to further diagnose the problem.

> OMNI-E-OBJ_NOT_EXISTEN, Service Error Class- Access: Non-Existent,

Explanation: Error. An error occurred when doing an upload, download, start or stop function. You referred to a nonexistent Domain or PI.
User Action: Issue a DIRECTORY command to find valid Domains and PIs.

> OMNI-E-STARTPI_REQ_ERR, Start Program Invocation Request Service Error,

Explanation: Error. An error occurred when attempting to do a "start" command. The /START_OPTIONS qualifier was probably specified improperly.
User Action: Specify the correct /START_OPTIONS qualifier in your start command.

> OMNI-E-RESETPI_REQ_ERR, Reset Program Invocation Request Service Error,

Explanation: Error. An error occurred when trying to stop a PI. The /STOP_OPTIONS qualifier was probably specified improperly.
User Action: Specify the correct /STOP_OPTIONS qualifier on your stop command.

> OMNI-E-OBJ_STATE_CONFL, Service Error Class- Service: Object State Conflict,

Explanation: Error. An error occurred when attempting to start or stop a PI. The start or stop was probably done twice.
User Action: None.

> OMNI-F-INVFUNC, Connection is not in a valid state for this omni function,

Explanation: Fatal. The device or Network has aborted or concluded the connection.
User Action: Check physical and network connections to the device.

> OMNI-E-GET-CAPABILITY, Get Capability List Confirm Error,

Explanation: Error. An error occurred when attempting to read device status.
User Action: Check that the device is still running.

> OSAP-E-ASONOTCRE, Association not created,

Explanation: Error. An error occurred when attempting to connect to a device.
User Action: Check local and remote configurations.

Previous | Next | Contents | Index