SQLC and SQLCO preprocessor messages (13000 through 13999)

SQL 13001

13001 An internal error occurred. The SQL statement could not be translated.

Cause

An unanticipated error was detected.

Effect

The issued command fails.

Recovery

Retry the operation. If the problem persists, contact your service provider.

SQL 13002

13002 A syntax error was found near line number.

Cause

There is a syntax error near line number.

Effect

The preprocessor ignores the line.

Recovery

Correct the error and resubmit.

SQL 13003

13003 This feature is not supported.

Cause

You attempted to perform an SQLCO function that is not supported.

Effect

The operation fails.

Recovery

None. If the problem persists, contact your service provider.

SQL 13004

13004 No error.

Cause

The preprocessor has executed successfully.

Effect

None.

Recovery

Informational message only; no corrective action is needed.

SQL 13005

13005 A general programming error occurred in file name at line number.

Cause

The preprocessor has received a general programming error in file name near line number.

Effect

The preprocessor could not continue.

Recovery

Internal error. Contact your service provider.

SQL 13006

13006 Switch has bad value, value, for its expression at line number in file name.

Cause

The EXC_SWITCH_PROG_ERR switch has a bad value, value, for its expression. It is near line number in file name.

Effect

The preprocessor has received an internal error and is unable to process with this value.

Recovery

Internal error. Contact your service provider.

SQL 13007

13007 The output file argument is missing after the -c option.

Cause

You specified the -c option without giving the output file argument, which is required.

Effect

The operation fails.

Recovery

Provide the output file argument and resubmit. The syntax is:

-c out-file
      

Where,

out-file specifies the name of the preprocessed output source file containing the translated embedded SQL/MX statements. If you are preparing a C++ application, specify the name with the .cpp extension.

SQL 13008

13008 The module definition file argument is missing after the -m option.

Cause

You specified the -m option without giving the module definition file argument, which is required.

Effect

The operation fails.

Recovery

Provide the module definition file argument and resubmit. The syntax is:

-m mod-def-file
      

Where,

mod-def-file is the name of the module definition file that is to be the input file for the SQL/MX compiler.

SQL 13009

13009 The listing file argument is missing after the -l option.

Cause

You specified the -l option without giving the listing file argument, which is required.

Effect

The operation fails.

Recovery

Provide the listing file argument and resubmit. The syntax is:

-l list-file
      

Where,

list-file is the name of the SQL/MX C/C++ preprocessor error and warning message file.

SQL 13010

13010 The timestamp argument is missing after the -t option.

Cause

You specified the -t option without giving the timestamp argument, which is required.

Effect

The operation fails.

Recovery

Provide the timestamp argument and resubmit. The syntax is:

-t timestamp
      

Where,

timestamp is a creation timestamp for the preprocessor that is written to the two output files: the C/C++ source file and the SQL/MX module definition file. timestamp overrides the default operating system timestamp.

SQL 13011

13011 option is an unknown command line option.

Cause

You specified an option that SQLC does not recognize or support.

Effect

The preprocessor ignores the option.

Recovery

Correct the option and resubmit.

SQL 13012

13012 argument is an invalid or undefined command line argument.

Cause

You specified an argument that SQLC does not recognize or support.

Effect

The preprocessor ignores the argument.

Recovery

Correct the option and resubmit.

SQL 13013

13013 Help for SQLC and SQLCO is available by typing SQLC or SQLCO on the command line.

Cause

You did not enter any options.

Effect

None.

Recovery

Informational message only; no corrective action is needed. For more information, see online help for SQLC and SQLCO.

SQL 13014

13014 The output source file name could not be opened.

Cause

The preprocessor was unable to open file name.

Effect

The operation fails.

Recovery

Verify that the file exists and is readable and resubmit.

SQL 13015

13015 The module definition file name could not be opened.

Cause

The preprocessor was unable to open the module definition file name.

Effect

The operation fails.

Recovery

Verify that the file can be opened, created, or written to, depending upon the action you are attempting, and resubmit.

SQL 13016

13016 Descriptor name name1 conflicts with SQLC default name name2.

Cause

In a START statement, you specified descriptor name1,which duplicates the SQLC default name2.

Effect

The preprocessor ignores the duplicate descriptor name.

Recovery

Select a descriptor name that does not duplicate the SQLC default name, and resubmit.

SQL 13017

13017 Descriptor name is multiply defined.

Cause

You defined descriptor name more than once.

Effect

The preprocessor ignores the second definition.

Recovery

Remove the duplicate definition and resubmit.

SQL 13018

13018 Descriptor name name is not valid.

Cause

You specified the descriptor name,which is invalid.

Effect

The preprocessor ignores the invalid descriptor name.

Recovery

Correct the definition of this name and resubmit. Descriptor name is a value-specification, a literal or host variable with character data type.

SQL 13019

13019 Statement name name uses name, a reserved name SQLC generates.

Cause

You specified the statement name, which is a reserved name in SQLC.

Effect

The preprocessor ignores the statement name.

Recovery

Change the name to one that does not conflict with SQLC's reserved names. For more information, see the SQL/MX Reference Manual for a list of reserved names.

SQL 13020

13020 Statement name name is multiply defined.

Cause

You defined statement name more than once.

Effect

The preprocessor ignores the duplicate definition.

Recovery

Remove the duplicate definition and resubmit.

SQL 13021

13021 name is already defined.

Cause

The host variable name, which you attempted to define, has already been defined.

Effect

The preprocessor ignores the duplicate definition.

Recovery

Remove the duplicate definition and resubmit.

SQL 13022

13022 Cursor name is already defined.

Cause

The cursor name, which you attempted to define, has already been defined.

Effect

The preprocessor ignores the duplicate definition.

Recovery

Remove the duplicate definition and resubmit.

SQL 13023

13023 name is already defined as a dynamic cursor.

Cause

The cursor name, which you attempted to define, has already been defined as a dynamic cursor.

Effect

The preprocessor ignores the second definition of the cursor.

Recovery

Remove the duplicate definition and resubmit.

SQL 13024

13024 Cursor name was not declared.

Cause

The cursor name,which you attempted to use, has not been declared.

Effect

The preprocessor ignores the cursor.

Recovery

Declare the cursor and resubmit.

SQL 13025

13025 Warning(s) near line number.

Cause

NonStop SQL/MX received warnings near line number.

Effect

None.

Recovery

Informational message only; no corrective action is needed.

SQL 13026

13026 The EXEC SQL MODULE statement must precede any cursor definitions or executable SQL statements.

Cause

You attempted to declare a cursor or execute an SQL/MX statement without first using an EXEC SQL MODULE statement.

Effect

The preprocessor ignores the cursor or statement.

Recovery

Add the EXEC SQL MODULE statement before the cursor declaration or SQL/MX statement, and resubmit.

SQL 13027

13027 Only one EXEC SQL MODULE statement is allowed.

Cause

You specified more than one EXEC SQL MODULE statement when only one is supported.

Effect

The preprocessor ignores the second EXEC SQL MODULE statement.

Recovery

Remove the extra EXEC SQL MODULE statement, and resubmit.

SQL 13028

13028 Static cursor name cannot be opened because host- variableis out of scope at time of open.

Cause

The host-variableyou specified in the declare cursor name could not be used because it was out of scope at the time you attempted to open it.

Effect

The preprocessor ignores the cursor you specified.

Recovery

Find where the variable is declared and put it into the correct scope.

SQL 13029

13029 Found host variable(s) declared as long. The size of this data type is 4 bytes for 32-bit and 8 bytes for 64-bit applications. This can cause unintended behavior if not used properly.

Cause

32-bit and 64-bit modes have different sizes for long data type. Because of this, there might be some differences in behavior between 32-bit and 64-bit applications.

Effect

This is a warning message. The application behavior is undefined. The application behavior differs between 32-bit and 64-bit modes depending on how you intend to use the long data type.

Recovery

Review the use of long data type in the application. You can ignore this warning if you intend to use 8 byte data type in 64-bit mode and a 4 byte data type in 32-bit mode. Consider using int data type if you intend to use 4 byte data type in both 32-bit and 64-bit modes, and using a long data type if you intend to use 8 byte data type in both modes. Also, if you want to maintain a single source code and compile the application for both 32-bit and 64-bit modes, consider using int for 32-bit storage and long for 64-bit storage.

SQL 13030

13030 line number detail text

Cause

This generic error is displayed when the preprocessor detects a syntax error.

Effect

The preprocessor could not prepare the statement.

Recovery

Use the detail text to determine the problem.

SQL 13031

13031 Expecting a single host variable of type string.

Cause

You attempted to execute a PREPARE or EXECUTE IMMEDIATE statement. The preprocessor found one of these errors:

• You did not specify more than one host variable of this type.

• The host variable that you specified is not character type STRING.

Effect

The preprocessor ignores the host variable.

Recovery

Correct the host variable and resubmit.

SQL 13032

13032 Not expecting input host variables for static cursor name.

Cause

You specified input host variables for cursor name. An open cursor does not need host variables.

Effect

The preprocessor ignores the host variables you specified for this cursor.

Recovery

Remove the host variables and resubmit.

SQL 13033

13033 Host variable name1 is in different scope than when cursor name2 was declared.

Cause

You specified a host variable name name1, which is out of scope with cursor name.

Effect

The preprocessor ignores the host variable you specified.

Recovery

Find where the variable is declared and put it in the correct scope.

SQL 13034

13034 Character set name is not yet supported.

Cause

You specified character set name, which is not supported.

Effect

The preprocessor ignores the specified character set and uses the default character set.

Recovery

Replace the character set name you specified with one that is supported. For more information about character sets, see the SQL/MX Reference Manual.

SQL 13035

13035 Invalid line number number for line pragma; ignoring the rest.

Cause

You specified an invalid line number.

Effect

The preprocessor ignores the line.

Recovery

Remove or correct the line number and resubmit.

SQL 13036

13036 C/C++ syntax error in switch/for/while condition near line number.

Cause

The preprocessor encountered a C/C++ syntax error near line number.

Effect

The preprocessor ignores the switch/for/while condition.

Recovery

Correct the syntax error and resubmit.

SQL 13037

13037 Function header syntax error was found near line� number.

Cause

There is a function header syntax error near line number.

Effect

The preprocessor ignores the function header syntax. The syntax error is not allowed.

Recovery

Correct the syntax and resubmit.

SQL 13038

13038 Array size size was expected to be an unsigned integer near line number.

Cause

You specified an array size, near line number, which was not an unsigned integer as required.

Effect

The preprocessor ignores the array specification.

Recovery

Replace the array size and resubmit.

SQL 13039

13039 Function definition is not allowed within a SQL declare section - near line number number.

Cause

You specified a function definition within an SQL/MX declare section near line number, which is not supported.

Effect

The preprocessor ignores the function definition.

Recovery

Move the function definition and resubmit.

SQL 13040

13040 A ")" was expected near line number.

Cause

The preprocessor requires a right parenthesis near line number.

Effect

The preprocessor ignores the parenthetical statement.

Recovery

Correct the syntax by adding a right parenthesis or removing an extra left parenthesis.

SQL 13041

13041 Typedef encountered near line number, and typedefs are not supported.

Cause

You specified a typedef near line number, which is not supported.

Effect

The preprocessor ignores the typedef.

Recovery

Remove the typedef and resubmit.

SQL 13042

13042 Unnamed declaration was found near line number.

Cause

You specified an unnamed declaration near line number,which is not supported.

Effect

The preprocessor ignores the declaration.

Recovery

Add a name for the declaration and resubmit.

SQL 13043

13043 syntax item was expected near line number.

Cause

The preprocessor required one of these items; equal sign (=), comma (,), or right parenthesis ()), and did not find it. The missing syntax item is near line number.

Effect

The preprocessor ignores the declaration list that contains this item.

Recovery

Correct the syntax and resubmit.

SQL 13044

13044 Type specification syntaxname is not a recognized type near - line number.

Cause

You specified an unrecognized type specification near line number.

Effect

The preprocessor ignores the type specification.

Recovery

Replace this type specification with one that is recognized.

SQL 13045

13045 An unexpected class declaration was found near line number;it will be ignored.

Cause

An unexpected class declaration occurred near line number.

Effect

The class declaration is ignored, and the preprocessor continues.

Recovery

Move the class declaration to its correct location and resubmit.

SQL 13046

13046 "}" was expected to end member declaration - near line number.

Cause

You did not specify a required right bracket (}) to end a member declaration. The missing bracket is near line number.

Effect

The preprocessor ignores the bracketed item.

Recovery

Supply the missing bracket.

SQL 13047

13047 Undefined tag name was found near line number.

Cause

You specified an undefined tag namenear line number.

Effect

The preprocessor ignores the tag.

Recovery

Define the tag and resubmit.

SQL 13048

13048 Tag name was redefined - near line number.

Cause

You redefined tag name near line number.

Effect

The preprocessor ignores the redefinition.

Recovery

Remove the redefinition and resubmit.

SQL 13049

13049 Input file is not good near line number.

Cause

The preprocessor could not read the input file.

Effect

The preprocessor ignores the input file.

Recovery

Correct the file problem and resubmit.

SQL 13050

13050 Cursor name is not closed.

Cause

Cursor name was not closed.

Effect

None.

Recovery

Informational message only; no corrective action is needed.

SQL 13051

13051 Cursor name is not opened.

Cause

Cursor name was not opened.

Effect

The cursor could not be used.

Recovery

Open the cursor.

SQL 13052

13052 Cursor name is not fetched.

Cause

Cursor name was not fetched.

Effect

None.

Recovery

Informational message only; no corrective action is needed.

SQL 13053

13053 Cursor name is not opened or closed.

Cause

Cursor name was not opened or closed.

Effect

The cursor could not be used.

Recovery

Open the cursor.

SQL 13054

13054 Cursor name is not fetched or closed.

Cause

Cursor name was not fetched or closed.

Effect

None.

Recovery

None. This is a warning message.

SQL 13055

13055 Cursor name is not opened or fetched.

Cause

Cursor name was not opened or fetched.

Effect

None.

Recovery

None. This is a warning message.

SQL 13056

13056 Cursor name is not used.

Cause

Cursor name was not used.

Effect

None.

Recovery

None. This is a warning message.

SQL 13057

13057 End-of-file processing generated unexpected cursor status of status for cursor name.

Cause

During end-of-file processing, the preprocessor received an unexpected cursor status for cursor name.

Effect

The preprocessor fails.

Recovery

Internal error. Contact your service provider.

SQL 13058

13058 SQL CLI header file name could not be opened.

Cause

The preprocessor was unable to open the SQL CLI header file name.

Effect

The preprocessor ignores the SQL CLI header file.

Recovery

Verify that the SQL CLI header file exists and is readable, and resubmit.

SQL 13060

13060 The listing file namecould not be opened.

Cause

The preprocessor was unable to open the listing file name.

Effect

The preprocessor ignores the listing file.

Recovery

Verify that the SQL CLI header file or device exists and is readable, and resubmit.

SQL 13061

13061 An invalid NUMERIC precision was specified - near line number.

Cause

You specified a data item with invalid NUMERIC precision near line number.

Effect

The preprocessor ignores the UNSIGNED NUMERIC item.

Recovery

Correct the precision of the item and resubmit.

SQL 13062

13062 Unsigned 64 bit Integer types are not allowed - near line linetext-number.

Cause

You have used one of the following unsupported data types as a host variable:

• Unsigned long in a 32-bit or 64-bit application

• Unsigned long in a 64-bit application

Effect

The preprocessor stops processing.

Recovery

Specify a corresponding SQL/MX type, which is supported for this item.

SQL 13063

13063 Identifier name is not defined - near line number.

Cause

Identifier name was not defined near line number.

Effect

The preprocessor ignores the identifier.

Recovery

Correct the syntax and resubmit.

SQL 13064

13064 Identifier name1 is not a member of struct name2 - near line number.

Cause

Identifier name1 is not a member of the structure name2 near line number.

Effect

The preprocessor ignores the identifier.

Recovery

Correct the syntax and resubmit.

SQL 13065

13065 End of file was found after syntax-item1 when syntax-item2 was expected, near line number.

Cause

The compiler found end-of-file specified after syntax-item1 when it was expecting syntax-item2near line number.

For example, when the preprocessor parses host variables in an EXEC SQL/MX statement, they must be preceded with a : (colon). If the colon is missing, the preprocessor would probably find the name of the host variable next, but keeps looking until it reaches the end of file or finds a colon. If it reaches end-of-file first and the next thing the preprocessor finds before reaching the end-of-file is the name of a host variable, the message would look like this:

*** ERROR[13065] End of file was found after host variable expression when : was expected, near line 54.

Effect

The preprocessor ignores the identifier.

Recovery

Correct the syntax and resubmit.

SQL 13066

13066 Identifier name was expected to be a structure type - near line number.

Cause

The identifier name you specified was expected to be a structure type near line number.

Effect

The preprocessor ignores the identifier.

Recovery

Correct the syntax and resubmit.

SQL 13067

13067 Source file namecould not be opened.

Cause

The preprocessor was unable to open file name.

Effect

The preprocessor ignores the referenced file.

Recovery

Verify that the file exists and is readable and resubmit.

SQL 13068

13068 A C/C++ syntax error was found - near line number.

Cause

NonStop SQL/MX detected a C/C++ syntax error near the line number listed in the message.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13069

13069 Module specification string argument is missing after -g option.

Cause

The option you specified was incomplete. The -g option, specified on the mxsqlcor mxsqlocommand line, was not followed by any other command line argument.

Effect

The option is incomplete, and mxsqlc or mxsqlo returns this error message.

Recovery

Reinvoke the preprocessor, either by totally omitting the -g option or by supplying a complete -g option (-g moduleGroup, -g moduleTableset, or -g moduleVersion).

SQL 13070

13070 Module Group Specification string MGSS-string is not a regular identifier, or is longer than 31 characters.

Cause

The Module Group Specification String (MGSS) you specified is not a regular identifier or is longer than 31 characters.

Effect

The embedded SQL source file is not successfully preprocessed.

Recovery

Reinvoke the preprocessor, this time specifying a regular identifier for the MGSS.

SQL 13071

13071 Module Tableset Specification string MTSS-string is not a regular identifier, or is longer than 31 characters.

Cause

The Module Tableset Specification String (MTSS) you specified is not a regular identifier or is longer than 31 characters.

Effect

The embedded SQL source file is not successfully preprocessed.

Recovery

Reinvoke the preprocessor, this time specifying a regular identifier for the MTSS.

SQL 13072

13072 Module Version Specification string MVSS-string is not a regular identifier, or is longer than 31 characters.

Cause

The Module Version Specification String (MVSS) you specified is not a regular identifier or is longer than 31 characters.

Effect

The embedded SQL source file is not successfully preprocessed.

Recovery

Reinvoke the preprocessor, this time supplying a regular identifier for the MVSS.

SQL 13073

13073 Module name module-name is not a valid OSS file name or is longer than 128 characters.

Cause

A MODULE directive has specified a delimited identifier module name that has one of four invalid characters (@, /, \, ^) or has more than 128 characters.

Effect

The module name is invalid, and this error is generated.

Recovery

Reinvoke the preprocessor, this time supplying an embedded SQL source file that has a valid module name in its MODULE directive.

SQL 13074

13074 One or more of the three parts of the externally qualified module name module-name is longer than 128 characters.

Cause

An externally qualified module name consists of three parts: a catalog, a schema, and a one-part module name that has been qualified with Module Group Specification String (MGSS), Module TableSet Specification String (MTSS), or Module Version Specification String (MVSS). If module name is longer than 128 characters (because of adding MGSS, MTSS, or MVSS) or if the catalog or schema is longer than 128 characters, this error message is generated.

Effect

The embedded SQL source file is not successfully preprocessed.

Recovery

Reinvoke the preprocessor, this time supplying a shorter value for any or all the MGSS, MTSS, MVSS, or for the one-part module name coded in the embedded SQL source file's MODULE directive.

SQL 13075

13075 Externally qualified module name module-name cannot be longer than 248 characters.

Cause

The length of the three-part externally qualified module name exceeds 248 characters.

Effect

It is not possible to the use the three-part externally qualified module name to name the OSS file in which the module will be stored. Also, the embedded SQL source file is not successfully preprocessed or the Java Profile is not customized.

Recovery

Reinvoke the preprocessor or customizer, this time supplying a shorter value for any or all the MGSS, MVSS, MTSS, for the one-part module name coded in the embedded SQL source file's MODULE directive, or the default catalog or schema if the MODULE directive is encoded as a one-part name.

SQL 13076

13076 Catalog name catalog-name is not a valid OSS file name or is longer than 128 characters.

Cause

The four invalid characters (@, /, \, ^) or has more than 128 characters.

Effect

The catalog name is invalid, and this error is generated.

Recovery

Reinvoke the preprocessor, this time supplying an embedded SQL source file that has a valid catalog name in its MODULE directive.

SQL 13077

13077 Schema name schema-name is not a valid OSS file name or is longer than 128 characters.

Cause

A MODULE directive specified a delimited identifier schema name that has one of the four invalid characters (@, /, \, ^) or has more than 128 characters.

Effect

The schema name is invalid, and this error is generated.

Recovery

Reinvoke the preprocessor, this time supplying an embedded SQL source file that has a valid schema name in its MODULE directive.

SQL 13078

13078 Module catalog catalog name is not a valid identifier or is longer than 128 characters.

Cause

You invoked an SQL preprocessor or mxCompileUserModule with a modulecatalog=catalog name option where catalog name is not a valid SQL identifier.

Effect

The operation fails.

Recovery

Verify that catalog name is a valid SQL identifier and retry the command.

SQL 13079

13079 Module schema schema name is not a valid identifier or is longer than 128 characters.

Where,

schema name is the name of the schema.

Cause

You invoked an SQL preprocessor or mxCompileUserModule with a moduleschema=schema name where schema name is not a valid schema name.

Effect

The operation fails.

Recovery

Verify that schema name is a valid schema name and retry the command.

SQL 13080

13080 Externally qualified module name module-name cannot be longer than 160 characters.

Cause

You invoked the COBOL preprocessor MXSLCO and the process of externally qualifying the input source file's MODULE directive resulted in a module file name that exceeds COBOL's maximum length for a non-numeric literal.

Effect

The command fails.

Recovery

Shorten one or more of the following and reissue the COBOL preprocessing command:

• The module name in the input source file's MODULE directive.

• -g moduleCatalog=module catalog name>.

• -g moduleSchema=module schema name>.

• -g moduleGroup=module group specification string>.

• -g moduleTableSet=module tableset specification string>.

• -g moduleVersion= module version specification string>.

SQL 13082

13082 Incompatible addressing model. This source file was generated for a mode addressing model.

Cause

The pre-processing mode and the C/C++ compilation mode do not match. If mode is 64-bit, the C/C++ compiler was in 32-bit mode or conversely.

Effect

The C/C++ compilation fails.

Recovery

Ensure that the host language compilation mode matches the pre-processing mode.

SQL 13083

13083 Only INVOKED structures or VARCHAR compatible structures or records(without the NULL structure option) can be standalone host variables.

Cause

An incompatible structure was specified to hold VARCHAR data in the embedded SQL application.

Effect

Preprocessor fails to process the application. Module and cpp files are not generated.

Recovery

Specify a structure compatible with VARCHAR data, and preprocess the application.

SQL 13084

13084 Exceeded the maximum nesting level of 200 at line-number

Where,

line-number is the line number of the #includedirective.

Cause

The #include directive exceeded the nesting limit of 200 levels in the embedded SQL application.

Effect

Preprocessor fails to process the application.

Recovery

Remove the #include directive that exceeds the maximum nesting level limit, and preprocess the application.

SQL 13085

13085 <SQLCODE/SQLSTATE >is not declared inside the SQL declare section

Where,

<SQLCODE/SQLSTATE> is the variable to hold either SQLCODE or SQLSTATE.

Cause

The variables to hold either SQLCODE or SQLSTATE or both were not declared in the SQL declare section of the embedded SQL application.

Effect

None. This message is a warning. The preprocessor continues to process the subsequent statements after returning this warning.

Recovery

Declare variables to hold either SQLCODE or SQLSTATE or both, in the SQL declare section and preprocess the application.

SQL 13086

13086 <SQLCODE/SQLSTATE> variable is not declared of type <long/char[6]>inside the declare section

Where,

<SQLCODE/SQLSTATE>is the host variable to hold either SQLCODE or SQLSTATE;

<long/char[6]> is the variable data type, either long or char[6].

Cause

The data type of a variable declared in the SQL declare section to hold either SQLCODE or SQLSTATE or both was not correct. The variable type to hold SQLCODE must be long and to hold SQLSTATE must be char[6].

Effect

None. This message is a warning. Preprocessor continues to process the application after returning this warning.

Recovery

Declare a long or char[6] variable to hold either SQLCODE or SQLSTATE in the declare section, and preprocess the application.

SQL 13087

13087 The warning type argument is missing after the -w option.

Cause

For preprocessing the embedded SQL application, command line argument was not specified after -w option.

Effect

Preprocessor fails to process the application because the -w option is incomplete.

Recovery

Specify any one of the options -w sqlcode, -w sqlstate, -w both, or do not specify the -woption, and preprocess the application.

SQL 13088

13088 The argument argumentis improper for -f option use CHAR_AS_ARRAY or CHAR_AS_STRING

Where,

argument is the argument specified for -f option.

Cause

For preprocessing the embedded SQL application, command line argument was not specified or was specified wrongly after -f option.

Effect

Preprocessor fails to process the application.

Recovery

Specify any one of the options -f CHAR_AS_ARRAY, -f CHAR_AS_STRING or do not specify the -f option, and preprocess the application.

Note: If both -f CHAR_AS_ARRAY or -f CHAR_AS_STRING are specified, the second option is considered.

SQL 13089

13089 The include file file-nameincludes itself at line-number.

Where,

file-name is the file name in the #include statement;

line-number is the line number of the #include statement.

Cause

Include file includes itself in a circular manner in the embedded SQL application.

Effect

None. This message is a warning. Preprocessor ignores the #include directive, and processes the subsequent statements.

Recovery

Remove the #include directive, which returns this warning.

SQL 13090

13090 Could not obtain the temporary directory for module definition file.

Cause

SQL/MX preprocessor could not obtain the temporary directory while attempting to create the temporary module definition file.

Effect

SQL/MX preprocessor stops processing the embedded SQL source file.

Recovery

SQL 13501

13501 Specified command option nameis not valid.

Cause

You specified an invalid command option name.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13502

13502 Source file name must be specified.

Cause

You did not enter the source file name, which is required.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13503

13503 Filename for command option nameis missing.

Cause

You did not enter the file name for the command option name.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13504

13504 Timestamp command option is missing.

Cause

You did not enter the timestamp command option.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13505

13505 Source input file name cannot be opened.

Cause

NonStop SQL/MX could not open the source input file name.

Effect

The operation fails.

Recovery

Check the file's location, name, and security, verify that no other process has it open, and resubmit. Check that the source and output file names are not the same, so that the preprocessor will not overwrite the source file.

SQL 13506

13506 COBOL output source file name cannot be opened.

Cause

NonStop SQL/MX could not open the COBOL output source file name.

Effect

The operation fails.

Recovery

Check the file's location, name, and security, verify that no other process has it open, and resubmit. Check that the source and output file names are not the same, as the preprocessor will not overwrite the source file.

SQL 13507

13507 Error while parsing source: detail text.

Cause

NonStop SQL/MX encountered an error while parsing the source detail text.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13508

13508 Expecting keyword, found keyword.

Cause

You did not enter the keyword or character that NonStop SQL/MX required. When the preprocessor is processing the code within a control block such as IF, WHILE, DO, or is at the end of one, it looks for the keyword that ends that block and then a semicolon, and issues this message if that keyword or character is not found: For example:

In an IF or WHILE block:

*** ERROR[13508] Expecting END, found EXEC.

When IF is not followed by THEN:

*** ERROR[13508] Expecting THEN, found ;.

When WHILE is not followed by DO:

*** ERROR[13508] Expecting DO, found ;.

When the keyword END is not followed by a semicolon while processing an IF or WHILE block:

*** ERROR[13508] Expecting ;, found EXEC.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13509

13509 Expecting keyword1 after keyword2, found keyword3.

Cause

You did not enter the keyword that NonStop SQL/MX was expecting. When the preprocessor encounters certain keywords, it expects them to be followed by other specific keywords. For example:

This error is issued if the preprocessor does not find the keyword DIVISION immediately after any of these keywords:

IDENTIFICATION

ENVIRONMENT

DATA

WORKING-STORAGE

PROCEDURE

***ERROR[13509] Expecting DIVISION after DATA, found EXEC.

This error is issued if the preprocessor does not find the keyword SECTION immediately after any of these keywords:

FILE

LINKAGE

***ERROR[13509] Expecting SECTION after FILE, found EXEC.

This error is issued if the preprocessor does not find the picture representation immediately after the keyword PICTURE:

***ERROR[13509] Expecting picture specification after PICTURE, found EXEC.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13510

13510 The SQL declare section may not contain COPY or REPLACE.

Cause

You specified COPY or REPLACE statements in the SQL declare section.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13511

13511 End of input file was reached while processing EXEC SQL.

Cause

NonStop SQL/MX reached the end of the input file while processing EXEC SQL. The preprocessor was looking for the termination of the EXEC SQL/MX statement and reached the end of the file before detecting the end of the statement. There can be mismatched quote marks or parentheses.

Effect

The operation fails.

Recovery

Correct the syntax of the EXEC SQL/MX statement and resubmit.

SQL 13512

13512 Input file error while processing EXEC SQL.

Cause

NonStop SQL/MX received an input file error while processing EXEC SQL.

Effect

The operation fails.

Recovery

Use the errors that accompany this one to diagnose and correct the problem.

SQL 13513

13513 The BIT data type is not implemented in SQL/MX.

Cause

You specified the BIT data type, which is not supported in NonStop SQL/MX.

Effect

The operation fails.

Recovery

Specify a data type that NonStop SQL/MX supports.

SQL 13514

13514 The CHARACTER SET attribute is not implemented in SQL/MX.

Cause

You specified the CHARACTER SET attribute, which is not supported in NonStop SQL/MX.

Effect

The operation fails.

Recovery

Specify a data type that NonStop SQL/MX supports.

SQL 13515

13515 Picture clause is not valid for a host variable.

Cause

You specified an invalid PICTURE clause for a host variable. The PICTURE clause must be one of:

PIC[TURE] X (length)

PICTURE [S] { 9(integer) [V9(scale)]][V9(scale) }

[USAGE [IS]] DISPLAY [SIGN [IS] LEADING SEPARATE [CHARACTER]]

PICTURE [S] { 9(integer) [V9(scale)]][V9(scale) }

[USAGE [IS]] { COMP[UTATIONAL]][COMP-5][BINARY }

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13516

13516 Unexpected end of input file encountered after line number.

Cause

NonStop SQL/MX reached the end of the input file while processing EXEC SQL.

Effect

The operation fails.

Recovery

Correct the input file and resubmit.

SQL 13517

13517 Line number is too long to process and has been truncated.

Cause

The text in line number is longer than the buffer and has been truncated.

Effect

NonStop SQL/MX truncates the line, which can affect compilation.

Recovery

Correct the syntax and resubmit.

SQL 13518

13518 Line number cannot be interpreted as a COBOL line type.

Cause

The text in line number could not be interpreted as a COBOL line type.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13519

13519 Line number contains an unterminated character literal.

Cause

The text in line number contains an unterminated character literal.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13520

13520 Line number does not correctly continue a character literal.

Cause

The text in line numberdoes not correctly continue a character literal.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13521

13521 Line number: DISPLAY host variables must be SIGN LEADING SEPARATE.

Cause

You attempted to define a DISPLAY host variable other than as a SIGN LEADING SEPARATE data type at line number.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13522

13522 DECLARE SECTION cannot be nested.

Cause

You specified the DECLARE SECTION as nested code.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13523

13523 END DECLARE SECTION encountered without a matching BEGIN DECLARE SECTION.

Cause

You specified an END DECLARE SECTION without a matching BEGIN DECLARE SECTION.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13524

13524 DECLARE SECTION encountered in unexpected program section.

Cause

You specified the DECLARE SECTION in a section where it was not expected by SQLCO.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13525

13525 Variable name may not be allocated correctly for a host variable.

Cause

Variable name might not be allocated correctly for a host variable.

Effect

Check that you declared the variable correctly. An incorrect variable can result in incorrect data from the COBOL compiler.

Recovery

Informational message only; no corrective action is needed.

SQL 13526

13526 Line number, variable name: clause type clause is not� valid for a host variable,

Cause

You specified a clause type JUST or OCCURS clause for variable name on line number.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13527

13527 The first declaration in a SQL DECLARE SECTION must have level 01 or 77.

Cause

You specified an incorrect SQL DECLARE SECTION. Its first declaration must be level 01 or 77.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13528

13528 Line number: Variable name is not alphabetic and cannot have a CHARACTER SET clause.

Cause

You defined variable name, which is not alphabetic, with a CHARACTER SET clause at line number.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13529

13529 Missing END DECLARE SECTION detected at line number.

Cause

The END DECLARE SECTION statement is missing near line number.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 13800

13800 Line number: name is not a valid character set name.

Cause

You specified an invalid character set name at line number.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.