MXCI messages (15000 through 15999)
SQL 15001
15001 A syntax error occurred at or before: statement info
Cause
A syntax error detected in statement info indicates the location of the error in characters from the start of the SQL statement.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15002
15002 Internal parser error: detail text
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Report the entire message to your service provider.
SQL 15003
15003 An incomplete statement was found in input: detail text
Cause
You specified an incomplete statement, which appears in detail text. The most common error is a missing semicolon (;) at the end of a statement.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15004
15004 Error number on change directory attempt to directory.
Cause
NonStop SQL/MX has received error number while attempting to change directory.
Effect
The operation fails.
Recovery
Correct the error and resubmit.
SQL 15005
15005 Unmatched quote in input (unterminated string): text
Cause
You specified text input with unbalanced quotation marks. Quoted text, whether literals or delimited identifiers, must not contain carriage returns.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15006
15006 Error number while reading from file.
Cause
NonStop SQL/MX received error number while reading from a file. The error number depends on the operating system.
Effect
The operation fails.
Recovery
Use the error number to diagnose and correct the problem.
SQL 15007
15007 Error number while opening file name.
Cause
NonStop SQL/MX received error number while reading from file name. The error number depends on the operating system.
Effect
The operation fails.
Recovery
Use the error number to diagnose and correct the problem.
SQL 15008
15008 The specified statement does not exist in the history buffer.
Cause
You attempted to reference a statement from the history buffer, but the statement does not exist there.
Effect
The operation fails.
Recovery
Check your entry for '!x;' instead of '!s;'. If you specified the wrong comment, resubmit the correct one. If you did enter the correct command, the statement is not in the history buffer, and you must enter it at the prompt.
SQL 15009
15009 The requested help topic is too long.
Cause
You entered more than 31 characters in your request for a help topic.
Effect
The operation fails.
Recovery
See the documentation for the topic.
SQL 15010
15010 The help file could not be opened.
Cause
NonStop SQL/MX was unable to open the help file.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 15012
15012 A file read error occurred on the help file.
Cause
NonStop SQL/MX was unable to read the help file.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 15013
15013 This command is not supported by the SQLCI OLE server.
Cause
You specified a command that the SQL/MX Conversational Interface (SQLCI) OLE server does not support.
Effect
The operation fails.
Recovery
None.
SQL 15014
15014 Section name not found in file name.
Cause
You specified section name, which is not found in file name.
Cause
The operation fails.
Recovery
Check the spelling of the section name. If the name is missing, add it to the file and resubmit.
SQL 15015
15015 PARAM name (value value) cannot be converted to type data type.
Cause
You tried to convert parameter name to data type.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15016
15016 PARAM name not found.
Cause
NonStop SQL/MX did not find parameter name.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15017
15017 Statement name not found.
Cause
NonStop SQL/MX did not find statement name.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15018
15018 Break was received. The last statement may be lost.
Cause
You pressed Break to stop processing of your most recent MXCI command.
Effect
The last statement might be lost.
Recovery
Informational message only; no corrective action is needed.
SQL 15019
15019 value values were supplied in the USING list while the statement contains value unnamed parameters.
Cause
You specified an EXECUTE command with a USING clause whose value number of parameters do not match the value number of unnamed parameters. NonStop SQL/MX requires these values to match.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15020
15020 The USING list must contain at least one parameter value.
Cause
You specified an EXECUTE command with a USING clause, but you did not specify parameter values. NonStop SQL/MX requires at least one parameter value.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15021
15021 The USING list cannot contain more than value parameter values.
Cause
You specified an EXECUTE command with a USING clause that has more parameter values than are supported.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15023
15023 The USING list value value1 exceeds the MXCI limit of value2 characters.
Cause
You specified an EXECUTE command with a USING clause, but the value1 item exceeds the number of characters, value2, that MXCI allows.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15024
15024 The USING list quoted literal name must be followed by either a comma or a semicolon.
Cause
You specified an EXECUTE command with a USING clause that included literal name, which must be followed by a comma or semicolon.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15025
15025 Cursor operations are not supported by MXCI.
Cause
You attempted to perform a cursor operation which MXCI does not support.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15026
15026 Break rejected.
Cause
A break you specified to cancel an SQL/MX statement failed.
Effect
The operation fails.
Recovery
None. Report the entire message to your service provider.
SQL 15028
15028 Break error.
Cause
A break that you specified to cancel an SQL/MX statement failed.
Effect
The operation fails.
Recovery
None. Report the entire message to your service provider.
SQL 15029
15029 Break was received. Please run RECOVER to recover any incomplete operations.
Cause
A break was received while running a utility operation such as PURGEDATA, DUP, or MODIFY.
Effect
The operation fails.
Recovery
Run RECOVER on the object that was being operated on, to ensure that it is returned to a consistent state.
SQL 15030
15030 The specified define already exists. Use ALTER or use DELETE and ADD.
Cause
You attempted to add a define that exists.
Effect
The operation fails.
Recovery
Alter the existing define or delete and add it.
SQL 15031
15031 The specified define does not exist.
Cause
You attempted to use a define that does not exist.
Effect
The operation fails.
Recovery
Correct the define name or add it, and resubmit.
SQL 15032
1503 An error occurred while adding, altering or deleting this define.
Cause
An error occurred while adding, altering, or deleting a define.
Effect
The operation fails.
Recovery
Use the file system errors that accompany this one to diagnose and correct the problem.
SQL 15033
15033 Break was received.
Cause
Break was received.
Effect
The operation fails.
Recovery
Informational message only; no corrective action is needed.
SQL 15034
15034 Specified LOG file name is not valid.
Cause
You specified an invalid LOG file name.
Effect
The operation fails.
Recovery
Correct the file name and resubmit.
SQL 15035
15035 Permission denied to access this file.
Cause
NonStop SQL/MX was unable to access the file.
Effect
The operation fails.
Recovery
Check the file permissions and reset them if necessary.
SQL 15036
15036 Specified file has an inappropriate filecode or an invalid function argument was specified.
Cause
You specified an invalid file code or invalid function argument.
Effect
The operation fails.
Recovery
Correct the file code or function argument.
SQL 15038
15038 A SQL/MX transaction is already in progress. The mode cannot be changed at this time.
Cause
You attempted to change the mode while a transaction was in progress.
Effect
The operation fails.
Recovery
Commit or abort the transaction and retry the MODE command.
SQL 15039
15039 DISPLAY_EXPLAIN is not supported any more, use EXPLAIN instead.
Cause
You attempted to run the DISPLAY_EXPLAIN command.
Effect
The operation fails.
Recovery
Use the EXPLAIN statement.
SQL 15040
15040 Help texts are not installed.
Cause
The HELP_CONTENTS metadata table has not been created on this system.
Effect
The
help command cannot retrieve help text information.
Recovery
Install help using the
InstallSqlMxHelp script with command-line option
-installHelp. Only the SUPER.SUPER user can run this script.
SQL 15041
15041 Help text not available for the topic1 topic.
Cause
Help text was not found for the given topic.
Effect
No help text is available.
Recovery
Enter
HELP; to find valid topics and then reissue the command with a correct topic. For more information, contact your Hewlett Packard Enterprise representative.
SQL 15042
15042 A SQL error occurred while accessing the HELP_CONTENTS table.
Cause
A SQL error occurred while accessing HELP_CONTENTS table. The actual error will be reported in an accompanying message.
Effect
The command fails.
Recovery
Investigate and correct the accompanying SQL error, then reissue the
HELP command.
SQL 15202
15202 LOWLAYER seq-nbr: string1.
-
Where,
-
seq-nbr is the error sequence number for this event, starting at 1. A number greater than 1 is rare;
-
string1 is an error message from a lower-level, often the file system or SQL compiler. See the Guardian Procedure Errors and Messages Manual. If another error number in included in the message, it refers to an SQL/MX error message documented in this manual, SQL/MX Messages Manual.
Cause
A lower-level error is reported. This message is usually intended for debug purposes but it also can give information relating to the problem. It is the third in a string of three error messages with the primary error (first) and subsystem error (second) preceding it.
Effect
The action fails, and this message provides information about the failure.
Recovery
Correct the problem defined by the first error message displayed for the event; which is usually the most meaningful for recovery action.
SQL 15203
15203 Maximum of int1 error messages exceeded, dropping the rest.
Cause
Excessive error messages are issued, and at least one is dropped.
Effect
The command fails with errors previously reported. This message is always the last one reported for a given error.
Recovery
Correct the problem defined by the first error, which is normally the most meaningful.
SQL 15205
15205 SUBSYSTEM: Request for LowLayer error message failed, return code int1 from CFGFetchError.
Cause
An attempt to determine a subsystem error fails. If the int1 value is 500, 501, or 516, connection to the service is not operational. In rare cases, a disconnect arrived from the SERVICE being examined.
Effect
A lower-level error might have been lost unless the connection just failed.
Recovery
See the first error message displayed for the event (primary message) to determine the problem and the recovery action.
SQL 15206
15206 SUBSYSTEM: Bad return code int1, library call function-name failed.
-
Where,
-
int1 is the value of the return code from the library call. This code is provided for problem analysis by support or development personnel;
-
function-name is the name of the library function called.
Cause
A subsystem error is not converted to a meaningful string. The error number has meaning only to the library subsystem for the specified function call.
Effect
The command and subsequent call to the subsystem fails.
Recovery
See the first error message displayed for the event to determine the problem and recovery action. If provided, also see lower-level error messages for additional information. Using an appropriate MACL INFO command, check the status of the target object or related object for indication of a problem.
SQL 15212
15212 SUBSYSTEM: Wrong length input parameter, library call function-name failed.
Cause
A field in the command is too long.
Effect
The operation fails.
Recovery
Look for one or more input strings that exceed the character limit. Then enter the command with one or more correct length fields.
SQL 15214
15214 SUBSYSTEM: User not authorized for this action, library call function-name failed.
Cause
You do not have authorization to issue the command.
Effect
The command and subsequent subsystem call fails.
Recovery
Obtain proper authorization from the ODBC administrator. Then enter the command.
SQL 15215
15215 SUBSYSTEM: SERVICE name used cannot supply this info, library call function-name failed. +++SUGG: SERVICE name was probably * and should be a specific SERVICE name.
Cause
The service name is an asterisk (*).
Effect
The command and subsequent subsystem call fails.
Recovery
Enter the command with a specific service name.
SQL 15216
15216 SUBSYSTEM: EVAR already defined, library call function-name failed. +++SUGG: Look at existing EVARs with \"INFO EVAR *, TYPE xxx>\".
Cause
You issued an ADD EVAR command and the EVAR name supplied already exists.
Effect
The command and subsequent subsystem call fails.
Recovery
Specify a different EVAR name. View a list of known EVARs using the INFO EVAR command.
SQL 15217
15217 Guardian file system error encountered, library call function-name failed. +++SUGG: Use "gtacl -c 'error errno" to decode.
-
Where,
-
function-name is the name of the library function called;
-
errno is the Guardian error code number.
Cause
Unknown.
Effect
The subsystem call and subsequent command fails.
Recovery
See the Guardian Procedure Errors and Messages Manual for the error number provided.
SQL 15218
15218 SUBSYSTEM: SERVER out of memory space, library call function-name failed.
Cause
Out of memory space.
Effect
The command and subsequent subsystem call fails.
Recovery
See the ODBC server documentation for handling server memory problems.
SQL 15219
15219 SUBSYSTEM: SERVICE is not in started state, library call function-name failed. +++SUGG: Start SERVICE and retry command.
Cause
The service is not in the started state.
Effect
The command and subsequent subsystem call fails.
Recovery
Start the service and enter the command again.
SQL 15220
15220 SUBSYSTEM: Configuration server on SERVICE is not operational, library call function-name failed. +++SUGG: Configuration server should soon be restarted by SERVICE, if not stop (kill) SERVICE and restart from Guardian TACL prompt.
Cause
The configuration server is not operational.
Effect
The command and subsequent subsystem call fails.
Recovery
Wait for the configuration server to complete restart. If necessary, stop and restart the server.
SQL 15221
15221 SUBSYSTEM: User input data problem, library call function-name failed. +++SUGG: Invalid environment variable definitions for example.
Cause
An attribute value entered on the command line is not valid for the command you issued.
Effect
The command and subsequent subsystem call fails.
Recovery
Enter the command with the correct attribute value.
SQL 15222
15222 SUBSYSTEM: Unspecified problem, library call function-name failed.
Cause
Unknown.
Effect
The command and subsequent subsystem call fails.
Recovery
See the lower-level error messages issued with this message.
SQL 15224
15224 SUBSYSTEM: SERVICE did not respond within the 5 second timeout, library call function-name failed.
Cause
Call to a subsystem timed out.
Effect
The requested action fails.
Recovery
The CPU running the SERVICE or the SERVICE is busy. Retry the request. If it fails again, wait until the target CPU is less busy and retry the action.
SQL 15226
15226 The 'invalid-char' character is in the wrong place, expected a keyword, command had: string1.
As of the ABU SPR, this message is no longer generated.
Cause
You inserted a semicolon or comma in the wrong place.
Effect
The operation fails.
Recovery
Enter the command again with the correct characters and syntax.
SQL 15227
15227 Command was missing the object type.
Cause
The command is missing the second of its two required parameters.
Effect
The operation fails.
Recovery
The command displays valid object types in a second message. Enter the command again providing the second parameter.
SQL 15228
15228 Command contained a invalid-char before the end, command had: string1. ++++SUGG: Surround the string containing this character with quotes.
-
Where,
-
invalid-char is the invalid character in the command;
-
string1 displays the start of the error.
As of the ABU SPR, this message is no longer generated.
Cause
The MXCI lower-level did not break the command apart on a semicolon or quotes did not enclose the character.
Effect
The operation fails.
Recovery
Retry the command. Report any subsequent failures of this command.
SQL 15229
15229 Object name must be followed by a semicolon or comma in the command.
As of the ABU SPR, this message is no longer generated.
Cause
You entered a character other than a semicolon or comma after the object name.
Effect
The operation fails.
Recovery
Enter the command with a semicolon or comma after the object name.
SQL 15230
15230 Opening quote unmatched in the command, command had: string1.
Cause
A string with single or double quotation mark (SQL identifier or literal) is missing the terminating mark.
Effect
The operation fails.
Recovery
Enter the command with the correct terminating single or double quotation mark.
SQL 15231
15231 Command had a 'invalid-char' character where an attribute was expected, command had: string1.
As of the ABU SPR, this message is no longer generated.
Cause
You entered a comma followed by either another comma or a semicolon.
Effect
The operation fails.
Recovery
Enter the command with the correct comma or semicolon.
SQL 15232
15232 Empty quoted strings are not permitted in the input command, text following problem was: string0.
Cause
You entered quotes without a character string within them.
Effect
The operation fails.
Recovery
Enter the command with characters inside the quoted string.
SQL 15233
15233 Keywords can not be quoted, command had: string0.
Cause
A keyword contains a quotation character.
Effect
The operation fails.
Recovery
Enter the command without quotation marks for the keyword.
SQL 15234
15234 Opening quote was matched but following separator not correct, command had: string1.
As of the ABU SPR, this message is no longer generated.
Cause
A token separator is incorrect, likely in the object name.
Effect
The operation fails.
Recovery
Enter the command using the correct separator value.
SQL 15235
15235 Attribute value not terminated with a comma or semicolon, command had: string0 string1 string2. +++SUGG: Command could be missing a comma or the whole value may need quotes. Only one token permitted for an attribute value.
Cause
The parser could not locate the terminator for the attribute. All attributes end with a comma or semicolon.
Effect
The operation fails.
Recovery
Enter the command using the correct syntax.
SQL 15237
15237 Command was missing the command name.
Cause
The command name, which is the first token, is missing, possibly because the command starts with a comma.
Effect
The operation fails.
Recovery
Enter the complete command, including the command name.
SQL 15238
15238 Empty command attribute found (extra comma) just before: string0.
Cause
You entered an extra comma instead of a value.
Effect
The operation fails.
Recovery
Enter the value instead of a comma and resubmit.
SQL 15240
15240 No attributes supported by this command, command had: string1 ....
Cause
The command does not support attributes.
Effect
The operation fails.
Recovery
Enter the command without the attribute.
SQL 15241
15241 Command is missing the required attribute "attribute-name".
Cause
The required attribute is missing from the command.
Effect
The operation fails.
Recovery
Enter the command including the required attribute.
SQL 15242
15242 Command has an invalid attribute attr-name. +++SUGG: Check spelling or use of extra commas.
Cause
You specified an incorrect attribute. The error can be a misspelled attribute or a missing comma, space character, or attribute value in the preceding attribute.
Effect
The operation fails.
Recovery
Correct the attribute and retry the command.
SQL 15244
15244 Command has a duplicate attribute "attribute-name". +++SUGG: Remove the duplicate keyword (and value).
Cause
A duplicate attribute is in the command.
Effect
The operation fails.
Recovery
Enter the command without the duplicate attributes.
SQL 15245
15245 This command attribute never has a value, command had: string0 string1. +++SUGG: Check syntax for missing comma after keyword.
Cause
A value is associated with an attribute.
Effect
The operation fails.
Recovery
Enter the command without the attribute value.
SQL 15246
15246 This command attribute has an invalid value, command had: string0 string1.
Cause
The value associated with an attribute is not correct.
Effect
The operation fails.
Recovery
Enter the command with the correct attribute value.
SQL 15247
15247 This command attribute must have a value, command had only keyword: string0.
Cause
An attribute value is not associated with the attribute name.
Effect
The operation fails.
Recovery
Enter the command with correct the attribute value.
SQL 15248
15248 This command has a non-numeric character invalid-char in a numeric field, command had: string1.
Cause
The attribute value is invalid.
Effect
The operation fails.
Recovery
Enter the command with the correct attribute value.
SQL 15249
||15249 Command has a quoted string not followed by a comma, semicolon, or the concat operator , command had:
string1.
As of the ABU SPR, this message is no longer generated.
Cause
A comma, semicolon, or concatenation operator does not follow the string enclosed in quotation marks.
Effect
The operation fails.
Recovery
Enter the command with the correct separator after the quoted string.
SQL 15255
15255 A name component may not contain unquoted white space, command had: Obj Name.
Cause
You either entered unquoted white space in the object name, or a comma was missing at the end of the name.
Effect
The operation fails.
Effect
Enter the command again with the correct object name syntax.
SQL 15256
15256 A user name must have two components: groupname.membername.
Cause
The user name field does not contain both the group and member name.
Effect
The operation fails.
Effect
Enter the command with a group and member name.
SQL 15257
15257 A component name may not contain wild cards * or ? within the name. The wild card * alone is often permitted. Use double quotes to protect these characters in DS and EVAR names when they are normal characters, command had: string0.
Cause
The component name is not quoted.
Effect
The operation fails.
Recovery
Enter the command with the component name enclosed in quotation marks.
SQL 15258
15258 Object name has too many components for a string1 name, max is int1.
-
Where,
-
string1 is the object type;
-
int1 is the maximum number of components allowed by the object type.
Cause
Too many components are entered for the object type.
Effect
The operation fails.
Recovery
Enter the command without the excess components for the object type.
SQL 15259
15259 string1 name component exceeds int1 character limit, command had string2.
-
Where,
-
string1 is the object type;
-
int1 is the maximum number of characters allowed by the component;
-
string2 is the component with too many characters.
Cause
Too many characters are in the component.
Effect
The operation fails.
Recovery
Enter the command with a reduced number of characters in the component specified in the error.
SQL 15260
15260 name name component must be * or start with $, command had string1. +++SUGG: Last component of name may be missing.
Cause
The service name is incorrect. The service name can be either an asterisk (*) or a ‘$' followed by a service name.
Effect
The operation fails.
Recovery
Enter the command with a valid service name. If necessary, issue an INFO command with an asterisk (*) wild card to see all valid names.
SQL 15261
15261 SYSTEM name component must start with the back-slash char, command had string1.
Cause
The system name does not have a backslash preceding its name.
Effect
The operation fails.
Recovery
Enter the command with a backslash preceding the system name.
SQL 15262
15262 string1 name component must not be defaulted yet.
Cause
The component is not specified in a previous command.
Effect
The operation fails.
Recovery
Enter the command with the proper component name. Do not use an asterisk (*) wild card.
SQL 15263
15263 Single quote at start of component name not permitted, command had: ‘string1'. +++SUGG: Identifiers use double quotes when needed to prevent upcasing. Some name components are not identifiers and should not be quoted at all.
Cause
The component name is enclosed in single quotes.
Effect
The operation fails.
Recovery
Enter the command without the single quotes around component name.
SQL 15264
15264 string1 name component is not an SQL identifier, can not be double quoted, command had: "string2".
Cause
The component name is not an SQL identifier.
Effect
The operation fails.
Recovery
Enter the command with the correct component name for an SQL identifier.
SQL 15265
15265 fname name component is not valid, command had: string1. +++SUGG: Last component of name may be missing, or double quotes on component name are missing.
Cause
The component name is not valid.
Effect
The operation fails.
Recovery
Enter the command with the correct component name for the command issued.
SQL 15266
15266 Object name component has invalid character char, command has name.
-
Where,
-
char is the invalid character;
-
name is the component of the object name as entered in the input.
Cause
The component name is incorrect; the name contained a nonalphanumeric character. Only system, service, and server component names are validated this way and they must not contain special characters.
Effect
The operation fails.
Recovery
Retry the command with a valid component name. To see all valid names, issue an appropriate MACL INFO command with an asterisk (*) wild card.
SQL 15267
15267 Attribute value requires single quotes, command had: string1 ....
Cause
The attribute value is not enclosed with single quotes.
Effect
The operation fails.
Recovery
Enter the command with the attribute value enclosed in single quotes.
SQL 15268
15268 Attribute takes only 'OFF' as value, command had: string1. +++SUGG: Omit key value or look for missing comma.
Cause
The attribute value is not specified as OFF.
Effect
The operation fails.
Recovery
Enter the command with the attribute value
off.
SQL 15269
15269 Attribute value is negative or 0, must be positive, command had: string1.
Cause
The attribute value is negative or zero.
Effect
The operation fails.
Recovery
Enter the command with the attribute value as a positive, nonzero number.
SQL 15271
15271 Attribute value too small, limit minimum, command had: string1.
-
Where,
-
minimum is the minimum value allowed for the attribute value;
-
string1 is the attribute name and value.
Cause
The attribute value entered is less than the minimum allowed value.
Effect
The operation fails.
Recovery
Enter the command with the attribute value equal to or larger than the minimum allowed value.
SQL 15272
15272 Attribute value too large, limit maximum, command had: string1.
-
Where,
-
maximum is the maximum value allowed for the attribute value;
-
string1 is the attribute name and value.
Cause
The attribute value entered is greater than the maximum allowed value.
Effect
The operation fails.
Recovery
Enter the command with the attribute value smaller or equal to the maximum allowed value.
SQL 15273
15273 Attribute value too small, limit -9,223,372,036,854,775,808, command had: string1.
Cause
The attribute value entered is less than the minimum allowed value.
Effect
The operation fails.
Recovery
Enter the command with the attribute value equal to or larger than the minimum allowed value.
SQL 15274
15274 Attribute value too large, limit 9,223,372,036,854,775,807, command had: string1.
Cause
The attribute value entered is greater than the maximum allowed value.
Effect
The operation fails.
Recovery
Enter the command with the attribute value smaller or equal to the maximum allowed value.
SQL 15275
15275 Concatenating strings of different quote types is not permitted, command had: string1.
Cause
A quoted string is concatenated with a different type of quoted string; for example, a single quoted string with a double quoted string.
Effect
The operation fails.
Recovery
Retry the command using the same type of quote characters for concatenation.
SQL 15276
15276 SERVICE name component * not permitted when accessing a SERVER.
Cause
The service name is an asterisk (*), which is invalid when trying to access a server.
Effect
The operation fails.
Recovery
Retry the command specifying a valid service name. To list valid service names, use the INFO SERVICE command.
SQL 15277
15277 Extra token invalid-char was found, command had: string1.
As of the ABU SPR, this message is no longer generated.
Cause
A | character follows a string within quotes.
Effect
The operation fails.
Recovery
Retry the command, either specifying a valid concatenation operator || or removing the invalid character.
SQL 15278
15278 Leading spaces are not allowed in SQL identifiers, command had: ‘string1'.
Cause
A component of the object name starts with a blank or tab character. Names with a leading space are not valid.
Effect
The operation fails.
Recovery
Enter the command without a space at the start of the component name, or use an underscore character.
SQL 15279
15279 Trailing spaces are not allowed in SQL identifiers, command had: ‘string1'.
Cause
A component of the object name ends with a blank or tab character.
Effect
The operation fails.
Recovery
Enter the command without a space at the end of the component name, or use underscores. Names ending with a space are invalid.
SQL 15280
||15280 A quoted string was followed by syntax error in the concat operator "", command had:
string0.
Cause
The parser detected the opening vertical bar after a quoted string ended, but the syntax after that was not legal. Concatenation requires two bars.
Effect
The operation fails.
Recovery
Enter the command with the correct syntax and resubmit.
SQL 15281
15281 No separator found after quote, command had: ‘string0'.
Cause
A quoted string must always be followed by a dot, comma, or semicolon. A dot must not be preceded by white space.
Effect
The operation fails.
Recovery
Enter the separator after the quote (a comma might be missing), and then enter the remaining attributes.
SQL 15284
15284 USAGE: Valid commands are: ADD, ALTER, DELETE, INFO, START, STOP, VERSION.
Cause
The command contains an invalid first parameter.
Effect
The operation fails. A preceding message states the problem, and this message lists valid parameters when
mode macl is set.
Recovery
Select a valid entry from the list as the first token of the input.
SQL 15285
15285 USAGE: "ADD" command supports object types: DS, EVAR, USER.
Cause
The input line contains either no second parameter or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid ADD command objects when
mode macl is set.
Recovery
Select a valid object type from the list as the object type for this command.
SQL 15286
15286 USAGE:"ALTER" command supports object types: DS, EVAR.
Cause
The input line contains either no second parameter, or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid ALTER command objects when
mode macl is set.
Recovery
Select a valid object type from the list as the object type for this command.
SQL 15287
15287 USAGE: "DELETE" command supports object types: DS, EVAR, USER.
Cause
The input line contains either no second parameter or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid DELETE command objects when
mode macl is set.
Recovery
Select a valid object type from the list as the object type for this command.
SQL 15288
15288 USAGE: "INFO" command supports object types: DS, EVAR, SERVER, SERVICE, USER.
Cause
The input line contains either no second parameter or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid INFO command objects when
mode macl is set.
Recovery
Select a valid object type from the list as the object type for this command.
SQL 15289
15289 USAGE "START" command supports object types: DS, SERVICE.
Cause
The input line contains either no second parameter or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid START command objects when
mode macl is set.
Recovery
Select a valid object type from the list as the object type for this command.
SQL 15290
15290 USAGE: "STOP" command supports object types: DS, SERVER, SERVICE.
Cause
The input line contains either no second parameter or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid STOP command objects when
mode macl is set.
Recovery
Select a valid object type from the list as the object type for this command.
SQL 15291
15291 USAGE: "VERSION" command supports object type: SERVICE.
Cause
The input line contains either no second parameter, or an invalid command and object pair.
Effect
The operation fails. A preceding message states the problem, and this message lists valid VERSION command objects when
mode macl is set.
Recovery
Select "service" as the object type for this command.
SQL 15294
15294 USAGE: [[[system.]service.]ds] are the name components for a DS object.
Cause
The object name did not have the correct format.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name.
Recovery
Enter the command using the correct syntax.
SQL 15295
15295 USAGE: [[[[system.]service.]ds.]evar] are the name components for an EVAR object.
Cause
The object name did not have the correct format.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name.
Recovery
Enter the command using the correct syntax.
SQL 15296
15296 USAGE: [[[system.]service.]server] are the name components for a SERVER object.
Cause
The object name did not have the correct format.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name.
Recovery
Enter the command using the correct syntax.
SQL 15297
15297 USAGE: [[system.]service] are the name components for a SERVICE object.
Cause
The object name did not have the correct format.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name.
Recovery
Enter the command using the correct syntax.
SQL 15298
15298 USAGE: [[system.] groupname.membername] are the name components for a USER object.
Cause
The object name or some component of it did not have the correct format.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name.
Recovery
Enter the command using the correct name syntax.
SQL 15299
15299 USAGE: command obj-type [obj-name][, attribute]...;
Cause
The command contains a syntax error.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax.
Recovery
Enter the command using the correct syntax.
SQL 15300
15300 Could not get the status for DS string0.
Cause
The lower-levels returned a status indicating no ability to provide state information for this DS. There could be several reasons for this. Look at additional lower-level messages.
Effect
The operation fails.
Recovery
Issue the
INFO DS* command to determine if the DS exists.
SQL 15305
15305 SUBSYSTEM: DS still in use somewhere, library call function-name failed.
Cause
The DS is in an active state with a service.
Effect
The operation fails.
Recovery
Enter the
STOP DS * command. Use the wild card
* for the service name.
SQL 15307
15307 SUBSYSTEM: DS already exists, library call function-name failed.
Cause
The data source currently exists.
Effect
The operation fails.
Recovery
Enter the command specifying a different data source name.
SQL 15308
15308 SUBSYSTEM: Parameter error on call to MXCS, library call string1 failed.
Cause
Lower- level client library function call fails.
Effect
The operation fails.
Recovery
See lower-level error messages.
SQL 15309
15309 SUBSYSTEM: DS not found, library call function-name failed.
Cause
You entered a data source name that does not exist on the system.
Effect
The operation fails. A preceding message states the problem, and this message shows the valid syntax.
Recovery
Retry the command using the correct syntax.
SQL 15310
15310 SUBSYSTEM: SQL error from LowLayer, library call function-name failed.
Cause
An SQL failure occurs in a lower client library.
Effect
The operation fails.
Recovery
Retry the command using the correct syntax.
SQL 15311
15311 SUBSYSTEM: Association server not available, library call function-name failed.
Cause
The association server is not available.
Effect
The operation fails.
Recovery
Make sure that an association server is available, and then enter the command.
SQL 15312
15312 SUBSYSTEM: Cannot change DS state, (failed to start/stop a server), library call function-name failed.
Cause
Either the data source is in a transitory state and cannot change state at the moment, or it is in an unchangeable state.
Effect
The operation fails.
Recovery
Wait for the data source to fully transition to a stable state, and then issue the command.
SQL 15313
15313 SUBSYSTEM: Cannot stop server process, library call function-name failed.
Cause
This error is returned when a call to Guardian API PROCESS_STOP_() fails. The system returns an error while trying to stop the server process. The process might appear to be running, but it might not be usable.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual.
SQL 15314
15314 SUBSYSTEM: SERVER not found here, library call function-name failed.
Cause
The server is not found on the system.
Effect
The operation fails.
Recovery
Use the INFO SERVER command to list the servers on the system. Then enter the command with a valid server.
SQL 15315
15315 SUBSYSTEM: DS is stopped, trace cannot be changed, library call function-name failed.
Cause
The data source is in a stopped state.
Effect
The operation fails.
Recovery
Start the data source and then change the trace status.
SQL 15316
15316 SUBSYSTEM: Port not available, library call function-name failed.
Cause
The port is used by another process or is not released from the operating system.
Effect
The operation fails.
Recovery
Wait for the port to clear, then enter the command.
SQL 15317
15317 SUBSYSTEM: DS not available now, library call function-name failed.
Cause
The data source is not currently available to make any changes.
Effect
The operation fails.
Recovery
Wait for the data source to fully transition to a stable state, then enter the command.
SQL 15318
15318 SUBSYSTEM: SERVER is in use by another client, library call function-name failed.
Cause
The server is accessed by another client process.
Effect
The operation fails.
Recovery
Wait until the other client process stops accessing the server, then enter the command.
SQL 15319
15319 SUBSYSTEM: Trace already enabled, library call function-name failed.
Cause
The trace status is already enabled.
Effect
The operation fails.
Recovery
Recovery not required.
SQL 15320
15320 SUBSYSTEM: Trace already disabled, library call function-name failed.
Cause
The trace status is already disabled.
Effect
The operation fails.
Recovery
Recovery not required.
SQL 15321
15321 SUBSYSTEM: Error enabling/disabling trace, library call function-name failed.
Cause
The client library fails to enable or disable tracing.
Effect
The operation fails.
Recovery
Check your MXCS service process (MXOAS). It might not be responding.
SQL 15322
15322 SUBSYSTEM: Busy, try again, library call function-name failed.
Cause
MXCS service is too busy so it cannot respond to the current request.
Effect
The operation fails.
Recovery
Try the command at a later time.
SQL 15323
15323 SUBSYSTEM: Cannot create SERVER, library call function-name failed.
Cause
This error comes from the client library calls CFGStartService() or CFGStartDS().
Effect
The operation fails.
Recovery
If this error occurs when starting a data source, run the INFO DS command to determine the data source state. If this error occurs when starting a service or server, check system state to determine why the new servers cannot start. See information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15324
15324 SUBSYSTEM: Error in Configuration server, library call function-name failed.
Cause
This error comes from the client library call CFGStartService().
Effect
The operation fails.
Recovery
Run the INFO command on the service to determine what state it is in; then stop and start the service. See information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15325
15325 Could not get the list of SERVICES on the system.
Cause
The lower-level could not return a list of services on the system to the MACL layer.
Effect
The operation fails.
Recovery
See information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15326
15326 Could not get the next SERVICE name from the list.
Cause
The lower-level could not return an entry off the services list.
Effect
The operation fails.
Recovery
Restart MXCI, which might correct the problem.
SQL 15327
15327 Failed to open a connection to SERVICE service-name.
Cause
Cannot open a connection to the service, which might have recently terminated.
Effect
The operation fails.
Recovery
Verify that the service exists by using the INFO SERVICE * command. Then retry the failed command.
SQL 15328
15328 Could not get the status for SERVICE service-name.
Cause
The lower-level cannot return status for the service. The system could be busy.
Effect
The operation fails.
Recovery
Use the INFO SERVICE command to verify that the specific service is still operational. See lower-level error messages issued with this message. Also, see information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15329
15329 Could not get the status for all DSs on the SERVICE.
Cause
The lower-level cannot return status for all the data sources on the service. The system could be busy.
Effect
The operation fails.
Recovery
Use the INFO SERVICE command to verify that the specific service is still operational. See lower-level error messages issued with this message. Also, see information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15330
15330 Could not get the status for the next DS in the list.
Cause
The lower-level cannot return status for the next data source on the service. The system could be busy.
Effect
The operation fails.
Recovery
Use the INFO SERVICE command to verify that the specific service is still operational or the INFO DS * command to verify that the DS still exists. See lower-level error messages issued with this message. Also, see information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15331
15331 CFG Trace file name is too long. Should be limited to 30 char.
Cause
The file name given for the trace file is too long.
Effect
The operation fails.
Recovery
Enter the command, specifying a shorter trace file name.
SQL 15332
15332 USAGE: FILE option is supported only with TCFG. TMACL displays to the screen.
Cause
You entered the command string
version service, tmacl, filexxx: MACL trace does not support the file option. Instead, the command output goes to the screen, and you cannot specify these two attributes together.
Effect
The operation fails.
Recovery
Enter the command without the file option. For example, enter the command string
version service, tcfg:.
SQL 15350
15350 Stop request failed for SERVER process process-name on SERVICE service-name, object reference was server-name.
-
Where,
-
process-name is the name of the process;
-
service-name is the name of the service;
-
server-name is the name of the server.
Cause
The server process fails to stop the service. A possible problem might exist in passing messages to the server.
Effect
The operation fails.
Recovery
See lower-level error messages issued with this message. Also, see information about this error in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with
$0 as the default.
SQL 15351
15351 SERVER name must be * if DS selection attribute is specified.
Cause
Server name is other than an asterisk (*) wild card to specify the DS selection attribute.
Effect
The operation fails.
Recovery
Run the INFO SERVER command using the asterisk (*) wild card for the server name when specifying the DS attribute.
SQL 15352
15352 Could not get list of SERVERs on the SERVICE service-name. +++SUGG: Use INFO SERVICE to see if it still exists.
Cause
The lower-level fails to return a list of servers for a service. The system might be busy.
Effect
The operation fails.
Recovery
Verify that the service exists via an INFO SERVICE * command and then retry the failed command. See the lower-level error messages issued with this message.
SQL 15353
15353 DS datasource-name not found on SERVICE service-name. +++SUGG: DS name is probably not valid.
Cause
The lower-level fails to find the data source on the specific service.
Effect
The operation fails.
Recovery
Run the INFO DS command with the asterisk (*) wild card, specifying the data source. Check the spelling and case of the data source name and, if necessary, use quotes to protect its case.
SQL 15354
15354 Could not get list of DSs names on SERVICE service-name.
Cause
The lower-level fails to return a list of data source names on the service. The system might be busy.
Effect
The operation fails.
Recovery
Run the INFO SERVICE * command to verify that the service exists, and then retry the failed command. See the lower-level error messages issued with this message.
SQL 15355
15355 Could not get name of next DS on the SERVICE service-name.
Cause
The lower-level fails to return the next data source name on the service. The system might be busy.
Effect
The operation fails.
Recovery
Use the INFO SERVICE * command to verify that the service exists, then retry the failed command. See the lower-level error messages issued with this message.
SQL 15356
15356 Failed in scan of SERVERs on the SERVICE service-name before finding target name, count were skipped before failure.
-
Where,
-
service-name is the name of the service;
-
count is the number of servers scanned on the service.
Cause
The lower-level fails to return data from scanning the list of servers or a specific server is not found on the service. The number of servers scanned is output. The system might be busy.
Effect
The operation fails.
Recovery
Run the INFO SERVICE * command to verify that the service exists, and then retry the failed command. See the lower-level error messages issued with this message.
SQL 15357
15357 SERVER server-name was not found, looked at count. +++SUGG: Perhaps name is not valid or it already terminated.
Cause
A specific server is not found. The number of servers scanned is output.
Effect
The operation fails.
Recovery
Check the spelling of the server name and verify that it is a valid name. Enter the command with the correct server name. If the error persists, verify that the server is operational.
SQL 15358
15358 SERVER server-name is not the type that can be stopped this way. +++SUGG: Perhaps name is the association or configuration server, use STOP SERVICE on them.
Cause
The lower-level could not stop the server.
Effect
The operation fails.
Recovery
See the lower-level error messages. Check for an attempt to stop the association or configuration servers.
SQL 15359
15359 SERVICE service-name not available, no info on SERVERs is available. +++SUGG: Use INFO SERVICE to see if it exists still.
Cause
The lower-level could not detect the service.
Effect
The operation fails.
Recovery
See the lower-level error messages. Verify that the service still exists.
SQL 15360
15360 SERVICE service-name cannot supply a list of SERVERS using DS datasource-name. +++SUGG: Use INFO SERVICE to see if it still exists.
Cause
The lower-level returns a bad status when the server list is requested. The service is unavailable and does not return an error about finding the specified DS.
Effect
The operation fails.
Recovery
Check the status of the service. See the lower-level error messages issued with this message.
SQL 15363
15363 SERVICE service-name has no SERVERs. +++SUGG: Use INFO SERVICE to see if it is stopped.
Cause
The lower-level detects no servers associated with this service. Service might be in a stopped state.
Effect
The operation fails.
Recovery
Run the INFO SERVICE command to verify the status of the service. If service is stopped, issue the START SERVICE command.
SQL 15365
15365 Could not get state info for DS "string0" from the service. +++SUGG: The service may never have been started and so may not know about any DS.
Cause
The lower-level returns a status indicating no ability to provide state information for this DS (or any other). The service had probably never been started. DS names are case-sensitive, and lower letters force the use of quotes around the DS name.
Effect
The operation fails.
Recovery
Issue the INFO SERVICE* command to see if the service exists and is in a started state. If service is stopped, issue the
START SERVICE command.
SQL 15366
15366 Could not get attribute info for DS "string0" from the database either. +++SUGG: The DS probably does not really exist.
Cause
The lower-level returns a status indicating no ability to provide state information for this DS and also fails to get attribute information from the database. Either the name contains a type, needs double quotes, or the DS might not exist.
Effect
The operation fails.
Recovery
Issue the INFO DS* command to determine if the DS exists.
SQL 15367
15367 Could not get state info for DS "string0" from the service and not trying for any other DSs. +++SUGG: The service may never have been started and so may not know about any DS.
Cause
The lower-levels returned a status indicating no ability to provide state information for this DS (or any other). The most likely cause is that the service has never been started. DS names are case-sensitive, and lower letters force the use of quotes around the DS name.
Effect
The operation fails.
Recovery
Issue the INFO SERVICE* command to determine if the service exists and is in a started state. If it is in a stopped state, issue the
START SERVICE command.
SQL 15368
15368 Could not set automatic start option on DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15369
15369 Could not set statistics on DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15370
15370 Could not set CPU list on DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15371
15371 Could not set process priority on DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15372
15372 DS string1 creation failed.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15373
15373 DS string1 creation failed, cleanup failed. +++SUGG: DS may need to be deleted or repaired.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message. Then remove the data source and re-create it.
SQL 15374
15374 DS name AND SERVICE name can not both be a wild card. +++SUGG: Specify either a DS name or a SERVICE name on command line.
Cause
Both the data source and service names are asterisks.
Effect
The operation fails.
Recovery
Enter the command specifying either a data source or service name.
SQL 15375
15375 Could not get statistics from DS string1
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15376
15376 Could not get CPU list from DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15377
15377 Could not get process priority from DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15378
15378 Can not delete the default DS, string1.
Cause
Removing the TDM_Default_DataSource data source is not allowed.
Effect
The operation fails.
Recovery
Recovery is not required.
SQL 15379
15379 DS creation failed, new DS name string1 already exists.
Cause
The specified data source already exists.
Effect
The operation fails.
Recovery
Enter the command specifying a different data source name.
SQL 15380
15380 DS not found, string1.
Cause
The data source is not found on the system.
Effect
The operation fails.
Recovery
Use the
INFO DS command to list known data source names.
SQL 15381
15381 Can not delete a DS that is in use, string1. +++SUGG: DS may need to be stopped on all services.
Cause
The data source is in the start state.
Effect
The operation fails.
Recovery
Stop the data source and rerun the command.
SQL 15382
15382 Connection is lost to the service, string0. +++SUGG: The SERVICE may have died.
Cause
The data source is not connected to the service.
Effect
The operation fails.
Recovery
Use the
INFO SERVICE* command to see the existing service. If the specific service does not exist, create a service or try a different service that is in a started state.
SQL 15383
15383 Unable to obtain all or part of the ENV variables on string1.
Cause
A failure in the client library.
Effect
The command is partially processed.
Recovery
See the lower-level error messages that precede this message.
SQL 15384
15384 ALLSTAT keyword must preceed all other statistical keywords on the command line.
Cause
ALLSTAT keyword is not in front of all other statistical keywords.
Effect
The operation fails.
Recovery
Enter the command with ALLSTAT keyword before all statistical keywords.
SQL 15385
15385 Reason text truncated, maximum characters allowed int1, int2 characters detected.
-
Where,
-
int1 maximum allowable characters in a reason string;
-
int2 is the number of reason text characters given in the command.
Cause
Too many characters in the reason string.
Effect
A warning message is displayed and the command is processed.
Recovery
Enter the command using less than the maximum allowed characters in the reason string.
SQL 15386
15386 Could not enable trace for DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15387
15387 Could not disable trace for DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15388
15388 Could not set the attributes of DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15389
15389 Idle server count int1 exceeds maximum server count int2, for DS string1.
-
Where,
-
int1 is the idle server count specified in the command;
-
int2 is the maximum server count for the data source specified in the command;
-
string1 is the data source name.
Cause
Idle server count is too large.
Effect
The operation fails.
Recovery
Either increase the maximum server count or decrease the idle server count of the data source.
SQL 15390
15390 Initial server count int1 exceeds maximum server count int2 (or 200, whichever is smaller) for DS string1.
-
Where,
-
int1 is the initial server count specified in the command;
-
int2 is the maximum server count for the data source specified in the command;
-
string1 is the data source name.
Cause
Initial server count is too large.
Effect
The operation fails.
Recovery
Either increase the maximum server count or decrease the initial server count of the data source.
SQL 15391
15391 Could not start DS string1. +++SUGG: Most likely reason is that SERVICE is in the stopped state. Use INFO SERVICE to check the SERVICE state.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15392
15392 Could not stop DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15393
15393 The ACTIVE attribute requires SERVICE name be specific and started, also DS name must be a wildcard.
Cause
The ACTIVE attribute is specified in the command, but the service name is not known.
Effect
The operation fails.
Recovery
Enter the command specifying the service name.
SQL 15394
15394 Must specify at least one attribute on the ALTER DS command line.
Cause
No attributes are specified in the alter command.
Effect
The operation fails.
Recovery
Enter the command specifying the attribute and possible value to alter.
SQL 15395
15395 Could not delete DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15396
15396 Could not get automatic start option for DS string1.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages that follow this message.
SQL 15397
15397 DS name can not be *. +++SUGG: Specify a DS name on the command.
Cause
The data source in the command is an asterisk (*).
Effect
The operation fails.
Recovery
Enter the command again, specifying the data source name. An INFO DS command will list known data source names.
SQL 15398
15398 Could not get attribute info for DS "string0" from database.
Cause
A failure occurs in the client library.
Effect
The operation fails.
Recovery
See the lower-level error messages below this message.
SQL 15399
15399 Invalid DS name in COPY option, starts with '$' or backslash without quotes. +++SUGG: Do not specify a system or service name here. The old and new DS must reside on the same system and service.
Cause
An invalid data source name is entered.
Effect
The operation fails.
Recovery
Enter the command specifying a valid data source file name.
SQL 15400
15400 No service active for tracing.
Cause
No services are available to activate tracing for this DS.
Effect
The trace operation is not processed. If this failure occurs during execution of an ADD DS command, it is possible the DS is successfully created in either the database or on a service before the service is terminated.
Recovery
If the error occurs during execution of ADD DS, run INFO DS to verify that the DS is successfully created. Then run INFO SERVICE to list known services. If the error occurs during ALTER DS, run INFO SERVICE to list known services. Enter the ALTER command, specifying the trace attribute. Specify a valid service name or wild card to set trace on one or all operational services.
SQL 15401
15401 EVAR type evar-name can not be used with the EVAR command evar-cmd.
Cause
The EVAR type ALL is not valid for EVAR object in the command.
Effect
The operation fails.
Recovery
Use a different EVAR type when using this EVAR command.
SQL 15402
15402 The attribute-name attribute is missing from this command.
Cause
The required attribute name is missing from the EVAR object for the command.
Effect
The operation fails.
Recovery
Supply an EVAR attribute name (for example, LIMIT or VALUE) with the command.
SQL 15403
15403 The attribute-name is not permitted on this command.
Cause
The attribute-name (for example, PREFIX, VALUE, LIMIT, ACTION) is not valid with the EVAR object for the command.
Effect
The operation fails.
Recovery
Either use a different EVAR attribute or delete the EVAR attribute from the command.
SQL 15405
15405 DS name can not be * on an EVAR command. +++SUGG: Use a specific DS name on the command.
Cause
EVAR belongs to a specific DS. The DS name must be specified. A DS name of * is not permitted on any EVAR command.
Effect
The operation fails.
Recovery
Use a specific DS name on the command.
SQL 15407
15407 evar-name does not exist in EVAR type evar-type.
-
Where,
-
evar-name is name of the EVAR specified in the command;
-
evar-type is the EVAR type specified in the command.
Cause
The indicated EVAR was not found for the specific EVAR type.
Effect
None, the command properly executed.
Recovery
Use the INFO EVAR command to display a list of all existing EVARs of this type. Use the asterisk (*) wild card as the name.
SQL 15408
15408 Lower layers failed to perform action requested.
Cause
Client library function fails.
Effect
The operation fails.
Recovery
See the lower-level error messages below this message.
SQL 15409
15409 The EVAR name must be * when the TYPE is ALL.
Cause
Incorrect command entry.
Effect
The operation fails.
Recovery
Either specify an asterisk (*) wildcard for the EVAR name, or remove the type ALL from EVAR object for this command.
SQL 15410
15410 Copying EVARs from source-ds data source to target-ds data source failed.
-
Where,
-
source-ds is the existing data source that defines the EVARs to be copied;
-
target-ds is the new data source being created.
Cause
A problem occurred in support routines during reading or writing to existing EVARs. See the subsequent messages for details of the problem.
Effect
The command fails, removing the partially created new DS.
Recovery
Correct the problem described by the lower-level error messages and enter the full command.
SQL 15411
15411 No EVAR named evar-name found in type evar-type. +++SUGG: Perhaps type is wrong, name is spelled wrong, or SYSTEM is wrong.
-
Where,
-
evar-name is name of the EVAR specified in the command;
-
evar-type is the EVAR type specified in the command.
Cause
Incorrect command entry.
Effect
The operation fails.
Recovery
Check command input for EVAR type, EVAR name, or system.
SQL 15412
15412 The first object-type with this name was deleted, but duplicate-count more duplicates were found. +++SUG: Run the delete command again if more clean-up is needed.
-
Where,
-
object-type is the object type specified on the command line;
-
duplicate-count is the number of duplicates found.
Cause
More than one object type for the specified name is found.
Effect
A warning message is displayed, and the command is processed.
Recovery
Delete the duplicates.
SQL 15413
15413 Duplicate object-type name found, add failed.
Cause
More than one object-type for the specified name is found.
Effect
The operation fails.
Recovery
Delete the duplicates.
SQL 15414
15414 The first object-type with this name was altered, but count more were found. +++SUGG: Delete all except last, it is the only one used.
-
Where,
-
object-type is the object type specified on the command line;
-
count is the number of duplicate EVARs found.
Cause
More than one object type for the specified name is found.
Effect
A warning message is displayed and the command is processed.
Recovery
Delete the duplicates.
SQL 15415
15415 No EVARs found, the DS datasource-name does not exist. +++SUGG: Probably the DS name is incorrect.
Cause
No EVARs exist because the data source does not exist.
Effect
The command fails.
Recovery
Check the name of the data source specified in the command.
SQL 15416
15416 A define EVAR name must be 2 to 24 characters long. The first two characters must be an equal sign followed by a letter. The remaining characters can be letters, numbers, hyphens, underscores or circumflexes (^).
Cause
An invalid define EVAR name is entered in the command.
Effect
The command fails.
Recovery
Enter the command with a valid define EVAR name.
SQL 15425
15425 Failed in scan of USERs on the SYSTEM system-name before end, number-users were scanned before failure.
-
Where,
-
system-name is the name of the system;
-
number-users is the number of users that were scanned in before failure.
Cause
A failure occurs in the lower-client library function.
Effect
The operation fails.
Recovery
See the lower-level error messages for details.
SQL 15428
15428 Failed to get the list of USERs on SYSTEM system-name from lower layer. +++SUGG: Perhaps a user ID was removed from the system, but not from the MXCS table permissions.
Cause
A failure occurs in the lower-client library function.
Effect
The operation fails.
Recovery
See the lower-level error messages for details.
SQL 15429
15429 This command does not permit * as the string1 component.
Cause
A wild card specifies either the group or member name.
Effect
The operation fails.
Recovery
Enter the command with a valid group or member name.
SQL 15430
15430 Specified user user-name not found in existing list. Nothing changed.
Cause
The user name was not found in the list of user names.
Effect
The operation fails.
Recovery
Run the info user command to see a list of users.
SQL 15431
15431 The permissions for SUPER.SUPER may not be changed or deleted.
Cause
The command was trying to change the SUPER.SUPER user.
Effect
The operation fails.
Recovery
None.
SQL 15432
15432 Failed to set up an output area for outputing USERs. New changes dropped.
Cause
A failure in the lower client library function.
Effect
The operation fails.
Recovery
See the lower-level error messages for details.
SQL 15433
15433 Failed to insert the user-type list buffer in output area. New changes dropped.
Cause
A failure occurred in the lower-client library function.
Effect
The operation fails.
Recovery
See the lower-level error messages for details.
SQL 15434
15434 Failed to write the USER changes in the output area to disk. New changes dropped. +++SUGG: Administrator must be super.super, and user name must be registered on this system to do this.
Cause
A failure occurred in the lower-client library function.
Effect
The operation fails.
Recovery
See the lower-level error messages for details.
SQL 15435
15435 Too many USERs for user-type list buffer size. New changes dropped. Max characters is char-max, failed user is number user-number of this type, user-name.
-
Where,
-
user-type is either operator or user;
-
char-max is the maximum number of characters in the user buffer;
-
user-number is count of what user that exceeded buffer size;
-
user-name is the user name.
Cause
A set buffer limit holds all user names. If the number of user names exceeds buffer capacity, this error occurs.
Effect
The operation fails.
Recovery
Delete some user names.
SQL 15436
15436 User name user-name is not found in the system system-name user list.
Cause
The user named for the operation does not exist on the system.
Effect
The operation fails.
Recovery
Add the user to the system and enter the command.
SQL 15437
15437 Groupname group-name is not found in the system system-name user list.
Cause
The group the operation was given against does not exist on the system.
Effect
The operation fails.
Recovery
Add the group to the system first, then reissue the command.
SQL 15438
15438 This command does not permit * as the comp-name component when the membername is present.
Cause
An invalid wild card is used on the command.
Effect
The operation fails.
Recovery
Re-enter the command again, using a valid component name.
SQL 15451
15451 DS string1 was not found, looked at int1.
-
Where,
-
string1 is the command and object type;
-
int1 is number of data source names searched without finding a match.
As of the ABU SPR, this message is no longer generated.
Cause
You possibly entered the incorrect service or data source name with the command.
Effect
The operation fails.
Recovery
Enter the correct data source name for the service or database.
SQL 15452
15452 Command not supported in this release, string1.
Cause
The command is not available.
Effect
The operation fails.
Recovery
No recovery required.
SQL 15453
15453 Unknown object type, string1.
Cause
The object type is invalid.
Effect
The operation fails.
Recovery
See the lower-level warning message that follows this message for a list of known object types.
SQL 15454
15454 Unknown command in MXCS mode, string1.
Cause
The command is invalid.
Effect
The operation fails.
Recovery
See the lower-level warning message that follows this message for a list of known commands.
SQL 15455
15455 Invalid command and object type combination, string1.
Cause
The command is not valid with the specified object type.
Effect
The operation fails.
Recovery
See the lower-level warning message that follows this message for a list of valid object types.
SQL 15457
15457 Could not open connection to SERVICE string1. +++SUGG: SERVICE name may be incorrect, system name was valid.
Cause
The service name is incorrect.
Effect
The operation fails.
Recovery
Enter the command specifying a valid service name. Use the INFO SERVICE command to list the valid services.
SQL 15458
15458 Could not open connection to system string1. +++SUGG: Check spelling, check connectivity, check that SQL/MX is operational there.
Cause
The system name is incorrect.
Effect
The operation fails.
Recovery
Enter the command, specifying a valid system name.
SQL 15459
15459 Could not open connection to DB of the local system, string1. +++SUGG: Verify SQL/MX is operational.
Cause
The database on the system is not installed or is not operational.
Effect
The operation fails.
Recovery
Verify that NonStop SQL/MX is installed and operational.
SQL 15501
15501 A syntax error was found.
Cause
You specified a command with invalid syntax.
Effect
The command failed.
Recovery
Check the syntax and reissue the command.
SQL 15502
15502 Invalid character in the command.
Cause
The MXCI command scanner found an invalid character in the command. The character was not recognized in context.
Effect
The operation fails.
Recovery
Correct the syntax and reissue the command.
SQL 15503
15503 String literal must be enclosed within identical quotes.
Cause
You specified a string literal that was not enclosed within identical quotation marks, as required.
Effect
The operation fails.
Recovery
Correct the command, verifying that quotation marks are balanced and reissue the command. Use two quotation marks for each quotation mark that you want to appear in the string.
SQL 15504
15504 Ampersand must be followed by another quoted string.
Cause
You specified a string without the continuation mark.
Effect
The operation fails.
Recovery
Either place an ampersand at the end of the previous line so that the new string in the next line is concatenated with the previous string, or separate the fields with a comma and resubmit.
SQL 15505
15505 This value is not allowed for this option.
Cause
You specified an invalid value for an option in the SET, SHOW, or RESET command.
Effect
The operation fails.
Recovery
Use the correct value for the option.
SQL 15506
15506 The value must be a period or comma.
Cause
The SET STYLE value that you specified for the DECIMAL_POINT option was not a period(.) or a comma (,).
Effect
The operation fails.
Recovery
Enter the corrected command.
SQL 15507
15507 The value must be between 1 and 255.
Cause
The value that you specified for RIGHT_MARGIN was not in the range 1 through 255.
Effect
The operation fails.
Recovery
Specify the correct command and resubmit.
SQL 15508
15508 The value must be between 0 and 32767.
Cause
The value that you specified in the SET LIST_COUNT command was out of range. The value must be from 0 through 32767.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15509
15509 The value must be exactly one character.
Cause
The SET STYLE value length that you specified for the NEWLINE_CHAR option was not 1.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15510
15510 The value must be between 1 and 32767 or ALL.
Cause
The SET LAYOUT value that you specified for the PAGE_LENGTH option was not in the value range.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15511
15511 The value must be between 0 and 255.
Cause
The SET LAYOUT value that you specified for the SPACE option was not in the valid range.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15512
15512 The value must be between 0 to 255 characters for the SET LAYOUT value for SUBTOTAL option.
Cause
The SET LAYOUT value that you specified for the SUBTOTAL option was not in the valid range.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15513
15513 The value must be between 1 and 255 for the SET LAYOUT value for WINDOWS option.
Cause
The SET LAYOUT value that you specified for the WINDOW option was not in the valid range.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15514
15514 The value must be between 1 and 255 for the LIST command.
Cause
The value that you specified in the LIST command was out of range. The value must be in the range 1 through 32767, or ALL.
Effect
The operation fails.
Recovery
Specify the correct value and resubmit.
SQL 15515
15515 This command is not allowed because a SELECT is in progress.
Cause
When a SELECT operation is in progress, you can enter only certain MXCI commands, such as report writer commands and:
ENV
EXIT|
RESET LAYOUT|REPORT|SESSION|STYLE FC
SET LAYOUT|SESSION|STYLE HELP
SHOW DEFINE|DEFMODE|LAYOUT|REPORT
INFO DEFINE|PARAM|SESSION|STYLE LOG
Effect
The operation fails.
Recovery
If you specified the command by mistake, enter the correct command. If you wanted to enter the command, use the CANCEL command to terminate the SELECT statement and reissue the command.
SQL 15516
15516 This command is allowed only when a SELECT is in progress.
Cause
You can enter these commands only when a SELECT is in progress:
BREAK DETAIL PAGE TITLE BREAK FOOTING LIST REPORT FOOTING BREAK
TITLE NAME REPORT TITLE CANCEL PAGE FOOTING SUBTOTAL TOTALEffect
The operation fails.
Recovery
Use these commands only with SELECT.
SQL 15517
15517 An invalid option was specified.
Cause
You specified an invalid option for the SET, RESET, SHOW, or SAVE command.
Effect
The operation fails.
Recovery
Specify a valid option and resubmit.
SQL 15518
15518 The value must be between 1 and 32767 for LINE_SPACING option.
Cause
The value that you specified for the LINE_SPACING option was not in the valid range.
Effect
The operation fails.
Recovery
Specify the correct LINE_SPACING value and resubmit.
SQL 15519
15519 The current PAGE_LENGTH length1 value is insufficient for the report. The PAGE_LENGTH should be length2.
Cause
The current page length specified was not large enough to allow printing of one detail plus the currently defined titles, footings, headings, and so forth.
Effect
No report is generated.
Recovery
Specify a new page length that is equal to or greater than the value displayed in the error message, or revise the report definition so that the report will fit within the given page length.
SQL 15520
15520 The column value value is not in the DETAIL list. All TOTAL and SUBTOTAL items must be in the DETAIL list.
Cause
One of the columns in the TOTAL or SUBTOTAL command is not present in the current DETAIL command print list.
Effect
The operation fails.
Recovery
Revise the TOTAL, SUBTOTAL, or DETAIL command so that all the TOTAL items also appear in the DETAIL print list.
SQL 15521
15521 You have a SUBTOTAL command but not a BREAK command. The SUBTOTAL command is being ignored.
Cause
You specified a SUBTOTAL command, but there are no break columns to subtotal.
Effect
The operation fails.
Recovery
Enter a BREAK command or delete the SUBTOTAL command by using RESET.
SQL 15522
15522 Because of the new report definition command(s), the report is being regenerated from the start.
Cause
A BREAK, SUBTOTAL, or TOTAL command was specified after some rows were listed, and then a LIST NEXT command was specified, as in the following sequence: SELECT; LIST FIRST n; BREAK ON...;LIST NEXT n.
Effect
Instead of listing the next n rows, the report is started over from the first row.
Recovery
Informational message only; no corrective action is needed.
SQL 15523
15523 The value of SPACE is out of range. The valid range is 0 through 255.
Cause
The value that you specified for the SPACE option was not in the range 0 through 255.
Effect
The DETAIL command fails.
Recovery
Correct the value of SPACE and resubmit.
SQL 15524
15524 The value of TAB is out of range. The valid range is the set of values from left margin to right margin.
Cause
The value that you specified for the TAB clause was less than the left margin or greater than the right margin.
Effect
The DETAIL command fails.
Recovery
Correct the value of TAB and resubmit.
SQL 15525
15525 The value for PAGE, NEED, or SKIP is out of range. The valid range is 1 through 32767.
Cause
The value that you specified for the PAGE, NEED, or SKIP clause was not in the range 1 through 32767.
Effect
The DETAIL command fails.
Recovery
Correct the value of PAGE, NEED, or SKIP and resubmit.
SQL 15526
15526 AS DATE or AS TIME format specified on an incompatible item type or on a value that is out of range.
Cause
You specified the AS DATE or AS TIME clause for an item whose type is not compatible with the format. These formats are valid only with numeric items with scale 0. The item value must be within the range 48731278400000000 through 274927291200000000. These values are the timestamps for the dates 02 JAN 0001 and 31 DEC 3999.
Effect
The operation fails.
Recovery
Correct the format and resubmit.
SQL 15527
15527 An internal error occurred in the report writer.
Cause
The operation resulted in the internal error of the Report Writer module specified in the command.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 15528
15528 Option name cannot be specified twice.
Cause
You specified an option more than once in the command.
Effect
The operation fails.
Recovery
Remove the duplicate entry and resubmit.
SQL 15529
15529 Alias OR detail-alias name cannot be used because a command-type command is using it.
Cause
You attempted to reset an alias name or detail-alias name that was being used in another report command. The name cannot be deleted while another command is dependent upon it.
Effect
The alias or detail-alias name is not reset.
Recovery
Remove all instances of this alias or detail-alias name from the current report commands and resubmit.
SQL 15530
15530 column-name not found in SELECT list.
Cause
The column name that you specified in the message could not be found in the list of columns specified in the SELECT statement.
Effect
The operation fails.
Recovery
Verify that the column is specified in the SELECT statement and that the name is spelled correctly, and resubmit.
SQL 15531
15531 Invalid column number. Numeric reference to a column specified in a SELECT statement must be an integer within the range 1 through value.
Cause
You specified an invalid column number that was not an integer within the range that is valid for the current select list. The column number must be an integer greater than zero and less than or equal to the number of columns specified in the select list.
Effect
The operation fails.
Recovery
Use a valid column number. and resubmit.
SQL 15532
15532 name is a duplicate item name.
Cause
The name that you specified has been previously specified. Each name must be unique.
Effect
The operation fails.
Recovery
Use only unique names and resubmit.
SQL 15533
15533 You have specified subtotal or break title or break footing or line_number on text1. You must specify a BREAK command on text2 before the LIST command.
Cause
You specified a SUBTOTAL, BREAK TITLE, or BREAK FOOTING command or a LINE_NUMBER function for a column that is not a BREAK column.
Effect
No report is generated.
Recovery
Enter a BREAK command for the specified column, or reissue the command that treats the column as a BREAK column.
SQL 15535
15535 The operand of JULTIME or DATEFORMAT function must have a DATETIME data type.
Cause
You used a JULIANTIMESTAMP or DATEFORMAT function with a column name having a data type other than DATETIME.
Effect
The operation fails.
Recovery
Reissue the command after connecting it.
SQL 15536
15536 The operand of the CONVERTTIMESTAMP function must have a LARGEINT data type (binary 64) with a scale of zero.
Cause
You used a CONVERTTIMESTAMP function with a column name having a data type other than LARGEINT (binary 64 with scale of zero).
Effect
The operation fails.
Recovery
Correct the problem and resubmit.
SQL 15537
15537 An invalid arithmetic operation was attempted between type1 and type2 data types.
Cause
The two operands of the binary arithmetic operator did not belong to data type classes that can be operated upon.
Effect
The operation fails.
Recovery
Check that the operands belong to data type classes that can be operated upon in a binary arithmetic expression.
SQL 15538
15538 An operand of the LIKE operator does not have a CHARACTER type.
Cause
You specified a column, pattern, or escape character in a LIKE predicate that does not have a character data type. The LIKE predicate can be used only on character data with type CHARACTER or VARCHAR.
Effect
The operation fails.
Recovery
Check the data types specified in the LIKE predicate and remove any numeric operands.
SQL 15539
15539 A literal string is required here.
Cause
The SQL parser required a literal string at or near the position pointed to by the marker.
Effect
The operation fails.
Recovery
Specify a literal string and recompile.
SQL 15540
15540 An invalid date and time was entered. The valid format is MM/DD/YY [Hr:Mi:Se:Ms:Us].
Cause
You specified an invalid date and time to compute the timestamp.
Effect
The operation fails.
Recovery
Correct the syntax or values and resubmit.
SQL 15541
15541 AS DATE or AS TIME format specified on an incompatible item type.
Cause
You specified an AS DATE or AS TIME format on an incompatible item type. AS DATE or AS TIME can be specified only on an item having a LARGEINT data type.
Effect
The operation fails.
Recovery
Correct the command and resubmit.
SQL 15542
15542 Unknown output device specified.
Cause
The report writer does not support the current output device.
Effect
The report writer output could show unexpected results.
Recovery
Set a valid output device by using the LOG command and resubmit.
SQL 15543
15543 Invalid hexadecimal characters were found in input.
Cause
A character other than a-z, A-Z, or 0-9 was found in the hexadecimal input.
Effect
The operation fails.
Recovery
Remove the invalid character and resubmit.
SQL 15544
15544 Comparisons between type1 and type2 data types are not allowed.
Cause
You attempted a comparison between incompatible data types in a relational, LIKE IN, or BETWEEN predicate. For example, you cannot compare a numeric value and a character value.
Effect
The operation fails.
Recovery
Check the data types of the operands of the predicate, and correct those that are incompatible.
SQL 15545
15545 Comparisons between SINGLEBYTE and MULTIBYTE datatypes are not allowed.
Cause
You attempted a comparison between incompatible data types in a relational, LIKE IN, or BETWEEN predicate.
Effect
The operation fails.
Recovery
Check the character sets of the operands of the predicate, and correct those that are incompatible.
SQL 15546
15546 Headings cannot span more than 15 lines.
Cause
You specified a heading clause that resulted in an item heading spanning more than 15 lines.
Effect
Although the command is accepted at parser level, it will fail at build time.
Recovery
Specify the heading clause with fewer "newline" characters.
SQL 15547
15547 name is a detail-alias-name. It not allowed in this command.
Cause
The column ID that you specified was a detail-alias name. In this command, a column ID must be a column name, COL n, or an alias name.
Effect
The operation fails.
Recovery
Reissue the command using only a column name, COL n, or an alias name.
SQL 15548
15548 The right margin does not exceed the left margin.
Cause
The right margin value that you specified did not exceed the left margin value, so the line width was less than or equal to zero.
Effect
The last margin value specified is ignored.
Recovery
Specify values that result in a right margin greater than the left margin.
SQL 15549
15549 column is nonnumeric. All total and subtotal items must be numeric.
Cause
You specified a non-numeric column in a TOTAL or SUBTOTAL command. Only numeric columns can be totaled or subtotaled.
Effect
The command is ignored.
Recovery
Reissue the command, using only numeric columns.
SQL 15550
15550 Format specification is not valid.
Cause
You specified an invalid format.
Effect
The operation fails.
Recovery
Correct the format and resubmit.
SQL 15551
15551 Numeric expression which was evaluated caused division by zero.
Cause
A numeric expression that you specified caused division by zero, which is not supported.
Effect
The operation fails.
Recovery
Correct the command and resubmit.
SQL 15552
15552 A delimited identifier must contain at least one nonblank character.
Cause
You specified a delimited identifier without a required nonblank character.
Effect
The operation fails.
Recovery
Correct the command and resubmit.
SQL 15553
15553 name is not an alias name.
Cause
The current command requires an alias name, but the name that you specified was not an alias.
Effect
The command is ignored.
Recovery
Reissue the command, using a valid alias name. To display current alias names, use the SHOW REPORT NAME command.
SQL 15554
15554 The operand for name must have a type datatype.
Cause
The operand for the function you specified does not have the correct data type.
Effect
The operation fails.
Recovery
Change the operand so that it has the specified data type.
SQL 15555
15555 Numeric literal has too many digits. A maximum of 17 digits can be specified with an integral number.
Cause
You specified a numeric literal with too many significant digits, which caused an arithmetic overflow.
Effect
The operation fails.
Recovery
Correct the literal and recompile.
SQL 15556
15556 Overflow occurred during arithmetic computation.
Cause
An intermediate result was too large to be held in the internal buffers. An intermediate result overflow can occur because of an arithmetic operation or an aggregation on large data values.
Effect
The operation fails.
Recovery
For an intermediate result overflow, use simpler arithmetic expressions in your statements.
SQL 15575
15575 column-ID is not specified in a current command-name command and cannot be reset.
Cause
The column ID displayed was specified in a RESET REPORT command. However, that column ID is not currently set by the corresponding report command.
Effect
The column ID is ignored by the RESET REPORT command.
Recovery
This is an informational message; no recovery is necessary.
SQL 15576
15576 There is no current name command to reset.
Cause
The command displayed was specified in a RESET REPORT command. However, there is no command of that type currently in effect.
Effect
The RESET REPORT command is ignored.
Recovery
This is an informational message; no recovery is necessary.
SQL 15577
15577 There are no more selected rows.
Cause
The command tried to list rows when there were no more rows to select.
Effect
None.
Recovery
If you do not want to select more data, use the CANCEL command to terminate the SELECT operation. If you want to see more data, use the LIST FIRST number command.
SQL 15803
15803 The current mode is Report.
Cause
You tried to change the mode to report while already in report mode.
Effect
The operation fails.
Recovery
None. This is an informational message only.
SQL 15804
15804 The current mode is SQL.
Cause
You tried to change the mode to SQL while already in SQL mode.
Effect
The operation fails.
Recovery
None. This is an informational message only.
SQL 15805
15805 The specified mode is not valid.
Cause
You tried to change the mode to an invalid mode.
Effect
None.
Recovery
Specify a valid mode.
SQL 15806
1558 The conversion failed.
Cause
You attempted to perform a conversion that is invalid.
Effect
The operation fails.
Recovery
None.
SQL 15807
15807 NULL cannot be assigned to a NOT NULL column.
Cause
You assigned NULL to a column for which NOT NULL was specified.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 15808
15808 An invalid column numberwas specified.
Cause
The column number specified in the table was invalid.
Effect
The operation fails.
Recovery
Specify a valid column number in the table and resubmit.
SQL 15809
15809 A string overflow occurred during the evaluation of a character expression.
Cause
A string overflow occurred during the evaluation of a character expression.
Effect
The operation fails.
Recovery
Increase the field size of the receiving field and resubmit.
SQL 15810
15810 The buffer allocated must be on an even boundary.
Cause
A computation occurred that resulted in an item overflowing its field.
Effect
The operation fails.
Recovery
The field size of the receiving field must be validated to be on an even boundary.
SQL 15811
15811 Unable to get a valid Report Writer Constructor.
Cause
MXCI was unable to connect to the Report Writer component.
Effect
Cannot switch to mode report in this session.
Recovery
Retry the command.
SQL 15812
15812 Unable to get a valid Report Writer Destructor.
Cause
MXCI was unable to connect to the Report Writer component.
Effect
Cannot disconnect from the Report Writer module.
Recovery
None.
SQL 15813
15813 The specified output device is not valid.
Cause
The output device specified was invalid.
Effect
Cannot switch to the output device specified.
Recovery
Specify a valid output device and resubmit.
SQL 15815
15815 An internal error occurred - unable to get a valid MXCS Constructor.
Cause
MXCI was unable to connect to the MXCS server and get a valid constructor.
Effect
The operation fails.
Recovery
Retry the operation.
SQL 15816
15816 An internal error occurred - unable to get a valid MXCS Destructor.
Cause
MXCI was unable to disconnect from the MXCS server.
Effect
The operation fails.
Recovery
Retry the operation.
SQL 15817
15817 The current mode is MXCS.
Cause
You tried to change the mode to MXCS while already in MXCS.
Effect
None.
Recovery
None. This is an informational message only.
SQL 15819
15819 Sequence generator does not support type-name datatype.
Cause
You attempted to create a sequence generator with an unsupported data type.
Effect
The statement fails.
Recovery
Modify and resubmit the statement.
SQL 15820
15820 ORDER and CACHE options are supported syntactically only.
Cause
You have specified the ORDER or CACHE in the CREATE SEQUENCE statement. These options are supported only at the syntax level.
Effect
The statement compiles with a warning.
Recovery
None.
SQL 15990
15990 Character set name for SQLCI attribute TERMINAL_CHARSET is not valid.
Cause
You specified an invalid character set name for SQLCI attribute TERMINAL_CHARSET in MXCI.
Effect
None.
Recovery
Specify a valid character set name for the TERMINAL_CHARSET attribute and resubmit.
SQL 15991
15991 Because of the new report definition command(s), the report is being started from the beginning.
Cause
A new report definition command(s) has been specified. The report is being started from the beginning.
Effect
A new report is being generated.
Recovery
None.
SQL 15592
15992 Usage information not found or could not be displayed.
Cause
The usage information for this module could not be found or could not be displayed.
Effect
No usage information is displayed.
Recovery
None.
SQL 15999
15999 An MXCI internal error occurred.
Cause
MXCI has received an internal error.
Effect
The operation fails.
Recovery
Report the entire message to your service provider.