Micro Focus Studio Enterprise Edition Test Server > Programming > Mainframe Programming > SQL Option for DB2 > Reference > Error Messages > X - Engine Error Messages > X350 - X399

X350 - X399

X352: Server violation.
The server experienced a protection exception while processing a user's command. The exception handling code has rolled back the user's current transaction and logged the user out.
X354: Error loading server communications DLL(name).
Make sure you have the DLL named in the correct DLL subdirectory.
X355: Error connecting to remote server(name).
An error has occurred while trying to connect to server name. Make sure you have enough remote engine threads and that the server-to-server connectivity setup is correct in your system catalogs.
X356: Error sending to remote server(name).
An error has occurred while trying to send to server name. Make sure you have enough remote engine threads and that the server-to-server connectivity setup is correct in your system catalogs.
X357: Error receiving from remote server(name).
An error has occurred while trying to receive from server name. Make sure you have enough remote engine threads and that the server-to-server connectivity setup is correct in your system catalogs.
X358: Governor limit exceeded.
One of the governor limits has been exceeded, and the server logged out the user. You could increase the governor limit for that user. The governor will be active only if the server security is ON.
X359: Error initializing remote server gateway.
An error has occurred while trying to connect to a remote server.
X360: Incorrect version of the server configuration file.
You have an old version of SRVCONFG.XDB. Delete your old SRVCONFG.XDB and run the new XDB Server Configuration utility to create a new one.
X361: No remote thread available to process request.
A client has tried to connect to a remote server and the primary server does not have any thread available to handle the request. In these cases, there are no remote threads set for the primary server, or all the remote threads are already in use.
X362: Index error during recovery.
While XDB Server was recovering a location, a fatal error occurred. You must compact and re-index the location immediately. Do not use the location until the compact and re-index has finished.
X363: No protocol threads available to process request.
The number of protocol threads for TCP/IP, SPX, or Named Pipes must equal the number of users using the protocol.
X364: The describe statement does not identify a prepared statement.
In order to describe a query, the query must first be prepared.
X365: Log path cannot be set to path.
The logging system cannot set the log to the path specified. Ensure that the path exists, and that there are no other logs present in the path.
X366: Error replacing alias name with actual table name.
XDB Server encountered an internal error when forming the alias substitution string. Contact Micro Focus Technical Support with the details of the query.
X367: GROUP BY/HAVING not allowed in subquery/embedded select.
XDB Server and DB2 does not allow a GROUP BY or HAVING clause on a nested query.
X368: Illegal string string found.
XDB Server received a different string than it expected. For example: SET CURRENT RULES <parm> must be either DB2 or STD. Using a different parameter will return an x368.
X369: Invalid index type.
The index type must be 1 or 2.
X370: The target location needs to be compatible with DB2 version version.
An attempt was made to perform new DB2 functionality against an XDB Server location that was created with this functionality. See the ALTER LOCATION command and CREATE LOCATION command in the SQL Reference and the readme file.
X371: The selected locksize and lockmax options do not match.
The DDL is illegal. See the SQL Reference for correct values.
X372: Illegal attempt to convert location to a lower version.
An ALTER LOCATION can only be used to move forward in DB2 functionality, not backwards (i.e., an ALTER LOCATION cannot be used to convert a location to a lower version).
X373: Invalid number of parameters (number expected) for stored procedure ProcName.
The number of parameters specified in your SQL CALL statement exceeds the number of parameters allowed by the ProcName stored procedure.
X374: Stored procedure ProcName received a null value for parameter number.
The SQL CALL statement for stored procedure ProcName contains a null value in its parameter list, and this stored procedure does not accept null values.
X375: Stored procedure ProcName has been placed in a must rollback state.
The stored procedure ProcName issued one of the following operations:
X376: Missing OBID clause when creating a table in a ROSHARE READ database.
The OBID clause was not specified in the CREATE TABLE command. The OBID clause is required whenever the database containing the table is defined as ROSHARE READ.
X377: A privilege cannot be revoked because it is not possessed by AuthID authid.
An AuthID can revoke only the privileges that it has explicitly granted to other AuthIDs, unless the AuthID has SYSADM or SYSCTRL authority and specifies the BY clause.
X378: Attempt to disable login with security off.
A DISABLE LOGIN command was issued while security was off on the XDB Server.
X379: The login was rejected due to logins being disabled.
The database administrator has disabled logins for this XDB Server, so your login command was rejected.
X380: The XDB Server has rejected this connection due to load balance requirements.
Your connection request was rejected because the XDB Server has exceeded the load balancing limits configured by the database administrator.
X381: Cannot connect with requested location. Location is offline.
The location you have requested is currently offline. (Your database administrator may have taken it offline for maintenance purposes.)
X382: Cannot take requested location offline. Location is in use.
The XDB Server cannot take the requested server offline because it is being used. You are allowed to take a location offline only when there are no users attached to it.
X383: Sequence error for reason code (ReasonCode) Message.
The XDB Server has received a request out of order.
X384: Invalid handle.
The XDB Server has received an invalid handle. This is an internal error.
X385: Login error with Reason Code ReasonCode Message (returned Number).
An error has occurred while logging on to the XDB Server through the Direct Flight software.
X386: Conflicting definitions for the same variable or parameter. Description
The SQL Server has received a parameter or host variable from the client application that does not match the data type it expected.
X387: Option conflict with location rules
The statement being executed has an option that is incompatible with the current location type.
X388: Invalid token 'token' found in PARMLIST for procedure proc-name
A Stored Procedure or Trigger definition has a syntax error.
X389: Illegal operation on temporary table
The current operation is not allowed on a temporary table. Temporary tables are not allowed to have primary/unique keys, or to be referenced by foreign keys. Also, update/delete operations on records in temporary tables are not allowed.
X390: Check option not allowed on temporary table
A view of a temporary table must not specify the CHECK OPTION clause.
X391: WITH DEFAULT clause not allowed on CREATE GLOBAL TEMPORARY TABLE
WITH DEFAULT clauses are not allowed on a CREATE GLOBAL TEMPORARY TABLE statement.
X392: Your SQL Option (for DB2 emulation) has expired.
The XDB component (e.g., XDB Server, XDB Link) you are attempting to use does not have a valid license from Micro Focus.
X393: Output host variable PositionNumber is incompatible with the query result.
The XDB Server is not able to return the result of a CALL, FETCH, or SELECT statement because the data type of the variable at PositionNumber in the output SQLDA (to which the result was to be written) does not match the data type of the result.
X394: Input host variable PositionNumber is incompatible with the current query.
The XDB Server is not able to execute the requested SELECT statement because it contains a host variable whose data type is not correct. (For example, the WHERE clause may be using a numeric host variable to select from a DATE field in the database.) The host variable causing the problem is located at PositionNumber in the input SQLDA.
X395: Value for data type Type is out of range for host variable PositionNumber.
The XDB Server cannot return the requested value because the returned value is larger than the host variable at PositionNumber in the output SQLDA (to which the value was to be written) can accept.
X396 ColumnName is not a column of specified table or view in the query.
The specified name is not a column in the table or view referenced. A bad column name in a FOR UPDATE OF clause can generate this error.
X397 Decimal host variable or parameter Identifier contains non-decimal data.
Data could not be used as specified in the statement because the data is not valid for this type.
X398 ColumnName is not an updateable column; it is not identified in the update clause.
In order to update this column, you need to specify its name in the FOR UPDATE OF clause for this cursor.
X399 Improper use of long string data, StringValue.
The operation is not supported on a long string value in DB2 mode.

Parent topic: X - Engine Error Messages