DB2 Server for VSE Messages and Codes (Version 7 Release 5)

Chapter 8. ARI0520-ARI0535, ARI5806-AR5810 Catalog

Maintenance Messages

All messages written during catalog generation,

Access Errors,” on page 365, or “INCLUDE FILE

catalog migration, and catalog index

ERRORS” in the HELP text.

reorganization are written to the SYSLST file.

System Action: If &1C. is ARISCAT, database

These include any error messages as well as

generation ends unsuccessfully.

status messages. If an error occurs while trying to

Programmer response: If &1C. is ARISCAT, take

write to SYSLST, message ARI0527A is written to

action based on the Reason Code and Return Code

the operator console.

values.

ARI0520E Storage allocation failure. Reason Code

ARI0522E Catalog generation control record error

= nn.

catalog generation control record.

Explanation: In allocating virtual storage during

Explanation: An error occurred while trying to

catalog generation, a GETVIS macro failure occurred.

process a catalog generation control record from the

the return code from the GETVIS macro:

ARISCAT file. This file is a library source statement

No more GETVIS storage available.

member (in the A sublibrary). One of the following

conditions was detected:

Hardware storage error.

v A missing or invalid keyword

any other value

v A missing or invalid parameter

DB2 Server for VSE system error.

v An invalid numeric field

System Action: Database generation ends.

v An invalid record format.

System Programmer Response: Take action based on

the REASON value:

The invalid record is printed as the second line of the

message.

The database manager partition does not have

enough virtual storage. Either modify DB2

System Action: Database generation ends.

Server for VSE initialization parameters so that

System Programmer Response: Make a record of

less storage is required, or reconfigure the

what went wrong and contact the designated support

system so you have a larger database manager

group for your installation. Restart the database

partition. Restart the database generation.

generation after the problem is corrected.

You have a main storage hardware error.

Report this to your installation hardware

ARI0523E DBSS error occurred while processing

service person. When the problem is corrected,

the system catalog. Reason Code = nn.

restart the database generation.

Explanation: In an attempt to update the database

Any other reason

during the catalog generation stage of database

Make a record of what went wrong and

generation, or the catalog update phase of ADD

contact the designated support group for your

DBSPACE, or while catalog migration was processing

installation. When the problem is corrected,

the catalog, a DBSS error occurred. The cause is

restart database generation.

described by the Reason Code=nn value in the message

text. The Reason Code values are DBSS return codes.

ARI0521E ACCESS error &1C. MACRO &2., input

Refer to the description of the DBSS return codes under

file. Reason Code = nn. Return Code =

Chapter 17, “DBSS Return Codes,” on page 231.

nn.

System Action: Processing is terminated.

Explanation: An error occurred while the system was

Operator Response: Refer this message to your

trying to access the ARISCAT file. This file is a member

system programmer.

in the library source statement member (in the A

sublibrary). The Reason Code is the Primary Error

System Programmer Response: Refer to the

Code. The Return Code value is the Secondary Error

description of the DBSS return codes under Chapter 17,

Code. For further explanation, look up the displayed

“DBSS Return Codes,” on page 231. Make a record of

error codes under either Chapter 22, “Include File

what went wrong and contact the designated support

group for your installation.

111

ARI0520-ARI0535, ARI5806-ARI5810 Catalog Maintenance Messages

If the problem occurred during database generation,

successfully created without the user ID on this user ID

restart database generation when the problem is

record defined in the catalog table

corrected.

SYSTEM.SYSUSERAUTH. You may either:

v Enter a GRANT command for the user specifying the

If the problem occurred during ADD DBSPACE,

appropriate authority and password. See the DB2

execute the DB2 Server for VSE start up procedure with

Server for VSE & VM Interactive SQL Guide and

the following parameters:

Reference manual.

STARTUP=W

SYSMODE=S

v Compare the invalid record with the description of

PROGNAME=ARISEGB

the NAME column in the SYSTEM.SYSUSERAUTH

catalog table as discussed in the DB2 Server for VSE

This is necessary because the information about the

System Administration manual.

DBSPACEs is already recorded in the database. By

specifying the above parameters only the catalog

ARI0527E access error filename. Reason Code = nn.

update phase of ADD DBSPACE will be executed.

Return Code = cc [nnnn].

Explanation: An error occurred in an attempt to

ARI0524E Required objecttype objectname not

access SYSLST or SYSIPT.

found in catalogname.

If the nnnn value is included in the message, it reflects

Explanation: In an attempt to locate the DB2 Server

an attempt to display message ARInnnn.

for VSE objecttype objectname, an error occurred.

objecttype can be index, link, column, catalog or

The Reason Code value is the Primary Error Code. The

package. If objecttype is an index, link, or column, the

Return Code value is the Secondary Error Code. For

associated catalogname is displayed in the message text.

further explanation, look up the displayed error codes

under either Chapter 21, “Sequential File Errors,” on

System Action: The DB2 Server for VSE database

page 361, or “SEQ FILE ERRORS” in the HELP text.

maintenance is terminated.

System Action: If access is GET or CLOSE for file

System Programmer Response: Make a record of

name SYSIPT, the system was trying to read an INSERT

what went wrong and contact the designated support

record during the catalog generation. The record and

group for your installation. Restart the database

any additional records will be ignored by the system;

maintenance function when the problem is corrected.

the database generation continues.

If access is OPEN for file name SYSLST, database

ARI0525E Number of columns is incorrect in

generation, index reorganization, or release empty

catalog catalogname.

pages processing ends, but catalog migration continues.

Explanation: This is a DB2 Server for VSE

If access is PUT or CLOSE for file name SYSLST,

programming error. An inconsistency was found in the

processing continues.

required number of columns for catalogname and the

actual number of columns which the database manager

Operator Response: For corrective action, look up the

defined for this catalog during database generation.

displayed error codes under either Chapter 21,

The catalog generation stage determined that internal

“Sequential File Errors,” on page 361, or “SEQ FILE

data areas were incorrect.

ERRORS” in the HELP text.

System Action: Database generation is terminated.

System Programmer Response: See Operator

Response.

System Programmer Response: Make a record of

what went wrong and contact the designated support

Refer to message ARInnnn (where nnnn is the value

group for your installation. Restart database generation

identified in the message text) to determine what

when the problem is corrected.

system condition caused the message to be displayed.

ARI0526A Error on user ID record. user ID record

ARI0528I

User userid defined with password

password auth.

Explanation: A user-supplied user ID record was

being processed during the catalog generation stage of

Explanation: User userid has been defined to the

database generation and a syntax error or

database with password password and authorization

missing/invalid keyword/parameter was detected. The

auth (where auth may be any combination of DBA,

incorrect record is displayed as the second line of the

SCHED, and RES) and inserted into the catalog table

message.

SYSTEM.SYSUSERAUTH.

System Action: The user ID record is ignored and

System Action: Database generation continues.

database generation continues.

System Programmer Response: The database has been

112

Messages and Codes

ARI0520-ARI0535, ARI5806-ARI5810 Catalog Maintenance Messages

System Programmer Response: Make a record of

ARI0529I

&1. is completed.

what went wrong and contact the designated support

Explanation: This is the expected response from the

group for your installation.

database manager. The function is successfully

completed. &1. can be:

ARI0532I

Package &1. has been marked invalid.

v CATALOG GENERATION

v INDEX REORGANIZATION

Explanation: Catalog index reorganization processing

v FORWARD MIGRATION

has marked a package invalid.

v RELEASE EMPTY PAGES

&1. is owner.packagename.

System Action: The program continues processing

User Response: You can use this message to

until the end.

determine which packages catalog index reorganization

has marked invalid.

ARI0530E An error occurred while attempting to

free storage. Reason Code = nn.

Note: If an error occurs that causes catalog index

reorganization to fail, these messages no longer

Explanation: In freeing virtual storage during catalog

apply.

generation, a VSE FREEVIS macro failure occurred. The

Reason Code value nn is the return code from the

FREEVIS macro. This condition is a VSE

ARI0533E Catalog migration error processing

object.

System Action: Processing continues.

Explanation: An error occurred during forward

System Programmer Response: Make a record of

migration while modifying the SYSTEM CATALOG.

what went wrong and contact the designated support

The object can be a SYSTEM CATALOG table, column,

group for your installation.

or index. This message is followed by message

ARI0504I, which indicates the condition that caused the

ARI0531E DBSS error. Return Code = &1A..

error and message ARI0505I. Message ARI0505I

Reason Code = &2A., &3.=&4..

provides the SQLCODE information.

Explanation: An error occurred during catalog index

Note: The SQLCODE information in the accompanying

reorganization when the database manager attempted

ARI0505I message should be less than 0 (zero).

to perform a DBSS action.

System Action: The catalog migration is terminated.

The DBSS returns an error code shown in the Return

Code value. (See Chapter 17, “DBSS Return Codes,” on

System Programmer Response: If this error occurs

page 231 for an explanation of DBSS return codes.)

during forward migration processing (STARTUP=M),

make a record of what went wrong and contact the

The Reason Code value describes the type of DBSS

designated support group for your installation.

operation that was in progress when the error occurred.

Opening a scan

ARI0534E A column named &1. already exists in

Closing a scan

&2..

Deleting (either a row or an Index Control

Explanation: A column name &1. was found in &2.

Record)

that was not created by the database manager. The

forward migration process cannot continue.

System Action: The program is terminated.

Fetch (either a row or an Index Control

Record)

System Programmer Response: If you are migrating

from SQL/DS^™ 2.2.0, you must change the column

Update

name from &1. to another name.

Insert (applies only to the Index Control

The recommended procedure is:

Record)

1. Drop any indexes that have been created on the

Acquiring an internal DBSPACE

named column and any programs that reference or

use it.

Releasing an internal DBSPACE

2. Drop the &1. column by deleting the row in

&3. is either INDEX or CATALOG.

SYSCOLUMNS where &1. = CNAME. Recreate the

column in &2. with a different name.

&4. is either index name or catalog name.

3. Recode and repreprocess the programs that were

dropped in step 1.

System Action: Utility execution stops. All changes to

the database are rolled back.

Chapter 8. ARI0520-ARI0535, ARI5806-AR5810 Catalog Maintenance Messages

113

ARI0520-ARI0535, ARI5806-ARI5810 Catalog Maintenance Messages

4. Rerun forward catalog migration. (This step can be

Explanation: The invalid entities table cannot be

performed before step 3.)

migrated to the new format because there is not

enough space in the database directory. There must be

If you are migrating from SQL/DS 3.1.0 or later,

at least four DBSPACE blocks remaining in the

contact the support group for your installation.

database directory for this migration step.

System Action: Database migration ends.

ARI0535E This catalog is not a release n catalog.

System Programmer Response: Increase the size of

Explanation: If you are performing forward migration,

the directory and rerun this migration step. Refer to the

this error occurred because the catalog information

DB2 Server for VSE System Administration manual for

indicates that the catalog is not at a release level

more information on increasing the size of the

supported by migration.

directory.

System Action: The program terminates with no

catalog updates performed.

ARI5810I

Release empty pages processing for

dbspace &1 is complete.

System Programmer Response: If you are certain that

the catalog is at the proper release level, contact the

Explanation: The release empty pages utility was

designated support group for your installation.

invoked for all dbspaces in the system. This message is

displayed after release empty pages processing is

complete for dbspace &1.

ARI5806E There is insufficient space in the server

directory for migration.

System Action: Processing continues.

114

Messages and Codes

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor

Messages

Messages from a preprocessor are written to the

The Reason Code value n2 is the Secondary Error

SYSLST and SYSPCH files. In addition, an

Code. For further explanation, look up the displayed

error codes under either Chapter 22, “Include File

expanded SQLCA structure will be placed in the

Access Errors,” on page 365, or “INCLUDE FILE

modified source for all SQL errors found by the

ERRORS” in the HELP text.

preprocessors or the database manager.

System Action: Preprocessing ends or binding.A new

Preprocessing can result in messages from the

package is not produced. If the package existed

preprocessor and other components of the

previously, it is restored.

database manager.

User Response: Take action based on the Return Code

and Reason Code values.

ARI0536I

Internal error n1. Records remaining n2.

ARI0538E The following is incorrect or missing:

Explanation: An error occurred during the merging of

[value] was found for keyword.

system internal files or closing system files. The n1

value indicates the type of error; the n2 value gives

Explanation: The value supplied for the indicated

additional data, as follows:

preprocessor or binding option keyword was either

invalid or missing.

Meaning and n2 Value

Probable causes of the error are:

Unexpected end of file on SYS002 workfile; n2

= 0.

You did not specify a value, or you specified an

incorrect value for the ISOLation keyword. Allowed

Unexpected end of file on SYS001 workfile; n2

values are CS, RR, UR, and USER.

= 0.

You did not specify a value or you specified an

Records not all merged for SYS001 workfile; n2

incorrect value for the DATE or TIME keyword.

= number of records remaining.

Allowed values are ISO, JIS, USA, EUR, LOCAL.

Records not all merged for SYS002 workfile; n2

You did not specify a value or you specified an

= number of records remaining.

incorrect value for the STDSQL keyword. Allowed

values are NO, 86, and 89.

Error while closing SYSIPT; n2 = 0.

You did not specify a value or you specified an

Error while closing SYS001; n2 = 0.

incorrect value for the CHARSUB keyword. Allowed

values are SBCS, MIXED, and BIT.

Error while closing SYS002; n2 = 0.

You did not specify a value or you specified an

Error while closing SYSPCH; n2 = 0.

incorrect value for the CTOKEN keyword. Allowed

values are YES and NO.

Error while closing SYSLST; n2 = 0.

You did not specify a value or you specified an

System Action: Processing continues; however, if the

incorrect value for the LABEL keyword. The

value n1 is 10, 20, 30, 40, or 80, the results may not be

label-text can be a maximum of 30 characters in

what you expected.

length.

System Programmer Response: This condition is a

You did not specify a value or you specified an

DB2 Server for VSE error. If problems persist, contact

incorrect value for the CCSIDSBCS, CCSIDMIXED, or

the designated support group for your installation.

CCSIDGRAPHIC keywords. Allowed values fall in

the range from 1 to 65534 inclusively, and must be

allowed in the database system.

ARI0537E operation failure on secondary input

source textname. Return Code = n1.

Note: Only the first eight characters appear in the

Reason Code = n2.

message text.

Explanation: During processing of an INCLUDE

You did not specify a value, or you specified an

statement, the specified operation (FIND or GET) for

incorrect value for the DBList keyword. Server

the secondary source identified by textname failed.

names can be a maximum of 18 characters in length.

textname identifies a library source member.

There are misplaced commas in the server name list

The Return Code value n1 is the Primary Error Code.

specified for the DBList keyword.

115

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

v There are duplicate server names in the server name

ARI0541E You have incorrectly specified the

list specified for the DBList keyword.

TEXTNAME portion of an SQL

v You did not specify a value, or you specified an

INCLUDE statement.

incorrect value for the QUALifier keyword. Qualifier

Explanation: A preprocessor SQL INCLUDE statement

names can be a maximum of 8 characters in length.

was specified with an incorrect string. One of the

v You did not specify a value, or you specified an

following may be the cause of the error:

incorrect value for the OWner keyword. Owner

v Text-file-name is longer than 8 characters.

names can be a maximum of 8 characters in length.

v Text-file-name contents do not follow the rules for

v You did not specify a value, or you specified an

SQL identifiers:

incorrect value for the MSGQueue keyword.

- First character of identifier must be a letter (A to

System Action: Preprocessing or binding ends. A new

Z), @, #, or $.

package is not produced. If the package previously

- Identifier must contain only letters (A to Z), @, #,

existed, it is restored.

$, numbers (0 to 9), or underscores (_).

User Response: Supply the valid preprocessor or

v Text-file-name was omitted.

binding option and rerun the preprocessor.

v Additional statements may not appear on the same

line after an INCLUDE (except in COBOL programs).

ARI0539I

description was expected, but string was

v The INCLUDE statement for text inclusion must be

found for option.

specified entirely on one line in PL/I and Assembler

Explanation: During preprocessing, the database

programs.

manager discovered that a DB2 Server for VSE

System Action: Processing continues, but the

Preprocessor parameter contained an unidentifiable

INCLUDE statement in error is not processed further. A

string.

new package will not be produced. If the package

description is a phrase indicating what was expected.

existed previously, it will be restored.

string is a string that could not be identified.

User Response: Correct the text-file-name in the

INCLUDE statement. Rerun the preprocessor.

option is a preprocessor parameter containing the string

in question.

ARI0542E An INCLUDE statement was specified

For example: For the LINECOUNT option, a number is

within the extended include source

required. If the character string 6P was somehow

text-file-name.

entered as the LINECOUNT value, this message would

read:

Explanation: Secondary input containing an SQL

INCLUDE statement other than an INCLUDE SQLCA

NUMERIC VALUE was expected

or INCLUDE SQLDA was found in the text-file-name

but (6P) was found for LINECOUNT.

specified. This is not allowed.

System Action: Preprocessing continues. For

text-file-name is the name of a library source member.

LINECOUNT, the value is set to 60.

The sublibrary depends on the host language:

User Response: If the default value of LINECOUNT is

A sublibrary - Assembler

not acceptable, correct the string and rerun the

B sublibrary - C

preprocessor.

C sublibrary - COBOL

G sublibrary - FORTRAN

P sublibrary - PL/I

ARI0540E The secondary input file named in an

INCLUDE statement was not found.

System Action: Processing continues, but the

INCLUDE statement in error is not processed further. A

Explanation: A preprocessor SQL INCLUDE statement

new package will not be produced. If the package

specified a textname that could not be found.

existed previously, it will be restored.

System Action: Processing continues, but the

User Response: Delete all invalid INCLUDE

INCLUDE statement that is in error is not processed

statements from the secondary input specified by

further. A new package will not be produced. If the

text-file-name. Rerun the preprocessor.

package existed previously, it will be restored.

User Response: Check the spelling of the specified

ARI0543I

INCLUDE SQLCA is not permitted

textname for accuracy. Ensure that the textname

when you request NOSQLCA support.

specified exists and is a library source member with the

correct sublibrary value.

Explanation: When preprocessing an application

program with the NOSQLCA support, you cannot

include the SQLCA structure in the source program.

116

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

System Action: The database manager ignores the

ARI0547I

You did not declare any host variables

INCLUDE SQLCA statement. Preprocessing continues.

in progname.

User Response: Remove the INCLUDE SQLCA

Explanation: The preprocessor detects valid host

statement.

variable declarations. At the end of each program, or

FORTRAN program unit, the preprocessor writes

ARI0544E A graphic string is either too long,

messages ARI0560I and ARI0561I, which list the valid

incorrectly terminated, or contains bytes

host variable declarations that it found. If the

that are not correctly paired for a

preprocessor found no host variable declarations,

graphic string.

message ARI0547I is issued.

Explanation: A graphic string cannot cross input

progname is the name of the program or program unit

record boundaries. It must also contain an even

(as specified in a FORTRAN SUBROUTINE,

number of bytes between the opening SO (X’0E’) and

FUNCTION, PROGRAM, or BLOCK DATA statement).

the closing SI (X’0F’).

User Response: If you did not have any host variable

System Action: Preprocessing continues, but a new

declarations in the specified program, then take no

package will not be produced. If the package existed

action. If you meant to have host variable declarations,

previously, it will be restored.

be sure that you did not incorrectly specify any of

them, and check that you placed all host variable

User Response:

declarations in an SQL DECLARE section.

1. Provide the correct pairing of bytes in the graphic

string or decrease the size of the graphic string.

ARI0548E The cursor cursorname has already been

2. Repreprocess the program.

declared.

Explanation: During an SQL DECLARE statement, the

ARI0545E You have not declared cursor

database manager discovered that the cursor being

cursorname.

referenced had already been declared.

Explanation: During an OPEN, FETCH, PUT, or

System Action: Processing of the SQL statement has

CLOSE cursor statement, the database manager

ended.

discovered that the cursor being referenced had not

been declared.

User Response: Ensure that the cursor being declared

has a unique name.

System Action: Processing of the SQL statement has

ended.

ARI0549E You have declared more than 512 cursors

User Response: Define the cursor by means of a

in this program.

DECLARE cursor statement.

Explanation: During preprocessing, the database

manager discovered that more than 512 cursors were

ARI0546I

The preprocessor did not process the

declared for the current program unit. This exceeds a

package.

DB2 Server for VSE preprocessor limit.

Explanation: The FORTRAN preprocessor performs

System Action: Processing of the SQL statement has

initialization processing before any package changes are

ended.

made. If one of the initialization processing items fails,

the preprocessor ends with a nonzero return code.

User Response: Rewrite the program to contain fewer

DECLARE cursor statements.

Preprocessor message ARI0598I is incomplete because

no processing has been done against a package. If a

package existed prior to the preprocessor run that gave

ARI0550E Host variable variable is declared with

this message, the preprocessor performed no operations

attribute that is incorrect for its use in

against the package and it is in the same state it was

the SQL statement.

before the preprocessing. Similarly, if a preprocessor

Explanation: During preprocessing, the database

run receives this message and no package existed

manager discovered that variable was declared using an

previously, a package will not exist after the

incorrect attribute.

preprocessing is complete.

The contents of variable can be any of:

User Response: Take appropriate action for the error

v The name of the variable with the declaration error

messages that precede this message.

v user-id, indicating that the user ID host variable has

a declaration error

v password, indicating that the password host variable

has a declaration error

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

117

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

v database, indicating that the application server-name

ARI0553E identifier name either missing, or greater

host variable has a declaration error.

than nn bytes.

The contents of attribute can be any of:

Explanation: During preprocessing, the database

manager discovered an identifier greater than the

v data type, indicating that the data type attribute of

number of bytes nn, the maximum allowable for that

the variable referenced in variable is incorrect

type of identifier.

v length, indicating that the length attribute of the

v identifier is the host variable name, user ID,

variable referenced in variable is incorrect

password, program name, file name, statement name,

v an attribute, indicating that the structure or array

statement, label, cursor name, or database name.

attribute of the variable referenced in variable is

v nn is the maximum length of the identifier name.

incorrect.

System Action: Preprocessing of the SQL statement

Some examples of incorrect attributes are:

ends.

v The user ID or the password host variable is not

User Response: Correct the length of the identifier

fixed character length 8.

name.

v The server-name host variable is not a character

For more information about the correct lengths of

string with a length between 1 and 18.

identifier names, refer to the identifiers description in

v The host variable that is used to contain an SQL

the DB2 Server for VSE & VM SQL Reference manual.

statement is not a fixed length character string in

FORTRAN.

ARI0554E SQL statement contains more than 256

v The indicator variable is not a small integer variable.

host variables.

v The structure is not a valid host structure.

Explanation: During preprocessing, the database

v Use of a host structure is not permitted.

manager discovered more than 256 host variables

v An indicator array used in place of a host variable or

referenced in a single SQL statement. This exceeds a

main variable.

DB2 Server for VSE limit.

System Action: Processing of the SQL statement has

ended.

User Response: Correct the declaration of the attribute

User Response: Change the SQL statement to contain

for the host variable.

fewer than 256 host variables.

ARI0551I

LINECOUNT specified incorrectly. The

ARI0555E You did not follow the colon marker

database manager set it to 60.

with a host identifier.

Explanation: During the checking of the preprocessor

Explanation: During preprocessing, the database

options, an error was found in the specification of the

manager identified a colon marker that was not

LINECOUNT option. The error is noted here and the

followed by a host identifier. The host identifier must

default value of 60 for the LINECOUNT option is set.

be the name of a host variable or indicator variable. In

System Action: The LINECOUNT value is set to 60.

those languages that support host structures, the host

Preprocessing continues.

identifier can be a host structure or host structure field.

The indicator variable can be an indicator array.

User Response: If you want a LINECOUNT value

other than 60, correct the error in the LINECOUNT

System Action: Processing of the SQL statement has

option specification and rerun the preprocessor.

ended.

User Response: Change the SQL statement so that a

ARI0552I

LINECOUNT value > 32767 or < 10. The

host identifier follows the colon marker. Rerun the

database manager set it to 60.

preprocessor.

Explanation: The value specified for LINECOUNT is

outside the range of valid values (from 10 to 32767).

ARI0556E ident-type contains incorrect characters.

System Action: The LINECOUNT value is set to 60.

Explanation: During preprocessing, the database

Preprocessing continues.

manager discovered that ident-type contained characters

that are not valid.

User Response: If you want a LINECOUNT value

other than 60, correct the error in the LINECOUNT

System Action: Processing of the SQL statement has

option specification and rerun the preprocessor.

ended.

118

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

User Response: Change the SQL statement so that all

varname is the declared name of a valid host variable,

characters are valid.

structure, structure field, indicator variable, or indicator

array.

ARI0558I

A statement label is not allowed on this

If varname is "OCCURRENCES nn", varname on the line

SQL statement. The label has been

immediately above it is the name of an indicator array

removed: &1..

with nn occurrences.

Explanation: During preprocessing, the database

vartype is the SQL data type of the variable identified in

manager discovered a label on a BEGIN DECLARE

varname.

SECTION, END DECLARE SECTION, WHENEVER, or

If vartype is empty, varname is a structure.

INCLUDE statement.

varlength is the number of bytes of storage required to

System Action: The identified label is blanked out.

store the host variable, structure field, or indicator

array element.

ARI0559E The language preprocessor does not

If varlength is empty, varname is a structure.

allow function.

User Response: You can use this message and error

Explanation: The specified language preprocessor

and warning messages to find errors in the declarations

does not permit the function identified in the message.

of host variables, structures, and indicator arrays.

System Action: Processing of the SQL statement has

Review the variables, structures, and arrays listed in

ended.

these messages to ensure that the specifications are

being recognized.

User Response: Change the SQL statement to

eliminate the disallowed function.

ARI0562I

The following SQL error and/or warning

conditions occurred for the language

ARI0560I

The DB2 Server for VSE language

preprocessor initiated SQL statement

preprocessor recognized the following

type statement.

host variable declarations: (* before the

level number indicates a structure which

Explanation: During preprocessing, the execution of

may be used as a host structure)

an SQL statement by the named preprocessor resulted

in a nonzero SQLCODE or a warning flag in the

LVL NAME SQL TYPE LENGTH

SQLCA.

Explanation: This message always appears together

language identifies the ASSEMBLER, COBOL, C, PL/I,

with message ARI0561I. The explanation for message

or FORTRAN preprocessor.

ARI0561I covers both messages.

statement type identifies the type of SQL statement tried.

Following this message will be SQL message lines that

ARI0561I

lvl varname vartype varlength

describe the SQL conditions encountered.

Explanation: During preprocessing, the preprocessor

System Action: If the SQL condition encountered was

identifies and keeps track of declarations of valid host

an error (negative SQLCODE for example), then

and indicator variables, host structures, and indicator

processing of the statement specified in the message

arrays. Messages ARI0560I and ARI0561I list all of

ends. The ASSEMBLER, COBOL, C, PL/I, or

these declarations. These messages are issued at the

FORTRAN preprocessor issues a ROLLBACK WORK

end of each program unit that contains these

statement. Preprocessing ends.

declarations.

If the SQL condition encountered was a warning

language identifies the preprocessor (assembler, C,

(positive SQLCODE for example), preprocessing

COBOL, FORTRAN, or PL/I).

continues.

lvl is the logical level of a field within a structure. The

User Response: Analyze the SQL problem described

logical level of a field is always one unit deeper than

in the messages that follow this message.

that of its immediate containing structure. All fields of

a structure are reported together and listed sequentially

If an error has occurred, correct the error and rerun the

in this message.

preprocessor.

Scalar variables have a logical level of one (1).

If this is a warning, check that the warning is

acceptable. If it is not, attempt to correct the warning

If lvl begins with an asterisk (*lvl), varname is the name

condition, and rerun the preprocessor.

of a host structure. If lvl is a structure, but it does not

conform to the rules for a host structure, then lvl does

not begin with an ’*’.

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

119

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

System Action: Processing of the SQL statement ends.

ARI0563I

jjj records read from source input file.

kkk records written to source output

User Response: Ensure that the varname specified in

file.

the message is correctly declared. Messages ARI0560I

and ARI0561I of the preprocessor listing output may be

Explanation: This message tells the number of records

helpful in resolving the problem.

that the preprocessor read from the input file and the

number of records written to the output file. The first

number (jjj) is the count of all records read from the

ARI0567E You have already declared host

input file, including records read from any secondary

identifier ident-name.

input file specified in an SQL INCLUDE statement. The

Explanation: The host identifier ident-name is declared

number of records written (kkk) is a count of the

more than once in an SQL DECLARE section, in this

records written to the modified source output file. This

program or subprogram unit. The host identifier is the

number is not the number of records written to the

name of a host variable or indicator variable. In those

preprocessor listing file.

languages that support host structures, the host

identifier can be a host structure or host structure field.

ARI0564E Source input file is empty.

The indicator variable can be an indicator array.

Explanation: The input file which the preprocessor

System Action: Preprocessing continues. A new

tried to read is empty.

package is not produced. If the package existed

previously, it is restored.

System Action: A new package will not be produced.

If the package existed previously, it will be restored.

User Response: Remove the duplicate declaration.

Rerun the preprocessor.

User Response: Ensure that the source program to be

preprocessed is in the input file.

ARI0568E The SQL statement or IF statement

exceeds the limit of 125 lines.

ARI0565I

The input source contains either no SQL

statements, or no SQL statements that

Explanation: The SQL statement or FORTRAN IF

will create a package.

statement is longer than 125 lines (1 plus 124

continuation lines). This number of lines exceeds a

Explanation: One of the following occurred:

FORTRAN preprocessor limitation.

v The EXEC SQL prefix was not found on any

statements in the input source program.

This message may also result from having a large

number of comment lines or blank lines in or

v The EXEC SQL prefix was found only on statements

immediately following the statement mentioned above.

that do not create a package (for example:

CONNECT, COMMIT, or ROLLBACK). COMMIT

System Action: The statement that caused the

and ROLLBACK apply only to the FORTRAN

message is treated as a comment in the modified source

preprocessor.

output and is not used. Preprocessing continues. A new

access module is not produced. If the access module

This condition may cause an empty package to be

existed previously, it is restored.

stored in the database for this program.

User Response: Compress the statement to fit on not

System Action: Preprocessing continues. A new

more than 125 lines (embedded comment lines and

package is not produced. If the package existed

blank lines included). If this is not possible, break the

previously, it is restored.

statement into two or more separate statements. Rerun

the preprocessor. If the error is caused by comment

User Response: Check the preprocessor input file to

lines or blank lines immediately following the

determine if errors were made in the SQL statements

statement, precede the comment lines or blank lines

embedded in the source program. Correct all errors.

with a FORTRAN CONTINUE statement and rerun the

Rerun the preprocessor.

preprocessor.

ARI0566E You did not declare host variable

ARI0569E string1 was expected, but string2 was

varname.

found.

Explanation: The host variable varname is used in an

Explanation: During processing of an SQL statement,

SQL statement, but it was not recognized as a valid

the database manager expected string1 but discovered

host variable declare in the current program or

string2. For example, if the preprocessor encountered

subprogram unit. For a FORTRAN program, a host

only a fragment of a command, such as EXEC SQL

variable used in an SQL statement must be declared in

FETCH, this message would be displayed as:

an SQL DECLARE section in the same program or

CURSOR NAME was expected

subprogram unit in which the SQL statement occurs.

but END OF STATEMENT was found.

120

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

System Action: Processing of the SQL statement has

parameter, the cursor may not be marked invalid when

ended.

the error is detected, and the OPEN, FETCH, PUT, or

CLOSE CURSOR statement is processed as if the cursor

User Response: Correct the syntax of the SQL

is valid.

statement.

ARI0573E An SQL statement was found in a

ARI0570I

User username not authorized to

program other than the first program or

perform action on object object.

the main program.

Explanation: During preprocessing, an SQL statement

Explanation: This message is issued only by the

was found which, when executed, would perform

COBOL preprocessor. A DB2 Server for VSE statement

action action on object object. The user username who is

was found in the source after the end of the main

preprocessing this program is not authorized to

program of a nested program, or after the end of the

perform this action on this object. However, the

first program in a batch compilation.

preprocessor will treat this as a warning and assumes

that the user will be properly authorized by the time

System Action: Preprocessing ends. A new package is

the program is executed.

not produced. If the package existed previously, it is

restored.

User Response: Ensure that the user is authorized

before executing the program.

User Response: Move the DB2 Server for VSE

statements and host variable declarations to the main

Note: This condition will cause additional system

program or first program and rerun the preprocessor.

overhead when the program is executed. If it is a

frequently executed SQL statement and if

ARI0574E Label is greater than number characters.

performance is important, the user should

consider repreprocessing the program once the

Explanation: While preprocessing an application

user has been properly authorized.

program, a label was found on an SQL statement or

host variable which was greater than the number of

characters allowed by the host language.

ARI0571I

User username not authorized to action.

For Assembler, C, COBOL, COBOL II, and PL/I, the

Explanation: During preprocessing, an SQL statement

maximum number of characters allowed in an SQL

was found which, when executed, would perform the

statement is 256.

action action. The user username who is preprocessing

this program is not authorized to perform this action.

For FORTRAN, this message refers to the label used in

However, the preprocessor will treat this as a warning

an SQL WHENEVER statement with the GOTO action

and assumes that the user will be properly authorized

specified:

by the time the program is executed.

v If the first character of the specified label is numeric,

it is assumed that the label is numeric and refers to a

User Response: Ensure that the user is authorized

statement number in the FORTRAN program. These

before executing the program.

labels can have no more than 5 characters.

Note: This condition will cause additional system

v If the first character of the specified label is

overhead when the program is executed. If it is a

alphabetic, it is assumed that the label is a variable

frequently executed SQL statement and if

name to be used in a FORTRAN assignment

performance is important, the user should

statement. These labels can have no more than 6

preprocess the program again after being

characters.

properly authorized.

System Action: Preprocessing continues. A new

package is not produced. If the package existed

ARI0572E Cursor cursorname is not valid.

previously, it is restored.

Explanation: This error occurs when preprocessing an

User Response: Correct the label. Rerun the

OPEN, FETCH, PUT or CLOSE cursor statement. It

preprocessor.

means that an error was discovered while processing

the DECLARE CURSOR or associated PREPARE

ARI0575E Comma delimiter between host

statement. The cursor has been marked invalid.

variables not found.

System Action: Preprocessing continues. A new

Explanation: While processing an OPEN, FETCH,

package is not produced. If the package existed

PUT, or EXECUTE SQL statement, the preprocessor

previously, it is restored.

found a host-variable-list that does not have comma

User Response: Correct the error in the DECLARE

delimiters between the host-variables. A comma is

CURSOR or associated PREPARE statement. Rerun the

required between host-variables.

preprocessor. If you specify ERROR as a preprocessing

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

121

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

System Action: Preprocessing continues. A new

ARI0579I

The preprocessor encountered the

package is not produced. If the package existed

following SQL error or warning

previously, it is restored.

conditions on return from a call to store

User Response: Add commas between host identifier

the package:

pairs. Rerun the preprocessor.

Explanation: The database manager returned a

nonzero SQLCODE or a warning flag in the SQLCA

ARI0576E The preceding source program lines

during an attempt to store the package in the database.

contain a string of nonblank characters

The SQL message describing the SQL error or warning

that exceeds 256 characters. This exceeds

follows this message.

a preprocessor limitation.

System Action: If an error occurred, preprocessing

Explanation: The preprocessor encountered a string of

ends. Message ARI0598I (which follows the SQL error

characters of length greater than 256. This will cause an

messages) indicates that the package was not produced

overflow of preprocessor internal storage areas.

or that it was restored if the package previously

existed.

System Action: Preprocessing ends or binding.A new

package is not produced. If the package existed

If a warning occurred, preprocessing continues and

previously, it is restored.

message ARI0598I indicates that the package was

produced or replaced if it previously existed.

User Response: Break the statement into smaller

pieces by separating the pieces by blanks.

User Response: Check the SQL message lines that

follow this message for a description of the SQL error

or warning.

ARI0577E Unable to release storage. Reason Code

= nn.

If this was a warning, check that the warning is

acceptable. If it is not, attempt to correct the warning

Explanation: During preprocessing, the preprocessor

condition and rerun the preprocessor. Correct the

was unable to release storage. The reason code is the

problem and rerun the preprocessor.

return code from a VSE FREEVIS macro. This is a DB2

Server for VSE preprocessor error.

ARI0580E Required preprocessor option name not

System Action: This error may occur after the

specified.

preprocessor has attempted to store the package in the

database. The preprocessor tries to continue after the

Explanation: The identified option keyword is

point of this error to complete termination processing.

required in the parameters passed to the preprocessor

or to the binder, but it was not provided.

User Response: This message should be followed by

message ARI0598I which will tell you the state of your

For the preprocessor, name is either ’USERID=’ or

package. Final preprocessor results may be incorrect or

’PREPNAME=’. For binder, name is

in an inconsistent state. Notify your system

’PACKAGE(collection_id.package_id)’.

programmer.

System Action: Preprocessing ends or binding.A new

System Programmer Response: Make a record of

package is not produced. If the package existed

what went wrong and contact the designated support

previously, it is restored.

group for your installation.

User Response: Include the missing keyword in the

preprocessor or binding options and retry the

ARI0578I

INCLUDE SQLCA ignored. It has

operation.

already been found.

Explanation: An SQL INCLUDE SQLCA statement

ARI0581E Incorrect or missing parameter on name

was encountered, but an INCLUDE SQLCA statement

keyword.

was already found in the current program/subprogram

Explanation: The information supplied on the

unit.

indicated preprocessor or binding option keyword was

System Action: The SQL statement that caused the

either not valid or missing.

error is commented out in the modified source output

Probable reasons for error are:

and ignored. Preprocessing will continue. The

v No program name or incorrect program name

preprocessor warning count will be incremented. A

specified on 'PREPNAME=' keyword. The program

nonzero return code will be returned by the

name must be a character string of up to 8

preprocessor.

characters.

User Response: Remove the extra SQL INCLUDE

statement from the input source.

122

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

v No user ID or password, or incorrect user ID or

Note: The allowed values are CS, RR, and USER.

password specified on 'USERID=' keyword. User ID

The DATE keyword was specified with different

and password must be a character string of up to 8

format values, such as DATE (USA) and DATE (ISO).

characters.

The TIME keyword was specified with different

v No preprocessor file was specified or the format is

format values, such as TIME(USA) and TIME(EUR).

incorrect. The correct format is

'PREPFILE=(membername)' or

Note: Allowed formats for each of DATE and TIME

'PREPFILE=(membername.membertype)', as documented

are: ISO, JIS, USA, EUR, LOCAL.

in the DB2 Server for VSE & VM Application

Both STDSQL(89) and STDSQL(NO) were specified.

Programming manual.

v No server names, or incorrect server names, were

Note: STDSQL(86) is a synonym for STDSQL(89).

specified on the ’DBLIST’ keyword. Server names

Conflicting options of EXPLAIN were specified.

must be character strings of up to 18 characters.

The CCSIDSBCS preprocessor option was specified

v No package name, or incorrect package name or

more than once with different numeric values.

collection id, was specified on the ’PACKAGE’

Allowed values for these options must be in the

keyword. Collection is and package name must be

range 1 through 65534 and be allowed in the

character strings of up to 8 characters.

database manager.

v No file name, or incorrect file name, was specified on

The CCSIDMIXED preprocessor option was specified

the ’INfile’ keyword.

more than once with different numeric values.

System Action: Preprocessing ends or binding.A new

Allowed values for these options must be in the

package is not produced. If the package existed

range 1 through 65534 and be allowed in the

previously, it is restored.

database manager.

User Response: Supply valid parameter and retry the

The CCSIDGRAPHIC preprocessor option was

operation.

specified more than once with different numeric

values. Allowed values for these options must be in

the range 1 through 65534 and be allowed in the

ARI0582E Terminating error occurred during

database manager.

preprocessing.

The USERid option was specified more than once

Explanation: An SQL return code caused termination

with different values.

of the preprocessor.

The PASSWORD option was specified more than

System Action: Preprocessing ends or binding.A new

once with different values.

package is not produced. If the package existed

The DBList option was specified more than once.

previously, it is restored.

The PACKAGE option was specified more than once

User Response: Check the previous error message to

with different values.

determine the cause of the terminating error. Correct

The QUALifier option was specified more than once

the problem. Rerun the preprocessor.

with different values.

The OWner option was specified more than once

ARI0583E Keywords option and option were both

with different values.

found. Specify only one.

The INfile option was specified more than once with

different values.

Explanation: The keywords specified are mutually

exclusive, yet both were specified as preprocessor or

The MSGQueue option was specified more than once

binding options. Probable reasons for error:

with different values.

v Two of KEEP, REVOKE, and NEW were specified.

Both REPLACE and NEW were specified.

v Both PRINT (PR) and NOPRINT (NOPR) were

Here are some other conflicts that can cause this

specified.

message:

- REPLACE and NEW

v Two of CHECK, NOCHECK, and ERROR were

- PUNCH (PU) and NOPUNCH (NOPU)

specified.

- SEQUENCE (SEQ) and NOSEQUENCE (NOSEQ)

v Both PACKAGE and NOPACKAGE were specified.

- BLOCK (BLK) and NOBLOCK (NOBLK)

v Both BIND and NOBIND were specified.

- EXIST and NOEXIST

v Both QUOTE (Q) and APOST were specified.

Check the descriptions in the DB2 Server for VSE &

v Both GRAPHIC (GR) and NOGRAPHIC (NOGR)

VM Application Programming manual to resolve

were specified.

conflicts in options or values for CHARSUB,

v The ISOLATION preprocessor option was specified

SQLFLAG, or CTOKEN.

than once with conflicting values.

System Action: Preprocessing ends or binding.A new

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

123

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

package is not produced. If the package existed

ARI0587I

Object name owned by owner was not

previously, it is restored.

found.

User Response: Specify only one of the keywords and

Explanation: During preprocessing, an SQL statement

retry the operation.

was found which referenced the named object (for

example a table) owned by the specified owner. This

ARI0584E Unable to allocate storage of n1 bytes.

object could not be found. However, the preprocessor

Return Code = n2.

treats this as a warning condition; it assumes that the

object will have been created by the time the program

Explanation: During preprocessing, the preprocessor

is executed.

was unable to allocate storage of the specified size

needed for processing. The Return Code value is the

name is the name of the object.

return code from a VSE GETVIS macro.

owner is the owner of the object.

System Action: Preprocessing ends. A new package is

System Action: Preprocessing continues.

not produced. If the package existed previously, it is

restored.

User Response: Ensure that the owner name and

object name are correct. If they are correct, ensure that

User Response: For Return Code = 12, increase the

the object is created before executing the program.

partition size or change some DB2 Server for VSE

initialization parameters to reduce virtual storage

Note: This condition will cause additional system

requirements.

overhead when the program is executed. If it is a

For all other Return Code values, notify your system

frequently executed SQL statement and if

programmer.

performance is important, consider

repreprocessing the program after the object has

System Programmer Response: Perform problem

been created.

determination. If a database system error occurred,

make a record of what went wrong and contact the

designated support group for your installation.

ARI0588E Incorrect string string in preprocessor

options.

ARI0585E operation failed on dname. Reason = n2.

Explanation: The preprocessor found the specified 1-

Return = n1.

to 26-character string in the preprocessor options, but it

has no meaning to the preprocessor. Using a

Explanation: During preprocessing, the indicated

preprocessor option file and specifying two

operation (OPEN, CLOSE, GET, or PUT) failed on the

preprocessor options on the same input record, or

indicated file. The dname is specified in the job control.

including a comment not beginning with an asterisk (*)

The Return value is the Primary Error Code. The

may have caused the error.

Reason value is the Secondary Error Code. For further

explanation, look up the displayed error codes under

Note: The option DYNALC is not valid for the

either Chapter 21, “Sequential File Errors,” on page 361,

FORTRAN preprocessor.

or “SEQ FILE ERRORS” in the HELP text.

System Action: Preprocessing ends or binding.A new

package is not produced. If the package existed

previously, it is restored.

User Response: Correct the preprocessor options.

User Response: For corrective action, look up the

Rerun the preprocessor.

displayed error codes under either Chapter 21,

“Sequential File Errors,” on page 361, or “SEQ FILE

ARI0589E Error in message formatter, R.C. > 16.

ERRORS” in the HELP text.

Explanation: The preprocessor message handler was

called to format a message and received a return code

ARI0586I

Preprocessing ended with n1 errors and

greater than 16. The DB2 Server for VSE message may

n2 warnings.

not be completely generated.

Explanation: The preprocessor ended with the

System Action: Preprocessing continues.

specified number of SQL errors or SQL warnings.

User Response: Notify your system programmer.

System Action: Processing ends.

System Programmer Response: Perform problem

User Response: If errors or warnings occurred, look

determination. If a database system error occurred,

through the SYSLST output for the specific error or

make a record of what went wrong and contact the

warning message. Correct the problem, if necessary,

designated support group for your installation.

and rerun the preprocessor.

124

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

ARI0590E No valid END DECLARE SECTION

ARI0594E Incorrect scan mode in COBOL

found.

preprocessing.

Explanation: A BEGIN DECLARE SECTION was

Explanation: An incorrect SCAN Mode was found in

found in the user’s source program, but no

COBOL preprocessing.

corresponding END DECLARE SECTION was found

System Action: This is a DB2 Server for VSE error.

before the end of the source program was reached.

Preprocessing ends or binding.A new package is not

System Action: Preprocessing continues. A new

produced. If the package existed previously, it is

package is not produced. If the package existed

restored.

previously, it is restored.

User Response: Give the output listing to your system

User Response: Check the program and ensure that a

programmer.

valid END DECLARE SECTION is present after the last

System Programmer Response: Make a record of

valid BEGIN DECLARE SECTION.

what went wrong and contact the designated support

group for your installation.

ARI0591E No valid BEGIN DECLARE SECTION

found.

ARI0595E Incorrect condition of a literal.

Explanation: An END DECLARE SECTION was

Explanation: An alphanumeric literal in COBOL has

found in the source program, but no corresponding

been improperly ended.

BEGIN DECLARE SECTION was found.

condition is either LENGTH (>120 in COBOL or >160 in

System Action: Preprocessing continues. A new

COBOL II) or CONTINUATION.

package is not produced. If the package existed

previously, it is restored.

Either:

User Response: Check the program and ensure that a

v Continuation line does not begin with a quote mark,

valid BEGIN DECLARE SECTION is present.

or a beginning quote mark was detected, but an

ending quote mark was not found on the same or

subsequent line.

ARI0592E Incorrect continuation during language

v Length of the literal is greater than 120 characters

preprocessing.

(the maximum allowed by COBOL) or is greater than

Explanation: For an SQL statement embedded in an

160 characters (the maximum allowed by COBOL II).

Assembler application program, columns 1 to 15 of a

System Action: The COBOL preprocessor ends

continuation of an SQL statement or a host variable

processing of the program where the error occurred.

declaration contained nonblanks.

User Response: Correct the literal. Rerun the

language identifies that the application program is being

preprocessor.

preprocessed by the Assembler preprocessor.

System Action: Preprocessing continues. A new

ARI0596E End of source file found without

package is not produced. If the package existed

finding either a procedure division, a

previously, it is restored.

working storage section, or an END

User Response: For an Assembler program, ensure

EXEC for the last SQL statement.

that columns 1 to 15 of continuation lines are blank.

Explanation: During preprocessing of a COBOL

program, one of the following conditions has been

ARI0593E FROM clause of PREPARE or EXECUTE

detected:

IMMEDIATE statement does not contain

v The end of the source program was found without

the name of a variable.

finding a WORKING-STORAGE SECTION.

Explanation: A quoted string is not allowed for the

v The end of the source program was found without

PREPARE or EXECUTE statement.

finding a PROCEDURE DIVISION.

v The end of the source program was found without

System Action: Preprocessing continues. A new

finding the END-EXEC terminator to end the last

package is not produced. If the package existed

EXEC SQL indicator encountered.

previously, it is restored.

System Action: Preprocessing ends or binding.A new

User Response: Specify only a variable name in the

package is not produced. If the package existed

FROM clause of a PREPARE or EXECUTE IMMEDIATE

previously, it is restored.

statement.

User Response: Add the missing item to the source

program. Rerun the preprocessor.

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

125

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

The following SQL statements do not require a

ARI0597E SQL statements other than the

package:

INCLUDE statement are not allowed in

the declare section.

CONNECT

COMMIT WORK [RELEASE]

Explanation: The SQL statement identifier EXEC SQL

ROLLBACK WORK [RELEASE]

was found in a DECLARE SECTION (for example, after

DROP PACKAGE/PROGRAM using host variables

a BEGIN DECLARE SECTION and before a valid END

Extended PREPARE

DECLARE SECTION). Only the extended INCLUDE

Extended DECLARE CURSOR

Extended OPEN, FETCH, PUT, CLOSE

statement is allowed in a DECLARE SECTION. No

Extended DESCRIBE

other SQL statement is allowed in a DECLARE

Extended EXECUTE

SECTION. A possible explanation for this error is that

DROP STATEMENT

the END DECLARE SECTION statement was

CREATE PROGRAM

inadvertently omitted, or was incorrectly declared.

System Action: The status is as specified in the

System Action: Preprocessing continues. A new

explanation.

package is not produced. If the package existed

previously, it is restored.

User Response: Refer to other ARI05xx messages

produced for this program.

User Response: Ensure that the DECLARE SECTION

contains no SQL statements other than an extended

INCLUDE statement. Rerun the preprocessor.

ARI0599E The preprocessor termination processing

encountered a serious error. The results

of the preprocessing are unreliable.

ARI0598I

The application server [server] status the

package for program name.

Explanation: An error occurred during normal or

error termination processing of the preprocessor. This

[DATE: yyyy-mm-dd

error may seriously affect the results of the

TIME: hh:mm:ss]

preprocessor. A specific error message precedes this

message. This and other error messages may be issued

Explanation: Preprocessing of program name is

as write-to-operator messages if both SYSLST and

completed and the status of the package is one of the

SYSPCH are disabled.

following:

System Action: The preprocessor tries to complete

replaced, or produced if it did not already exist

termination processing. A new package may or may not

The program was successfully preprocessed,

be produced (or an existing one may or may not be

and the package replaced the package for this

replaced or restored), depending on when the system

program from a previous preprocess.

error occurred.

produced

User Response: The actual problem is usually found

This program was preprocessed successfully

in the error messages preceding this one. Follow the

for the first time. The preprocessor produced a

USER RESPONSE for those messages.

package.

restored or did not produce

ARI5361E Statement name statementname has not

Either:

been prepared.

v The program failed during preprocessing

Explanation: During preprocessing of a DECLARE or

and the previous package for this program

EXECUTE statement, the database manager discovered

is restored.

that the statement name being referenced has not been

v A failure did not occur, but no SQL

prepared.

statement encountered in the program

required the creation of a package. The

System Action: Processing of the SQL statement has

previous package for this program is

ended.

restored.

User Response: Define the statement name by means

did not produce

of the PREPARE statement.

Either:

v The program failed in the preprocessing

ARI5362E Statement name statementname is not

step and no package exists for it.

valid because of an error in the

v A failure did not occur, but no SQL

PREPARE statement.

statement encountered required the creation

Explanation: The DECLARE or EXECUTE statement

of a package.

in the application cannot be preprocessed because an

error was discovered during the processing of the

PREPARE statement. The EXECUTE or DECLARE

126

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

statement references the PREPARE statement by the

ARI5367E You cannot use the SQL EXECUTE

statement name.

statement to perform a COMMIT or

System Action: Preprocessing continues. A new

ROLLBACK.

package is not produced. If the package existed

Explanation: The commands that control logical units

previously, it is restored.

of work cannot be the object of dynamic SQL

User Response: Correct the error in the PREPARE

commands: PREPARE, EXECUTE, or EXECUTE

statement. Rerun the preprocessor.

IMMEDIATE.

System Action: Processing of the SQL statement has

ARI5363E Cursor name cursorname is not valid

ended.

because the prepared statement, named

User Response: Correct the statement. Try again.

statementname, was a character constant

which contained a command other than

an INSERT or SELECT.

ARI5368E A package name consisting of more than

two parts is not supported.

Explanation: During processing of a DECLARE

statement, an error was encountered involving the

Explanation: In a DROP PACKAGE statement, a

statement identified by the statementname. That SQL

package name of more than two parts was used. This is

statement was a string spec and PREPAREd as a result

not supported.

of the previous execution of a PREPARE statement. The

System Action: Processing of the SQL statement ends.

only SQL statements that can be used in a string spec

for subsequent cursor operations are INSERT and

User Response: Correct the statement. Try again.

SELECT. The cursor has been marked as invalid.

System Action: Processing of the SQL command has

ARI5370E The following host identifier reference

ended.

is ambiguous: varname

User Response: Correct the PREPARE statement to

Explanation: The host variable varname is declared as

process either a SELECT or INSERT statement.

a field of more than one structure. The preprocessor

cannot determine the occurrence of the variable that is

referenced in this SQL statement.

ARI5365E More than 512 unique statement names

have been used in this program.

System Action: Preprocessing continues. A new

package is not produced. If the package existed

Explanation: During preprocessing, the database

previously, it is restored.

manager discovered that more than 512 unique

statement names were specified in PREPARE

User Response: Fully qualify the host variable

statements within the current program unit. This

reference. Rerun the preprocessor.

number exceeds a DB2 Server for VSEpreprocessor

limit.

ARI5375E More than one cursor is declared for

System Action: Processing of the SQL statement has

statement name statement-name

ended.

Explanation: You can only declare one cursor for

User Response: Rewrite the program to contain fewer

statement name statement-name.

PREPARE statements.

System Action: Preprocessing of the command ends.

User Response: Correct your application program

ARI5366E Statement name statementname has

such that there exists only one cursor per statement

already been used in a previous

name.

PREPARE statement.

Explanation: During the preprocessing of an SQL

Note: This message is issued in all environments of the

PREPARE statement, the database manager discovered

database manager system.

that the statement name statementname has already been

used in a previously preprocessed PREPARE statement.

ARI5376E Preprocessor parameter file filename not

System Action: Processing of the SQL statement has

found.

ended.

Explanation: The preprocessor cannot find the

User Response: Ensure that the statement name being

preprocessor option input file.

PREPAREd has a unique name.

System Action: Preprocessing ends. The preprocessor

does not create a new package nor change the existing

package.

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

127

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

User Response: Check the spelling of the specified file

perform these code expansions. Your program is

name for accuracy. Ensure that the preprocessor

preprocessed successfully, however, unless other errors

parameter file specified exists, and is a library source

occurred.

member with the correct sublibrary value.

System Action: Preprocessing continues.

User Response: If your program depends on the code

ARI5377E Invalid specification of preprocessor

expansion, you should change your application so that

parameters and PREPFILE parameter.

it does not depend on the above statements.

Explanation: The preprocess request contained both

preprocessor parameters (other than the PREPNAME,

Note: All environments of the database manager

USERID, and DBNAME parameters) directly in the

receive this message.

preprocess request and a PREPFILE parameter.

System Action: Preprocessing ends. The preprocessor

ARI5387E The SQL statement length exceeds 8192

does not create a new package nor change the existing

positions.

package.

Explanation: The maximum length of an SQL

User Response: In single user mode, specify either

statement is 8192 bytes. This statement exceeds the

one of the following (but not both) after the

maximum. The possible causes are:

preprocessor name, and the PREPNAME, USERID, and

v The SQL statement is too long.

DBNAME parameters in the PARM field of the EXEC

v The end of statement delimiter is missing.

job control statement:

v The individual preprocessor parameters (excluding

v A FOR UPDATE OF clause is added to the end of a

the PREPFILE parameter)

static cursor query statement.

v The PREPFILE parameter alone.

v The expansion of a host structure reference has

increased the size of the SQL statement.

The preprocessor name can be ARIPRPA, ARIPRPB,

System Action: Preprocessing of the SQL statement

ARIPRPC, ARIPRPF, or ARIPRPP.

ends.

In multiple user mode, specify either one of the

User Response: Either break the SQL statement into

following (but not both) after the PREPNAME,

smaller statements or remove unnecessary conditions

USERID, and DBNAME parameters in the PARM field

that may exist in the statement.

of the EXEC job control statement:

v The individual preprocessor parameters (excluding

ARI5390E statement-type statement not referencing

the PREPFILE parameter)

cursor-type cursor.

v The PREPFILE parameter alone.

Explanation: The FETCH, DELETE, and UPDATE

statements must reference a SELECT cursor. PUT

ARI5382E Incorrect option specified in

statements must reference an INSERT cursor. The

preprocessor option file.

statement-type identified in the message references a

Explanation: The preprocessor option file contains

cursor with an incorrect cursor-type.

either the PREPNAME, USERID, or DBNAME

System Action: Preprocessing of the SQL statement

parameters. Specifying these parameters through the

ends.

preprocessor option file is invalid.

User Response: Change the cursor reference in the

System Action: Preprocessing ends or binding.A new

FETCH or PUT statement to reference the correct

package is not produced. If the package existed

cursor and rerun the preprocessor.

previously, it is restored.

User Response: Remove the invalid parameters from

ARI5391E Preprocessor module modname

the preprocessor option file. Specify these parameters in

encountered an internal error. Internal

the preprocess request directly.

Error Code = code-num

Explanation: The preprocessor module specified failed

ARI5383I

Warning: statement-type is not supported.

due to an internal program problem.

Explanation: The database manager system does not

System Action: Preprocessing ends or binding.A new

support the SQL command shown (statement-type). The

package is not produced. If the package existed

statement-type can be DECLARE TABLE, DECLARE

previously, it is restored.

STATEMENT, or DISCONNECT. In other IBM SQL

products, these statements cause code expansions to

User Response: Make a record of the problem and

occur. Because the database manager system does not

notify your system programmer.

support these statements, the preprocessors did not

System Programmer Response: Document the

128

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

problem and contact the designated support group for

successful before continuing the processing of the

your installation.

second statement.

System Action: Preprocessing continues. A new

ARI5392E An error occurred while retrieving the

package is not produced. If the package existed

value value due to a CDLOAD failure.

previously, it is restored.

Return code = X’return_code’.

User Response: Correct the problem in the DECLARE

Explanation: A severe error occurred while the

CURSOR statement and rerun the preprocessor.

preprocessor retrieved the value value. For

CHARTRANS value, the value is retrieved from the

ARI5398E End of string found before the SQL

ARISSCRD phase.

statement ended. Statement is

System Action: Processing terminated and the

incomplete.

package was not created.

Explanation: The end of the SQL statement string was

User Response: Notify your system programmer.

reached before all required segments of the statement

were found. This may be caused by an incorrectly

System Programmer Response: Correct the CDLOAD

placed statement delimiter or by the presence of an

error. Refer to the message text for the return code

open-ended literal in the statement.

from the CDLOAD.

System Action: Preprocessing continues. A new

package is not produced. If the package existed

ARI5395E String beginning with string is invalid

previously, it is restored.

or incorrectly placed in this statement.

User Response: Supply the required missing

Explanation: The portion of the SQL statement that

statement segments or correct the problem with the

has or begins with the string string is incorrect. Possibly

string or statement delimiter. Rerun the preprocessor.

a host variable is required, but string was found.

System Action: Preprocessing continues. A new

ARI5399I

The preprocessor found errors. [Return

package is not produced. If the package existed

Code 8 was changed to 4. The error

previously, it is restored.

statements were accepted] because the

User Response: Remove or correct the invalid string

preprocessor parameter, ERROR, was

and rerun the preprocessor.

specified.

Explanation: When the preprocessor parameter

ARI5396E The preprocessor options file is too

ERROR is specified, the preprocessor tolerates most

large.

statement-parsing errors. The error message is inserted

into the modified source and listing files in comment

Explanation: The preprocessor options file contains

form, and processing continues. The program can be

too many parameters. This situation occurs when

compiled and executed, but the erroneous statement

parameters are duplicated or when parameters that are

cannot be executed on the application server that

not permitted in the preprocessor options file are

issued the error. See the DB2 Server for VSE & VM

found.

Application Programming manual for a discussion of the

System Action: Preprocessing ends. A new package is

ERROR parameter.

not produced. If the package existed previously, it is

System Action: Preprocessing continues. The modified

restored.

source code is generated and package functions are

User Response: If parameters are duplicated remove

performed.

the duplicates. If parameters that are not permitted in

User Response: If you intend to execute the erroneous

the preprocessor options file (for example,

statement on the application server that issued the

PREPNAME) have been included, remove them. Rerun

error, correct the statement and rerun the preprocessor.

the preprocessor.

If you do not intend to execute the statement on that

application server, ignore the message.

ARI5397E Statement statement-name is not valid

because an error occurred while

ARI5400I

Warning: statement-type is not supported.

processing the associated DECLARE

CURSOR statement.

Explanation: The SQL statement shown

(statement-type) is not supported by the database

Explanation: During processing of the DECLARE

manager. Examples of statement-type values are

CURSOR statement, an error occurred while storing the

DECLARE TABLE, DECLARE STATEMENT, etc. In

statement in the package. Because the DECLARE

other IBM SQL products, these statements cause code

CURSOR and the PREPARE statements are related,

expansions to occur. As the database manager does not

processing of the first statement in the pair must be

support these statements, these code expansions have

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

129

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

not been done by the preprocessors. However, your

ARI5404E The preprocessor version and the

program will be preprocessed successfully unless errors

application server version are

occur and you did not specify ERROR as a

incompatible. Preprocessing failed.

preprocessing parameter.

Explanation: The release level of the preprocessor is

System Action: Preprocessing continues.

incompatible with the target application server release

User Response: If your program depends on the code

level. Preprocessing is terminated and the portable

expansion, change your application so that it does not

package is not created.

depend on either of the above statements.

System Action: None.

System Programmer Response: Make sure that the

ARI5401E Cursor name, cursorname, was declared

target application server release level supports the

before this statement was prepared.

preprocessor release level, or preprocess the program to

Explanation: Your application has a DECLARE for a

a application server at a compatible release level, and

statement from a quoted literal. The PREPARE for this

then unload or reload the package to the target

statement must appear in the application before the

application server.

DECLARE CURSOR for this statement.

System Action: Preprocessing continues. A new

ARI5406I

The C preprocessor ignored all input

package is not produced. If the package existed

after the semicolon in the SQL external

previously, it is restored.

INCLUDE statement.

User Response: Change your program so that the

Explanation: The preprocessor found input after the

PREPARE appears before the DECLARE cursor

semicolon in the SQL external INCLUDE statement and

statement. Alternatively, you can assign the quoted

on the same line as the statement.

literal to a host variable, and use the host variable in

System Action: The preprocessor ignored the input

the PREPARE statement in place of the quoted literal.

after the semicolon and did not copy it to the modified

In this case, the DECLARE statement can precede the

source file. Preprocessing continues.

PREPARE statement.

User Response: If the ignored input is not a comment

starting and ending on the same line, move everything

ARI5402I

Preprocessor failed to retrieve the DBCS

after the semicolon to a separate line.

option. The DBCS option is set to NO.

Explanation: A DB2 Server for VSE error occurred

ARI5407I

The application server status the bind

when the preprocessor retrieved the DBCS option from

file file name.

the SQLGLOB file.

Explanation: Bind process of file name is completed

System Action: Processing continued and DBCS

and the status of bind file creation is one of the

defaulted to NO.

following:

User Response: Check the SQLGLOB file for valid

replaced, or produced if it did not already exist

DBCS options. If the option does not exist, or is invalid,

The program was successfully preprocessed,

use the DSQU transaction to create it, or notify your

and the bind file replaced the one for this

system programmer.

program from a previous preprocess.

Programmer response: Use the DSQG transaction to

produced

create a valid DBCS option in the SQLGLOB file.

This program was preprocessed successfully

for the first time. The preprocessor produced a

ARI5403E You cannot submit an SQL statement

bind file.

containing host variables by way of a

restored or did not produce

PREPARE statement.

A failure did not occur, but no SQL statement

Explanation: During the preprocessing of an SQL

encountered in the program required the

PREPARE statement, a host variable was found in the

creation of a package. The previous bind file

SQL statement being prepared. The SQL statement

for this program is restored.

must not contain input or output host variables.

did not produce

System Action: Preprocessing continues. A new

A failure did not occur, but no SQL statement

package is not produced. If the package existed

encountered in the program required the

previously, it is restored.

creation of a package.

User Response: Correct the SQL PREPARE statement.

System Action: The status is as specified in the

explanation.

130

Messages and Codes

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

User Response: Refer to other ARI05xx messages

information for the file. Refer to the message text for

produced for this program.

the return code from the label verification.

ARI5408E Error reading bind file file_id.

ARI5415E Unexpected VSAM error:

Record key:

Procedure= procedure

Collection id: collection_id

Filename= filename

Package id:

package_id

Operation= operation

Sequence number: sequence_number

Return Code= X’return code’

EIBRCODE = X’return-code’.

Error Code= X’error code’

Reason Code= X’reason code’

Explanation: A CBND transaction was entered for

collection_id.package_id, but an error occurred while

Explanation: An error was detected while performing

reading the VSAM file file_id. Refer to the EIBRCODE

the operation on the file filename. The procedure will

for the cause of the error.

contain the name of the DB2 Server for VSE module

that detected the error.

System Action: Processing ends.

User Response: Refer to the EIBRCODE and fix the

error. If the problem persists, notify your system

User Response: Notify your system programmer.

programmer.

System Programmer Response: Check the VSE

System Programmer Response: Refer to the error

messages for the cause of the error.

message text for the cause of the problem.

ARI5417E The collection_id.package_id bind file

ARI5409I

option option [in the bind file]

records are invalid. Preprocess the

overridden by option option.

program again to regenerate the bind

file records.

Explanation: The bind option NOCHECK, CHECK, or

ERROR was specified on the Bind transaction (CBND).

Explanation: Binding process and detected a problem

This value will override the NOCHECK, CHECK or

with the bind file header record.

ERROR parameter specified during the preprocess of

System Action: Processing ends.

this program.

User Response: Repreprocess the program to recreate

System Action: The options specified on the binding

the bind file records.

replace the options specified on the preprocess.

ARI5418I

The bind options currently in effect for

ARI5411E Keywords NOBIND, NOCHECK and

package collection_id.package_id are:

NOPACKAGE are specified. No

preprocess will be done for this

{NOCHECK | CHECK | ERROR}

operation.

{KEEP | REVOKE}

Explanation: The preprocessing parameters NOBIND,

{BLOCK | NOBLOCK}

NOCHECK, and NOPACKAGE were all specified. No

ISOL(value)

action will be taken for this preprocessing operation.

{DATE(value) | APPLICATION

SERVER DEFAULT DATE}

System Action: Processing ends. No package or bind

EXPLAIN(value)

file is created.

{TIME(value)| APPLICATION

User Response: Retry the operation with a valid

SERVER DEFAULT TIME}

combination of preprocessing parameters.

{EXIT | NOEXIT}

{REPLACE | NEW}

{APOST | QUOTE}

ARI5413E Incorrect label information:

CTOKEN(value)

CCSIDSBCS(value)

Filename= filename

CCSIDMIXED(value)

Return Code= X’return code’

CCSIDGRAPHIC(value)

Explanation: An error was detected in the label

{CHARSUB(value) | APPLICATION

information for file filename.

SERVER DEFAULT CHARSUB}

{LABEL(value) | DEFAULT PACKAGE

System Action: Processing ends.

LABEL}

User Response: Notify your system programmer.

Explanation: Binding was invoked for the package

collection_id.package_id with the QRY option. The values

System Programmer Response: Check the label

Chapter 9. ARI0536-ARI0599, ARI5361-ARI5431 Preprocessor Messages

131

Preprocessor Messages - ARI0536-ARI0599, ARI5361-ARI5431

displayed are the options that were specified when the

ARI5426I

process process successful. [Target

package was preprocessed.

database: db-name]

System Action: No connection to any application

Explanation: The process has completed successfully.

server is established. The options that were specified

when the package was preprocessed are displayed.

System Action: Processing is completed.

User Response: No action required.

ARI5419E BIND process is not supported by

FORTRAN preprocessor.

ARI5427E process process unsuccessful. Target

Explanation: The BIND option was specified while

database: db-name [CB2D abend code:

preprocessing a FORTRAN program. This function is

abend-code]

not supported by the DB2 server for VSE preprocessor.

Explanation: The process did not complete successfully.

System Action: Processing ends.

User Response: Preprocess the FORTRAN program

User Response: Refer to previous messages for the

without the BIND option.

reason of the failure. If necessary, notify your system

programmer.

ARI5420I

CBND process for collection_id.package_id

System Programmer Response: Refer to previous

against server application server started.

messages for the cause of the error.

Date: yyyy-mm-dd

TIME: hh:mm:ss

ARI5428I

Binding on [Target database: db-name]

successful though warnings occurred.

Explanation: The CBND transaction has been started

on the target database.

Explanation: Either ERROR option was used and

atleast one SQL statement was not recognized by the

System Action: Processing continues.

target database or object referenced is not present in the

User Response: No action required.

database.

User Response: This message is followed by some

ARI5421E Keyword keyword is not allowed with

other messages. Review the previous warning messages

keywords already specified.

and take appropriate action, if required.

Explanation: Binding has multiple keywords that are

in conflict with each other. Only one of the keywords

ARI5429E Binding on [Target database: db-name]

or sets of keywords can be specified.

failed because of a severe error.

System Action: Processing ends.

Explanation: A severe error occurred when BIND

process was running.

User Response: Try the binding without the keyword

specified.

System Action: Binding ends.

User Response: Notify your system programmer.

ARI5425E Message output error occurred during

System Programmer Response: Perform problem

the process process.

determination. If a database system error occurred,

make a record of what went wrong and contact the

Message number = number

designated support group for your installation.

CICS/VSE service = service

TS queue name = queue-name

EIBRCODE = X’return-code’

ARI5430E Either required or positional binding

[Target database = db_name]

option name not specified.

Explanation: The process encountered an error trying

Explanation: The identified option keyword is

to display a message.

required in the parameters passed to binder, but it was

not provided. ’PACKAGE(collection_id.package_id)’ must

System Action: Processing ends.

be specified as well as it should be first parameter.

User Response: Refer to the message text to fix the

System Action: Binding ends. A new package is not

cause of the error, and then retry the process.

produced. If the package existed previously, it is

restored.

User Response: Include the missing keyword or

include at correct position in the Binding and retry the

operation.

132

Messages and Codes

Chapter 10. ARI5500-ARI5593

FLAGGER Messages

The FLAGGER messages use both SQL and ANSI

QUERY EXPRESSION

terms. The ANSI terms are defined below. For a

A fullselect.

definition of the SQL terms, refer to the DB2

QUERY TERM

Server for VSE & VM SQL Reference manual.

A subselect or a fullselect that is

surrounded by parentheses.

These terms are in uppercase letters in both this

manual and the DB2 Server for VSE & VM SQL

QUERY SPECIFICATION

Reference manual.

A subselect.

ALL SET FUNCTION

RESULT SPECIFICATION

ALL column function. Any column

The columns to be searched for in a

function where ALL is implicitly or

subquery.

explicitly specified. (In other words,

SEARCH CONDITION

duplicate values are not eliminated.)

One or more Boolean terms.

AUTHORIZATION IDENTIFIER

SELECT LIST

The name of the owner or creator of an

List of columns or expressions, or *

object, such as a table.

specified in the SELECT statement.

COLUMN DEFINITION

SELECT TARGET LIST

The definition of a column of a table.

One or more TARGET SPECIFICATIONs.

COLUMN SPECIFICATION

SET FUNCTION SPECIFICATION

Reference to a named column.

One of the following column functions:

COMPARISON PREDICATE

v COUNT (*)

A basic predicate. A predicate that

v A column function with DISTINCT

compares two values.

explicitly specified

DEGREE

v A column function with ALL implicitly

The number of columns or expressions

or explicitly specified.

selected in an SQL statement.

SORT SPECIFICATION

DISTINCT SET FUNCTION

The clause comprised of column names,

DISTINCT column function. Any column

integers, ASC, and DESC that follows the

function with which DISTINCT has been

keywords in an ORDER BY clause. For

specified. (In other words, duplicate

example, in the clause ORDER BY COL1

values are to be eliminated.)

DESC, COL1 DESC would be the SORT

SPECIFICATION.

GROUPed view or GROUPed table

A view or table that is a result of a

TABLE EXPRESSION

GROUP BY clause, a HAVING clause or

A FROM clause optionally followed by a

both of these clauses. A view can also be

WHERE clause, a GROUP BY clause, or a

GROUPed view if any view referenced in

HAVING clause.

the FROM clause is a GROUPed view.

TARGET SPECIFICATION

GROUPing column

Specification of a parameter or variable

A column referenced in a GROUP BY

that can be assigned a value.

clause.

VALUE EXPRESSION

IDENTIFIER

A value specified as the value itself,

An alphameric token used to form a

through a variable name, or as an

name.

arithmetic expression.

OUTER REFERENCE

A correlated reference.

135

FLAGGER Messages - ARI5500-ARI5593

VIEW COLUMN LIST

ARI5505I

FLAGGER Message: An SQL syntax

A list of column names provided on the

deviation occurred. The statement is not

CREATE VIEW statement.

complete.

Explanation: The SQL statement terminated before all

ARI5500I

FLAGGER Message: The FIPS standard

required elements were found.

is used for syntax flagging.

System Action: Processing continues.

Explanation: Information message to identify the

User Response: Correct the SQL statement to meet

standard used for flagging during preprocessing.

installation standards.

System Action: Processing continues.

ARI5506I

FLAGGER Message: Identifier

ARI5501I

FLAGGER Message: The SAA standard

identifiername is more than 18 characters.

is used for syntax flagging.

Explanation: AUTHORIZATION IDENTIFIER, table

Explanation: Information message to identify the

identifier, column name, correlation name, module

standard used for flagging during preprocessing.

name, cursor name, procedure name, or parameter

name has a length of more than 18 characters.

System Action: Processing continues.

ARI5502I

FLAGGER Message: The statement

User Response: Correct the SQL statement to meet

deviates from the SQL standard syntax

installation standards.

at the token starting with the text text.

Explanation: A syntax deviation from the standard

ARI5507I

FLAGGER Message: Column column

named in the earlier message (FIPS or SAA) was

has an invalid length, precision, or scale

encountered in the SQL statement.

attribute.

System Action: Processing continues.

Explanation: One of the following conditions has not

been met:

User Response: Correct the SQL statement to meet

v Length value should be greater than zero.

installation standards.

v Precision value should be greater than zero.

v Scale value should not be greater than precision.

ARI5503I

FLAGGER Message: A data definition

System Action: Processing continues.

statement is not within a CREATE

SCHEMA statement.

User Response: Correct the SQL statement to meet

installation standards.

Explanation: The FIPS standard requires that all data

definition statements are contained within a CREATE

SCHEMA statement.

ARI5508I

FLAGGER Message: The data type of

datatype should be an exact numeric with

System Action: Processing continues.

a scale of zero.

User Response: Correct the SQL statement to meet

Explanation: Data type of an indicator variable should

installation standards.

be exact numeric with a scale of zero.

System Action: Processing continues.

ARI5504I

FLAGGER Message: There is a

nonstandard embedded comment.

User Response: Correct the SQL statement to meet

installation standards.

Explanation: A comment embedded in an SQL

statement does not meet the requirements of the

standard being flagged:

ARI5509I

FLAGGER Message: The SET

v The SAA standard is being checked and the

FUNCTION SPECIFICATION references

comment is not introduced as required by the host

column column.

language.

Explanation: One of the following conditions has not

System Action: Processing continues.

been met:

v The COLUMN SPECIFICATION of a DISTINCT SET

User Response: Correct the SQL statement to meet

FUNCTION cannot reference a column derived from

installation standards.

a SET FUNCTION SPECIFICATION.

136

Messages and Codes

FLAGGER Messages - ARI5500-ARI5593

v COLUMN SPECIFICATIONs in the VALUE

ARI5514I

FLAGGER Message: Column column

EXPRESSION of an ALL SET FUNCTION cannot

does not identify a column of a table

reference a column derived from a SET FUNCTION

within the current scope.

SPECIFICATION.

Explanation: One of the following conditions has not

System Action: Processing continues.

been met:

User Response: Correct the SQL statement to meet

v The table or correlation name used as a qualifier

installation standards.

does not exist.

v The column name does not exist within the current

ARI5510I

FLAGGER Message: A VALUE

scope or the scope of the qualifier.

EXPRESSION containing column cannot

System Action: Processing continues.

include operators.

User Response: Correct the SQL statement to meet

Explanation: A VALUE EXPRESSION cannot include

installation standards.

operators in an OUTER REFERENCE COLUMN

SPECIFICATION.

ARI5515I

FLAGGER Message: A column function

System Action: Processing continues.

that contains the OUTER REFERENCEd

User Response: Correct the SQL statement to meet

column column is not in the subquery

installation standards.

of a HAVING clause.

Explanation: A column function must be contained in

ARI5511I

FLAGGER Message: The COLUMN

a subquery of a HAVING clause if it contains an

SPECIFICATION is missing or is

OUTER REFERENCE COLUMN SPECIFICATION.

invalid for the ALL SET FUNCTION

System Action: Processing continues.

function.

User Response: Correct the SQL statement to meet

Explanation: The VALUE EXPRESSION of an ALL

installation standards.

SET FUNCTION SPECIFICATION should include a

COLUMN SPECIFICATION.

ARI5516I

FLAGGER Message: The result of a

System Action: Processing continues.

SUM or AVG function cannot be a

User Response: Correct the SQL statement to meet

character string.

installation standards.

Explanation: Character string is not valid for the

result of a SUM or AVG SET FUNCTION

ARI5512I

FLAGGER Message: Column column is

SPECIFICATION.

not unique and requires qualification.

System Action: Processing continues.

Explanation: The specified column is not unique with

User Response: Correct the SQL statement to meet

the current scope. Qualification must be given to

installation standards.

uniquely identify the required column.

System Action: Processing continues.

ARI5517I

FLAGGER Message: Operator operator

User Response: Correct the SQL statement to meet

is invalid in this context.

installation standards.

Explanation: One of the following conditions has not

been met:

ARI5513I

FLAGGER Message: A VALUE

v A VALUE EXPRESSION containing a DISTINCT SET

EXPRESSION may not contain a SET

FUNCTION cannot include dyadic operators.

FUNCTION SPECIFICATION.

v The first character following a monadic operator

Explanation: The VALUE EXPRESSION of an ALL

cannot be a plus or minus sign.

SET FUNCTION must not contain a SET FUNCTION

v A VALUE EXPRESSION should not contain

SPECIFICATION.

operators if primary is of type character string.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

Chapter 10. ARI5500-ARI5593 FLAGGER Messages

137

FLAGGER Messages - ARI5500-ARI5593

ARI5518I

FLAGGER Message: The exptype

ARI5522I

FLAGGER Message: Name occurs more

EXPRESSION is comparing

than once in a FROM clause.

incompatible data types.

Explanation: One of the following conditions has not

Explanation: The data types of one of the following

been met:

(identified by exptype) do not match:

v Table name occurs more than once in a FROM

v exptype = COMPARISON - Comparison operators

clause.

must match.

v Correlation name is identical to a table name or to

v exptype= BETWEEN - The three VALUE

another correlation name in a FROM clause.

EXPRESSIONs must match.

System Action: Processing continues.

v exptype = IN - VALUE EXPRESSION, subquery and

all VALUE SPECIFICATIONs must match.

User Response: Correct the SQL statement to meet

installation standards.

v exptype = QUANTIFIED - VALUE EXPRESSION and

subquery must match.

ARI5523I

FLAGGER Message: Only one table

System Action: Processing continues.

reference is allowed in the FROM clause

User Response: Correct the SQL statement to meet

for a GROUPed view.

installation standards.

Explanation: If the table identified by table name is a

GROUPed view, then the FROM clause must contain

ARI5519I

FLAGGER Message: The operand in the

exactly one table reference.

LIKE predicate is not a character string.

System Action: Processing continues.

Explanation: One of the following conditions has not

User Response: Correct the SQL statement to meet

been met:

installation standards.

v Data type of the column in a LIKE predicate is not a

character string.

ARI5524I

FLAGGER Message: A reference to

v Data type of the pattern in a LIKE predicate is not a

column column derived from a column

character string.

function is invalid in a WHERE clause.

System Action: Processing continues.

Explanation: A VALUE EXPRESSION directly

User Response: Correct the SQL statement to meet

contained in the SEARCH CONDITION of a WHERE

installation standards.

clause must not include a reference to a column

derived from a column function.

ARI5520I

FLAGGER Message: The ESCAPE

System Action: Processing continues.

character must be a one-byte character

User Response: Correct the SQL statement to meet

string.

installation standards.

Explanation: Escape character in a LIKE predicate

must have the data type of character string with the

ARI5525I

FLAGGER Message: A HAVING clause

length of 1.

must contain the WHERE clause when

System Action: Processing continues.

the WHERE clause has a column

function.

User Response: Correct the SQL statement to meet

installation standards.

Explanation: If a VALUE EXPRESSION directly

contained in the SEARCH CONDITION is a column

function, then the WHERE clause must be contained in

ARI5521I

FLAGGER Message: The WHERE

a HAVING clause.

clause, GROUP BY clause, or HAVING

clause is invalid for the GROUPed view

System Action: Processing continues.

view.

User Response: Correct the SQL statement to meet

Explanation: If the table identified in the FROM

installation standards.

clause is a GROUPed view, then the TABLE

EXPRESSION must not contain a WHERE clause,

ARI5526I

FLAGGER Message: The COLUMN

GROUP BY clause, or HAVING clause.

SPECIFICATION for column must be an

System Action: Processing continues.

OUTER REFERENCE.

User Response: Correct the SQL statement to meet

Explanation: If a VALUE EXPRESSION directly

installation standards.

contained in the SEARCH CONDITION is a function,

then the COLUMN SPECIFICATION in the column

138

Messages and Codes

FLAGGER Messages - ARI5500-ARI5593

function expression must be an OUTER REFERENCE.

ARI5531I

FLAGGER Message: The COLUMN

System Action: Processing continues.

SPECIFICATION for column is invalid.

User Response: Correct the SQL statement to meet

Explanation: One of the following conditions has not

installation standards.

been met:

v For a GROUPed table, the COLUMN

SPECIFICATION must reference a GROUPing

ARI5527I

FLAGGER Message: Column column is

column or be specified within a SET FUNCTION

duplicated within the current scope.

SPECIFICATION.

Explanation: The specified column is duplicated

v If not a GROUPed table and VALUE EXPRESSION

within the current scope.

includes a SET FUNCTION SPECIFICATION, then

System Action: Processing continues.

each COLUMN SPECIFICATION must be specified

within a SET FUNCTION SPECIFICATION.

User Response: Correct the SQL statement to meet

installation standards.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

ARI5528I

FLAGGER Message: The COLUMN

installation standards.

SPECIFICATION for table should be a

GROUPing column or should be

ARI5532I

FLAGGER Message: DISTINCT is

specified within a column function.

specified more than once.

Explanation: Each COLUMN SPECIFICATION

Explanation: One of the following conditions has not

contained in a subquery in the SEARCH CONDITION

been met:

of a HAVING clause must reference a GROUPing

v DISTINCT must not be specified more than once in a

column or be specified within a column function.

QUERY SPECIFICATION, excluding any subquery of

System Action: Processing continues.

that QUERY SPECIFICATION.

User Response: Correct the SQL statement to meet

v DISTINCT must not be specified more than once in a

installation standards.

subquery, excluding any subquery contained in that

subquery.

ARI5529I

FLAGGER Message: DEGREE of table

System Action: Processing continues.

table should be 1 when using a RESULT

User Response: Correct the SQL statement to meet

SPECIFICATION of *.

installation standards.

Explanation: The DEGREE of the TABLE

EXPRESSION must be 1 if the RESULT

ARI5533I

FLAGGER Message: The

SPECIFICATION * is specified in a subquery of any

COMPARISON PREDICATE subquery

predicate other than an EXISTS predicate.

cannot contain a GROUP BY or

System Action: Processing continues.

HAVING clause.

User Response: Correct the SQL statement to meet

Explanation: If a subquery is specified in a

installation standards.

COMPARISON PREDICATE, then the TABLE

EXPRESSION whose FROM clause identifies the named

table must not contain a GROUP BY clause or a

ARI5530I

FLAGGER Message: The column

HAVING clause.

function is not valid for the TABLE

EXPRESSION beginning with table

System Action: Processing continues.

table.

User Response: Correct the SQL statement to meet

Explanation: One of the following conditions has not

installation standards.

been met:

v If the TABLE EXPRESSION is a GROUPed view, the

ARI5534I

FLAGGER Message: The

RESULT SPECIFICATION of a subquery cannot

COMPARISON PREDICATE subquery

contain a SET FUNCTION SPECIFICATION.

cannot identify a GROUPed view.

v If the TABLE EXPRESSION is a GROUPed view, the

Explanation: If a subquery is specified in a

SELECT LIST of a QUERY SPECIFICATION cannot

COMPARISON PREDICATE, then the TABLE

contain a column function.

EXPRESSION whose FROM clause identifies the named

System Action: Processing continues.

table must not identify a GROUPed view.

User Response: Correct the SQL statement to meet

System Action: Processing continues.

installation standards.

Chapter 10. ARI5500-ARI5593 FLAGGER Messages

139

FLAGGER Messages - ARI5500-ARI5593

User Response: Correct the SQL statement to meet

ARI5540I

Warning: There is not enough memory

installation standards.

for the FLAGGER. Flagging is

suspended for this statement.

ARI5535I

FLAGGER Message: Invalid

Explanation: The FLAGGER has run out of stack

AUTHORIZATION IDENTIFIER authid.

space.

Explanation: The AUTHORIZATION IDENTIFIER

System Action: Flagging continued for subsequent

prefixed to the table name is invalid.

statements.

System Action: Processing continues.

User Response: Notify the system programmer.

User Response: Correct the SQL statement to meet

System Programmer Response: Check whether the

installation standards.

memory allocation for the preprocessor can be

expanded. Allocate more memory for the FLAGGER

ARI5536I

FLAGGER Message: Table or view name

operation if possible. Refer to the DB2 Server for VSE &

already exists.

VM Diagnosis Guide and Reference manual for more

information on failure analysis procedures.

Explanation: The table name or view name specified

already exists in the catalogue.

ARI5541I

Warning: An error occurred when

System Action: Processing continues.

attempting to load the FLAGGER

User Response: Correct the SQL statement to meet

modulename. Flagging capability is

installation standards.

affected.

Explanation: The FLAGGER data or load module

ARI5537I

FLAGGER Message: The COLUMN

used to describe the syntax for the standard being

DEFINITION is missing.

flagged was not found during FLAGGER initialization.

Explanation: At least one COLUMN DEFINITION

System Action: If the module that failed to load was a

should be specified for a CREATE TABLE.

syntax module (ARIFF00 or ARIFS00), then flagging is

discontinued. If the module was a semantics module,

System Action: Processing continues.

then semantics checking stops, and only syntax

checking continues.

User Response: Correct the SQL statement to meet

installation standards.

User Response: Notify the system programmer.

System Programmer Response: Refer to the message

ARI5538I

FLAGGER Message: The data type type1

produced by the operating system for details of causes

of the target is not compatible with the

and proceed as instructed for that message. Refer to the

data type type2 of the source.

DB2 Server for VSE & VM Diagnosis Guide and Reference

manual for more information on failure analysis

Explanation: Data types should match between both

procedures.

the target and source:

v In a FETCH statement

v In a SELECT statement.

ARI5542I

Warning: An error occurred when

initializing the FLAGGER. Flagging is

System Action: Processing continues.

discontinued.

User Response: Correct the SQL statement to meet

Explanation: An internal error occurred during

installation standards.

FLAGGER initialization.

System Action: Preprocessing continues but

ARI5539I

FLAGGER Message: You must specify a

FLAGGER operation is discontinued.

VIEW COLUMN LIST for table.

User Response: Notify the system programmer.

Explanation: If any two columns in the table specified

by the QUERY SPECIFICATION have the same column

System Programmer Response: Refer to the DB2

name, or if any column of that table is an unnamed

Server for VSE & VM Diagnosis Guide and Reference

column, then a VIEW COLUMN LIST must be

manual for more information on failure analysis

specified.

procedures.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

140

Messages and Codes

FLAGGER Messages - ARI5500-ARI5593

Server for VSE & VM Diagnosis Guide and Reference

ARI5543I

Warning: The FLAGGER could not

manual for more information on failure analysis

process the SQL statement. Flagging is

procedures.

discontinued.

Explanation: An SQL statement passed to the

ARI5547I

Warning: Not enough memory for

FLAGGER caused an internal error within it.

FLAGGER operation.

System Action: Preprocessing continues but

FLAGGER operation is discontinued.

Return Code = nn.

User Response: Notify the system programmer.

Explanation: The FLAGGER does not have enough

memory available to operate.

System Programmer Response: Refer to the DB2

Server for VSE & VM Diagnosis Guide and Reference

System Action: Preprocessing continues but

manual for more information on failure analysis

FLAGGER operation is discontinued.

procedures.

User Response: Notify the system programmer.

System Programmer Response: Refer to the DB2

ARI5544I

Warning: An error occurred when

Server for VSE & VM Diagnosis Guide and Reference

terminating the FLAGGER.

manual for more information on failure analysis

Explanation: An internal error occurred during

procedures.

FLAGGER termination.

System Action: Preprocessing continues but

ARI5548I

Warning: Error releasing FLAGGER

FLAGGER operation is discontinued.

memory during termination.

User Response: Notify the system programmer.

Explanation: The FLAGGER could not release

memory back to the operating system.

System Programmer Response: Refer to the DB2

Server for VSE & VM Diagnosis Guide and Reference

System Action: Flagging termination stops.

manual for more information on failure analysis

User Response: Notify the system programmer.

procedures.

System Programmer Response: Refer to the DB2

Server for VSE & VM Diagnosis Guide and Reference

ARI5545I

Warning: Error during FLAGGER access

manual for more information on failure analysis

to the system catalog. Flagging

procedures.

continues to check syntax only.

SQLCODE = nnn SQLERRP = modname

SQLERRD1 = nnn Creator = creatorname

ARI5570I

FLAGGER Message: You must declare

Table = tablename

column column as NOT NULL.

Explanation: An internal error occurred during

Explanation: All columns identified as UNIQUE must

FLAGGER access to the system catalog.

be defined with the NOT NULL option.

System Action: Flagging continues for syntax

System Action: Processing continues.

checking only.

User Response: Correct the SQL statement to meet

User Response: Notify your system programmer.

installation standards.

System Programmer Response: Refer to the DB2

Server for VSE & VM Diagnosis Guide and Reference

ARI5571I

FLAGGER Message: The viewed table

manual for more information on failure analysis

table must be updateable.

procedures.

Explanation: When the WITH CHECK OPTION is

specified then the viewed table must be updateable.

ARI5546I

Warning: An error occurred when

System Action: Processing continues.

processing FLAGGER internal memory

blocks.

User Response: Correct the SQL statement to meet

installation standards.

Explanation: The FLAGGER could not find an internal

memory block.

ARI5572I

FLAGGER Message: Invalid number of

System Action: Preprocessing continues but

column names.

FLAGGER operation is discontinued.

Explanation: The number of column names in the

User Response: Notify the system programmer.

VIEW COLUMN LIST should be the same as the

System Programmer Response: Refer to the DB2

141

Chapter 10. ARI5500-ARI5593 FLAGGER Messages

FLAGGER Messages - ARI5500-ARI5593

DEGREE of the table specified by the QUERY

greater than the number of columns in the table.

SPECIFICATION.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

ARI5578I

FLAGGER Message: Table table is a

ARI5573I

FLAGGER Message: You must declare

read-only table.

cursor cursor before using it.

Explanation: A DELETE, an INSERT, or an UPDATE

Explanation: The cursor specified has not been

statement was specified for a read-only table.

declared in a DECLARE CURSOR statement.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

ARI5579I

FLAGGER Message: Table table must

ARI5574I

FLAGGER Message: Cursor cursor is

not be identified in a FROM clause of

already declared.

any subquery contained in a SEARCH

CONDITION.

Explanation: The cursor specified has already been

declared in a DECLARE CURSOR statement.

Explanation: A table specified in a DELETE or an

UPDATE cannot be used in a FROM clause of any

System Action: Processing continues.

subquery contained in its SEARCH CONDITION.

User Response: Correct the SQL statement to meet

System Action: Processing continues.

installation standards.

User Response: Correct the SQL statement to meet

installation standards.

ARI5575I

FLAGGER Message: Only * or column

names are valid in this context.

ARI5580I

FLAGGER Message: Table table1 is not

Explanation: When UNION is specified, the SELECT

the first table table2 specified in the

LIST for the specification of the two TABLE

DECLARE CURSOR statement.

EXPRESSIONs identified by the QUERY EXPRESSION

and QUERY TERM should consist of * or COLUMN

Explanation: The table specified in a DELETE or an

SPECIFICATIONs.

UPDATE statement should be the first table specified in

the FROM clause of the DECLARE CURSOR statement.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

User Response: Correct the SQL statement to meet

installation standards.

ARI5576I

FLAGGER Message: The descriptions of

tables identified by the QUERY

ARI5581I

FLAGGER Message: The number of

EXPRESSION beginning with table

TARGET SPECIFICATIONs does not

table1 and the QUERY TERM beginning

match the DEGREE of cursor cursor.

with table2 should be identical.

Explanation: The number of TARGET

Explanation: When UNION is specified, the

SPECIFICATIONs in the FETCH statement does not

descriptions of the two tables should be identical,

match the DEGREE of the table specified.

except for the column names.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

ARI5582I

FLAGGER Message: The target table

ARI5577I

FLAGGER Message: The SORT

table of the INSERT statement is also in

SPECIFICATION number is outside the

the FROM clause or in the subquery.

DEGREE of cursor cursor.

Explanation: The named table must not be identified

Explanation: If the SORT SPECIFICATION contains an

in a FROM clause of a QUERY SPECIFICATION or of

unsigned integer, it should be greater than 0 and not

142

Messages and Codes

FLAGGER Messages - ARI5500-ARI5593

any subquery contained in the QUERY

ARI5586I

FLAGGER Message: You cannot use a

SPECIFICATION.

GROUP BY or HAVING clause or

System Action: Processing continues.

identify a GROUPed view in this

context.

User Response: Correct the SQL statement to meet

installation standards.

Explanation: The table identified in the FROM clause

of the TABLE EXPRESSION in a SELECT statement

should not include a GROUP BY or HAVING clause

ARI5583I

FLAGGER Message: The number of

and should not identify a GROUPed view.

columns specified does not match the

number of values specified.

System Action: Processing continues.

Explanation: In an INSERT statement, the number of

User Response: Correct the SQL statement to meet

columns specified does not match the number of values

installation standards.

specified.

System Action: Processing continues.

ARI5587I

FLAGGER Message: The number of

elements specified in the SELECT LIST

User Response: Correct the SQL statement to meet

should match the number in the

installation standards.

SELECT TARGET LIST.

Explanation: In the SELECT statement, the number of

ARI5584I

FLAGGER Message: The number of

elements specified in the SELECT LIST should match

columns specified does not match the

the number of elements in the SELECT TARGET LIST.

DEGREE of the QUERY

SPECIFICATION beginning with table

System Action: Processing continues.

table.

User Response: Correct the SQL statement to meet

Explanation: In an INSERT statement, the number of

installation standards.

columns specified does not match the DEGREE of the

table specified in the QUERY SPECIFICATION.

ARI5588I

FLAGGER Message: Column function

System Action: Processing continues.

function is not allowed in an UPDATE

statement.

User Response: Correct the SQL statement to meet

installation standards.

Explanation: A VALUE EXPRESSION in a SET clause

of an UPDATE statement should not include a column

function.

ARI5585I

FLAGGER Message: There is a data

type or length mismatch between

System Action: Processing continues.

column column and the INSERT or

User Response: Correct the SQL statement to meet

UPDATE item.

installation standards.

Explanation: One of the following conditions has not

been met:

ARI5589I

FLAGGER Message: You cannot specify

v If the data type of the column name is a character

NULL for NOT NULL column column.

string, then the corresponding item in the INSERT or

Explanation: If NULL is specified in the SET clause of

UPDATE statement should be a character string of

the UPDATE statement, then the corresponding column

length equal to or less than the length of the column

should allow nulls.

name.

v If the data type of the column name is exact numeric,

System Action: Processing continues.

then the corresponding item in the INSERT or

User Response: Correct the SQL statement to meet

UPDATE statement should be exact numeric.

installation standards.

v If the data type of the column name is approximate

numeric, then the corresponding item in the INSERT

or UPDATE statement should be approximate

ARI5590I

FLAGGER Message: Invalid SQL

numeric or exact numeric.

terminator for host language.

System Action: Processing continues.

Explanation: The SQL statement was not terminated

by the correct construct for the host language being

User Response: Correct the SQL statement to meet

processed.

installation standards.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

Chapter 10. ARI5500-ARI5593 FLAGGER Messages

143

FLAGGER Messages - ARI5500-ARI5593

ARI5591I

FLAGGER Message: You must define

the host variable identifier.

Explanation: The host variable named was either:

v Not defined within the program

v Defined outside the SQL Declare Section.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

ARI5592I

FLAGGER Message: Table table not

found in the catalog.

Explanation: The named table or view does not exist

in the system catalog.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

ARI5593I

FLAGGER Message: For the host

language language, there is an invalid

IDENTIFIER or LABEL name.

Explanation: The format of the IDENTIFIER name or

LABEL name displayed does not meet the requirements

of the host language.

System Action: Processing continues.

User Response: Correct the SQL statement to meet

installation standards.

144

Messages and Codes

Chapter 11. ARI0600-ARI0699, ARI6000-ARI6299,

ARI0700-ARI0799 EXEC Messages

table and column privileges will be

ARI0613E You did not specify the required EXEC

generated.

parameter &1.

Explanation: The SQLDBDEF utility is indicating the

Explanation: The named keyword parameter (&1) is

output that is to be generated.

needed for correct execution of the EXEC.

System Action: Processing continues.

System Action: Processing ends.

User Response: Reenter the command with the

ARI6204I

The output-file will be written to device.

parameter specified.

Explanation: This message is generated by the

SQLDBDEF utility. Output-file value is either SYSPCH

ARI0629E Keyword &1 is invalid or has a value

or SYSLST.

that is invalid or a value not properly

enclosed within parentheses.

System Action: Processing continues.

Explanation: The specified keyword is either not

valid, or it needs a parameter value.

ARI6205I

Invoking ARIDBDEF to generate SQL

statements.

System Action: Processing ends.

Explanation: The SQLDBDEF EXEC is about to invoke

User Response: Reenter the command with a correct

the phase that generates SQL statements to recreate

keyword and parameter value, if needed.

database objects.

System Action: Processing continues.

ARI0661E Duplicate keyword &1 specified.

Explanation: EXEC processing was not successful.

ARI6206I

No SQL statements will be generated.

This EXEC keyword parameter &1 has been specified

more than once.

Explanation: The SQLDBDEF EXEC can generate any

of the following:

System Action: EXEC processing ends.

v GRANT statements for user authorities

User Response: Rerun the EXEC without duplicate

v CREATE statements for stored procedures and, if the

keyword parameters.

output DBSU job will run against a DB2 Server for

VSE & VM database, CREATE statements for stored

ARI6203I

FORMAT 1:

procedure servers

GRANT statements for user authorities

v SQL object definitions

will be generated.

FORMAT 2:

You have indicated that the SQLDBDEF utility should

CREATE statements for stored

not generate any of the above types of statements.

procedures will be generated.

System Action: Processing ends.

FORMAT 3:

CREATE statements for stored

procedures and stored procedure servers

ARI6209E Phase name not found.

will be generated.

Explanation: The SQLDBDEF utility calls the phase

FORMAT 4:

ARIDBDEF to extract the SQL object definitions and

SQL statements to create all objects will

generate SQL statements to re-create those objects. This

be generated.

phase should have been installed into a library in the

FORMAT 5:

search path.

SQL statements to create all objects in

dbspace dbspace will be generated.

System Action: Processing ends.

FORMAT 6:

User Response: Refer to the description of the

SQL statements to create all object-types

SQLDBDEF utility in DB2 Server for VSE System

will be generated.

Administration, Appendix G: Service and Maintenance

FORMAT 7:

Utilities for instructions to create the ARIDBDEF phase.

SQL statements to create all tables, and

145

EXEC Messages-ARI0600-ARI0699, ARI6000-ARI6702, ARI0700-ARI0799

Programmer response: Take appropriate action based

ARI6210E Errors or warnings occurred during

on the previous messages.

SQLDBDEF EXEC processing. Refer to

the listing file for more information.

ARI0717I

Start &1 EXEC: &2 &3 &4.

Explanation: Processing of the SQLDBDEF utility

failed. Error information is contained in the listing file.

Explanation: This is the expected response from the

database manager.

System Action: Processing ends.

&1 is the EXEC name.

Operator Response: Correct the errors identified in

the listing file and run the utility again.

&2 is the date.

&3 is the time.

ARI6212E Keyword1 and keyword2 cannot be both

&4 is the time zone.

specified.

Explanation: This message is displayed if conflicting

ARI0796I

End &1 EXEC: &2 &3 &4.

keywords are provided for the SQLDBDEF utility.

Keywords that cannot both be specified include

Explanation: This is the expected response from the

DBSpaces and Objects, and SYSPUnch and NOPUnch.

database manager.

System Action: Processing ends.

User Response: Correct the specification of the

keywords, and run the utility again.

ARI6213I

Parameter is ignored in VSE.

Explanation: This message is displayed if SYSPRint or

SYSPUnch is specified for the SQLDBDEF utility in

VSE. Parameter is SYSPRint or SYSPUnch. In VSE, the

generated DBSU job always goes to SYSPCH, and the

output listing goes to SYSLST if NOPUnch is not

specified.

System Action: Processing continues.

ARI0708I

All exec-name EXEC processing

completed successfully.

Explanation: This is the expected response from the

database manager.

ARI0709I

Warning: Warnings occurred during

exec-name EXEC processing.

Explanation: This message indicates that the highest

level of error from processing this EXEC was

WARNING.

Programmer response: Inspect the LISTPREP file

produced to verify that the warning does not require

additional action.

ARI0710E Errors occurred during &1 EXEC

processing.

Explanation: This message indicates that at least one

error has occurred during execution.

If this message was issued at the end of the SQLPREP

EXEC, either a previous message has been issued or the

LISTPREP listing contains an error message. If this

message was not issued at the end of the SQLPREP

EXEC, refer to the previous message issued.

146

Messages and Codes

Chapter 12. ARI7001-ARI7970

ISQL Messages

OFF Any work entered for the database manager

ARI7001E ISQL is not supported on this terminal.

since the beginning of the logical unit of work

Explanation: You tried to run ISQL on a terminal

was rolled back.

which is not supported. ISQL supports IBM 3270

System Action: The system issued a ROLLBACK

terminals or 3270-compatible display devices having a

command. The system waits for you to enter the next

24 X 80 or larger mode (a line size of at least 80

statement.

characters and 24 lines on the screen).

User Response: Read the SQL error message for the

System Action: ISQL ends.

message preceding this one, its system and user action.

User Response: Run ISQL only on terminals which

If the problem is still not clear, notify your system

are supported. Ensure that you are using a supported

programmer. If you want to reenter the work that was

terminal type for your operation.

rolled back when SET AUTOCOMMIT was:

ON Reenter the last command you had entered.

ARI7020E System problem. The message normally

OFF Reenter all commands entered since you began

displayed giving the result of the SQL

your logical unit of work.

command just entered cannot be

printed. The SQL statement ended with

System Programmer Response: Perform problem

an SQLCODE of code. Report this

determination. If a database system error occurred,

message to your system programmer.

make a record of what went wrong and contact the

designated support group for your installation.

Explanation: ISQL tried to display message ARI0500I,

ARI0501I, ARI0502I, ARI0503E, ARI0504I, or ARI0505I,

but the system had problems getting it.

ARI7022E System message error. Notify your

system programmer.

System Action: ISQL printed this message instead of

the one it normally would. The system waits for you to

Explanation: An internal error occurred while ISQL

enter the next statement.

was trying to display a message.

User Response: Look up the text for the SQLCODE

System Action: The system waits for you to enter the

indicated in the message. Notify your system

next statement.

programmer.

User Response: Notify your system programmer. You

System Programmer Response: There is a problem

can continue your ISQL session.

with the DB2 Server for VSE language message text

System Programmer Response: Perform problem

module ARIMS001 or equivalent. Perform problem

determination. If a database system error occurred,

make a record of what went wrong and contact the

designated support group for your installation.

ARI7040I

CANCEL processing complete.

ARI7021E The application server has issued a

ROLLBACK statement. All work

Explanation: CANCEL processing has completed.

entered for processing since the last

System Action: The system waits for you to enter the

COMMIT statement was rolled back.

next statement.

You may have to reenter some

statements.

ARI7041D AUTOCOMMIT is OFF. Do you still

Explanation: During DB2 Server for VSE error

want to CANCEL? Enter 0(No) or 1(Yes).

processing, it was discovered that the database

manager issued a ROLLBACK command for the user.

Explanation: You entered CANCEL while autocommit

The reason is stated in the DB2 Server for VSE message

is off. If the cancel process is done, not only will the

immediately preceding this one. If SET AUTOCOMMIT

command running now be cancelled, but all the work

was:

you did since you set autocommit off or since the last

COMMIT WORK will be rolled back. You are asked if

ON Any work entered for this command was

the cancel should still be done.

rolled back.

System Action: The system waits for your reply.

147

ISQL Messages - ARI7001-ARI7970

User Response: Enter YES if the cancel should still be

User Response: You may enter another CICS

done. Enter NO if the cancel should not be done.

transaction. You may enter ISQL CANCEL. You may

wait for the output from the SQL command being

processed.

ARI7042E Routine ended. It was cancelled because

of your request or an error detected by

ISQL.

ARI7045E CANCEL processing caused a

ROLLBACK. The ROLLBACK was

Explanation: A routine was executing at the time a

unsuccessful. See previous messages for

CANCEL command was entered. The command could

more details.

have been entered from the terminal or it could have

been read from a routine. The CANCEL command

Explanation: The specified ROLLBACK operation was

could also have been entered by ISQL if an error was

performed because a CANCEL command had been

detected while processing a routine. Additional

entered previously. The ROLLBACK processing was not

messages will be displayed when ISQL finds an error

successful. Additional messages are displayed to

condition.

indicate why the ROLLBACK processing failed.

System Action: A ROLLBACK WORK is performed.

System Action: ROLLBACK processing is always

The routine is ended immediately. The system waits for

performed when a CANCEL command is entered.

you to enter the next statement.

Additional messages are displayed to indicate the

reason for the failure.

User Response: If additional error messages are

displayed, correct the error and rerun the routine.

User Response: See the other messages for the reason

for the failure.

ARI7043I

CANCEL processing caused a

ROLLBACK. The ROLLBACK was

ARI7046D Do you want to CANCEL? Enter 0(No)

successful.

or 1(Yes).

Explanation: The specified ROLLBACK operation was

Explanation: While the terminal is free during

performed because a CANCEL command had been

processing of a SQL command, you entered the ISQL

entered previously. The command could have been

transaction identifier followed by blanks or something

entered from the terminal or it could have been read

other than CANCEL. The only valid input with the

from a routine. The CANCEL command could also

transaction identifier at this time is CANCEL. You are

have been entered by ISQL if an error was detected

asked if the cancel processing should be done.

while processing a routine. The ROLLBACK processing

System Action: The system waits for your reply.

was successful.

User Response: Enter YES if the cancel should still be

System Action: The system waits for you to enter the

done. Enter NO if the cancel should not be done.

next statement.

ARI7047I

CANCEL request accepted.

ARI7044I

Command in progress, terminal is now

free.

Explanation: You entered a CANCEL request with

AUTOCOMMIT on, or you entered YES when asked if

Explanation: The terminal is now available for other

a CANCEL request should be done. This message

CICS transactions while ISQL processes your SQL

indicates that the request has been accepted and the

command. If you execute another CICS transaction and

system will do the necessary cancel processing.

ISQL completes processing your SQL command before

the other CICS transaction completes, display of the

System Action: The system continues to process the

output from the SQL command is delayed until the

cancel request.

other CICS transaction completes execution. If you do

nothing, ISQL will display the output from the SQL

ARI7048I

CANCEL request ignored.

command when the SQL command is complete. If you

wish to cancel the SQL command, enter the ISQL

Explanation: You entered NO when asked if a

transaction identifier followed by the word CANCEL;

CANCEL request should be done. This message

for example, ISQL CANCEL.

indicates that the request will be ignored.

The new transaction must not be See

System Action: The system waits for you to enter the

"Pseudo-conversational Transaction Considerations" in

next statement.

the DB2 Server for VSE System Administration manual

for more information.

System Action: The system waits for you to enter

another CICS transaction, to cancel the SQL command,

or to complete the SQL command.

148

Messages and Codes

ISQL Messages - ARI7001-ARI7970

System Action: The error message is displayed and

ARI7050I

CANCEL already in progress.

module ARIIRWI returns to the caller. Processing

Explanation: You entered the CANCEL command

continues.

while your command was already being cancelled.

User Response: Notify your system programmer. Give

System Action: This CANCEL command is ignored.

the system programmer a list of the five previous

Your original CANCEL command processing continues.

commands entered.

System Programmer Response: Perform problem

ARI7051E Routine or EXEC processing ended. It

determination. If a database system error occurred,

was cancelled as you requested or

make a record of what went wrong and contact the

because ISQL detected an error.

designated support group for your installation.

Explanation: A routine was executing when a

CANCEL command was entered. The command could

ARI7063I

Continuation character detected and

have been entered by the user from the terminal or it

ignored. Make sure your input is correct

could have been read from a routine. The CANCEL

and without the continuation character.

command could also have been entered by ISQL if an

Explanation: You entered a continuation character on

error was detected while processing a routine.

a message reply. The continuation is ignored.

Additional messages will be displayed when ISQL

finds an error condition.

System Action: The system uses the reply without the

continuation character as the full reply. If the reply is

System Action: A ROLLBACK WORK is performed.

not valid, the original message will be issued again.

The routine is ended immediately. The system waits for

you to enter the next statement.

ARI7064I

Routine processing cancelled. The error

User Response: If additional error messages are

indicated by a previous message

displayed, correct the error and rerun the routine.

cancelled the processing of your routine,

as you requested with the SET

ARI7060I

Maximum input length of 2048

RUNMODE command.

characters has been reached. Remainder

Explanation: While a routine was running, an error

of input is lost.

was detected by ISQL. ISQL cancelled the routine

Explanation: You entered too many continuation lines.

processing because you requested that routines should

Your input must not be longer than 2 048 characters.

be cancelled when errors are detected. See the SET

The first 2048 characters of your input have been

RUNMODE command for additional information.

accepted, but the rest is lost.

System Action: ISQL issues a ROLLBACK WORK

System Action: The system will try to process your

command to undo all work done since the last

command anyway. More messages will be displayed to

COMMIT WORK. Routine processing ends. The system

let you know whether or not the command was

waits for you to enter the next statement.

processed successfully.

User Response: Correct the cause of the error as

User Response: If the command you entered was an

indicated by previous error messages, and rerun the

SQL command, you can shorten it with the CHANGE

routine.

command so that it is not longer than 2 048 characters.

Then enter the START command to process it again.

ARI7065I

Routine processing stopped. The error

indicated by a previous message has

ARI7061I

Previous input ignored.

caused processing of your routine to be

stopped, as you requested with the SET

Explanation: An IGNORE command was entered on a

RUNMODE command.

multi-line input.

Explanation: While a routine was running, an error

System Action: All lines for this multi-line input are

was detected by ISQL. ISQL stopped the routine

ignored. The system waits for you to enter the next

processing because you requested that routines should

statement.

be stopped when errors are detected. See the SET

RUNMODE command for additional information.

ARI7062E Report the following error to your

System Action: Routine processing ends. ROLLBACK

system programmer. Invalid call to

WORK is not issued. The system waits for you to enter

ARIIRWI. Length=0.

the next statement.

Explanation: An ISQL module has called module

User Response: Correct the cause of the error as

ARIIRWI, but the length of the information to be

indicated by previous error messages, and rerun the

displayed is given as 0.

routine.

Chapter 12. ARI7001-ARI7970 ISQL Messages

149

DB2 Server for VSE Messages and Codes (Version 7 Release 5) - page 4