cc/td/doc/product/voice/uone/srvprov/r42s
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Software Log File Messages Descriptions

Software Log File Messages Descriptions

The Software (Sof) log message tables in this Appendix are divided into the following five sections:

Within each of these sections, messages are grouped by severity:

Debug and Informational messages should normally be turned off. The Quick Configuration tool configures them off automatically. To configure logging refer to the uOne Gateserver Installation and Configuration Manual. To dynamically change logging see "Working with uOne Log Files" in this document.


Note   Debug and CMA informational messages are intended only for developer lab debugging. You should not use debug or CMA informational logging in a production environment. File system overflow and severe performance degradation may result otherwise.

ACB Messages


Table A-1: ACB —API Messages
Message Body Description Action

API,
API 1.0

%s

General API message commonly used for tracing or indicating the initialization of one logging API.

None.


Table A-2: ACB—Debug Messages
Message Body Description Action

com_debug, Debug 1.0

%s

This message is used by developers to embed debugging messages in the code.

None.

com_end,
Debug 1.0

Complete execution of:%s

Provides general information about object processing; used in initialization and termination dispatch routines to identify what processing has occurred.

None.

com_parm,
Debug 1.0

Input initialization parm%s is%s

Displays input parameter during the initialization phase; allows a user to see what was set as the object's operational parameters.

None.

com_start,
Debug 1.0

Starting execution of:%s

Provides general information about object processing. It is used in initialization and termination dispatch routines to identify what processing has occurred

None.

com_unknownparm
Debug 1.0

Unknown Keyword %s line %d, in file %s

Issued during initialization when an input scanner routine cannot determine a valid parameter for a specified keyword.

Remove/correct the appropriate keyword, or contact TAC.


Table A-3: ACB—Error Messages
Message Body Description Action

app_badparmlen,
Error 1.0

Keyword %s detected %s as bad as it is longer than %d characters 

A parameter value of invalid length was passed to the parse routine which terminated the startup on the line being processed and the message is issued to the log.

Reduce the length of the parameter value.

app_execerr,
Error 1.0

ERROR: Abnormal termination detected for %s, pid: %d, RetVal: %d

This message will display for a number of reasons. Two possibilities: The file exists, but could not be executed, or the program returned a non-zero value (indicating an error in the UNIX environment).

Use the return value to determine why the file could not be executed and correct the problem.

app_GenErr
Error 1.0

%s

A general error message used for free-form error messages.

Dependent on error message content.

app_invalidparm,
Error 1.0

File %s,  line %d:  Invalid %s  provided  (%s)

An invalid parameter value was presented to the parse routine. This condition terminated the startup on the line being processed. The message is issued to the log.

If an parameter is not set correctly, reset it to a desired value.

app_nopgm,
Error 1.0

ERROR: Unable to execute scheduled program %s, (%d-%s)

The system call stat() failed for the scheduled program.

Use the supplied error code string; check the scheduled program path and check the existence of an executable file for that path. Correct the problem.

app_numparm,
Error 1.0

File %s,  Line %d:  Keyword %s  expects %d parameters.

Indicates that the incorrect number of parameters were passed to the parse routine in the specified input file at the specified line. This condition made it impossible to evaluate the value for that keyword. The message is issued to the log.

If an attribute is not set correctly, reset it to a desired value.

app_statictime,
Error 1.0

File %s, line %d:  Schedule times do not apply to Static Application.

The schedule file specifies the time range for a Static Application.

Specify * for the Start Time and the End Time for a Static Application.

CmdGenErr
Error 1.0

%s

A general error message.

Dependent on error message content.

com_API,
Error 1.0

API: %s Failed to %s, RTNCD= %d, STATCD= %d

API routine failed.

Correct problem and reissue the call.

con_datatype
Error 1.0

Unknown UTLXDR data type %d

A query to UTLXDR failed to find the translation function for the given data type (unknown).

Correct the incorrect data type or provide the translation function.

com_E_DSERV_Lkup
Error 1.0

UTLDSERV Lookup, Token %s Object %s(%d) %s 

A domain services lookup for the token and type listed has been requested. The token and object type are not found in the domain services table or an error has occurred.

Add the missing entry to the table or contact TAC.

com_errfile,
Error 1.0

ERROR: Could not locate file: %s

An attempt to open a file failed.

Determine why the file could not be opened and correct the problem.

com_errline,
Error 1.0

ERROR: Found on line %d, in file %s

Issued during initialization when an input scanner routine cannot determine a valid parameter for a specified keyword.

Determine what is wrong with the value and correct the problem.

com_error
Error 1.0

%s

A general error message used for free-form error messages.

Dependent on error message content.

com_Eutilmsg,
Error 1.0

UTIL: %s CMD: %s RC: %s SC: %s SM: %s

Issued for all SP internal utilities to provide diagnostics for utility failures.

UTIL = Name of the utility.

CMD = Command mnemonic.

RC = Last known return code.

SC = Last known status code.

SM = Service message defined by the service. 

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.

com_GenErr
Error 1.0

%s

A general error message used for free-form error messages.

Dependent on error message content.

com_initerr,
Error 1.0

%s object stopped normal processing in module %s

Object initialization failure.

Gather the logging messages for the object that issued the message and contact TAC.

com_invalidparm,
Error 1.0

Keyword %s detected %s as an invalid parameter

Invalid parameter was presented to the parse routine. This condition terminated the startup on the line being processed and the message was issued to the log.

If a parameter is not set correctly, reset it to the desired value.

com_netreject,
Error 1.0

CMD:(%i) Host:(%s) process:(%i) is unknown to Object (%s)

Issued by an object when a message is sent to the server interface, but is unknown to the object

Determine why the message was sent to the object and correct the error.

com_numparm,
Error 1.0

Keyword %s expects %i parameters

This message indicates the number of incorrect parameters that were passed in the input file to the parse routine. This condition terminates startup on the line being processed and the message is issued to the log.

If an attribute is not set correctly, reset it to the desired value.

com_parmerr,
Error 1.0

Keyword %s line %d, in file %s

Issued during initialization when an input scanner routines cannot determine a valid parameter for a specified keyword.

Remove/correct the appropriate keyword.

com_rejmsgdata,
Error 1.0

Data: TotalLen(%i) hex(%s)

The OBJ_TransmitParms message rejected the remaining portion of the message. Up to 50 bytes of data are displayed in hex. If less than 50 bytes exist, only those bytes are displayed.

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.

com_rejmsghead,
Error 1.0

SubSource(%i) SubDest(%i) Host(%s) Trace(%c) ObjType(%i)

A message was rejected because it was not recognized. The message is formatted and discarded.

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC

com_rejmsgnxt1,
Error 1.0

ReqId(%i) SerId(%i) Ver(%i) Handle(%g) TranNumber(%i)

The OBJ_TransmitParms message rejected the header file. A message was rejected because it was not recognized. The message is formatted and discarded.

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.

com_rejmsgnxt2,
Error 1.0

OpReturn(%i) OpStatus(%i) User1(%i) User2(%i) EventOrCmd(%d)

The OBJ_TransmitPams message rejected the remaining portion of the message. Up to 50 bytes of data are displayed in hex. If less than 50 bytes exist, only those bytes are displayed.

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.

com_syserr,
Error 1.0

ERROR: System Call %s failed, System error number = %i

This message is issued by internal Objects when a UNIX system call attempt fails. It indicates the failure of the UNIX kernel to provide a critical service to the SP object code.

Gather the logging messages for the object which issued the message and contact TAC.

com_syserrstr,
Error 1.0

System Call %s failed, error = %s

This message is issued by internal SP objects when a UNIX system call attempt fails. It indicates the failure of the UNIX kernel to provide a critical service to the object code.

Gather the logging messages for the object that issued the message and contact TAC.

com_threrr,
Error 1.0

Thr Err: Mod[%s] Ln[%d] Thr[%d] RC[%d] SC[%d] Msg[%s] Host[%s] Obj[%s]

New message utility failure; a critical error has been generated by a thread.

Mod = Name of the module.

Ln = Line number (LineNumber).

Thr = Thread ID (ThreadId).

RC = Last known return code.

SC = Last known status code.

Msg = Service message defined by the service

Host = Host name. 

Obj = Object name. 

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.

com_vererr,
Error 1.0

(%s) %s is invalid with (%s) at level %s

The first component (in brackets) had a version/release mismatch when compared with the second component (in brackets). The version, release, and modification level is printed for visual verification. 

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.


Table A-4: ACB—Informational Messages
Message Body Description Action

app_GenInfo
Informational 1.0

%s

A general informational message used for free-form error messages.

None.

app_IstaticExit, Informational 1.0

Static Application (%s) exited %d time(s).

Static Application exited specified number of times.

Find out why the static application goes down so many times and try to correct it.

app_I_noReStart, Informational 1.0

Do not restart Application (%s) due to reload of schedule table.

Static Application is not reloaded due to reload of the schedule table.

If needed, add this application back to the schedule table and reload.

app_nostart
Informational 1.0

Instance (%) token (s) set to no restart.

Instance set to no restart due to APP_EVENTORCMDID_NOSTART. Instance cannot be started due to no restart command

If needed, send RESTART command.

com_GenInfo
Informational 1.0

%s

A general informational message.

None.

com_init
Informational 1.0

Init/Term: %s

This message provides general information about object processing. It is used in initialization and termination dispatch routines to identify what processing has occurred.

None.

com_log,
Informational 1.0

Local Logging for file[%s] - %s

This message provides general information about the local Logging subsystem. It is issued when a local log dataset gets started and ended. The parameter (RollOver) affecting this is in Attrib.Global. It specifies the amount of time in hours that the logs should remain open.

None.

com_Iutilmsg, Informational 1.0

UTIL: %s CMD: %s RC: %s SC: %s SM: %s

This message is issued for all SP internal utilities to provide diagnostics for utility failures.

UTIL = Name of the utility.

CMD = Command mnemonic.

RC = Last known return code.

SC = Last known status code.

SM = Service message defined by the service. 

None.

com_shut,
Informational 1.0

Normal shutdown requested for %s Object

This message is issued when a shutdown order is recognized.

None.


Table A-5: ACB—Warning Messages
Message Body Description Action

app_badreload,
Warning 1.0

Cannot Reload the Groups and Tokens file - %s

An error occurred in the reloading of the groups and tokens file.

Verify the syntax and attributes in the groups and tokens files.

app_badtime,
Warning 1.0

Cannot start appl for token %s at %2d:%2d hrs - Out of Scheduled hours

An attempt was made to start an application instance outside of its scheduled.

Verify the start and stop times for the application instance.

app_GenWarn
Warning 1.0

%s

A general warning message used for free-form error messages.

Dependent on warning message content.

app_maxGrpInst, Warning 1.0

Cannot start for token (%s); Already running Max Inst under Group %s

Attempted to start an instance while running the maximum number maximum of group instances (a configurable parameter).

Increase the maximum group instances value.

app_maxInst,
Warning 1.0

Cannot fire instance for token (%s); Already running MaxInstances(%d)

Attempted to start an instance while running the maximum number of instances (a configurable parameter).

Increase the MaxInstances attribute value after looking at the schedule file.

app_quiesceInst,
Warning 1.0

Cannot fire Instance for token (%s); App object in QUIESCE state.

Attempted to start an instance after APP object has been put into QUIESCE.

Retry the start instance after the APP object state has been changed.

app_WstaticExit
Warning 1.0

Static Application (%s) exited (%d) times(s).

Static Application exited the number of times specified in StaticAppRetryCount configuration parameter.

Increase the Max Group Instances value in Attrib.hostname or Attrib.global for APP.

com_GenWarn
Warning 1.0

%s

A general warning message used for free-form error messages.

Dependent on warning message content.

com_syswarn,
Warning 1.0

WARNING: System Call %s returned error number = %d

Issued by internal objects when a UNIX system call attempt fails UNIX kernel failed to provide a service to the object code. The service, while needed by the object code, was not considered critical. These messages can occur for such things as fork() failures. 

Examine the message to determine if UNIX kernel tuning parameters can be adjusted to prevent the error. These messages should be forwarded to your system administrator in order to determine if any system tuning actions can be undertaken. 

com_warnfile,
Warning 1.0

WARNING: Could not locate file: %s

An attempt to open a file failed.

Determine why the file could not be opened and correct the problem.

com_W_DSERV_Lkup
Warning 1.0

UTLDSERV Lookup, Token %s Object %s(%d) %s 

A domain services lookup for the token and type listed has been requested. The token and object type are not found in the domain services table or an error has occurred.

Add the missing entry to the table or contact TAC.

com_Wutilmsg,
Warning 1.0

UTIL: %s CMD: %s RC: %s SC: %s SM: %s

This message is issued for all internal utilities to provide diagnostics for utility failures.

UTIL = Name of the utility.

CMD = Command mnemonic.

RC = Last known return code.

SC = Last known status code.

SM = Service message defined by the service. 

Determine why the host rejected the message and correct the problem. If you are unable to correct the problem, collect the information written to the log and contact TAC.

General Application/API Messages


Table A-6: General Application/API—Debug Messages
Message Body Description Action

app_GenDebug
Debug 1.0

%s

A general debug message.

None.

tntapi_GenDebug
Debug 1.0

%s

A general TNT api debug message.

None.


Table A-7: General Application/API—Error Messages
Message Body Description Action

app_GenErr
Error 1.0

%s

A free form general error message.

Dependent on the error message content.

app_imaplogin,
Error 1.0

IMAP login failure for user %d on server %s.

Messaging server is down

or

A subscriber attempted to access his or her mailbox, but the login failed.

Check the operation of the messaging server.

Check to ensure data in the subscriber profile is valid.

app_ldapbind,
Error 1.0

machine:  %s running slapd at %d has %s problem.

An invalid DN or password was used.

Check the subscriber profiles on the directory server for invalid data.

app_ldapopen,
Error 1.0

machine:  %s running slapd at %d has %s problem for %s account.

An invalid host name or port number was used.

or

The directory server is down

Check the operation of the directory server.

pag_connect,
Error 1.0

Unable to connect to the Paging server %s on port %d

The SNPP paging server is down.

Start the SNPP paging server and try to telnet to the port (e.g.., 444)

tntapi_GenErr
Error 1.0

%s

A free form TNT api error message.

Dependent on the error message content.


Table A-8: General Application/API—Informational Messages
Message Body Description Action

app_GenInfo
Informational 1.0

%s

A general informational message.

None.

tntapi_GenInfo
Informational 1.0

%s

A general TNT api informational message.

None.


Table A-9: General Application/API—Warning Messages
Message Body Description Action

app_GenWarn
Warning 1.0

%s

A general warning message.

Dependent on the warning message content.

tntapi_GenWarn
Warning 1.0

%s

A general TNT api warning message.

Dependent on the warning message content.

UM Application Messages


Table A-10: UM Application—Debug Messages
Message Body Description Action

UM_debug
Debug 1.0

%s

A general debug message.

None.


Table A-11: UM Application—Error Messages
Message Body Description Action

UM_error
Error 1.0

%s

A free form general error message.

Dependent on the error message content.

UM_inimissing
Error 1.0

ini File missing

Indicates that the .ini file specified in the schedule table doesn't exist in the $PARMLIB/apps/UM directory

Ensure that the .ini files that is specified in the schedule file exists in the $PARMLIB/apps/UM directory.


Table A-12: UM Application—Informational Messages
Message Body Description Action

UM_info
Informational 1.0

%s

A general informational message.

None.


Table A-13: UM Application—Warning Messages
Message Body Description Action

UM_noiniinSch
Warning 1.0

ini File not specified in the Schedule file.

Indicates that the .ini file is not specified in the schedule file.

Ensure that the correct .ini file is specified in the Schedule file. Otherwise, the default .ini file, <APP_NAME>.ini, will be used in its place.

UM_warn
Warning 1.0

%s

A general warning message.

Dependent on the warning message content.

MWI_Notify Application Messages


Table A-14: MWI_Notify Application—Debug Messages
Message Body Description Action

mwinotify_debug
Debug 1.0

%s

A general debug message.

None.


Table A-15: MWI_Notify Application—Error Messages
Message Body Description Action

mwinotify_err
Error 1.0

%s

A free form general error message.

Dependent on the error message content.


Table A-16: MWI_Notify Application—Informational Messages
Message Body Description Action

mwinotify_info
Informational 1.0

%s

A general informational message.

None.


Table A-17: MWI_Notify Application—Warning Messages
Message Body Description Action

mwinotify_warn
Warning 1.0

%s

A general warning message.

Dependent on the warning message content.

MWI_OnOff Application Messages


Table A-18: MWI_OnOff Application—Debug Messages
Message Body Description Action

mwinonoff_debug
Debug 1.0

%s

A general debug message.

None.


Table A-19: MWI_OnOff Application—Error Messages
Message Body Description Action

mwinonoff_err
Error 1.0

%s

A free form general error message.

Dependent on the error message content.


Table A-20: MWI_OnOff Application—Informational Messages
Message Body Description Action

mwinonoff_info
Informational 1.0

%s

A general informational message.

None.


Table A-21: MWI_OnOff Application—Warning Messages
Message Body Description Action

mwinonoff_warn
Warning 1.0

%s

A general warning message.

Dependent on the warning message content.

Status Codes

The following table shows status codes and mnemonics generated by the uOne system along with descriptions. Those messages that are API specific are noted with an X in the right-hand column of the table. You can often pinpoint your problems to a particular subsystem or operation by determining the mnemonic associated with a status code seen in a log file.


Table A-22: uOne Status Codes
Code Mnemonic Description API Specific

4601

SP_STAT_BADPARM

The expected parameters were not passed or the parameter string format is bad.

AINAcceptBind - The pUserData parameter does not have the requesting application's address.

AINBind - The pSpAddr parameter is not valid.

AINStartApp - Improper token data passed in the pUserData parameter.

AINUnbind - An invalid ComHandle value was passed in pUserData parameter.

X

4602

SP_STAT_BADCOM

AINReply, AINRequest AINUnbind - The entry for this ComHandle could not be located in internal table.

X

4603

SP_STAT_INTERROR

Error reading/writing the data portion of the files.

4605

SP_STAT_SERVFAIL

The data length exceeds the maximum allowable transmission size for this operation.

4609

SP_STAT_NETDOWN

Could not send reply to the client instance.

4611

SP_STAT_NORESOURCE

Insufficient storage to malloc.

AINStartApp - The maximum number of instances are running for either the specified group, or under the ALO.

X

4612

SP_STAT_NOPROGRAM

AINStartApp - No corresponding program was found for the passed token.

X

4615

SP_STAT_APITIMEOUT

AINRequest - Synchronous API call timed out without getting a reply.

X

4616

SP_STAT_INTERRUPT

AININIT - The process has received the TERMINATE indication from APP object.

X

4622

SP_STAT_LOSTCOM

Communications were lost.

4623

SP_STAT_NOSTATUS

No status is the default. No other information was provided to override this default.

4628

SP_STAT_BUSYCOM

This communications session is busy executing previous API.

7401

SSIO_STATUS_ALREADYREGISTERED

The subsystem that is attempting to register with SSIO is already registered.

7402

SSIO_STATUS_BADCOMMAND

The Event or command ID that is being attempted is not known to UTLSSIO.

7403

SSIO_STATUS_BADLENGTH

Attempting to allocate a buffer larger than the maximum buffer size.

Subscriber attempting to output a message larger than the maximum buffer size.

7404

SSIO_STATUS_BUSY

The subsystem for this message already has the maximum number of messages queued.

7405

SSIO_STATUS_INTERR

SSIO internal error. Notify TAC.

7406

SSIO_STATUS_INVALIDOBJECT

Not a valid object type for this request.

7410

SSIO_STATUS_NOMEMORY

Insufficient area in SSIO file for:

Registering a subsystem; or

Allocating a data buffer.

7411

SSIO_STATUS_NOMESSAGE

No message available for a GetMessage attempt

Event or command ID requires input data but none present.

7413

SSIO_STATUS_NOSIO

SSIO file was initialized.

7415

SSIO_STATUS_NOTNOW

Maximum number of subsystems already registered; subscriber cannot register now.

7416

SSIO_STATUS_NOTREGISTERED

Subscriber attempting to deregister a subsystem that is not registered.

7417

SSIO_STATUS_OK

Event or command ID is successful.

7419

SSIO_STATUS_SYSERR

UNIX system calls error. Notify TAC.

8201

SIOF_STATUS_ALLOCFAIL

NT allocation failure in UTLSIOF.

8202

SIOF_STATUS_ALREADYREGISTERED

Status returned to subscriber when 7401 is returned to UTLSIOF from UTLSSIO.

8203

SIOF_STATUS_BADCOMMAND

The event or command ID that is being attempted is not known to UTLSIOF.

8204

SIOF_STATUS_BUFTOOLARGE

Attempting to allocate a buffer larger than maximum buffer size.

8205

SIOF_STATUS_FIFOEMPTY

No messages available matching the selection criteria.

8206

SIOF_STATUS_LLMGRFAIL

Failure of any of a number of calls to the UTLLLMGR (Utility Link List Manager) utility.

8207

SIOF_STATUS_NOSTATUS

Event or command ID is successful.

8208

SIOF_STATUS_NOTAVAILABLE

Status returned when status 7414 is returned to UTLSIOF from UTLSSIO.

8209

SIOF_STATUS_NOTREGISTERED

Subscriber attempting certain commands before subsystem is registered.

8210

SIOF_STATUS_SSIOFAIL

Certain SSIO commands from UTLSIOF failed.

Developer Status Codes

The following Status Codes are either self-explanatory, or are used by developers for debugging.


Table A-23: Developer Status Codes
Code Mnemonic Code Mnemonic

4604

SP_STAT_BADFORMAT

10210

DSERV_STATUS_ALREADYREG

4605

SP_STAT_DATATOOLONG

10211

DSERV_STATUS_NOTREGISTERED

4606

SP_STAT_NOREG

10212

DSERV_STATUS_NOKEYWORDS

4608

SP_STAT_SERVOFF

10213

DSERV_STATUS_NULLUSERAREA

4610

SP_STAT_FORKFAILED

12100

SERV_STATUS_ALREADYREG

4613

SP_STAT_MAXGROUP

12101

SERV_STATUS_NOTREGISTERED

4614

SP_STAT_XDRFREE

12102

SERV_STATUS_INVALIDCMD

4921

AIN_BSERV_STAT_UNKNOWN

12103

SERV_STATUS_NOFUNCTION

4922

AIN_BSERV_STAT_NOTFOUND

12104

SERV_STATUS_NOTRANSPORT

4923

AIN_BSERV_STAT_INTERNAL

12105

SERV_STATUS_NOTCP

4617

SP_STAT_FIRSTDATA

12106

SERV_STATUS_VALIDFAILED

4618

SP_STAT_NEXTDATA

12107

SERV_STATUS_VALIDERROR

4619

SP_STAT_ENDOFDATA

12108

SERV_STATUS_RESULTFAILED

4620

SP_STAT_ONLYDATA

12109

SERV_STATUS_XDRFREE

4621

SP_STAT_INVALIDATTRID

12110

SERV_STATUS_NOFDSET

4626

SP_STAT_INVALIDATTRVALUE

12111

SERV_STATUS_UNKNOWN

4627

SP_STAT_INVALIDINSTANCE

12112

SERV_STATUS_XDRINFAILED

4629

SP_STAT_INVALIDVERSION

12113

SERV_STATUS_RUNNING

4630

SP_STAT_NOPTFUNC

12114

SERV_STATUS_NOSUPPORT

4631

SP_STAT_MAXINSTANCES

13201

COMH_STATUS_NOREG

4920

AIN_BSERV_STAT_NOTREGISTERED

13202

COMH_STATUS_INTERNAL

7414

SSIO_STATUS_NOTAVAILABLE

13203

COMH_STATUS_NOHOST

9200

LIST_STATUS_NOCNTL

13204

COMH_STATUS_INVALIDCMD

9201

LIST_STATUS_TOOLITTLE

13205

COMH_STATUS_ALREADYREG

9202

LIST_STATUS_TOOMUCH

13206

COMH_STATUS_NOTREGISTERED

9203

LIST_STATUS_INVALIDCMD

15104

LOG_STATUS_NOTRANSPORT

9204

LIST_STATUS_LISTEMPTY

15105

LOG_STATUS_NOTREGISTERED

9205

LIST_STATUS_LISTEND

15106

LOG_STATUS_LOGINFOFAILED

9206

LIST_STATUS_ALLOCFAIL

22101

XDR_STATUS_NOSTATUS

9207

LIST_STATUS_BADBUFR

15101

LOG_STATUS_HAVEREGISTERED

9208

LIST_STATUS_NOGET

15102

LOG_STATUS_ALREADYREG

9209

LIST_STATUS_NOTEMPTY

15103

LOG_STATUS_INVALIDCMD

10201

DSERV_STATUS_NOSTATUS

22109

XDR_STATUS_NOTFOUND

10202

DSERV_STATUS_NOSERVICE

22110

XDR_STATUS_NOMEMORY

10203

DSERV_STATUS_INVALIDOBJECT

22111

XDR_STATUS_BADLENGTH

10204

DSERV_STATUS_NOTENOUGHPARMS

22102

XDR_STATUS_NOSYMBOL

10205

DSERV_STATUS_LISTERROR

22103

XDR_STATUS_REGISTERED

10206

DSERV_STATUS_INVALIDCMD

22105

XDR_STATUS_INVALIDCOMMAND

10207

DSERV_STATUS_NOUSERDATA

22106

XDR_STATUS_BADXDRTYPE

10208

DSERV_STATUS_NOINDEXHOST

22107

XDR_STATUS_INTERNAL

10209

DSERV_STATUS_NOHOSTOBJECT

22108

XDR_STATUS_NOTZERO


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Sep 25 20:12:33 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.