NonStop™ ODBC Server Messages Manual Abstract This manual documents the error and warning messages that can occur during the execution of the NonStop™ ODBC Server. It includes event messages reported to $0 (or the default collector) that can be interpreted by the Event Management Service (EMS). Product Version NonStop ODBC Server, Release 2.0 Supported Releases N.A. Part Number Published 429394.
Document History Part Number Product Version Published 120562 NonStop ODBC Server D42 August 1996 130620 NonStop ODBC Server 2.0 November 1996 133119 NonStop ODBC Server 2.0 June 1997 422975-001 NonStop ODBC Server 2.0 September 1999 429394.001 NonStop ODBC Server 2.0 May 2001 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative.
NonStop ODBC Server Messages Manual Glossary Index Figures Tables What’s New in This Manual iii Manual Information iii New and Changed Information iii About This Manual v Audience v NonStop ODBC Message Sources v Related Manuals vi Your Comments Invited vii Notation Conventions vii 1. NonStop™ ODBC Server Messages Messages Displayed on the Workstation 1-1 Message Format 1-1 Event Messages 1-68 2.
Figures Contents Figures Figure 1-1. Message Generated by the NonStop™ ODBC Server and Displayed on the Workstation 1-2 Figure 1-2. Message Sent by NonStop™ ODBC Server to $0 1-68 Figure 2-1. Message Generated by SCS and Reported Using EMSDIST 2-2 Tables Table 1-1. NonStop™ ODBC Server Event Messages Table 2-1. SCS Event Messages 1-68 2-3 NonStop ODBC Server Messages Manual—429394.
What’s New in This Manual Manual Information NonStop ODBC Server Messages Manual Abstract This manual documents the error and warning messages that can occur during the execution of the NonStop™ ODBC Server. It includes event messages reported to $0 (or the default collector) that can be interpreted by the Event Management Service (EMS). Product Version NonStop™ ODBC Server, Release 2.0 Supported Releases N.A. Part Number Published 429394.
What’s New in This Manual New and Changed Information NonStop ODBC Server Messages Manual—429394.
About This Manual The NonStop™ ODBC Server allows applications to use the Microsoft ODBC interface, Microsoft SQL Server interface, or Sybase SQL Server interface to access a NonStop SQL/MP database. This manual documents the error and warning messages that can occur during the execution of the NonStop ODBC Server. It includes event messages reported to $0 (or the default collector) that can be interpreted by the Event Management Service (EMS).
Related Manuals About This Manual • DOS DBLIB clients can return the following error message if a client times out while waiting for a server process or if the primary SCS process fails when a data transfer is in progress: DB-LIBRARY: SQL Server connection failed.
Your Comments Invited About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
Notation for Messages About This Manual NonStop ODBC Server Messages Manual—429394.
1 NonStop™ ODBC Server Messages This section lists messages generated by the NonStop™ ODBC Server. It describes both messages that are displayed on the workstation and event messages that are logged to $0 (or the default collector). Messages Displayed on the Workstation This subsection lists in numeric order the messages that are generated by the NonStop™ ODBC Server and displayed on the workstation.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages Figure 1-1. Message Generated by the NonStop™ ODBC Server and Displayed on the Workstation SQL Server Message Number NonStop ODBC Server Message Number 1> create table my_files (filename char (12), filecode binary) 2> go Msg 18001, Level 15, State 1: ODBC Server message (32035) : The data type BINARY is not valid or not supported. 1> 002 32000 Invalid user name user-name. Cause.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32004 Invalid TDS inout token: token. Cause. An internal error occurred. Effect. The statement or batch of statements fails. Recovery. Contact your service provider. 32005 Invalid TDS inout status: status. Cause. An internal error occurred. Effect. The statement or batch of statements fails. Recovery. Contact your service provider. 32006 feature is not supported. Cause. The feature indicated in feature is not supported. Effect.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32009 Internal error: The message is not from the client. Cause. An internal error occurred. Effect. The statement or batch of statements fails. Recovery. Contact your service provider. 32010 Syntax error near statement. Cause. The statement contains a syntax error or unsupported feature. Effect. The statement or batch of statements fails. Recovery. Correct the statement or remove the unsupported feature from the statement.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32014 Cannot convert data type data-type. Cause. The requested data type conversion is not supported. Effect. The statement fails. Recovery. Correct the statement or remove the unsupported request. 32015 A data value (character or numeric) was truncated. Cause. While accessing an object created by NonStop™ SQL/MP, data was truncated while being converted to an ODBC/SQL Server data type. Effect. The data is truncated. Recovery. None.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. DB-Library must be fixed. Contact your Microsoft SQL Server representative if you have one; otherwise, contact your service provider. 32019 Client error: Invalid floating number format. Cause. DB-Library specified an incorrect floating point number during login. The NonStop™ ODBC Server supports only IEEE floating point format. Effect. The login fails. Recovery. Reconfigure DB-Library to use IEEE floating point format.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32023 Cannot find system catalog in subvolume. Cause. The system catalog is either missing or cannot be opened. For example, another user has opened the system catalog in exclusive mode. Effect. The NonStop™ ODBC Server terminates. Recovery. Try logging on again when the system catalog is available. 32024 Internal error: Cache error. Cause. An internal error occurred while opening the system catalog. Effect.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages Effect. The statement or batch of statements fails. Recovery. Declare the variable before referencing it. 32028 Transaction name transaction-name does not exist. Cause. On a ROLLBACK TRANSACTION statement, a transaction name was specified that does not match the transaction name specified in the previous BEGIN TRANSACTION statement. Effect. The transaction is rolled back. Recovery. None; this is a warning message only.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32032 Cannot assign incompatible data. Cause. The statement specified an incompatible value for this field. For example, an integer value was assigned to a character field. Effect. The statement fails. Recovery. Correct the statement to assign a compatible value. 32033 An internal error occurred during expression evaluation. Cause. An overflow occurred while processing a variable. Effect. The statement fails. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32037 option is not a valid CREATE INDEX option. Cause. An unsupported clause was specified on a CREATE INDEX statement. Effect. The statement or batch of statements fails. Recovery. Remove the unsupported clause. 32039 For DROP INDEX, you must give both the table and the index name in the form table-name.index-name. Cause. The table name is required but was omitted. Effect. The statement or batch of statements fails. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32043 OPEN failed on process. Cause. A process creation error occurred while the NonStop™ ODBC Server was starting another process. Effect. The statement fails. Recovery. Try executing the statement again. If it fails repeatedly, contact your service provider. 32045 RUN error: System not found. Cause. The RUN statement specified a nonexistent system. Effect. The statement fails. Recovery. Specify a valid system name.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages Recovery. Specify a valid priority. 32049 RUN error: MEM memory-address out of range. Cause. The RUN statement specified an invalid memory range. Effect. The statement fails. Recovery. Specify a valid memory range. 32050 RUN internal error: error. Cause. An internal error occurred. Effect. The statement fails. Recovery. Try executing the statement again. If it fails repeatedly, contact your service provider.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Correct the statement to assign only nonnull values to variables. 32054 date-part is not a recognized date part. Cause. An incorrect or unsupported date part was specified. Effect. The statement or batch of statements fails. Recovery. Correct the statement to include only correct or supported date parts. 32055 Fatal mapping error. Cause. An internal error occurred. Effect. The NonStop™ ODBC Server stops. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Correct the statement to create an index that does not already exist. 32059 Cannot drop the index index-name because it does not exist. Cause. Either the statement referenced an index that does not exist, or the index is not registered in the NonStop™ ODBC Server mapping tables. Effect. The statement fails. Recovery. If the index does not exist, correct the statement to reference an existing index.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages Recovery. If the table or view does not exist, correct the statement to reference an existing table or view. If the table or view exists but for some reason is not registered in the mapping tables, you can execute the REFRESH statement. 32063 Invalid object name: database-name. Cause. The specified database name is invalid, does not exist, or is not customized.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32067 The variable variable-name is NULL. Cause. You cannot reference a null variable. Variables are null when they are declared. Effect. The statement fails. Recovery. Before you reference the variable, assign a value to it. 32070 NOS-NOSUTIL communication error: error. Cause. A communication error occurred while NOSUTIL was processing a request from the NonStop™ ODBC Server (for a pass-through utility command, for example). Effect.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32113 Object mapping error: Retry failed. Use another name. Cause. In creating a database, table, view, or index, the NonStop™ ODBC Server could not create a mapping table entry for the specified object. For example, if you are creating a table named TAB1 and other users have also created tables named TAB1 in this database, the NonStop™ ODBC Server must map your table to a different name.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32118 User name user-name does not exist. Cause. When creating an object, a nonexistent owner name was specified. Effect. The statement fails. Recovery. Correct the statement to specify an existing owner name. 32119 statement failed. Error code = error-code. Cause. An internal error occurred while processing trace information. Effect. The statement fails. Recovery. Analyze the error code for this operation.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32122 Trace MODE has been turned off. continues. However, processing Cause. Other messages will accompany this error message. To determine the cause of this message, examine the other messages. Effect. No trace information is logged. Recovery. Correct the problem indicated in the accompanying messages and reset MODE to ON. 32125 Trace log table could not be created; however, processing continues. Cause.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32128 RUN command error: Bad file name file-name. Cause. The RUN command specified an invalid file name Effect. The statement fails Recovery. Specify a valid file name 32129 RUN command error: Bad file code. Cause. The RUN command specified an invalid file code Effect. The statement fails Recovery. Specify a valid file code 32130 RUN command error: File file-name does not exist. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Correct the problem and execute the statement again. 32133 TRACE parameter parameter-name syntax error. Cause. A syntax error occurred during a trace statement. Effect. The statement fails. Recovery. Correct the problem and execute the statement again. 32134 TRACE command command will be effective only after the next TRACE SET MODE = ON. Cause. The requested TRACE command takes effect after the next TRACE SET MODE = ON.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32137 TRACE command statement is not allowed when MODE = ON. Cause. A DROP LOG statement was executed when MODE was set to ON. Effect. The statement fails. Recovery. Set MODE to OFF, then execute the DROP LOG statement again. 32138 TRACE command statement is ignored within the current user transaction. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32141 TRACE error: No log file found for command command. Cause. The log table name was not set. For example, no log table name was set and the DISPLAY_LOG, CLEAR_LOG, or DROP_LOG statement was executed Effect. The statement fails Recovery. Set the LOG_TABLE before executing the statement 32142 Changed database context from 'value-1' to 'value-2'. Cause. A USE DATABASE statement was executed, changing the current database. Effect.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Change the buffer size to a value between 512 and 8192 bytes. 32146 Cannot create named pipe pipe-name. Cause. The NonStop™ ODBC Server is unable to communicate with SCS because of a communication error. Effect. The login fails. Recovery. Check the SCS configuration file and the communication connection, then try logging on again. 32147 Cannot connect named pipe pipe-name. Cause.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32150 Object mapping internal error: Validate catalog catalog-name. Mapping failed on object. Cause. While creating an object, an internal error occurred, resulting in an inconsistent state. Effect. The statement fails. Recovery. Execute the REFRESH statement against the catalog named in ctatlogname, then re-execute the statement that failed. 32151 Object mapping internal error: Cannot find mapping for object. Validate catalog catalog.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32154 Invalid column name column-name. Cause. The SELECT statement lists column names but is missing the FROM clause. Effect. The statement fails. Recovery. Correct the statement, making sure it includes a FROM clause. 32155 Syntax error encountered. Cause. A syntax error occurred in the statement. Effect. The statement fails. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Correct the format of the object name. 32159 The table name contains more than the maximum number of prefixes. The maximum is 2. Cause. The format for the specified table name is incorrect. Effect. The statement fails. Recovery. Correct the format of the table name. 32160 A subquery is not allowed in a select list. Cause. Stated in the error message. Effect. The statement or batch of statements fails. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32166 Missing statement name in pass-through RELEASE statement. Cause. The RELEASE statement is missing the statement name, which is required. Effect. The statement fails. Recovery. Correct the statement to include a statement name. 32167 Syntax error encountered in passthrough PREPARE statement. Cause. The PREPARE statement contains a syntax error. Effect. The statement or batch of statements fails. Recovery. Correct the statement.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Correct the statement to include matching quotation marks. 32172 Log table has been dropped, but the mapping entry remains. Cause. Either a transaction error occurred or there was a problem deleting a record from the mapping table ZNUOBJ. Other messages will accompany this error message. Examine the messages to try to determine the cause of the error. Effect. The log table is dropped; this is a warning message only. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Enter a statement that evaluates to a correct timestamp value. 32184 Invalid Day is entered as TIMESTAMP. Cause. A statement received in pass-through mode evaluated to a timestamp value that contained an incorrect day value. Effect. The statement fails. Recovery. Enter a statement that evaluates to a correct timestamp value. 32185 Invalid Year is entered as TIMESTAMP. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32188 Invalid Second is entered as TIMESTAMP. Cause. A statement received in pass-through mode evaluated to a timestamp value that contained an incorrect second value. Effect. The statement fails. Recovery. Enter a statement that evaluates to a correct timestamp value. 32189 Invalid Millisecond is entered as TIMESTAMP. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32192 Timeout, no activity for n seconds Cause. The workstation client has not submitted work in the last n seconds. Effect. The NonStop™ ODBC Server terminates. Recovery. Check the time-out value in the SCS configuration file. Increase the value if necessary and restart both SCS and the NonStop™ ODBC Server. 32193 Client initiated shutdown of the gateway Cause. The workstation client terminated the connection. Effect.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Effect. The NonStop™ ODBC Server terminates. Recovery. Contact your service provider. 32201 The text of error error-code cannot be accessed in subsystem message file Cause. Internal error. Effect. The NonStop™ ODBC Server terminates. Recovery. Contact your service provider. 32202 Unnamed parameter number parameter-number is not specified in the USING clause. Cause. Stated in the error message. Effect. The statement fails. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32205 Statement must be prepared before this operation. Cause. You must prepare the statement prior to requesting this operation. Effect. The statement fails. Recovery. Prepare the statement first, or use a statement that does not require preparation. 32206 Need to open the cursor before this operation. Cause. You must open the cursor prior to requesting this operation. Effect. The statement fails. Recovery. Open the cursor first.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32209 The login name does not map to a valid user name or an error occurred while reading ZNSALT, ZNSUS or ZNSDB tables. Cause. The login name was invalid, or there was an error in the content or existence of the ZNS tables, or the default database specified for the login name is not a catalog customized for the NonStop™ ODBC Server. Effect. The server does not start. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32213 Attempt to assign or compare NULL to a column which does not allow NULL values. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct the statement so that NULL values are not used in assignments and comparisons to NonStop™ SQL/MP columns that do not allow NULLs. 32214 Try to assign or compare a value data-value with incompatible data type. Cause. Stated in the error message. Effect.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32217 Value-1 exceeds the maximum limit of value-2. Priority has been changed to value-3. Cause. Statement priority exceeded the specified limit. Effect. The priority was changed and the statement continues. Recovery. No recovery is necessary. 32218 Limit was exceeded, and transation has been aborted according to ResGov profile. Cause. Stated in the error message. Effect. The transaction aborts. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Check the length and scale of the data item. 32304 A maximum of 6 decimal places is supported in timestamp values Cause. You specified a timestamp value that is not valid. Effect. The statement fails. Recovery. Check the format and make sure the timestamp has 6 or fewer decimal places. 32306 Invalid SQL command type Cause. Internal error. Effect. The statement fails. Recovery. Contact your service provider.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32309 The value given in the command-name command is out of the legal range or is the wrong syntax Cause. You specified an invalid value for the command. Effect. The command fails. Recovery. Check the syntax and range of the value supplied to the command. 32310 Error %d opening the SQLCS process. Server terminating. Cause. A server could not open the SCS process. Effect. SCS terminates abnormally. Recovery.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 249 Network error, operation terminated abnormally 250 All paths to the system are down 251 Network protocol error 252 Required EXPAND class is not available 255 Net line handler flooded—too many interrupts For information about the format of this type of message, see Message Format on page 1-1. 32311 Server no longer needed by SQLCS. Server Terminating. Cause. SCS no longer needs a server.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32314 I/O-operation-error error. Cause. During the execution of a stored procedure, the NonStop™ ODBC Server encountered an I/O error in its communication with the Pathway server. The I/Ooperation-error entry identifies the I/O operation that failed. Effect. The stored procedure execution fails. Recovery. Verify, by calls to SPELIB routines, the stored procedure side of the interprocess communication and retry the execution.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32318 The stored procedure procedure-name does not exist. Cause. The stored procedure identified by procedure-name either does not exist or is not registered in the NonStop™ ODBC mapping tables. Effect. The statement fails. Recovery. If the stored procedure does not exist, correct the statement to refer to an existing one.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Correct the volume name and retry the command. A valid volume name consists of a dollar sign ($) followed by one to seven alphanumeric characters, the first of which must be a letter. 32322 Invalid subvolume name subvolume-name specified. Cause. The subvolume portion of the database identifier exceeds the maximum length. Effect. The statement fails. Recovery. Correct the subvolume name and retry the command.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32326 Unexpected SPELIB error error-code from procedure procedurename. Cause. SPELIB encountered an error that is not in the range 32450 through 32468, the error numbers of the usual set of SPELIB errors. Effect. The stored procedure execution fails. Recovery. Correct the error identified by error-code and retry the stored procedure execution. 32327 Unsupported TDS type TDS-type. Cause. Internal error. Effect. Depends on error.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32330 User authentication warning: password has expired. Security Administrator to re-enable user/password. See Cause. Your password has expired. Effect. You cannot access the account. Recovery. Contact your security administrator. 32331 Change password failed. Cause. Stated in the error message. Effect. The password is not changed. Recovery. Contact your security administrator.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32334 Invalid high level SQL version: version. Cause. A call to the SQLGETSYSTEMVERSION procedure returned an invalid SQL version of NonStop™ SQL/MP software. Effect. The NonStop™ ODBC server does not try to access the NonStop™ SQL/MP database. Recovery. Check the version of the NonStop™ SQL/MP database and report this problem to your system administrator. 32335 Account log table log-table-name is full. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32451 Buffer is full during SPEIPC encoding. Cause. Stated in the error message. Effect. The stored procedure execution fails. Recovery. Do either of the following: • • Use call-back. If call-back is already being used, correct the maximum buffer length specified in the stored procedure or in ZNUPROC to accommodate each IPC message. 32452 Buffer used for SPEIPC encoding or decoding is too small. Cause. Stated in the error message.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32455 Unknown SQLDA version. Cause. Stated in the error message. Effect. The stored procedure execution fails. Recovery. Ensure that the version of the SQLDA in the stored procedure is supported in the current release. 32456 Unknown SQLCA version. Cause. Stated in the error message. Effect. The stored procedure execution fails. Recovery. Ensure that the version of the SQLCA in the stored procedure is supported in the current release.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Check the calling sequence in the NonStop™ ODBC Server Reference Manual and then correct the calling sequence in the stored procedure. 32460 Invalid address. Cause. Stated in the error message. Effect. The stored procedure execution fails. Recovery. Correct the parameter pointer to give it a valid address before calling SPELIB functions. 32461 Invalid parameter value. Cause. Stated in the error message. Effect.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32464 Invalid sequence number. Cause. Stated in the error message. Effect. The stored procedure execution fails. Recovery. This is an internal error. Contact your service provider. 32465 Cannot open the requestor. Cause. Stated in the error message. Effect. The stored procedure execution fails. Recovery. The NSODBC server process is missing. Contact your service provider. 32466 Cannot write to the requester. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. Check the location in the stored procedure where this error occurs, and report this location to your service provider. 32501 Startup message invalid, argument-list. Cause. An error was detected when parsing the startup message. Effect. The utility program is not started. Recovery. Use HELP command to determine correct syntax. Reissue the command with correct syntax. 32502 Cannot open utility batch file, file-name.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32511 The command command-name cannot be executed because no TMF transaction is currently in progress. FS Error : errnum. Cause. Either NOSUTIL was invoked with INHERITTXN and there was no transaction to assume, or NOSUTIL was unable to start a transaction for the listed command. Effect. The utility program aborts. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32515 Unable to open log file log-file-name. FS Error : errnum. Cause. The designated log file could not be opened for write. Effect. The utility aborts or continues without logging according to profile entry SQL_ERROR_RESPONSE. Recovery. Determine from the subsequent file system error number the actual cause of error for the indicated log file. 32516 Unable to write to log file log-file-name. FS Error : errnum. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32519 Unable to retrieve IMMU message text for error error-code. FS Error : errnum. Cause. NSODBC or NOSUTIL are not successfully installed, or the ODBCMSG version is incorrect. Effect. The command fails. Recovery. Reinstall NSODBC. 32520 User does not have sufficient privileges to execute command command-name. Cause.
Messages Displayed on the Workstation NonStop™ ODBC Server Messages 32523 SQL Statement statement-part-1 statement-part-2 failed. SQLCODE : SQLCODE. FS Error : errnum. Cause. An internal error occurred that resulted in a ROLLBACK. The error occurred on the indicated SQL statement, which returned the SQLCODE and file-system error. Effect. The command fails. Recovery. Determine the cause by examining the SQLCODE and FS errors, and take appropriate action.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32527 REPLY failed. FS Error : errnum. Cause. Stated in the error message. Effect. The command fails. Recovery. Attempt to execute the statement again. If the error re-occurs, use the SQLCODE value and the subsequent file system exception value to determine appropriate action. If the statement fails repeatedly, contact your service provider. 32528 Invalid subvolume name subvolume-name specified. errnum. FS Error : Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Effect. The command fails. Recovery. Correct the command and re-execute. 32533 Invalid parameter parameter-name detected for command command-name. Cause. The argument indicated cannot be interpreted or is invalid for the command. Effect. The command fails. Recovery. Correct the command. 32534 Invalid parameter value parameter-value detected for parameter parameter-name. Cause. Either too many or too few arguments have been supplied.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32537 Catalog catalog-name must be NOS customized before performing command-name. Cause. Stated in the error message. Effect. The command fails. Recovery. Correct the subvolume name and re-execute the command. 32538 Catalog catalog-name must not be NOS customized before performing command-name. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32544 Catalog is not empty. Cause. The request to DEINSTALL failed because either RESTRICT was indicated and there are NonStop™ ODBC objects in the catalog, or CASCADE_NSSQL was indicated and there are NonStop™ SQL objects in the catalog after purging all NonStop™ ODBC objects. Effect. The utility program terminates abnormally. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32571 Catalog integrity violation for object-type object-name. Cause. An error occurred that violates the integrity rules for the NSODBC catalog mapping tables. Effect. The command fails. Recovery. You should be able to determine the recovery based on the SQLCODE and the subsequent file-error code. 32572 Error occurred mapping object-type object logical-name performing command catalog-command. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32575 Object object-type object-username already exists. Cause. Performing an INSERT received an SQLCODE of 0, indicating the object already exists. Effect. The command fails. Recovery. The command can be retried with a corrected object name if it was not a fatal NonStop™ SQL/MP error. 32576 Object object-type object-username not found. Cause. A MODIFY or REMOVE did not find a named object. Effect. The command fails. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32580 Column definition list for ADD PROCEDURE not terminated. Cause. The list of parameters and their descriptions was not properly terminated. Effect. The command fails. Recovery. The command can be retried after fixing syntax. 32583 Unable to start SCS name. FS error errnum. Cause. Could not start the SCS process. Effect. The command fails. Recovery. Check the file system error and correct the error condition.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32587 Invalid IPC messageVersion messageVersion-value. Cause. The message version in the SCS to NOSUTIL IPC message was invalid. Effect. The command fails. Recovery. Reinstall SCS or NOSUTIL to correct message version incompatibility. 32590 Use USERCAT INSTALL to customize user catalogs. Cause. Attempt to use SYSCAT INSTALL on a catalog other than the system SQL catalog. Effect. The utility program terminates abnormally. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Recovery. No recovery is necessary. 32602 ***WARNING. Integrity violation for value-1 value-2 performing command name. Cause. Stated in the error message. Effect. The command completes successfully. Recovery. No recovery is necessary. 32603 system-object-name is a system object. Cause.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32644 UPGRADE must be run to update catalog mapping tables before this command utility-command can be executed. Cause. An attempt was made to REFRESH or VALIDATE a user catalog that is not the latest version, or to add or delete a procedure reference to a catalog whose version predates procedure support. Effect. The command fails to execute. Recovery.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation 32653 Object object-type object-name mapping to value-3 dropped. Cause. The object mapping references a Guardian object that is dropped during a DEINSTALL...CASCADE operation. Effect. The object name is deleted from the mapping tables. Recovery. None. 32654 Object object-name value mapping removed. Cause. Stated in the error message. Effect. The operation completes successfully. Recovery. No recovery is necessary.
NonStop™ ODBC Server Messages Messages Displayed on the Workstation Effect. The command fails. Recovery. The SQL/MP file (table, index, or view) with an owner value that is no longer valid must be deleted or have the ownership value changed before the NOSUTIL command can be rerun. 32687 Use SYSCAT VALIDATE to validate the system catalog. Cause. Attempted to use the USERCAT VALIDATE statement on a system catalog. Effect. The utility program terminates abnormally. Recovery.
Event Messages NonStop™ ODBC Server Messages Event Messages This subsection lists messages that the NonStop™ ODBC Server process logs to $0 (or the default collector) when it encounters processing problems. You can run the Event Management Service (EMS) Distributor to log these event messages elsewhere and format them for display. See “Installing the NonStop™ ODBC Server” in the NonStop™ ODBC Server Installation and Management Manual to learn how to collect event messages.
Event Messages NonStop™ ODBC Server Messages Table 1-1. NonStop™ ODBC Server Event Messages (page 2 of 2) Event Number Event Name Description 32148 ZNOS-EVT-NOSS-STARTUP-INVKWD An invalid keyword was specified during login. 32161 ZNOS-EVT-NOSS-DBG-INVLOGTABLE The log table name was invalid. 32216 ZNOS-EVT-HSQL-GT-LIM-WARN An element exceeded its maximum limit. 32310 ZNOS-EVT-NOSS-SQLCSCANNOTOPEN A server could not open the SQLCS process.
Event Messages NonStop™ ODBC Server Messages 32002:ZNOS-EVT-USER-PASSWD-ERR The login included an invalid user name or password. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING Event-Message Text Login incorrect: invalid user and/or password. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32021:ZNOS-EVT-NOSS-HOST-INTERN-ERR An internal error occurred. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Internal error in LOGIN. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32063:ZNOS-EVT-NOSS-INVALID-DBNAME The specified database name is invalid, does not exist, or is not customized. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Cannot Trace: Invalid database name in log table table-name.
Event Messages NonStop™ ODBC Server Messages 32120:ZNOS-EVT-NOSS-CANT-MAPLOG The trace log table could not be found. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Cannot Trace: Log table file-name is NOT found. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual.
Event Messages NonStop™ ODBC Server Messages 32144:ZNOS-EVT-STARTUP-IBUF-RANG-ERR Size specified for inbound buffer was invalid. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING Event-Message Text Inbound buffer should be between 512 and 8192 bytes. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32145:ZNOS-EVT-STARTUP-OBUF-RANG-ERR Size specified for outbound buffer was invalid. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING Event-Message Text Outbound buffer size should be between 512 and 8192 bytes. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32148:ZNOS-EVT-NOSS-STARTUP-INV-KWD An invalid keyword was specified during login. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Invalid keyword: keyword. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32161:ZNOS-EVT-NOSS-DBG-INV-LOGTABLE The log table name was invalid. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Cannot Trace: Invalid log table name log-table. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32216:ZNOS-EVT-HSQL-GT-LIM-WARN The indicated element exceeded the maximum limit. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text variable exceeds the maximum limit of limit. Execution of this statement is stopped.
Event Messages NonStop™ ODBC Server Messages 32310:ZNOS-EVT-NOSS-SQLCS-CANNOTOPEN A server could not open the SQLCS process. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-IOERROR Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-INT Event-Message Text Error error-number opening SQLCS. Server terminating. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual.
NonStop™ ODBC Server Messages Event Messages 031 Unable to obtain file system buffer space 032 Unable to obtain storage pool space (SYSPOOL) or extended pool space 033 I/O process is unable to obtain buffer space 034 Unable to obtain file system control block 109 Client has broken the connection 201 The SCS process has failed 233 Pipe not connected 240 Network line handler error, operation not started 241 Network error, operation not started 246 External cluster bypass error, operation
Event Messages NonStop™ ODBC Server Messages 32311:ZNOS-EVT-NOSS-SQLCS-NOTNEEDED SQLCS no longer needs a server. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING Event-Message Text Server no longer needed by SQLCS. Server terminating. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32312:ZNOS-EVT-NOSS-SQLCS-CONNECTERR The server cannot indicate to SQLCS that it is available to service clients. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-IOERROR Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-INT Event-Message Text error-number connecting to SQLCS. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual.
Event Messages NonStop™ ODBC Server Messages 32313:ZNOS-EVT-NOSS-SQLCS-IOERR An error occurred within SQLCS software. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-IOERROR Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-INT Event-Message Text error-number communicating with SQLCS. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
Event Messages NonStop™ ODBC Server Messages 32321:ZNOS-EVT-NOSS-INVALID-VOLUME The volume portion of the database identifier exceeds the maximum length. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Invalid default location volume-name, using default database instead.
Event Messages NonStop™ ODBC Server Messages 32328:ZNOS-EVT-USER-AUTHENTICATE-ERR A user authentication error occurred. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-FS-ERR ZNOS-TKN-STATUS Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-INT ZSPI-TYP-INT Event-Message Text User authentication error, error error-number, status statusnumber. Check USER_AUTHENTICATE_ procedure call for detail.
Event Messages NonStop™ ODBC Server Messages 32332:ZNOS-EVT-NOSS-CHANGE-PWD-X-USER A change password operation failed. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE ZNOS-TKN-USER-NAME Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Change password failed, the change password user user-name is not the same as login user login-user-name.
Event Messages NonStop™ ODBC Server Messages 32333:ZNOS-EVT-NOSS-INVALID-SECURITY An invalid security value for the DEFAULT_SECURITY attribute was configured in the profile. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Invalid Default Security profile-security, using Default Security of the logon user.
Event Messages NonStop™ ODBC Server Messages 32335:ZNOS-EVT-NOSS-METRICS-TBL-FULL The accounting log table is full. Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZNOS-TKN-SERVER-NAME ZNOS-TKN-LOG-TABLE Token Type ZSPI-TYP-SSID ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Account log table table-name is full. Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for NOS and is described in the SPI Programming Manual. The value of this token is always ZNOS-VAL-SSID.
2 SQL SQL Communications Subsystem (SCS) Messages This section lists messages generated by the SQL Communications Subsystem (SCS) process and logged to $0 or the default collector. You can run the Event Management Service (EMS) Distributor to log SCS messages elsewhere and format them for display. See the NonStop™ ODBC Server Installation and Management Manual to learn how to collect event messages. See the EMS Manual for more information about that product.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Message Format for SCS CPU List A CPU list is a pair of integers enclosed in parentheses and separated by a comma: (n, n) where n is the number of a running processor in the system. Multilan (MLAD) Device Name A device name begins with a dollar sign and contains from 1 to 7 alphanumeric characters, the first of which must be alphabetic. A subdevice name is concatenated to the device name and begins with a number sign.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Event Messages Table 2-1 lists the event messages that SCS can generate. The subsections that follow describe these messages in more detail. Table 2-1. SCS Event Messages (page 1 of 2) Event Number Event Name Description 1 ZSCS-EVT-INTERNAL An internal logic error or unrecoverable configuration error occurred.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Table 2-1. SCS Event Messages (page 2 of 2) Event Number Event Name Description 18 ZSCS-EVT-SRVCL-CONFIGREJECT The configuration for the server class was rejected. 19 ZSCS-EVT-SERVER-KILL After an SQLCancel request, SCS is trying to stop a busy NOS server process. 20 ZSCS-EVT-SERVERSTOP-ERROR After an SQLCancel request, SCS failed to stop a NOS server process because of a file-system error.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 1:ZSCS-EVT-INTERNAL SCS detected an internal logic error or unrecoverable configuration error. SCS abends after generating this event.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-GMOMJOBID is the operating system job ID associated with the SCS process that generated the event. Recommended Action First, consult the EMS event log to determine whether a configuration error occurred; for example, SCS could not create a NonStop™ ODBC Server process. If the problem is not obvious after consulting the EMS log, contact your service provider. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 2:ZSCS-EVT-CONFIG-ERROR A configuration error occurred. SCS generates the following message and abends.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-CONFIG-ERROR is a number that describes the configuration problem. Possible values are: 34001 SCS could not allocate reserve memory of 32KB. Set the SCS swap volume to a disk drive with more free space. 34003 The configured IOP is not a MULTILAN, IPX/SPX, or TCP/IP IOP. 34004 The open of the communications IOP failed. A file-system error is provided.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 3:ZSCS-EVT-SQLCS-NO-RESOURCES Insufficient resources were available for a client connection. Subsequent attempts by client programs to connect to SCS may encounter errors.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-RESOURCE-ERROR is a number that describes the resource error type encountered by the server class or SCS process. The only possible value is: 34101 SCS encountered a resource problem. This failure can almost always be attributed to insufficient virtual memory for the SCS process. The condition should only be temporary.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 4:ZSCS-EVT-MEMORY-WARNING The SCS process is running short of virtual memory. 32KB of reserve memory has been freed for immediate memory needs; SCS releases this memory and attempts to continue processing, but no new additional connections will be allowed until SCS can reserve additional memory.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Recommended Action Set the SCS swap volume to a disk drive with more available space. The SCS process can dynamically extend its memory segment if disk space is available. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 5:ZSCS-EVT-SERVERCREATE-ERROR SCS failed to create an NSODBC Server process. The return codes from the process creation procedure appear in the SERVER-ERR and SERVER-SUBERR tokens. Likely causes are an invalid object file name or a CPU list that contains no usable processors.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-SERVER-SUBERR is the subcode for the error (in D-series format), returned on the interface to the server process. ZSCS-TKN-SERVER-ERR is the operating system error code (in D-series format), returned on the interface to the server process. The error code can be a file-system error, in which case server-suberr can be a subsidiary file-system error.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 6:ZSCS-EVT-SERVERSTARTUP-ERROR SCS could not send a startup message to a newly created NSODBC Server process. The NSODBC Server failed after it was successfully started by SCS, but before it read the startup message. The cause is probably a code problem either in SCS or the NSODBC Server. Occasionally, timing problems on a heavily loaded system can produce this event.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-SERVER-PROCESS is the name of the NonStop™ ODBC Server process. ZSCS-TKN-FS-ERROR is the file-system error code associated with this event. ZSCS-TKN-GMOMJOBID is the job ID associated with the SCS process that generated the event. Recommended Action Analyze the file-system error to determine the reason for the failure, and correct the configuration or program error as necessary.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 7:ZSCS-EVT-STATE-CHANGE The Subsystem Programmatic Interface (SPI) status of an SCS process, session, or path has changed. This event message is informational only.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZCOM-TKN-OBJSTATE is the current state of the SCS process, session, or path referenced by this event. Possible values are any of the following: DEFINED PROC/SESS/SERVER object created. STARTING SESS/SERVER object initializing and waiting for work. STARTED PROC/SESS/SERVER beginning to process work. For processes, this means the process has been successfully initialized and is initializing subcomponents.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 8:ZSCS-EVT-SMB-ERROR A LAN Manager Server Message Block (SMB) error was returned to the client workstation. The client/server communication protocol has deviated from its expected range; the problem could be in either the client or the server.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-SMB-ERROR is the DOS error value returned for the SMB error reply. ZSCS-TKN-SMB-CMD is the SMB command code. ZSCS-TKN-SMB-SUB-CMD is the SMB command subcode for commands with multiple actions (for example, SmbTrans). ZSCS-TKN-CLIENT-NAME is the NETBIOS name of the client workstation associated with the event.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Unconditional Tokens ZSPI-TKN-SSID is the subsystem ID for SCS and is described in the SPI Programming Manual. The value of this token is always ZSCS-VAL-SSID. ZEMS-TKN-EVENTNUMBER is the event number. Its value is 9. ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token. ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE, indicating this event message is not potentially critical.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 10:ZSCS-EVT-TCPIP-IO-ERROR A TCP/IP error occurred while SCS was communicating with a client workstation. Both a file-system error and a TCP/IP error code are reported with this event. SCS terminates the session between itself and the client.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-FS-ERROR is the file-system error code associated with this event. ZSCS-TKN-GMOMJOBID is the operating system job ID associated with the SCS process that generated the event. Recommended Action The TCP/IP action associated with the error might have been a SEND, RECEIVE, BIND, LISTEN, ACCEPT, or SHUTDOWN operation. Analyze the TCP/IP error code to determine the nature of the failure.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 11:ZSCS-EVT-SRVCL-WARNING A client could not link to a server or start new server processes because of insufficient resources.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-RESOURCE-ERROR is a number that describes the resource error type encountered by the server class or SCS process. Possible values are: 34201 SCS could not initialize a server class because of insufficient system resources. Specifically, SCS could not start the number of servers specified in MINSERVERS for the server class.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 12:ZSCS-EVT-SRVCL-TIMEOUT A client exceeded a time-out value while waiting for a server process to become available because too few servers were configured to meet client connection needs. Other clients might be unable to connect to the NSODBC Server as well.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Recommended Action Adjust the server class configuration so that it has a higher MAXSERVERS value for the class reported in the event. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 13:ZSCS-EVT-SRVCL-NOSERVER A client could not link to a server because no server exists that satisfies the request. SCS must start a new process.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Recommended Action Set MINSERVERS to a higher value for the server class name reported in the event, unless you prefer that clients wait for a new server to be started, in which case you can ignore this message. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 14:ZSCS-EVT-MAPPING-IOERROR An I/O operation to the mapping server failed. All client login requests are forwarded to the default class if available. Clients already connected can continue to communicate with servers.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-MAPPER-LOGICALNAME is the name the mapping server is attempting to map. ZSCS-TKN-SERVERCLASS-NAME is the name of the server class where the mapping server resides. ZSCS-TKN-GMOMJOBID is the operating system job ID associated with the SCS process that generated the event. Recommended Action This is usually a server configuration error, but might reflect an error within the NonStop™ ODBC Server system catalog.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 15:ZSCS-EVT-MAPPING-MAPERROR The mapping server failed while attempting to map a client to a server class. All client login requests are forwarded to the default class if available. Clients already connected are allowed to continue communicating with servers.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-MAPPER-SQLERROR is the SQL error code associated with this event. ZSCS-TKN-FS-ERROR is the file-system error code associated with this event. ZSCS-TKN-MAPPER-LOGICALNAME is the name the mapping server is attempting to map. ZSCS-TKN-SERVERCLASS-NAME is the SCS server class where the mapping server resides.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 16:ZSCS-EVT-NW-IO-ERROR A Novell Netware SPX error or a file-system error has occurred while communicating with a client workstation. Both a file-system error and a Netware SPX error code are reported with this event.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-NETWARE-CLIENTNAME is the IP address and port number of the client program that encountered the error. It is a hexadecimal string of the form: network-address:node-address:port-number for example, 000000F2:00001B30DD8C:0451. ZSCS-TKN-NETWARE-OP is a string describing the communication function that failed. ZSCS-TKN-FS-ERROR is the file-system error code associated with this event.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 17:ZSCS-EVT-SRVCL-CONFIGERR A error was detected in one of the server class configuration attributes.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-GMOMJOBID is the operating system job ID associated with the SCS process that generated the event. Recommended Action Correct the server class configuration and retry the configuration for the server class. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 18:ZSCS-EVT-SRVCL-CONFIGREJECT The configuration of a server class was rejected.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages Recommended Action Retry the configuration action for the specified server class once the problem has been corrected. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 19:ZSCS-EVT-SERVER-KILL After an SQLCancel request from a client, SCS is trying to stop a busy NonStop™ ODBC server process.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Recommended Action This is an informational message only; no action is required. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages 20:ZSCS-EVT-SERVERSTOP-ERROR After an SQLCancel request from a client, SCS failed to stop a NonStop™ ODBC server process because of a file-system error returned from a PROCESS_STOP_ procedure.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages Event Messages ZSCS-TKN-GMOMJOBID is the operating system job ID associated with the SCS process that generated the event. Recommended Action Refer to the Guardian Procedure Errors and Messages Manual for an explanation and the recovery for the file-system error returned from the PROCESS_STOP_ procedure. NonStop ODBC Server Messages Manual—429394.
SQL Communication Subsystem (SQL Communications Subsystem (SCS) Messages NonStop ODBC Server Messages Manual—429394.
3 TACL Messages This section lists the messages generated by an SCS process and reported to TACL on the NonStop™ system. These messages are displayed on the NonStop™ system terminal from which the SCS process was started and are listed here in numeric order, from 35100 to 35207.
TACL Messages 35129 The value specified for SQLCS-OBJECTCODE is not a valid filename Cause. You supplied an invalid file name for the SCS program in the configuration file, or the configuration file has not been updated to match the current system configuration on which SCS is installed. Effect. SCS fails to start. Recovery. Check that the value for SQLCS-OBJECTCODE in the configuration file references a valid operating system file name.
TACL Messages Recovery. Check that the value for SWAPVOL in the configuration file is a valid disk (volume) name. Correct formats for disk names are given at the beginning of this subsection. Correct the value and reissue the start command. 35134 The SQLCSSWAPVOL disk-name does not exist Cause. The configuration file has not been updated to match the current system on which SCS is installed. Effect. SCS fails to start. Recovery.
TACL Messages Recovery. Check that the value for PROCESS-NAME in the configuration file is a valid process name. See Correct Name Formats on page 2-1 for the format for process names. Correct the value and reissue the start command. 35138 The value specified for the SQLCS CPU-PRIMARY is not a number Cause. The value for the CPU-PRIMARY parameter in the configuration file is not numeric. Effect. SCS fails to start. Recovery.
TACL Messages 35142 NETWORK-NAME specified for the SQLCS process section is longer than 16 characters Cause. The value specified for NETWORK-NAME in the configuration file is too long. Effect. SCS fails to start. Recovery. Change the value for SERVER-NAME to a name that contains 16 or fewer characters. Reissue the start command. 35143 The value specified for the SQLCS INPUT-BUFFER is not a number Cause. The value specified for INPUT-BUFFER in the configuration file is not numeric. Effect.
TACL Messages 35146 OUTPUT-BUFFER specified for the SQLCS process not in the range 2400 through 32000 Cause. The value specified for OUTPUT-BUFFER in the configuration file is less than the minimum value of 2400 or greater than the maximum value of 32000. Effect. SCS fails to start. Recovery. Change the value to a number between 2400 and 32000. Reissue the start command. 35147 The mapping server file filename does not exist. Cause.
TACL Messages 35151 Invalid SQLCS MULTILAN-GATEWAY value specified: value gateway- Cause. The value for MULTILAN-GATEWAY in the configuration file is not valid. Effect. SCS fails to start. Recovery. Change the MULTILAN-GATEWAY parameter in the configuration file to correspond to an existing Multilan gateway defined under IOP-DEVICENAME. The syntax is #gateway, where gateway is 5 or fewer alphabetic characters. Reissue the start command.
TACL Messages Effect. SCS fails to start. Recovery. Change the MULTILAN-DOMAIN parameter in the configuration file to correspond to the name of an existing Multilan domain defined under IOPDEVICENAME. The syntax is #gateway, where gateway is 5 or fewer alphabetic characters. Reissue the start command. 35155 The value specified for SQLCSIOP-DEVICENAME is not a valid device name Cause. The configuration file has not been updated to match the current system configuration on which SCS is installed. Effect.
TACL Messages 35156 Fatal error in TACL configuration macro - macro terminating Cause. A coding problem in the TACL macro provided by Compaq. Effect. SCS fails to start. Recovery. Contact your service provider. 35160 The value specified for IN-FILE in the ODBCSERVER_PROGRAM section is not a valid device name Cause. An improperly formed device name was specified for the IN-FILE parameter in the configuration file. Effect. SCS fails to start. Recovery.
TACL Messages 35163 The value specified for CPUS in an ODBC SERVER_CLASS does not begin with a ( Cause. The value for the CPU list parameter in the configuration file is not in the correct format. Effect. SCS fails to start. Recovery. Change the value for the CPU list parameter in the configuration file to the correct format. Correct the value and reissue the start command. 35164 The value specified for CPUS in ODBCSERVER_CLASS section is not a number Cause.
TACL Messages 35173 The value specified for HEAP-SIZE (size) in an ODBCSERVER_CLASS section is not a number in the range 750 through 2,147,483,647 Cause. The value for the HEAP-SIZE parameter was not a numeric value in the valid range. Effect. SCS fails to start. Recovery. Correct the parameter value. 35174 The value specified for PRIORITY (priority) in an ODBCSERVER_CLASS section is not a number in the range 0 through 199 Cause.
TACL Messages 35178 The value specified for MINSERVERS (value) in an ODBCSERVER_CLASS section is not a number in the range 0 through 32768 Cause. The value for the MINSERVERS parameter was not a numeric value in the valid range. Effect. SCS fails to start. Recovery. Correct the parameter value. 35180 The value specified for SWAPVOL (value) in an ODBCSERVER_CLASS section is not a device Cause. The value for the SWAPVOL parameter was not a valid device name. Effect. SCS fails to start. Recovery.
TACL Messages 35183 The value specified for NETSEND-SLOWDOWN in the SQLCS process section is not a number Cause. The value for the NETSEND-SLOWDOWN parameter was not numeric. Effect. SCS fails to start. Recovery. Change the parameter value. 35184 NETSEND-SLOWDOWN value specified in the SQLCS process section is greater than 32000 or less than 0 Cause. The value for the NETSEND-SLOWDOWN parameter was outside the specified range. Effect. SCS fails to start. Recovery. Change the parameter value.
TACL Messages 35187 The start-up string exceeds 255 characters in an ODBCSERVER_CLASS section Cause. More than 255 characters follow the keyword STARTUP-STRING. Effect. SCS fails to start. Recovery. Reduce the length of the startup string. 35193 The value specified for SQLCS PIPE-TESTING is not a number Cause. The value for the PIPE-TESTING parameter in the configuration file was not numeric. Effect. SCS fails to start. Recovery. Change the parameter value to 0 or 1.
TACL Messages 35198 Default IOP-DEVICENAME IOP-name is not a TCPIP, NPP, or MULTILAN IOP Cause. The default device name, IOP-name, is not a TCP/IP, NPP (Netware Protocol Process), or MULTILAN IOP on your system. Effect. SCS fails to start. Recovery. Locate the correct device name and add it as an IOP-DEVICENAME parameter to the SCS section. 35199 A SQLCS process with the name process-name already exists. Terminating TDBSRV:START attempt Cause.
TACL Messages NonStop ODBC Server Messages Manual—429394.
4 Configuration Manager Messages This section lists messages generated by the NonStop™ ODBC Server Configuration Manager. Messages are listed here in numerical order. Each message description includes the following information: • • • • • Message number Message text Cause of the message Effect to the system as a result of the message cause Recovery strategy suggested to correct the error or warning 37000 Unable to allocate memory for an environment handle during the connection process. Try again. Cause.
Configuration Manager Messages Effect. The NonStop™ ODBC Server does not submit the SQL statement and discontinues the connection process. Recovery. Quit one or more running applications to free up memory and then reconnect. 37300 The required attribute value is missing. Cause. You did not enter the required attribute value before clicking the Apply button. Effect. The Apply command fails. Recovery. If you are executing an Add command, make sure you enter values for all required attributes.
5 NOSCOM Messages This section lists the messages that are generated by the NOSCOM command interpreter and reported to TACL on the NonStop™ system. These messages are displayed on the NonStop™ system terminal where the NOSCOM program was started. Each description includes the following information: • • • • Message number and text Cause of the message Effect to the system as a result of the message cause Recovery action suggested to correct the error or warning 31000 Number expected. Cause.
NOSCOM Messages 31003 Unknown system. Cause. You specified a system that does not exist or is unavailable. Effect. The requested operation is ignored. Recovery. Specify a system that is available. 31004 Illegal number. Cause. You specified a number that is invalid or out of range. Effect. The requested operation is ignored. Recovery. Specify a valid number that is in the appropriate range. 31005 Priority must be in the range 1-199. Cause.
NOSCOM Messages 31008 Illegal character. Cause. The command contains an illegal character. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31009 Missing parameter. Cause. The command is missing a required parameter. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31010 Expecting a quoted string. Cause. The command is missing a character string surrounded by quotation marks. Effect. The requested operation is ignored.
NOSCOM Messages 31013 Command line too long. Cause. You entered a command line that is too long. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31014 Expecting semicolon or return. Cause. The command is missing a semicolon or return. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31015 Missing parameter. Cause. The command ended unexpectedly; a required parameter is probably missing. Effect.
NOSCOM Messages 31018 Keyword expected. Cause. The command is missing a required keyword. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31019 Unrecognized object. Cause. You specified an object that the NOSCOM command interpreter does not recognize. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31020 Illegal disk file name. Cause. You specified an illegal disk file name. Effect. The requested operation is ignored.
NOSCOM Messages 31023 Colon expected between hour and minute. Cause. You specified an invalid date/time. There must be a colon between the hour and minute. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31024 Expecting a 3-character alphabetic month name. Cause. You specified an invalid date/time. The month must be specified by a threecharacter alphabetic name. Effect. The requested operation is ignored. Recovery. Correct the command and try again.
NOSCOM Messages 31028 Illegal default volume specified. Cause. You specified an illegal default volume. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31029 Illegal file name. Cause. The command included an illegal file name. Effect. The requested operation is ignored. Recovery. Correct the command and try again. For the format of a fully-qualified file name, see Correct Name Formats on page 2-1. 31030 Unable to open out file. Cause.
NOSCOM Messages Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31033 Comment exceeds maximum length. Cause. The command contains a comment that exceeds the maximum length. A comment is text that follows two dashes ( -- ). Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31034 Maximum length exceeded. Cause. The command contains an element that exceeds the maximum length. Effect. The requested operation is ignored.
NOSCOM Messages 31037 Expecting a quote. Cause. The command is missing a quotation mark Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31038 No concatenated commands are allowed after ?, !, or FC. Cause. You concatenated an additional command following one of the three commands indicated in the message. Effect. The requested operation is ignored. Recovery. Enter the concatenated command separately. 31039 ?, !, and FC are not allowed with obey or out files.
NOSCOM Messages Recovery. Correct the command and try again. 31042 Invalid table name specified. Cause. You specified an invalid table name. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31043 Unknown option, expecting SECURE. Cause. You specified an option that the NOSCOM command interpreter does not recognize. The command is missing the keyword SECURE. Effect. The requested operation is ignored. Recovery. Correct the command and try again.
NOSCOM Messages Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31047 Invalid governing attribute specified. Cause. You specified an invalid governing attribute. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31048 Expecting GOV_ACTION. Cause. The command is missing the keyword GOV_ACTION. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31049 Invalid governing action specified.
NOSCOM Messages Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31052 Unknown option, expecting CASCADE or RESTRICT. Cause. You specified an option that the NOSCOM command interpreter does not recognize. The command is missing either the keyword CASCADE or the keyword RESTRICT. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31053 Invalid NSK userid specified. Cause. You specified an invalid Guardian user ID. Effect.
NOSCOM Messages 31056 Expecting RO or RW. Cause. The command is missing either the keyword RO or the keyword RW. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31057 Transaction isolation level cannot exceed 4. Cause. You specified a transaction isolation level greater than 4. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31058 Expecting N, Y, or S. Cause.
NOSCOM Messages Recovery. Correct the command and try again. 31061 Expecting USER. Cause. The command is missing the keyword USER. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31062 Expecting SESSION. Cause. The command is missing the keyword SESSION. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31063 Expecting GOV_ATTRIBUTE. Cause. The command is missing the keyword GOV_ATTRIBUTE. Effect.
NOSCOM Messages Recovery. Correct the command and try again. 31066 Expecting NOWAIT. Cause. The command is missing the keyword NOWAIT. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31067 Expecting an equal. Cause. The command is missing an equal sign (=). Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31068 Expecting NET_PROTOCOL. Cause. The command is missing the keyword NET_PROTOCOL. Effect.
NOSCOM Messages 31071 Expecting 0 or 1. Cause. The command is missing a 0 or 1. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31072 Expecting a sharp character #. Cause. The command is missing the “#” character. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31073 Expecting TCP/IP, NETBIOS, or SPX/IPX. Cause. The command is missing either the keyword TCP/IP, the keyword NETBIOS, or the keyword SPX/IPX. Effect.
NOSCOM Messages 31076 Unrecognized command. Cause. You specified a command that the NOSCOM command interpreter does not recognize. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31077 Expecting IN. Cause. The command is missing the keyword IN. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31078 Expecting FROM. Cause. The command is missing the keyword FROM. Effect. The requested operation is ignored. Recovery.
NOSCOM Messages Recovery. Try to determine what is preventing the LOG file from being opened and take action as appropriate. 31082 Expecting (. Cause. The command is missing an opening parenthesis. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31083 Expecting ). Cause. The command is missing a closing parenthesis. Effect. The requested operation is ignored. Recovery. Correct the command and try again. 31084 Incorrect number of commas. Cause.
NOSCOM Messages Effect. The requested operation fails. Recovery. Try to determine the root cause of failure from the file-system error code that was returned and take action as appropriate. For information on file-system errors, refer to the Guardian Procedure Errors and Messages Manual. 31091 Unable to create a process name. Cause. The system could not create a process name for a new process. Effect. The requested operation fails. Recovery. Wait and try again.
NOSCOM Messages PROCESS_CREATE_ procedure; this parameter returns additional information about some classes of errors. Effect. The requested operation fails. Recovery. Try to determine the root cause of failure from the values of error and error-subcode that were returned and take action as appropriate. For more information on process creation errors, refer to the Guardian Procedure Errors and Messages Manual. 31095 No server is currently running. Cause. No server is currently running. Effect.
NOSCOM Messages 31101 Unknown error number error. Cause. An unrecognized error code was returned; error is the unrecognized code. Effect. The requested operation is ignored. Recovery. Contact your service provider. NonStop ODBC Server Messages Manual—429394.
NOSCOM Messages NonStop ODBC Server Messages Manual—429394.
Index C Client error messages vi Configuration Manager messages, NonStop ODBC Server 4-1 CPU list 2-2 NonStop ODBC Server (continued) messages displayed on the workstation 1-1 NOSCOM command interpreter messages 5-1 O E Event Management Service (EMS) 1-68, 2-1 Event messages from NonStop ODBC Server 1-68 from SQL Communication Subsystem (SCS) 2-3 Operating system file name 2-1 process name 2-1 P Process name, operating system 2-1 F S File name, operating system 2-1 SQL Communications Subsystem (SCS
T Index NonStop ODBC Server Messages Manual—429394.
