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

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility

Messages

AUTOCOMMIT=ON processing initiated by a

Common Error Action

user-supplied DBS SET AUTOCOMMIT ON

If the error was not a serious DB2 Server for

command.

VSE error, and the processing mode established

by a SET ERRORMODE CONTINUE command

If AUTOCOMMIT=ON, message ARI0811I is

is in effect, DBS Utility command processing

generated after each successful COMMIT of

continues.

database changes by DBS Utility processing.

If the error was not a serious DB2 Server for

VSE error, and the processing mode established

ARI0800I

...Begin COMMIT. Input Record Count

by a SET ERRORMODE CONTINUE command

= count-value.

is not in effect:

Explanation: This message is issued before

1. SQL ROLLBACK statement is executed.

DATALOAD or RELOAD COMMITCOUNT processing

2. The DBS Utility enters error mode

issues a COMMIT statement. The successful completion

processing (ERRORMODE=ON).

of the COMMIT will be identified by the subsequent

message:

If the error was a serious DB2 Server for VSE

ARI0811I ...COMMIT of any database

error, the DBS Utility enters error mode

changes successful.

processing (ERRORMODE=ON).

During DBS Utility error mode processing, only

count-value is the current input record count value.

a DBS Utility SET ERRORMODE OFF or a SET

After the COMMIT statement successfully completes,

ERRORMODE CONTINUE command will be

this value should be used as the RESTARTCOUNT

executed.

value (rcount) if DATALOAD or RELOAD processing

fails before the next COMMIT statement successfully

Other SQL and DBS Utility commands are not

completes.

executed. They are read from the command file

and displayed in the DBS Utility message

System Action: DBS utility processing continues.

listing. The DBS Utility only performs

command identification and DBS Utility

ARI0801I

DBS Utility started: &1. &2..

command syntax checking for the commands

that are ignored during error mode processing.

AUTOCOMMIT=OFF

Errors that would be detected during the

ERRORMODE=OFF

execution of a command or a data file

ISOLATION LEVEL=REPEATABLE READ.

input/output operation are not detected.

Explanation: Identifies the start of DBS Utility

processing and that AUTOCOMMIT=OFF and

ERRORMODE=OFF, and ISOLATION

Rerunning DBS Utility

LEVEL=REPEATABLE READ are in effect for command

If no COMMIT of database changes occurred

processing.

during this execution of the DBS Utility, all

&1. and &2. are a 17-position date and time

commands that altered the database should be

(mm/dd/yy hh:mm:ss) identifying when the message

reprocessed through the DBS Utility.

was issued.

System Action: Processing continues.

If a COMMIT of database changes occurred

during this execution of the DBS Utility, rerun the

DBS Utility but omit all the commands from the

ARI0802I

End of command file input.

control statement input that altered the database

Explanation: The last record has been read from the

prior to the last COMMIT of database changes.

command file or an error has occurred that prevents

further command file read processing. If a command

A COMMIT of database changes may have

file read error occurred, message ARI0814E will precede

occurred as a result of processing a user-supplied

this message.

SQL COMMIT statement or as a result of the

191

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

System Action: DBS Utility end of program

DBS

Reason

R15

processing is initiated.

Module

Code

DESCRIPTION

Contents

ARIDBS

Invalid pointer was

803

ARI0803E Invalid command identifier.

passed to the

module that loads

Explanation: The last command displayed in the DBS

the character

Utility message listing cannot be identified. The

translation table.

command is not supported by DBS Utility processing

or it does not begin with valid DBS Utility or SQL

ARIDCFI

Invalid CALL to

804

command identifier keywords.

module. A CALL to

the module was

All command file records are displayed as

made to read the

continuations of the invalid command up to but not

command file:

including the command file record beginning the next

v Before the

recognizable command.

command file

was opened,

System Action: The command is not processed. See

v After the

“Common Error Action” on page 191 for more

command file

information.

was closed, or

Programmer response: The command is not

v After a command

processed. See “Common Error Action” on page 191 for

file I/O error

more information.

occurred.

ARIDCSP

An entry to the

805

module, the

ARI0804E Internal DBS error occurred:

command file

Module=&1. Reason Code=&2A.

status, and the

Explanation: An internal DBS Utility error has

ARIDCSP

occurred.

processing control

fields were in an

&1. is the name of the DBS Utility module detecting the

inconsistent state.

error.

ARIDCSP

Command build

805

&2A. is a value that identifies the specific error

logic error. During

detected by the module. The possible values and

command build

associated descriptions vary for each module and are

processing, the last

described below.

nonblank position

of the command file

After the message is generated, a storage dump is

record was less

taken. Register 15 is set to a hexadecimal value unique

than the first

to each module. These dump identification values

nonblank position.

(DUMP ID) are also described below.

ARIDDFI

Invalid CALL to

806

DBS

Reason

R15

module. A CALL to

Module

Code

DESCRIPTION

Contents

the module was

made to read the

ARIDALC 4

Invalid CALL to

800

command file:

module. The call

v Before the

type parameter was

command file

not ALLOCATE

was opened

(X’00’) or FREE

v After the

(X’08’).

command file

ARIDALI

Invalid CALL to

801

was closed, or

module. The call

v After a command

type parameter was

file I/O error

not ALLOCATE

occurred.

(X’00’) or FREE

ARIDDLO

The current

807

(X’08’).

command was not

ARIDALT 4

Invalid CALL to

802

a DBS DATALOAD

module. The call

TABLE command

type parameter was

when the module

not ALLOCATE

ARIDDLO was

(X’00’) or FREE

entered.

(X’08’).

192

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

DBS

Reason

R15

DBS

Reason

R15

Module

Code

DESCRIPTION

Contents

Module

Code

DESCRIPTION

Contents

ARIDDLO

Command

807

ARIDDUL

Command

813

processing logic

error. An ARIDCSP

return code (R15)

value > 8 was

received while

reading commands

for actual

processing (no

processing. (That is,

previous errors

no previous

have occurred).

commands

ARIDDLO

A command

807

occurred.)

sequence check

ARIDDUL

A command

813

logic error occurred

sequence check

during normal

logic error occurred

command sequence

during normal

processing.

command sequence

ARIDDLO

A logic error

807

processing.

occurred during

ARIDDUL

Command

813

DATALOAD input

processing logic

OPEN processing.

error. An ARIDCSP

The last command

return code (R15)

processed was not

value > 8 was

an INFILE or

received while

INMOD command.

reading commands

ARIDDLO

Command

807

after an error

processing logic

occurred.

error. An ARIDCSP

ARIDEXI

Invalid CALL to

808

return code (R15)

module. The call

value > 8 was

type parameter was

received while

not OPEN (X’12’),

reading commands

FETCH (X’02’), or

after an error

CLOSE (X’04’).

occurred.

ARIDSFA

Invalid CALL to

809

ARIDDLO

An input data field

807

module. The call

was not processed

type parameter was

for a column

not ALLOCATE

during INSERT

(X’00’), COMPUTE

processing based on

(X’02’), or FREE

column nodes

(X’04’).

already matched to

ARIDSQL

Invalid CALL to

810

data fields.

module. The call

ARIDDUL

The current

813

type parameter was

command was not

not valid.

a DATAUNLOAD

ARIDUNL

Internal logic error.

812

command when

The SQL I/O area

module ARIDDUL

is too small.

was entered.

System Action:

Processing of the command is

terminated. A storage dump request is issued. See

“Common Error Action” on page 191 for more

information.

Programmer response: Contact system programmer.

System Programmer Response: Perform problem

determination. If a database system error occurred,

Chapter

13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

193

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

make a record of what went wrong and contact the

ARI0808I

DBS processing completed: &1.&2..

designated support group for your installation.

Explanation: Identifies the end of DBS Utility

command processing.

ARI0805E Command is incomplete.

&1.&2. is a 17-position date and time (mm/dd/yy

Explanation: The last command displayed in the DBS

hh:mm:ss) identifying when the message was issued.

Utility message listing is not complete.

System Action: DBS Utility end of program

All command file records were read or a command file

processing continues. The message file is closed and

read error occurred before the end of the command

processor storage areas acquired at the start of DBS

was identified.

Utility processing are released before DBS Utility

The command file records comprising the command

processing terminates.

and any command file processing error messages

appear before the ARI0805E message in the DBS Utility

ARI0809I

...No errors occurred during command

message listing.

processing.

Note: Unbalanced quotes in a command or command

Explanation: All commands supplied were processed

information appearing in positions 73 through 80

successfully, or all commands since the last SET

of a command file record may cause an

ERRORMODE OFF command were processed

erroneous end of file condition to occur.

successfully.

System Action: The command is not processed. See

System Action: DBS Utility end of program

“Common Error Action” on page 191 for more

processing continues.

information.

Programmer response: Refer to the previous messages

ARI0810E Command file record truncated after

in the DBS Utility message listing to identify the type

position &1A..

of command being built and a description of any

Explanation: The last command displayed in the DBS

abnormal command file processing conditions.

Utility message listing exceeds the maximum command

Correct the command error or the command file

length of 8192 positions.

problem identified and rerun the job. (See “Rerunning

&1. is the position (column in the control statement

DBS Utility” on page 191.)

record) of last control statement displayed that was

identified as position 8192 of the command.

ARI0806E The command length already is greater

than 8192 positions.

Note: If no commands approaching the maximum

command length were present in the DBS Utility

Explanation: The last command displayed in the

command file input, reasons for the error

message listing is longer than 8192 positions. The

condition prompting this message are:

maximum command length has already been exceeded

v Unbalanced quotes in a command.

before this control statement was read. The contents of

v Command information appearing in positions 73

this control statement cannot be appended to the

through 80 of a control statement record.

command being built.

System Action:

This message will only appear after the condition

v The command is not executed.

described by message ARI0810E has occurred.

v DBS Utility continues to read command file records

System Action: Refer to message ARI0810E.

until the end of the command is encountered.

Programmer response: Refer to message ARI0810E.

v Subsequent command file records comprising the

command will cause the message ARI0806E to be

issued.

ARI0807E ...Errors occurred during command

processing.

v Command processing is terminated.

v Also see “Common Error Action” on page 191.

Explanation: Indicates that all user commands have

not processed successfully during execution of the DBS

Programmer response: Analyze the previous

Utility.

command file records displayed in the DBS Utility

message listing.

System Action: DBS Utility end of program

processing continues.

Correct the command or if necessary, reduce the length

of the command by eliminating unnecessary blanks

Programmer response: Refer to the previous messages

between command parameters in each control

in the DBS Utility message listing to identify the errors

statement, then reprocess the command. (See

encountered.

“Rerunning DBS Utility” on page 191.)

194

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

&1. is either OPEN, CLOSE, READ (GET), or WRITE

ARI0811I

...&1. of any database changes

(PUT).

successful.

&2. is DNAME identifying the file.

Explanation: The DBS Utility initiated execution of an

SQL COMMIT or SQL ROLLBACK command was

&3A. is the Primary Error Code describing the error.

successful. The command was not supplied as user

&4A. is the Secondary Error Code describing the error.

input, but was executed automatically by DBS Utility

processing. Any database changes made since the

Primary Error Code: The Reason Code = &3A. value

beginning of DBS Utility processing, or since the last

reflects an error detected by either a DBS Utility

SQL COMMIT or SQL ROLLBACK command was

module or the DB2 Server for VSE Operating System

executed, have been committed or rolled back.

Dependent Service Module Generalized I/O Routine

(ARISYSD5). The code values in the following list are

&1. is COMMIT or ROLLBACK.

provided by the DBS Utility:

System Action: DBS Utility processing continues.

Module ARIDMGE print message call, but the

Programmer response: If a ROLLBACK of database

message number in the CPA field CPAMSGNO

changes is indicated, reference the previous error

is 0.

messages to identify the errors that caused the

Module ARIDMGE print line call (not a

ROLLBACK and the action to be taken.

message), but the CPA field CPAMSGNO is

If a COMMIT of database changes is indicated, DBS

not 0.

Utility processing committed the database changes

Module ARIDMGE print SQL message call,

automatically because AUTOCOMMIT=ON or because

but the CPA field CPAMSGNO is not 0.

ERRORMODE=OFF was in effect when the DBS Utility

end of program processing was initiated.

Module ARIDDFI detected an unsupported or

incorrect record format (RECFM) after the file

was successfully opened.

ARI0812I

...Resume command execution:

AUTOCOMMIT=OFF

Module ARIDDUL detected an incorrect

ERRORMODE=OFF.

record format (RECFM) after the file was

successfully opened. The DATAUNLOAD

Explanation: A DBS SET ERRORMODE OFF

processing requires an output record length

command was successfully processed. DBS Utility will

greater than 32760 bytes, but the output file

resume execution of commands at this point with

identified is not defined with spanned records

AUTOCOMMIT=OFF and ERRORMODE=OFF.

(RECFM = VS or VBS).

System Action: Proceeds to process and execute

Module ARIDRLP detected an empty file.

commands with AUTOCOMMIT=OFF and

RELOAD PROGRAM processing requires a

ERRORMODE=OFF.

non-empty file and may be created by

UNLOAD PROGRAM processing.

ARI0813I

...Suspend command execution:

ARIDMGE detected an unknown error. The

AUTOCOMMIT=OFF

message processing status fields are in an

ERRORMODE=ON.

inconsistent state.

Explanation: This message identifies that DBS Utility

error mode processing is being initiated

All other Primary Error Code values are provided by

(AUTOCOMMIT=OFF and ERRORMODE=ON).

ARISYSD5. For further explanation, look up the

displayed error codes under either Chapter 21,

System Action:

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

v Proceeds with DBS Utility error mode processing.

ERRORS” in the HELP text.

v Command identification and DBS Utility command

syntax checking will occur but no further commands

Secondary Error Codes: The Return Code =&4A; value is

will be executed.

an error code provided by the DB2 Server for VSE

v Errors that would be detected during execution of a

Operating System Dependent Service Module

command or any associated data file input/output

Generalized I/O Routine (ARISYSD5).

operations will not be detected.

If the Primary Error Code is provided by a DBS Utility

module, the Secondary Error Code is zero. For further

ARI0814E File &1. error: DNAME=&2. Reason

explanation, look up the displayed error codes under

Code = &3A.. Return Code = &4A..

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

Explanation: An input/output file processing error

or “SEQ FILE ERRORS” in the HELP text.

occurred.

System Action: Command processing is ended. See

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

195

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

“Common Error Action” on page 191 for more

System Action: DBS Utility end of program

information.

processing is initiated.

Programmer response: Determine problem with the

Programmer response: If the message ARI0814E

file identified by analyzing any reason code displayed

precedes this message in the DBS Utility message

in this message, and any DBS Utility messages

listing, correct the command file error indicated. Rerun

displayed previous to this message or by operating

the job. (See “Rerunning DBS Utility” on page 191.)

system messages displayed on the operator console or

terminal.

ARI0818E

Module &1. load error: Reason

If possible, correct the error and reprocess the last

Code=&2A..

command displayed in the DBS Utility message listing.

Explanation: A module necessary for INMOD

(See “Rerunning DBS Utility” on page 191.)

command processing could not be loaded into storage.

If the error cannot be corrected, notify the system

The module name (&1) was supplied by the INMOD

programmer.

command displayed in the DBS Utility message listing

System Programmer Response: Perform problem

preceding this message.

determination. If a database system error occurred,

The reason code (&2A) is the VSE CDLOAD macro

make a record of what went wrong and contact the

return code value. Refer to the IBM VSE/ESA System

designated support group for your installation.

Macros Reference manual for an explanation of the

codes.

ARI0815I

...&1. Processing Mode = &2..

System Action: Command processing is ended. See

Explanation: This message is displayed as a result of

“Common Error Action” on page 191 for more

processing a Database Services Utility SET

information.

AUTOCOMMIT or SET UPDATE STATISTICS

Programmer response: Take the appropriate action

command. It identifies whether DBS AUTOCOMMIT or

necessary to correct the error identified by the reason

UPDATE STATISTICS processing will be ON or OFF

code or contact your system programmer.

for subsequent command processing.

System Programmer Response: Take the appropriate

&1. is AUTOCOMMIT or UPDATE STATISTICS.

action necessary to correct the error identified by the

&2. is ON or OFF.

reason code. Rerun the job.

System Action: Processing proceeds.

ARI0819I

...Command not processed:

ERRORMODE=ON.

ARI0816E DBS COMMENT command does not

end with a single quote.

Explanation: The command displayed preceding this

message in the DBS Utility message listing was not

Explanation: An error has occurred in the last DBS

processed because of a previous error.

COMMENT command displayed in the DBS Utility

message listing. The terminating single quote for the

System Action: DBS Utility error mode processing

comment text was not found.

continues.

System Action: See “Common Error Action” on page

191.

ARI0821E Module module-name interface error.

Reason Code = reason-code

Programmer response: Ensure that there are no

unbalanced quotes in the command and that command

Explanation: An error has been detected by module

information is not supplied in positions 73 through 80

module-name. The INMOD command is displayed

of the command file records comprising the command.

preceding this message in the DBS Utility message

Correct the command and reprocess it. (See “Rerunning

listing.

DBS Utility” on page 191.)

The reason-code is the return code issued by

module-name. The values are:

ARI0817I

...Command file processing was

Processing error.

interrupted.

System Action: See “Common Error Action” on page

Explanation: Command file processing was

191 for more information.

interrupted because the command file was empty or

because a command file read error occurred before the

Programmer response: Refer to the previous DB2

first command was completed. One of the following

Server for VSE messages in the message output listing

occurred:

to identify the error encountered and the action to be

taken.

196

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

System Programmer Response: If the problem

ARI0822E Commands are out of sequence or a

identified by the reason code (&3A.) cannot be

subcommand is missing.

corrected, perform problem determination. If a database

Explanation: The last command displayed is out of

system error occurred, make a record of what went

sequence. Either required DBS DATALOAD or

wrong and contact the designated support group for

DATAUNLOAD subcommands have been omitted, or

your installation.

the command file records are out of sequence.

System Action: The DATALOAD or DATAUNLOAD

ARI0825E &1. &2. storage not released: Reason

command is not executed. See “Common Error Action”

Code = &3A..

on page 191 for more information.

Explanation: The identified DBS Utility module could

Programmer response: Supply all required commands

not release processor storage.

and subcommands in the correct sequence and

&1. is a module name.

reprocess the commands. (See “Rerunning DBS Utility”

on page 191.)

&2. is an area name.

&3A. is a code describing the error (see below).

ARI0823E SQL message formatting error.

The code value (&3A.) is the return code supplied by

SQLCODE=&1A..

the DB2 Server for VSE Common Service Module

Explanation: An internal DBS Utility error has

(ARISYSD) in response to the acquire storage request

occurred. The DBS Utility module ARIDSQL received a

made through the entry point ARISYSD2.

return code = 20 or 24 from the module ARIMSMF

The code value is the same as the return code supplied

while attempting to format the descriptive text for the

by the FREEVIS macro. The FREEVIS macro return

identified SQLCODE.

codes are described in the IBM VSE/ESA System Macros

System Action: Processing continues.

Reference manual.

Programmer response: Notify your system

System Action: Processing of the last command

programmer.

displayed in the DBS Utility message listing is

terminated. Also see “Common Error Action” on page

System Programmer Response: Perform problem

191 for more information.

determination. If a database system error occurred,

make a record of what went wrong and contact the

Programmer response: Correct the problem identified

designated support group for your installation.

by the reason code (&3A.) supplied in the message text.

If the problem cannot be corrected, contact the system

ARI0824E &1. storage unavailable. Bytes

programmer.

Requested = &2A. Reason Code = &3A.

System Programmer Response: If the problem cannot

Explanation: The identified DBS Utility module could

be corrected, perform problem determination. If a

not acquire the required amount of processor storage.

database system error occurred, make a record of what

went wrong and contact the designated support group

&1. is a module name.

for your installation.

&2A. is the amount of storage requested in bytes.

&3A. is a code describing the error (see below).

ARI0827I

...Begin command execution:

ERRORMODE=CONTINUE.

The code value (&3A.) is the return code supplied by

the DB2 Server for VSE Common Service Module

Explanation: This message is generated after a DBS

(ARISYSD) in response to the acquire storage request

Utility SET ERRORMODE CONTINUE command was

made through the entry point ARISYSD1.

successfully processed. It is also generated during the

DBS Utility program initialization if the control file is

The code value is the same as the return code supplied

assigned to the terminal.

by the GETVIS macro. The GETVIS macro return codes

are described in the IBM VSE/ESA System Macros

The DBS Utility will execute subsequent commands

Reference manual.

with the normal DBS Utility error processing

suppressed. If a command processing error is detected,

System Action: See “Common Error Action” on page

the Database Services Utility will neither execute an

191.

SQL ROLLBACK statement nor enter DBS Utility error

Programmer response: Correct the problem identified

mode processing. Subsequent commands will be

by the reason code (&3A.) displayed in the message

executed by the DBS Utility. For a further explanation

text.

of this processing, refer to the description of the DBS

Utility SET ERRORMODE command CONTINUE

If the problem cannot be corrected, contact the system

parameter.

programmer.

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

197

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

System Action:

ARI0832I

Column &1. data truncation or data

v Command processing continues.

overflow may occur.

v If other than a serious DB2 Server for VSE error is

Explanation: This message identifies one of the

detected, the appropriate error message or messages

following conditions:

will be generated, but the DBS Utility will not

v A select-list column defined with a nonnumeric data

execute an SQL ROLLBACK statement or enter DBS

type and a length greater than the length of the

Utility error mode processing.

associated output record CHAR, GRAPHIC, or

v If a serious DB2 Server for VSE error is detected,

ZONED data field. Nonblank, trailing (low-order)

DBS Utility command processing will be suspended.

positions of column values will be truncated by

DATAUNLOAD processing.

ARI0828I

...&1. reset to &2A..

v A select-list column defined with a numeric data

type that may result in a value with more significant

Explanation: This message is generated after a DBS

digits than the length of the associated output record

Utility SET LINECOUNT/LINEWIDTH command was

CHAR, GRAPHIC, or ZONED data field allows.

successfully processed.

Asterisks will be placed in the output record data

&1.

LINECOUNT or LINEWIDTH.

field if this numeric data value overflow condition

occurs.

LINECOUNT identifies the number of lines

per print page to be used for the DBS Utility

&1. is a column name or integer value specified in the

message file output.

Data-Field-Identification subcommand that identifies a

LINEWIDTH identifies the number of print

select-list column in the SQL SELECT statement

positions per line to be used for the DBS

supplied after the DATAUNLOAD command.

Utility message file output resulting from SQL

System Action: DBS Utility processing continues.

SELECT command processing.

&2A. LINECOUNT or LINEWIDTH value to be

ARI0833E Column &1. data overflow. Rowcount =

used for the DBS Utility message file output.

&2A..

System Action: Command processing continues.

Explanation: This message identifies an occurrence of

a numeric select-list column value that exceeds the

ARI0830E User-supplied SELECT statement error

capacity of the output record numeric data field. The

encountered.

significant digits of the column value cannot be

contained in the output record data field.

Explanation: An error was detected during SQL

processing of the SQL SELECT statement supplied by

&1. is a column name or integer value specified in the

the user for DATAUNLOAD processing.

Data-Field-Identification subcommand.

System Action: Command processing is ended. See

&2A. is an SQL SELECT row count at the time the

“Common Error Action” on page 191 for more

condition was detected. For example, if this condition

information.

was detected in the tenth row selected from the

database by the SQL SELECT statement supplied for

Programmer response: Refer to the error messages in

DATAUNLOAD processing, this value will be 10.

the DBS Utility message listing prior to this message

for a description of the SQL error encountered. Correct

System Action: The row cannot be written to the

the SQL SELECT statement error and rerun the

output file. If the row is written to the output file, the

command.

data may be truncated or replaced by asterisks. DBS

Utility processing will be stopped when end-of-input,

SQLCODE 100 is detected.

ARI0831I

Column &1. data will not be unloaded.

Programmer response: Verify that the output file

Explanation: This message identifies a column in the

contains the expected data. If it does not, correct the

select-list of the DATAUNLOAD command that is not

applicable dataunload Data-Field-Identification

referenced by the user-supplied Data-Field-

subcommand and rerun the command.

Identification subcommands. The data for the column

will not be unloaded.

ARI0834E Invalid data field position for column

&1. is the column name of the select-list column that

&1..

will not be unloaded.

Explanation: This message identifies that a data field

System Action: DBS Utility processing continues.

for a column referenced by a DATAUNLOAD

Data-Field-Identification subcommand starts or ends in

an output record position exceeding the specified

length of the output record. The length of the output

198

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

record is identified in the previous ARI0868I message

v Extra information is specified.

that appears in the DBS Utility message listing.

v The statement is not terminated by a semicolon.

&1. is a column name or integer value specified in the

System Action: The command is not processed. See

Data-Field-Identification subcommand that identifies a

“Common Error Action” on page 191 for more

select-list column in the SQL SELECT statement

information.

supplied after the DATAUNLOAD command.

Programmer response: Correct the command and

System Action: Command processing is ended. See

reprocess it. (See “Rerunning DBS Utility” on page

“Common Error Action” on page 191 for more

191.)

information.

Programmer response: Correct the applicable

ARI0839E LINEWIDTH is not less than message

DATAUNLOAD Data-Field-Identification subcommand

record length = &1A..

or increase the length of the output record and rerun

the command.

Explanation: An invalid value is specified for the

LINEWIDTH parameter in the last command displayed

in the DBS Utility message file listing. The value is

ARI0835I

&1A. records were written to the output

equal to or greater than the DBS Utility message file

data file.

record length.

Explanation: Identifies the number of records written

&1A. is a DBS Utility message file record length.

to the output data file by DATAUNLOAD processing.

System Action: Command processing is ended. See

&1A. is the number of records.

“Common Error Action” on page 191 for more

information.

System Action: DBS Utility processing continues.

Programmer response: Correct the command or define

the DBS Utility message file with a larger record length

ARI0836I

Default output record data field

and rerun the job. (See “Rerunning DBS Utility” on

positions:

page 191.)

Explanation: This message precedes the ARI0837I

messages that identify the default output record data

ARI0840E Invalid data type = &1A. encountered in

field positions for a DATAUNLOAD command

the SQLDA.

select-list.

Explanation: While processing the last command

System Action: DBS Utility processing continues. One

displayed in the DBS Utility message listing, an invalid

or more ARI0837I messages will be generated after this

SQLDA data type value was detected after the

message.

execution of a DBS-initiated SQL DESCRIBE command.

This is a DBS Utility program error or a DB2 Server for

ARI0837I

&1. &2A.-&3A..

VSE system error.

Explanation: Identifies the default output record data

&1A. is the invalid data type detected.

field positions for a DATAUNLOAD command

System Action: Processing of the current command is

select-list column. This message follows message

terminated. Also see “Common Error Action” on page

ARI0836I or another occurrence of message ARI0837I in

191.

the DBS Utility message listing.

Programmer response: Notify your system

&1. is the column name or integer value that identifies

programmer.

the source of the data.

System Programmer Response: Perform problem

&2A. is the default start position for the column data in

determination. If a database system error occurred,

the output data record.

make a record of what went wrong and contact the

&3A. is the default end position for the column data in

designated support group for your installation.

the output data record.

System Action: DBS Utility processing continues.

ARI0841E End of file or read error before data

record completed.

ARI0838E Invalid SQL CONNECT statement

Explanation: During DATALOAD continued record

syntax.

processing, the last data record read indicated that the

data was continued in the following data record. An

Explanation: The syntax of an SQL CONNECT

end of file condition or read error occurred before the

statement is not valid. For example:

continuation record was read.

v An SQL CONNECT statement keyword or parameter

is missing or misspelled.

System Action: DATALOAD command processing is

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

199

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

ended. Also see “Common Error Action” on page 191.

ARI0845I

Process input table data: &1..&2.

Programmer response: If a command file read error is

Explanation: The input table identified will be

indicated by the error message ARI0814E displayed

processed by the RELOAD DBSPACE or the RELOAD

previous to this message in the DBS Utility message

TABLE command.

listing, correct the file problem identified.

v If NEW was specified in the RELOAD DBSPACE or

If a command file read error did not occur, correct the

the RELOAD TABLE command:

continuation indicator in the input data record.

- The input table definition was used to create a

Reprocess the command. (See “Rerunning DBS Utility”

new table in the database.

on page 191.)

- The input table data will be loaded into the

database table created.

ARI0842E COMMITCOUNT specified and DBS

v If PURGE was specified in the RELOAD DBSPACE

Utility AUTOCOMMIT = OFF.

command:

- The input table exists in the DBSPACE specified in

Explanation: This message is issued when the

the command.

COMMITCOUNT parameter is specified on the

DATALOAD INFILE or RELOAD INFILE subcommand

- All rows will be deleted from the database table.

and Database Services Utility AUTOCOMMIT

- The input table data will be loaded into the

processing is OFF. A Database Services Utility SET

database table.

AUTOCOMMIT command must be issued prior to

v If PURGE was specified in the RELOAD TABLE

running a DATALOAD or RELOAD command with

command:

COMMITCOUNT processing in effect.

- The output table exists in the database.

System Action: DATALOAD or RELOAD command

- All rows will be deleted from the database table.

processing is ended.

- The input table data will be loaded into the

Programmer response: Rerun after supplying a SET

database table.

AUTOCOMMIT ON command before the DATALOAD

or RELOAD command or removing the

&1. is the input table owner.

COMMITCOUNT parameter from the DATALOAD

INFILE or RELOAD INFILE subcommand.

&2. is the input table name.

System Action: DBS Utility processing continues.

ARI0843I

Restart processing at input data record =

&1A..

ARI0846I

Ignore input table data: &1..&2.

Explanation: This message identifies the input record

count at which DATALOAD or RELOAD processing

Explanation: The input table identified will not be

will begin after the number of records specified by the

processed by the RELOAD DBSPACE command.

RESTARTCOUNT value (rcount) are read and skipped.

v If NEW was specified in the RELOAD DBSPACE

The value (&1A.) is one more than RESTARTCOUNT

command, a table cannot be created in the database

value.

using the input table definition, because that table

already exists in the database.

System Action: Processing continues.

v If PURGE was specified in the RELOAD DBSPACE

command, the input table does not exist in the

ARI0844E End of data or read error occurred

DBSPACE specified in the command.

during RESTART processing.

Explanation: This message is issued when an input

&1. is the input table owner.

file read error or end-of-file condition occurs before the

number of records specified in the RESTARTCOUNT

&2. is the input table name.

value (rcount) are read.

System Action: DBS Utility processing continues.

System Action: Command processing is ended.

Programmer response: Either a bad input file was

ARI0847I

...No input tables processed.

used or an incorrect RESTARTCOUNT value (rcount)

Explanation: No tables were loaded as a result of

was specified. Rerun using a good input file or with

processing the last RELOAD DBSPACE command

the correct RESTARTCOUNT value.

displayed in the DBS Utility message listing.

If the last command displayed is a RELOAD DBSPACE

command with the NEW option, none of the tables in

the input file could be created and loaded because they

200

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

already exist in the database.

ARI0851E SQL SELECT processing unsuccessful:

If the last command displayed is a RELOAD DBSPACE

Rowcount = &1A..

command with the PURGE option, none of the tables in

Explanation: Identifies that the processing of an SQL

the input file could be loaded because they do not exist

SELECT statement by the DBS Utility was not

in the specified DBSPACE.

successful.

System Action: Processing continues.

&1A. is the number of rows retrieved by the SQL

Programmer response: None if the desired results

SELECT statement before the error was encountered.

were produced.

System Action: See “Common Error Action” on page

If the desired results were not produced, review the

191.

commands displayed in the DBS Utility message

Programmer response: Refer to the previous messages

listing, supply the correct command, and reprocess.

in the DBS Utility message listing for a description of

the errors encountered.

ARI0848E Reload of system tables not allowed.

Explanation: The last command displayed in the DBS

ARI0852I

parm1 parm2 processing started.

Utility message listing is a Database Services Utility

Explanation: This message identifies the start of actual

RELOAD command that attempted to load one of the

execution of the indicated command.

DB2 Server for VSE catalog tables. Any table with an

v parm1 is the primary command name.

owner = SYSTEM cannot be loaded with a Database

Services Utility RELOAD command.

v parm2 is the DBSPACE/TABLE/INDEX/blank/

PACKAGE.

System Action: Processing of the command is

terminated. Also see “Common Error Action” on page

If no subsequent messages appear in the DBS Utility

191.

message listing, VSE or the DB2 Server for VSE system

Programmer response: Do not attempt to load a

may have terminated the DBS Utility package. Check

catalog table with a Database Services Utility RELOAD

the operator console messages to determine the reason

command.

for termination.

System Action: Processing continues.

ARI0849E Definition of the input table &1..&2. is

not identical to the definition of the

ARI0853I

parm1 parm2.parm3.parm4 successful.

current table &3..&4..&5.

Explanation: The indicated DBS Utility processing for

Explanation: The last command displayed in the DBS

a database table or DBSPACE has completed

Utility message listing requested that an existing

successfully.

application server table be loaded with erroneous input

file data.

v parm1 is the UNLOAD or RELOAD.

v parm2 is the application server.

The definition of the table from which the input file

table data originated is not identical to the definition of

v parm3 is the owner of table/blank/DBSPACE/

the target table in the application server.

program.

v parm4 is the table name/DBSPACE name/program

System Action: Processing of the last command

name.

displayed in the DBS Utility message listing is

terminated. Also see “Common Error Action” on page

System Action: Processing continues.

191.

Programmer response: Correct the command and

ARI0854E parm1 parm2.parm3.parm4 unsuccessful.

reprocess it. (See “Rerunning DBS Utility” on page

Explanation: The indicated DBS Utility processing for

191.)

a database table or DBSPACE has not completed

successfully:

ARI0850I

SQL SELECT processing successful:

v parm1 is UNLOAD or RELOAD.

Rowcount = &1A..

v parm2 is the application server.

Explanation: Identifies that the DBS Utility processing

v parm3 is the owner of table/blank/DBSPACE/

of an SQL SELECT statement has completed without

program.

error.

v parm4 is the table name/DBSPACE name/program

&1A. is the number of rows selected.

name.

System Action: Processing continues.

System Action: See “Common Error Action” on page

191.

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

201

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

Programmer response: Correct the command errors

description of the errors encountered and the action to

identified by previous messages in the DBS Utility

take.

message listing and reprocess the command. (See

“Rerunning DBS Utility” on page 191.)

ARI0858E DATALOAD of more than 16 tables is

not allowed.

ARI0855I

&1. &2. processing successful.

Explanation: More than 16 DATALOAD TABLE

Explanation: The DBS Utility processing of the

commands were entered before an INFILE

identified command has completed successfully.

subcommand. The concurrent load of more than 16

tables through a single sequence of Database Services

&1. is the primary command name.

Utility DATALOAD TABLE commands is not allowed.

&2. is TABLE, INDEX or blank.

System Action: DATALOAD TABLE processing is

System Action: Processing continues.

ended. Also see “Common Error Action” on page 191.

Programmer response: Reduce the number of

ARI0856E The following SQL error and/or warning

DATALOAD TABLE commands preceding the INFILE

conditions occurred for a DBS-initiated

subcommand to 16 and reprocess the commands. (See

SQL &1. statement.

“Rerunning DBS Utility” on page 191.)

Explanation: While processing the last command

displayed in the DBS Utility message listing, an SQL

ARI0859E Invalid column reference.

warning or error condition occurred for the DBS Utility

Explanation: The last DATALOAD TABLE

initiated execution of an SQL statement.

Table-Column-Identification (TCI) or DATAUNLOAD

The SQL messages that immediately follow this

Data-Field-Identification (DFI) subcommand displayed

message describe the SQL conditions encountered.

in the DBS Utility message listing contains an invalid

column name or column reference. The column is not

&1. identifies the SQL statement executed by the DBS

in the table specified in the last DATALOAD TABLE

Utility that resulted in the SQL error or warning

command or in the select-list of the SQL SELECT

conditions.

statement for the last DATAUNLOAD command

System Action: Processing of the last command

displayed in the DBS Utility message listing.

displayed in the DBS Utility message listing is

System Action: Command processing is ended. See

terminated. Also see “Common Error Action” on page

“Common Error Action” on page 191 for more

191.

information.

Programmer response: Analyze the SQL problem

Programmer response: Determine the correct column

described in the following SQL messages. If possible,

name or column reference, alter the command and

correct the error and reprocess the command. (See

rerun.

“Rerunning DBS Utility” on page 191.)

If the SQL error indicated cannot be corrected, contact

ARI0860E ...ENDDATA command missing.

your system programmer.

Explanation: An end of command file input condition

System Programmer Response: If the SQL error

occurred while reading the DATALOAD TABLE

cannot be corrected, it is a probable database manager

command input data records embedded within the

program error. Gather all job output (include the DBS

command file. The ENDDATA command identifying

Utility generated messages, any storage dumps

the end of embedded data records was not encountered

generated, and the operator console output related to

before the end of command file input condition

the job), and then contact the designated support group

occurred.

for your installation.

The end of command file input condition may have

occurred because of a command file read error or

ARI0857E &1. &2. processing unsuccessful.

because all command records were read.

Explanation: The DBS Utility processing of the

System Action: DATALOAD TABLE processing is

identified command has not completed successfully.

terminated unsuccessfully. Also see “Common Error

&1. is the primary command name.

Action” on page 191.

&2. is TABLE, INDEX or blank.

Programmer response: If a command file read error is

indicated by the error message ARI0814E displayed

System Action: See “Common Error Action” on page

previous to this message in the DBS Utility message

191.

listing, correct the file problem identified.

Programmer response: Refer to previous error

If a command file error did not occur, supply an

messages in the DBS Utility message listing for a

202

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

ENDDATA command after the last embedded input

being used for the table identified in the message, the

data record in the command file input.

data record containing the bad data value will be

displayed. If insert blocking is being used for the table,

Reprocess the command. (See “Rerunning DBS Utility”

the data record displayed will be the current data

on page 191.)

record being processed when the DBS Utility

processing detected the SQL error. The bad data value

ARI0861E NULL/CURRENT clause specified for

may be in the record displayed or in a previous data

column defined as NOT NULL or

record.

invalid data type.

System Action: Command processing is ended. See

Explanation: The last DATALOAD TABLE

“Common Error Action” on page 191 for more

Table-Column-Identification (TCI) or DATAUNLOAD

information.

Data-Field-Identification (DFI) subcommand displayed

Programmer response: Correct the command and

in the DBS Utility message listing contains:

reprocess it. (See “Rerunning DBS Utility” on page

v A null-clause or set-null-clause, but the associated

191.)

column does not allow null values.

v A current-clause, but the associated column is not

ARI0863E &1..&2..&3. &4. data field positions

defined as a (correct) DATETIME or CHAR data

exceed input record length.

type.

Explanation: A table column data field is not complete

System Action: Command processing is ended. See

in an input data record. The start position or end

“Common Error Action” on page 191 for more

position of the table column data field exceeds the

information.

length of an input data record.

Programmer response: Correct the command and

&1. is the server-name.

reprocess it. (See “Rerunning DBS Utility” on page

191.)

&2. is the table owner.

&3. is the table name.

ARI0862E SQL INSERT error (table name is

&4. is the column name.

&1..&2..&3.).

System Action: DATALOAD TABLE processing is

Current input record count is &4A..

ended. Also see “Common Error Action” on page 191.

Explanation: An SQL error or warning condition

Programmer response: Correct the DATALOAD

occurred while processing the last or last group of DBS

TABLE Table-column-identification subcommand.

Utility commands displayed in the DBS Utility message

Rerun the job. (See “Rerunning DBS Utility” on page

listing. The input record count when the error occurred

191.)

is also identified. If insert blocking is not being used for

the table identified in the message, the record count

ARI0864E Data field is longer than the column.

displayed will be the record in error. If insert blocking is

being used for the table, the record count is the count up

Explanation: The last DATALOAD TABLE

to the end of the current block. The record in error may

Table-Column-Identification (TCI) displayed in the DBS

be a previous record in the block. Setting

Utility message listing specifies:

COMMITCOUNT to 1 will turn off blocking.

v An input record CHAR data field length greater than

The actual table being processed when the SQL

the length of the target CHAR column, or

condition occurred is identified in the message:

v An input record DECIMAL data field with a

precision or scale greater than the precision or scale

&1. is the server-name.

of the target DECIMAL column, or

&2. is the table owner.

v An input record ZONED data field with a scale

greater than the scale of the target DECIMAL

&3. is the table name.

column.

&4A. is the input record count.

v An input record 8-byte FLOAT data field with a

The SQL error or warning condition is identified by the

length greater than the 4-byte FLOAT target column.

preceding SQL messages in the DBS Utility message

System Action: DATALOAD TABLE processing is

listing.

ended. Also see “Common Error Action” on page 191.

Hexadecimal Display:

Programmer response: Correct the command or

A hexadecimal display of the data record being

correct the input data. Rerun the job. (See “Rerunning

processed when the SQL error occurred will follow the

DBS Utility” on page 191.)

message text. If DB2 Server for VSE insert blocking is not

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

203

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

v Data record data fields with the data type DATE

ARI0865E Invalid data field data type for column.

must be at least 10 bytes in length.

Explanation: The last DATALOAD TABLE

v Data record data fields with the data type TIME

Table-Column-Identification (TCI) or DATAUNLOAD

must be long enough to accommodate the full length

Data-Field-Identification (DFI) subcommand displayed

of the time format being used.

in the DBS Utility message listing specifies an invalid

v Data record data fields with data type TIMESTAMP

input or output record field data type for the associated

must be at least 19 bytes in length.

table or select-list column.

System Action: DATALOAD TABLE processing is

ended. Also see “Common Error Action” on page 191.

Programmer response: Correct the command and

Programmer response: Correct the command or

reprocess it. (See “Rerunning DBS Utility” on page

correct the input data. Reprocess the command. (See

191.)

“Rerunning DBS Utility” on page 191.)

ARI0868I

DNAME=&1. RECFM=&2. RECSZ=&3A.

ARI0866E Input record data field error: Column =

BLKSIZE=&4A..

&1.. Input Record Count = &2A..

Explanation: This message contains the input or

Explanation: A data conversion error occurred.

output file specifications being used by DBS Utility

The input data could not be converted to the table

command processing to open the input or output data

column numeric data type because the input data field

file.

contains one of the following errors:

The information reflects the INFILE or OUTFILE

v Nonnumeric character data.

command specifications or indicates the DBS Utility

v Blanks embedded within the character data.

defaults that are being used.

v A data value that is too small or too large for the

This message will be generated after an input or output

target column.

data file has been successfully initialized (opened) for

processing.

&1. is the table column name.

&1. is the INFILE or OUTFILE dname parameter.

&2A. is the input record count at the time the error

&2. is the record format specification:

occurred.

S or VS

= Variable, spanned, unblocked

SB or VBS

= Variable, spanned, blocked

Hexadecimal Display:

= Fixed, unblocked

= Fixed, blocked

A hexadecimal display of the data record containing

= Variable, unblocked

the incorrect data value will follow the text.

= Variable, blocked

System Action: DATALOAD TABLE processing is

&3A. is the logical record length specification.

ended. Also see “Common Error Action” on page 191.

Programmer response: Correct the input data. Rerun

Note: For input or output data files with

the job. (See “Rerunning DBS Utility” on page 191.)

variable-length spanned records, the actual

logical record length may be greater than the

record length displayed in the message.

ARI0867E Invalid data field length.

Explanation: The last DATALOAD TABLE

&4A. is the block size specification.

Table-Column-Identification (TCI) or DATAUNLOAD

System Action: DBS Utility processing continues.

Data-Field-Identification (TFI) subcommand, displayed

in the DBS Utility message listing, specifies an invalid

length for a FIXED, FLOAT, REAL, DOUBLE

ARI0871E Table &1..&2..&3. not found.

PRECISION, GRAPHIC, TIME, DATE or TIMESTAMP

Explanation: The identified table was not found in

data record data field:

SYSTEM.SYSCATALOGS.

v Data record data fields with the data type FIXED

must be 1, 2, or 4 bytes in length.

&1. is the server-name.

v Data record data fields with the data type FLOAT

&2. is the table owner.

must be 4 or 8 bytes in length.

&3. is the table name.

v Data record data fields with the data type GRAPHIC

must be an even number (2, 4, 6, .. 100 ...,) of bytes

System Action: Command processing is ended. See

in length.

204

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

“Common Error Action” on page 191 for more

&3. is the table owner.

information.

&4. is the table name.

Programmer response: Ensure the table name

System Action: Processing continues.

specified in the command is correct.

If incorrect, correct the command and reprocess it. (See

ARI0875I

&1A. rows loaded into table &2..&3..&4..

“Rerunning DBS Utility” on page 191.)

Explanation: Identifies the number of rows loaded

If correct, the table must be created before it can be

into a table.

processed by an UNLOAD or DATALOAD command

or the NEW parameter must be specified in the

&1A. is the number of rows.

RELOAD TABLE command.

&2. is the server-name.

&3. is the table owner.

ARI0872E DBSPACE &1. not found.

&4. is the table name.

Explanation: The identified DBSPACE is not in the

database. If owner.DBSPACE name was specified in the

System Action: Processing continues.

last command displayed in the DBS Utility message

listing, that specific DBSPACE was not found. If only a

ARI0876E Data file record error: Record Type =

DBSPACE name was specified in the last command,

&1A.. Input record count = &2A.. Reason

neither a private or public DBSPACE with this name

Code = &3A..

was found.

Explanation: An error has been detected in the

System Action: Command processing is ended. See

RELOAD TABLE or RELOAD DBSPACE input data

“Common Error Action” on page 191 for more

file. The format or content of the input file is incorrect.

information.

RECORD TYPE (&1A.) identifies the type of input

Programmer response: Ensure that the DBSPACE

record expected, or the type of record being processed

name specified in the UNLOAD DBSPACE or RELOAD

when the error occurred.

DBSPACE command is correct.

Possible types are:

If incorrect, correct the command and reprocess it. (See

“Rerunning DBS Utility” on page 191.)

Unload header record

If correct, the DBSPACE must be acquired and tables

SQLDA table description record

created in the DBSPACE before the DBSPACE can be

unloaded.

Table row data record.

Input record count (&2A.) identifies the number of

ARI0873E DBSPACE &1..&2..&3. contains no

input file records read before the error was detected.

tables.

Explanation: The identified DBSPACE is empty.

Reason Code (&3A.) identifies the particular error that

was encountered.

&1. is the server-name.

&2. is the DBSPACE owner.

The definition of the REASON CODE values are:

&3. is the DBSPACE name.

A premature end of file occurred. &1A.

identifies the record type value expected when

System Action: Command processing is ended. See

the end of file condition occurred.

“Common Error Action” on page 191 for more

information.

An unexpected record type was read or the

format of a record read is invalid. &1A.

Programmer response: Do not attempt to UNLOAD

identifies the expected record type.

the DBSPACE until tables are created in the DBSPACE.

System Action: Command processing is ended. See

“Common Error Action” on page 191 for more

ARI0874I

&1A. rows unloaded from table

information.

&2..&3..&4..

Programmer response: If the input file was created by

Explanation: Identifies the number of rows unloaded

DBS UNLOAD processing, contact the system

from a table and written to the output file during

programmer.

UNLOAD command processing.

If the input file was not created by DBS UNLOAD

&1A. is the number of rows.

processing, correct the error and rerun the job.

&2. is the server-name.

System Programmer Response: Perform problem

Chapter

13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

205

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

determination. If a database system error occurred,

ARI0880I

&1A. rows deleted from table

make a record of what went wrong and contact the

&2..&3..&4..

designated support group for your installation.

Explanation: Identifies the number of table rows

deleted while processing the last RELOAD command

ARI0877E Table &1..&2..&3. not created. It already

displayed in the DBS Utility message listing.

exists.

&1A. is the number of rows in the table that were

Explanation: A table with the tablename specified in

deleted.

the last RELOAD TABLE command displayed in the

DBS Utility message listing could not be created since a

&2. is the name of the server-name.

table with the same owner.tablename already exists in

&3. is the owner of the table.

the database.

&4. is the name of the table.

&1. is the name of the application server.

System Action: Processing continues.

&2. is the owner of the table.

&3. is the name of the table.

ARI0881E &1. &2..&3. was not found.

System Action: Command processing is ended. See

Explanation: The table name specified by the

“Common Error Action” on page 191 for more

INTABLE or RESTARTTABLE parameter in the last

information.

RELOAD TABLE command displayed in the DBS

Programmer response: Correct the command by

Utility message listing was not found on the input data

specifying a different tablename or the PURGE

file.

parameter and reprocess the command. (See

&1. is a RELOAD parameter value (either INTABLE or

“Rerunning DBS Utility” on page 191.)

RESTARTTABLE).

&2. is the table owner (if specified in either INTABLE

ARI0878E Creation of &1. &2..&3..&4. failed.

or RESTARTTABLE).

Explanation: While processing the last RELOAD

&3. is the table name specified in the INTABLE or

command displayed in the DBS Utility message listing,

RESTARTTABLE parameter.

an SQL CREATE TABLE or INDEX statement executed

by DBS Utility resulted in an SQL error or warning

System Action: Command processing is ended. See

condition.

“Common Error Action” on page 191 for more

information.

&1. is TABLE or INDEX.

Programmer response: Correct the command and

&2. is the server-name.

reprocess it. (See “Rerunning DBS Utility” on page

&3. is the owner of the table or index.

191.)

&4. is the name of the table or index.

ARI0882E Missing the &1. &2. parameter.

System Action: Command processing is ended. See

“Common Error Action” on page 191 for more

Explanation: A command parameter is missing from

information.

the last command displayed in the DBS Utility message

listing.

Programmer response: Refer to the messages

preceding this message in the DBS Utility message

&1. is the command or command parameter identifier.

listing to identify the SQL error or warning conditions

&2. is the command parameter subidentifier (optional).

encountered. Perform the actions necessary to correct

the SQL condition. Rerun the job. (See “Rerunning DBS

System Action: Command processing is ended. See

Utility” on page 191.)

“Common Error Action” on page 191 for more

information.

ARI0879I

Table &1..&2..&3. created.

Programmer response: Correct the command and

reprocess it. (See “Rerunning DBS Utility” on page

Explanation: Identifies that a table has been

191.)

successfully created while processing the last RELOAD

command displayed in the DBS Utility message listing.

ARI0883E Extra command parameters.

&1. is the server-name.

Explanation: The last command displayed in the DBS

&2. is the table owner.

Utility message listing contains additional information

&3. is the table name.

after all valid command parameters have been

specified.

System Action: Processing continues.

206

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

The message may also occur because the command file

System Action: Command processing is ended. See

record after a DBS Utility command does not contain a

“Common Error Action” on page 191 for more

valid command identifier, or information has been

information.

specified after the terminating semicolon in an SQL

Programmer response: Correct the command and

statement parsed by DBS Utility processing.

reprocess it. (See “Rerunning DBS Utility” on page

191.)

Note: Only the various forms of the SQL COMMIT,

ROLLBACK, and CONNECT statements are

parsed by DBS Utility processing.

ARI0888E Invalid &1. parameter.

System Action: Command processing is ended. See

Explanation: An unknown keyword parameter or an

“Common Error Action” on page 191 for more

invalid parameter value was specified in the last

information.

command displayed in the DBS Utility message listing.

Programmer response: Correct the command and

&1. identifies the command parameter.

reprocess it. (See “Rerunning DBS Utility” on page

System Action: Command processing is ended. See

191.)

“Common Error Action” on page 191 for more

information.

ARI0884I

...Command processed.

Programmer response: Correct the command and

Explanation: The last command displayed in the DBS

reprocess it. (See “Rerunning DBS Utility” on page

Utility message listing was processed.

191.)

System Action: DBS Utility processing continues.

ARI0889E Second keyword in the command must

be TABLE.

ARI0885E Invalid &1. value length.

Explanation: The command identifier keyword TABLE

Explanation: The length of a command parameter

is missing in the last command displayed in the DBS

value is invalid in the last command displayed in the

Utility message listing.

DBS Utility message listing.

System Action: Command processing is ended. See

&1. identifies the command parameter.

“Common Error Action” on page 191 for more

System Action: Command processing is ended. See

information.

“Common Error Action” on page 191 for more

Programmer response: Correct the command and

information.

reprocess it. (See “Rerunning DBS Utility” on page

Programmer response: Correct the command and

191.)

reprocess it. (See “Rerunning DBS Utility” on page

191.)

ARI0890E Second keyword in the command must

be either TABLE, DBSPACE, PACKAGE,

ARI0886E Incomplete &1. parameter.

or PROGRAM.

Explanation: A command parameter is incomplete in

Explanation: The command identifier keyword

the last command displayed in the DBS Utility message

TABLE, DBSPACE, PACKAGE or PROGRAM is

listing.

missing in the last command displayed in the DBS

Utility message listing.

&1. identifies the command parameter.

System Action: Command processing is ended. See

“Common Error Action” on page 191 for more

information.

Programmer response: Correct the command and

reprocess it. (See “Rerunning DBS Utility” on page

191.)

ARI0891E &1. &2. parameter is missing a &3..

ARI0887E Invalid &1. &2. value.

Explanation: A command parameter is missing a

Explanation: An invalid command parameter value is

required symbol or a quoted string value is empty

contained in the last command displayed in the DBS

(quoted string value length = 0) in the last command

Utility message listing.

displayed in the DBS Utility message listing.

&1. is the command parameter identifier.

&1. is the primary command parameter identifier.

&2. is the command

parameter subidentifier (optional).

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

207

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

&2. is the secondary command parameter identifier

ARI0895E Invalid SQLCODE detected. See

(optional).

following message.

&3. Identifies the missing symbol.

Explanation: An invalid SQLCODE has been received

System Action: Command processing is ended. See

after the execution of an SQL statement. The SQLCODE

“Common Error Action” on page 191 for more

value is not within the value range -999 through +999.

information.

This is a serious DB2 Server for VSE error and

subsequent Database Services Utility SET

Programmer response: Correct the command and

ERRORMODE OFF commands will be ignored.

reprocess it. (See “Rerunning DBS Utility” on page

191.)

System Action: Command processing is ended. See

“Common Error Action” on page 191 for more

information.

ARI0892E &1. parameter(s) not found.

Programmer response: Contact your system

Explanation: A required command parameter is

programmer.

missing or a keyword parameter has been specified

without parameter values in the last command

System Programmer Response: Probable DB2 Server

displayed in the DBS Utility message listing.

for VSE system error. Perform problem determination.

If a database system error occurred, make a record of

&1. identifies the command parameter.

what went wrong and contact the designated support

System Action: Command processing is ended. See

group for your installation.

“Common Error Action” on page 191 for more

information.

ARI0896E Duplicate or conflicting &1. parameter.

Programmer response: Correct the command and

Explanation: A duplicate or conflicting command

reprocess it. (See “Rerunning DBS Utility” on page

parameter is specified in the last command displayed

191.)

in the DBS Utility message listing.

&1. is the command parameter identification.

ARI0893E &1. &2. parameter is longer than &3A.

positions.

System Action: Command processing is ended. See

“Common Error Action” on page 191 for more

Explanation: A command parameter is too long in the

information.

last command displayed in the DBS Utility message

listing.

Programmer response: Correct the command and

reprocess it. (See “Rerunning DBS Utility” on page

&1. is the command parameter identification.

191.)

&2. is the command subparameter identification

(optional).

ARI0897E Unknown parameter starting at or near

&3A. is the maximum allowable parameter length.

position &1A..

System Action: Command processing is ended. See

Explanation: An invalid parameter was detected in

“Common Error Action” on page 191 for more

the last command displayed in the DBS Utility message

information.

listing.

Programmer response: Correct the command and

&1A. is the approximate position in the command

reprocess it. (See “Rerunning DBS Utility” on page

where the incorrect parameter begins.

191.)

System Action: Command processing is ended. See

“Common Error Action” on page 191 for more

ARI0894I

Isolation level level in effect.

information.

Explanation: This message identifies the isolation level

Programmer response: Correct the command and

in effect for subsequent processing performed by the

reprocess it. (See “Rerunning DBS Utility” on page

DBS Utility (level = CURSOR STABILITY, REPEATABLE

191.)

READ, or UNCOMMITTED READ). The message is

issued after a user-supplied DBS ISOL(CS), ISOL(RR),

ARI0898I

...Command ignored because of severe

or ISOL(UR) control parameter or SET ISOLATION

system error.

command is processed. The identified isolation level

remains in effect until the next SET ISOLATION

Explanation: A SET ERRORMODE OFF or SET

command is processed or DBS Utility processing ends.

ERRORMODE CONTINUE command has been

encountered after a severe DB2 Server for VSE error

System Action: DBS Utility processing continues.

has occurred during DBS Utility processing.

208

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

A severe DB2 Server for VSE error is an error that does

&3. is the name of the table or view.

not allow further SQL processing or an error that will

System Action: Processing continues.

normally result in the failure of all subsequent SQL

statements executed by DBS Utility processing. If both

SQLWARN0 and SQLWARN6 are set to S after an

ARI8003I

...Extended DBCS (DBCS=YES)

attempt to process an SQL statement has been made,

processing now in effect.

the DBS Utility assumes that a severe DB2 Server for

Explanation: This message is issued when extended

VSE system error has occurred.

DBCS processing is in effect for the database being

System Action: No action taken. DBS Utility error

accessed by DBS Utility processing. The DBS Utility

mode processing continues.

determines when extended DBCS processing is in effect

for a database by accessing the database

SYSTEM.SYSOPTIONS catalog table. If a row with the

ARI0899I

...Command ignored.

SQLOPTION column value equal to DBCS and the

Explanation: A SET ERRORMODE OFF, SET

VALUE column value equal to YES exists, extended

ERRORMODE ON, or SET ERRORMODE CONTINUE

DBCS processing is in effect for the database.

command has been encountered, but the error mode

System Action: DBS Utility processing continues

processing status identified in the command is already

WITH EXTENDED DBCS processing in effect.

in progress.

System Action: No action taken. DBS Utility

ARI8004I

User userid connected to server

processing continues.

server-name.

Explanation: This message shows the current user and

ARI8000I

...Ignore previous error. Processing is

the current application server accessed as the result of a

continuing.

CONNECT command.

Explanation: Because a SET ERRORMODE

If the value of userid in the message is UNKNOWN, no

CONTINUE command was supplied before the

userid is established yet, as in the CONNECT TO

DATALOAD command, and the COMMITCOUNT

dbname after a previous COMMIT RELEASE or

parameter was specified on the DATALOAD INFILE

ROLLBACK RELEASE statement.

subcommand, the error identified by the preceding

ARI0862E or ARI0866E message is ignored.

System Action: No action taken.

System Action: DATALOAD processing continues.

ARI8005I

One or more arithmetic exception errors

occurred. Exception error &1. occurred

ARI8001E Invalid graphic data starting at or near

during &2. operation on &3. data,

position &1A..

position &4..

Explanation: If extended graphic support is in effect

Explanation: This message is issued whenever an

for the database, this message is issued after DBS

arithmetic operation on numeric data causes an

Utility processing detects an SO delimiter without a

arithmetic exception error. The cause may be a division

terminating SI delimiter or the graphic data is not

by zero or overflow (exceeds maximum) during the

represented in paired bytes. The message refers to the

processing of a SELECT statement or a DATAUNLOAD

last command record entered. The last command record

command. The data from this error is denoted by

entered is displayed immediately preceding this error

number signs (# # #) across the width of columns of the

message in the DBS Utility message file.

queried table:

&1A. is the approximate position in the command

&1. is the type of exception error.

record where the invalid graphic data begins.

&2. is the arithmetic operation on data.

&3. is the data type.

System Action: Command processing is ended.

&4. is position N, where N is an item in the

Programmer response: Correct input command and

select-list, if applicable. Position 0 is returned if an

rerun.

exception error occurs in the WHERE clause of a

SELECT statement.

ARI8002I

Blocked INSERT processing was

Note: The message describes the first arithmetic

suppressed for &1..&2..&3.

exception error in the queried table.

Explanation: Insert blocking was suppressed during

System Action: Processing continues.

DATALOAD processing for the table or view identified.

&1. is the server-name.

&2. is the owner.

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

209

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

Programmer response: Refer to the messages

ARI8006E An arithmetic error occurred during

preceding this message in the DBS Utility message

unloading of data into a numeric field.

listing to identify the SQL error conditions encountered.

Exception error &1. occurred during &2.

Command processing ends. Correct the command and

operation on &3. data, position &4..

reprocess it. (See “Rerunning DBS Utility” on page

Explanation: This message is issued whenever an

191.)

arithmetic exception error (indicated by number signs #

# #) is being written into a numeric datatype field of an

ARI8010E Package name owner.package-name is not

output file defined for DATAUNLOAD processing.

the same as the package name in the

The user is informed about the first occurrence of an

input file.

arithmetic exception error caused by the SELECT

Explanation: The package-name in the RELOAD

statement while processing the DATAUNLOAD

PACKAGE command does not match the

command:

package-name in INFILE.

&1. is the type of exception error.

&2. is the arithmetic operation on data.

System Action: Command processing is ended. Also

&3. is the data type.

see “Common Error Action” on page 191 for more

&4. is position N, where N is an item in a select-list,

information.

if applicable. Position 0 is returned if an exception

Programmer response: Determine the correct package

error occurs in the WHERE clause of a SELECT

name, alter the command, and rerun the package.

statement.

System Action: DATAUNLOAD command processing

ARI8011I

Package &1.&2. was {created|replaced}.

is ended. Also see “Common Error Action” on page

191.

Explanation: A package was created or replaced.

Programmer response: Correct the arithmetic error or

v &1. = owner

change the numeric data type to CHARacter data type

v &2. = package name

in the output file.

System Action: Processing continues.

ARI8007I

Error(s) occurred during ERRORMODE

ARI8012E Package name &1..&2. not found &3.

CONTINUE processing.

&4..

Explanation: Some commands processed while SET

Explanation:

ERRORMODE CONTINUE was in effect were not

processed successfully.

v &1. = owner

v &2. = package-name

System Action: DBS Utility end of program

processing continues.

v &3. = in server

v &4. = application server name

Programmer response: Refer to previous messages

during ERRORMODE CONTINUE processing in the

DBS Utility message listing to identify any unexpected

The identified package was not found in

errors.

SYSTEM.SYSACCESS. If you specified an UNLOAD

PACKAGE FROM clause, &3. and &4. indicate the

application server where the package was not found.

ARI8008E The FROM/TO parameter not valid in

VSE.

Programmer response: Ensure the package-name

specified in the command is correct. If incorrect, correct

Explanation: DBS Utility in VSE environment does not

the command, and reprocess it. (See “Rerunning DBS

allow connections to different databases; therefore, the

Utility” on page 191.) If correct, the package must be

user may only UNLOAD/RELOAD PROGRAMS on

created before it can be processed by an UNLOAD

initially connected database.

PACKAGE or a REBIND PACKAGE command.

System Action: Command processing is ended. Also

see “Common Error Action” on page 191 for more

ARI8015E command failed.

information.

Explanation: Indexes are re-created and PRIMARY

KEYS, FOREIGN KEYS, and UNIQUE CONSTRAINTS

ARI8009E &1. PACKAGE failed.

are reactivated, after reloading the data. The attempt to

re-establish entity or Referential Integrity has failed.

Explanation: &1. = UNLOAD or RELOAD. UNLOAD

The command indicates the first command that failed.

or RELOAD PACKAGE failed.

System Action: Processing of the DBS Utility

System Action: Command processing ends.

command has ended.

210

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

User Response: Correct the data and reissue the

ARI8020E Invalid CREATE SCHEMA statement.

RELOAD, or manually establish the missing indices

and keys.

Explanation: You must make the first (and only the

first) statement within the schema sequential input file

the CREATE SCHEMA statement.

ARI8016I

command successful.

System Action: Command processing ends.

Explanation: Indexes are re-created and PRIMARY

KEYS, FOREIGN KEYS, and UNIQUE CONSTRAINTS

User Response: Correct the command and reprocess

reactivated, after the data is reloaded. A step in this

it. If a COMMIT of database changes occurred during

process has succeeded.

this execution of the SCHEMA command, rerun the

Database Services Utility for this command, but omit

System Action: Processing of the DBS Utility

all the statements within the sequential input file that

command continues.

altered the database prior to the last COMMIT of

database changes.

ARI8017E Second keyword in command must be

PACKAGE.

ARI8021E Statement not supported within a

Explanation: The command identifier keyword

Schema.

PACKAGE is missing from the last command displayed

Explanation: The last statement displayed in the

in the Database Services Utility message listing.

Database Services Utility message listing is not a valid

System Action: Command processing ends. See

schema statement.

“Common Error Action” on page 191 for more

System Action: Processing of this statement ends.

information.

User Response: Correct the command and reprocess

System Programmer Response: Correct the command

it. If a COMMIT of database changes occurred during

and reprocess it. See “Rerunning DBS Utility” on page

this execution of the SCHEMA command, rerun the

191 for more information.

Database Services Utility for this command, but omit

all the statements within the sequential input file that

ARI8018E Command is not supported for primary

altered the database prior to the last COMMIT of

or unique keys.

database changes.

Explanation: Using the Database Services Utility

REORGANIZE INDEX command for an index that the

ARI8022E Second keyword in command must be

database manager created to enforce the uniqueness of

INDEX.

a primary or unique key is invalid. Use the following

Explanation: The command identifier keyword INDEX

commands instead:

is missing in the last command displayed in the

v ALTER TABLE ACTIVATE PRIMARY KEY for

Database Services Utility message listing.

primary keys.

v ALTER TABLE ACTIVATE UNIQUE KEY for unique

System Action: Command processing ends. See

keys.

“Common Error Action” on page 191 for more

information.

System Action: The Database Services Utility ignores

the command.

User Response: Correct the command and reprocess

it. (See “Rerunning DBS Utility” on page 191.)

ARI8019I

No server has been connected yet.

ARI8023E User userid1 is not authorized to create a

Explanation: A null CONNECT was issued before an

Schema for another user userid2.

application server was connected.

Explanation: The AUTHORIZATION user ID userid2

System Action: When a null CONNECT is issued

on the CREATE SCHEMA statement must be the same

before an application server connection is established,

as the currently connected user userid1.

the resource adapter returns a blank user ID and

application server name in the SQLERRMT field, with

System Action: Command processing ends.

SQLCODE set to 0.

User Response: Correct the command and reprocess

Programmer response: Use null CONNECT only after

it.

a user ID and an application server connection are

established.

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

211

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

database manager, and the table cannot be created by

ARI8027E Infile contents invalid.

the DBS utility.

Explanation: An error has been detected in the

&1. is the owner of the table.

RELOAD PACKAGE input data file. In the input file,

the format or content or both are incorrect.

&2. is the name of the table.

System Action: Command processing is ended. See

System Action: Command processing is ended.

“Common Error Action” on page 191 for more

Programmer response: To reload the data, use

information.

RELOAD with the PURGE parameter. The table must

Programmer response: Contact the system

already exist.

programmer. The system programmer should perform

problem determination. If a system error occurred,

ARI8034I

command

make a record of what went wrong and contact the

designated support group for your installation.

Explanation: The DBS Utility is processing a RELOAD

command that includes the COMMITCOUNT

parameter, but neither the RESTARTCOUNT or

ARI8031E The package &1. cannot be reloaded to a

RESTARTTABLE parameters. RELOAD processing will

back level release server.

DROP all indexes and DEACTIVATE all primary and

Explanation: The package cannot be reloaded to the

unique keys before reloading data. The

target application server because of package format

COMMITCOUNT parameter indicates that these DROP

differences. This message will be issued when reloading

statements will be committed to the database before the

an SQL/DS Version 3 Release 1 or above package to a

RELOAD process has completed. If the RELOAD

pre-Version 3 Release 1 database. The RELOAD

process does not complete successfully, the dropped

PACKAGE command failed.

objects can no longer be recovered. To aid the user in

recovering these objects, the ARI8034I messages

&1. is the name of the package.

provide the CREATE statements required to recover the

System Action: The package is not reloaded.

dropped objects. If no error occurs reloading the data,

all dropped objects will be recreated during normal

User Response: Issue ROLLBACK to the logical unit

RELOAD processing. Refer to ARI8035I to identify the

of work.

clustering index.

System Action: Processing continues.

ARI8032I

The length of the SQL CREATE TABLE

statement for table &1..&2. exceeds 8192

Programmer response: If an error occurs during

bytes. It will not be possible to reload

RELOAD processing, refer to the ARI8034I messages to

with the parameter NEW.

create or activate the dropped and deactivated objects.

Explanation: The CREATE TABLE statement of the

identified table exceeds 8192 bytes. The CREATE

ARI8035I

The clustering index for

TABLE statement that the DBS Utility places into the

table-creator.table-name is index-type

unload output file may be incomplete, because of

index-owner.index-name

truncation.

Explanation: This message identifies the INDEX,

To reload the data from this unload output file,

PRIMARY KEY or UNIQUE KEY that is currently the

RELOAD with the PURGE parameter must be used,

clustering index for the table.

and the table or tables must already exist in the

System Action: Processing continues.

database.

Programmer response: When recovering from a failed

&1. is the owner of the table.

RELOAD, this object should be the first to be created or

&2. is the name of the table.

activated so that it will be used as the clustering index.

System Action: Processing continues.

ARI8980I

Statistics were generated automatically

for table &1..&2..

ARI8033E DBS-initiated SQL CREATE TABLE

statement for table &1..&2. exceeds 8192

Explanation: The database manager generated table or

bytes. RELOAD with the PURGE

DBSPACE statistics while the Database Services Utility

parameter should be used.

loaded the rows. The Database Services Utility does not

need an SQL UPDATE STATISTICS request, and one is

Explanation: During reload with the parameter NEW,

not issued during Database Services Utility command

the CREATE TABLE statement built by the DBS utility

processing.

for use in creating the table exceeds the 8192 byte

maximum SQL statement length allowed by the

&1. is the owner of the table or DBSPACE.

212

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

&2. is the name of the table or DBSPACE.

form of statistics collection for the concurrent loading

of more than one table.

System Action: Database Services Utility processing

continues.

System Action: Database Services Utility processing

continues. The Database Services Utility issues an SQL

UPDATE STATISTICS request to generate the statistics

ARI8981I

Dynamic statistic accumulation was

for each table.

disallowed for table &1. &2. Reason

Code = &3..

ARI8990I

The table &1..&2..&3. is in a

Explanation: The database manager does not allow

nonrecoverable storage pool.

the automatic accumulation of table statistics while

loading data for this DATALOAD command.

Explanation: This message identifies each table in the

nonrecoverable storage pool that will be loaded by

&1. is the owner of the table.

DATALOAD processing.

&2. is the name of the table.

&1. is the name of the application server.

The reason code identifies why the automatic

&2. is the owner of the table.

accumulation of table statistics was disallowed:

&3. is the name of the table.

One or more indexes exist on the table.

System Action: Processing continues.

The ROWCOUNT in the SYSCATALOG entry

for this table was greater than zero, or was -2

(indicating that a failed DATALOAD was

ARI8991I

If the database manager is executing

restarted).

with LOGMODE=A|Y, any rows

inserted into the database will not be

System Action: Database Services Utility processing

deleted by ROLLBACK processing.

continues. The Database Services Utility issues an SQL

UPDATE STATISTICS request to generate the statistics.

Explanation: This message is issued before Database

Services Utility RELOAD PURGE insert processing that

will update a nonrecoverable storage pool is started. If

ARI8982I

Statistics for loaded rows replace

a subsequent error occurs during DBS RELOAD

statistics for table &1..&2..

PURGE processing, the table or tables may be partially

Explanation: The Database Services Utility processed a

loaded, because ROLLBACK processing will not

DATALOAD command, and the ROWCOUNT value in

remove the rows inserted into the database.

the SYSCATALOG entry for the loaded table was not

If running in single user mode with LOGMODE=N,

greater than zero. As a result, the database manager

ROLLBACK processing will remove the inserted rows.

automatically generated statistics for the loaded rows,

and replaced the table's current statistics.

If running in multiple user mode, or in single user

mode with LOGMODE=A or Y, ROLLBACK processing

&1. is the owner of the table.

will not remove the inserted rows; it will commit the

&2. is the name of the table.

rows to the database.

If the table was not empty prior to the DATALOAD,

System Action: Processing continues.

the generated statistics do not accurately reflect the

Programmer response: If RELOAD PURGE processing

table's contents. This prevents the DB2 Server for VSE

fails to complete successfully, rerun the DBS Utility to

Optimizer from selecting the most efficient access path

reload the tables.

when retrieving rows from the table.

System Action: Database Services Utility processing

ARI8992I

If the database manager is executing

continues. The Database Services Utility issues an SQL

with LOGMODE=A|Y, any rows

UPDATE STATISTICS request to generate statistics for

inserted into the table

each table.

[server-name.]owner.table-name will not be

deleted by ROLLBACK processing.

ARI8983I

Dynamic statistic accumulation was

Explanation: An error occurred during Database

disallowed for all tables named in the

Services Utility DATALOAD processing, and rows were

DATALOAD command.

inserted into a table in a nonrecoverable storage pool.

Explanation: A DATALOAD command that loaded

This message identifies that subsequent ROLLBACK

data into more than one table was processed. For this

processing may not remove the inserted rows.

DATALOAD, the database manager cannot accumulate

If running in multiple user mode, or in single user

statistics while the Database Services Utility loads the

mode with LOGMODE=A or Y, ROLLBACK processing

rows. The database manager does not support this

will not remove the inserted rows. In fact, the rows will

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

213

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

be committed to the database by a ROLLBACK.

ARI8994I

Blocked FETCH or INSERT processing

If running in single user mode with LOGMODE=N,

was suppressed.

ROLLBACK processing will remove the inserted rows.

Explanation: This message identifies that blocked

System Action: Processing continues.

fetch or insert processing was suppressed by the

database manager while processing the previous

Programmer response: If running in multiple user

command displayed in the DBS Utility message file.

mode, or in single user mode with LOGMODE=A or Y,

Possible causes include:

perform the recovery actions required for a

v The DBS Utility is running in single user mode.

nonrecoverable storage pool before rerunning the DBS

utility.

v A table or view with a LONG VARCHAR or LONG

VARGRAPHIC column was referenced by the

command.

ARI8993I

If the database manager is executing

v There was insufficient virtual storage to support

with LOGMODE=A|Y, you should not

blocked fetch or insert processing.

use DATALOAD RESTART processing

before the last &1A. rows inserted into

v Two or more rows of the fetched or inserted data

the table &2..&3..&4. are deleted.

will not fit into an 8K block.

Explanation: An error occurred during Database

System Action: DBS Utility processing continues.

Services Utility DATALOAD processing, and rows were

inserted into a table in a nonrecoverable storage pool.

ARI8995I

parm1 continuing. Record Count =

This message identifies that DATALOAD RESTART

parm2.

processing may not be applicable until special action is

taken.

Explanation: This message is written to the operator

console or user terminal after every 15000 input or

&1A. is the number of rows inserted into the table since

output data file records are processed by a DBS Utility

the start of DATALOAD processing or since the last

command.

ARI0800I message was displayed.

parm1 is either DATALOAD, DATAUNLOAD,

&2. is the name of the application server.

RELOAD, or UNLOAD.

&3. is the owner of the table.

parm2 value is either:

&4. is the name of the table.

v The current data file record count (parm1 is

DATALOAD or RELOAD)

If running in multiple user mode, or in single user

v The current output data file record count (parm1 is

mode with LOGMODE=A or Y, ROLLBACK processing

DATAUNLOAD or UNLOAD).

will not remove the rows inserted since the start of

DATALOAD processing or since the last ARI800I

Note: During DATALOAD command processing, the

message was generated. Special action is required

message is written only if the DBS Utility

before rerunning the DBS Utility to load the identified

message file is not assigned to:

tables.

v A console or terminal, and

If running in single user mode with LOGMODE=N,

v DATALOAD COMMITCOUNT processing is

ROLLBACK processing will remove the inserted rows.

not in progress.

System Action: Processing continues.

System Action: DBS Utility processing continues.

Programmer response: If running in single user mode

with LOGMODE=N, the DBS Utility can be rerun to

ARI8996I

...Begin UPDATE STATISTICS for

load the identified tables without taking any special

&1..&2..&3..

action.

Explanation: This message is written to the DBS

If running in multiple user mode, or in single user

Utility message file before an SQL UPDATE

mode with LOGMODE=A or Y, ROLLBACK processing

STATISTICS statement is issued for a table during DBS

will commit (not remove) the rows inserted since the

Utility command processing.

last ARI0800I message was displayed. You must

&1. is the name of the application server.

perform the recovery actions required for a

nonrecoverable storage pool before rerunning the DBS

&2. is the owner of the table.

Utility.

&3. is the name of the table.

System Action: DBS Utility processing continues.

214

Messages and Codes

DBS Utility Messages - ARI0800-ARI0899, ARI8000-ARI8999

ARI8997I

...Begin COMMIT [RELEASE]

processing.

Explanation: This message is written to the DBS

Utility message file before an SQL COMMIT or SQL

COMMIT RELEASE statement is issued. The successful

completion of the COMMIT will be identified by the

subsequent message:

ARI0811I ...COMMIT of any database

changes successful.

System Action: DBS Utility processing continues.

ARI8998I

...Begin ROLLBACK [RELEASE]

processing.

Explanation: This message is written to the DBS

Utility message file before a ROLLBACK or

ROLLBACK RELEASE statement is issued by DBS

Utility command processing. Successful completion of

the ROLLBACK will be identified by the subsequent

message:

ARI0811I ...ROLLBACK of any database

changes successful.

System Action: DBS Utility processing continues.

ARI8999E Invalid SQL statement or parameter:

&1..

Explanation: An invalid control parameter or SQL

statement was encountered in the DBS Utility

invocation parameter list.

&1. is the first 20 positions of the invalid parameter

string; or the phrase INVALID LENGTH OR CALL

TYPE.

System Action: DBS Utility processing completes.

Programmer response: If the phrase INVALID

LENGTH OR CALL TYPE is displayed for variable &1.,

correct the user program. The program specified an

invalid DBS Utility call type or an invalid parameter

string length.

When the variable &1. contains a portion of the DBS

Utility parameter string, correct the parameter string.

After the appropriate corrections are made, rerun.

Chapter 13. ARI0800-ARI0899, ARI8000-ARI8999 DBS Utility Messages

215

Chapter 14. ARI0900-ARI0949

Database Maintenance and

Database I/O Messages

Operator Response: Complete the storage pool

ARI0900E operation error on DDNAME =

recovery process by starting the database with

xxxxxxxx. Return Code = nn. EREASON

STARTUP=U.

= nn.

Explanation: An error occurred in a sequential input

ARI0903E DBGEN keyword CUREXTNT was not

or output operation on the xxxxxxxx file during

specified.

database generation, ADD DBSPACE processing, or

ADD and DELETE DBEXTENT processing.

Explanation: The required CUREXTNT keyword

control statement was not specified as input to the

The Return Code value is the Primary Error Code

database generation process.

value. The EREASON value is the Secondary Error

Code value. For further explanation, look up the

System Action: The program ends.

displayed error codes under either Chapter 21,

Operator Response: Return the console output with

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

the output listing.

ERRORS” in the HELP text.

System Programmer Response: Supply the

System Action: The program ends.

CUREXTNT keyword control statement and rerun the

Operator Response: Return the console output with

program.

the output listing.

System Programmer Response: For corrective action,

ARI0904E Value specified for DBGEN keyword

look up the displayed error codes under either

keyword is invalid.

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

Explanation: The value specified for keyword was

“SEQ FILE ERRORS” in the HELP text.

either null or exceeded eight characters in length.

System Action: The program ends.

ARI0901E End of file on SYSIPT before DBGEN

process complete.

Operator Response: Return the console output with

the output listing.

Explanation: End of file was encountered on SYSIPT

before all required control information was received by

System Programmer Response: Correct the value

the database generation process. Either:

specified for the keyword and rerun the program.

v The CUREXTNT keyword was not specified, or

v The number of DBEXTENT control statements was

ARI0905E Invalid keyword specified.

not the same as specified by the CUREXTNT

Explanation: You did not specify a valid keyword for

keyword control statement, or

database generation or an ADD and DELETE

v There were no DBSPACE control statements.

DBEXTENT function.

System Action: The program ends.

Operator Response: Return the console output with

the output listing.

System Programmer Response: Make the appropriate

System Programmer Response: Correct the

correction and rerun the program.

unrecognizable keyword and rerun the program.

ARI0902E Pool Recovery is in progress, expansion

ARI0906E Value for keyword exceeds maximum of

not allowed.

nnnnnnn.

Explanation: The Data Restore storage pool recovery

Explanation: The value specified for keyword exceeded

process was initiated, but has not yet been completed

the maximum allowed value nnnnnnn.

by starting the database manager with STARTUP=U.

Storage Pool recovery must be completed before

System Action: The program ends.

directory expansion may be done.

Operator Response: Return the console output with

System Action: Directory expansion is cancelled. The

the output listing.

original directory has not been changed.

217

Database Maintenance and I/O Messages - ARI0900-ARI0949

System Programmer Response: Correct the value

ARI0909E DBEXTENT number sequence error.

specified and rerun the program.

Explanation: If database generation is being

performed, one of the following errors occurred:

ARI0907E Incorrect value specified on DBSPACE

v The DBEXTENT control statements were not ordered

definition. Return Code = n.

so that the DBEXTENT numbers were in the required

Explanation: A value specified on a DBSPACE control

sequence. The required sequence is 1, 2, ...

statement was considered incorrect (not a valid type or

CUREXTNT value. The CUREXTNT value is

number). Values of n can be:

specified on the CUREXTNT control statement.

Unrecognized type of DBSPACE specified (not

v The DBEXTENT number on a DBEXTENT control

PUBLIC, PRIVATE, or INTERNAL).

statement was entered incorrectly or was omitted.

v The POOL keyword on the POOL control statement

Unrecognizable number of DBSPACEs

was misspelled. The POOL control statement was

specified on the INTERNAL DBSPACE control

assumed to be a DBEXTENT control statement (and

statement.

the misspelled word was assumed to be the

Unrecognizable number of pages specified for

DBEXTENT number).

a PUBLIC, PRIVATE, or INTERNAL DBSPACE

System Action: The program ends.

statement (nonnumeric value or value less

than 1).

Operator Response: Return the console output with

the output listing.

During database generation, one of the first

two PUBLIC DBSPACEs defined was allocated

System Programmer Response: Ensure that the

to a nonrecoverable storage pool. These are the

DBEXTENT control statements are correctly specified

catalog and package DBSPACEs and cannot be

and are in the proper sequence. Ensure that a POOL

assigned to a nonrecoverable storage pool.

control statement was not misspelled. Rerun the

Nonrecoverable storage pools are defined by

program.

the POOL control statement.

During database generation, the INTERNAL

ARI0910E Incorrect storage pool specified. Return

DBSPACE control statement was not

Code = n.

immediately followed by an END delimiter

Explanation: A specified storage pool number or a

control statement. You may have misspelled

DBEXTENT or DBSPACE control statement was not

the END delimiter control statement.

valid for the reason signified by the value of n:

System Action: The program ends.

A nonnumeric character was encountered.

Operator Response: Return the console output with

A value less than one or greater than

the output listing.

MAXPOOLS was specified.

System Programmer Response: Make the appropriate

A DBSPACE control statement specified a

change to the DBSPACE control statement and rerun

storage pool number for which no

the program.

DBEXTENTs were assigned.

System Action: The program ends.

ARI0908E Insufficient DBEXTENT information.

Operator Response: Return the console output with

Explanation: An END delimiter control statement was

the output listing.

encountered before the number of DBEXTENT control

statements specified by the CUREXTNT keyword were

System Programmer Response: Correct the value in

processed.

error and rerun the program.

System Action: The program ends.

ARI0911E Maximum number of DBSPACES

Operator Response: Return the console output with

exceeded.

the output listing.

Explanation: The number of DBSPACEs being defined

System Programmer Response: Ensure that the

exceeded the value specified by the MAXDBSPC

number of DBEXTENT control statements is the same

keyword.

as was specified by the CUREXTNT keyword and

rerun the program.

System Action: The program ends.

Operator Response: Return the console output with

the output listing.

System Programmer Response: Increase the value

specified on the MAXDBSPC keyword or reduce the

218

Messages and Codes

Database Maintenance and I/O Messages - ARI0900-ARI0949

number of DBSPACE control statements and rerun the

occurring after this message are in the catalog update

program.

phase of the ADD DBSPACE function.

System Action: The process continues with the catalog

ARI0912E Insufficient space in the application

update.

server directory.

Explanation: There is not enough space in the

ARI0916E Number of internal DBSPACES is zero,

application server directory to map the number of

or number of pages specified is zero.

DBSPACEs defined. You can use the output of the

Explanation: One of the following conditions

SHOW DBCONFIG operator command to estimate the

occurred:

amount of directory space available for adding

DBSPACEs.

v No INTERNAL DBSPACE control statement was

supplied

System Action: The program ends.

v The number of INTERNAL DBSPACEs on the

Operator Response: Return the console output with

INTERNAL DBSPACE control statement was

the output listing.

specified as zero during database generation or the

ADD DBSPACE process.

System Programmer Response: Reduce either the

v The number of pages specified on the INTERNAL

number or the size of the DBSPACEs being defined and

DBSPACE control statement was zero.

rerun the program, or use the expand directory

function to increase the size of the page map table to

allow more DBSPACE pages to be added.

In any case, a cancel request is issued and the database

changes are not made.

ARI0913E Maximum number of pages exceeded.

System Action: Processing is terminated.

Explanation: When formatting the DBEXTENTs the

Operator Response: Return the console output with

available space defined across all DBEXTENTs

the output listing.

exceeded the maximum number of pages.

System Programmer Response: Rerun the program,

System Action: The program ends.

specifying the INTERNAL DBSPACE control statement

(with more than zero DBSPACEs) and a correct number

Operator Response: Return the console output with

of pages.

the output listing.

System Programmer Response: Reduce the space

ARI0917E Maximum number of DBEXTENTS

defined across all DBEXTENTs and rerun the program,

exceeded.

or use the expand directory function to increase the

size of the allocation bitmaps and page map table to

Explanation: You attempted to add more DBEXTENTs

allow more DBEXTENT and DBSPACE pages to be

than the maximum number specified at database

added.

generation time (by the MAXEXTNTS keyword).

Note that the SHOW DBCONFIG operator command

ARI0914E System checkpoint failed.

displays the MAXEXTNTS value (MAXIMUM

DBEXTENTS=). The MAXEXTNTS database generation

Explanation: System checkpoint failed while

control statement defines the maximum number of

attempting to add DBSPACEs to database. This may be

DBEXTENTs that can be added to the database. The

due to a cancelled database or LOG ARCHIVE or an

SHOW DBCONFIG operator commands displays this

error found in the directory.

value.

System Action: The program ends.

Operator Response: Return the console output with

the output listing.

System Programmer Response: Perform problem

System Programmer Response: If more DBEXTENTS

determination. Make a record of what went wrong and

are required than are allowed by the MAXEXTNTS

contact the designated support group for your

value, you will need to do another database generation

installation.

and specify a larger value for MAXEXTNTS.

ARI0915I

One or more DBSPACES added to

ARI0918I

No input to ADD/DELETE DBEXTENT.

database.

Explanation: You invoked the ADD or DELETE

Explanation: The DBSPACEs specified in the SYSIPT

DBEXTENT function, but the input file did not supply

file have been added to the database by the Database

any ADD or DELETE control statements. POOL or

Storage System (DBSS) component. Any errors

Chapter 14. ARI0900-ARI0949 Database Maintenance and Database I/O Messages

219

Database Maintenance and I/O Messages - ARI0900-ARI0949

ARCHIVE control statements might not be in the input

Operator Response: If COLDLOG (log reformatting) is

file.

to be performed, reply COLDLOG.

System Action: The program ends normally.

If you do not want to perform COLDLOG (log

reformatting), reply CANCEL to end the application

Operator Response: Return the console output with

server.

the output listing.

System Programmer Response: Inform the operator of

System Programmer Response: Provide the desired

your intentions when running COLDLOG.

respective ADD and DELETE control statements (and

optionally, POOL and ARCHIVE control statements) in

the input file, and rerun the program.

ARI0921I

No input to add DBSPACE.

Explanation: The ADD DBSPACE function was

ARI0919D Database generation invoked. The

invoked, but no control information was provided in

database will be formatted and the

the SYSIPT file.

original database destroyed. Enter

System Action: The program ends normally.

either: DBGEN to continue, or CANCEL

to cancel.

Operator Response: Return the console output with

the output listing.

Explanation: The application server was started with

the STARTUP=C. This invokes the database generation

System Programmer Response: If the intent was to

process, which will format the directory, DBEXTENTs,

add DBSPACEs, provide the necessary control

and logs of the database.

information in the SYSIPT file and rerun the program.

System Action: The system waits for the operator’s

reply.

ARI0922I

DBEXTENT(s) have been added to or

deleted from the database.

If the reply is DBGEN, the database generation process

continues.

Explanation: Adding or deleting DBEXTENTs to or

from the database has been completed successfully.

If the reply is CANCEL, the application server is ended

without modification to the database.

System Action: The program continues.

Any other reply causes the message to be reissued.

ARI0923E Space allocation for filename is less than

Operator Response: If database generation is to be

minimum.

performed, reply DBGEN.

Explanation: The space allocated for the DBEXTENT

If you do not want database generation to be

or log identified by filename is less than the minimum

performed, reply CANCEL.

allowed by DB2 Server for VSE storage management.

System Programmer Response: Inform the operator of

System Action: The program ends.

your intentions when running database generation.

Operator Response: Return the console output with

the output listing.

ARI0920D Cold-log function invoked. Logs will be

formatted and existing log data

System Programmer Response: Increase the space

destroyed.

allocation for the DBEXTENT or log identified by file

name and rerun the program. For the minimum space

Enter either: COLDLOG to continue,

allocation for the device type on which this DBEXTENT

or CANCEL to cancel.

or log is defined, refer to the DB2 Server for VSE System

Administration manual.

Explanation: The application server was started with

STARTUP=L. This invokes the COLDLOG function,

which will format the database logs.

ARI0924I

It is recommended that a database

archive be taken.

System Action: The system waits for the operator’s

reply.

Explanation: The directory expansion process

completed successfully. It is strongly recommended that

If the reply is COLDLOG, the DB2 Server for VSE logs

a database archive be taken immediately. Any updates

are reformatted to indicate no prior logging activity

made to the database after the directory expansion may

and initialization continues. (Any logging of database

not be applied correctly during a restore if a database

updates is lost.)

archive taken before the directory expansion is used as

If the reply is CANCEL, the application server is ended

the starting point of the restore set.

without modification to the logs.

System Action: Processing ends.

Any other reply causes this message to be reissued.

220

Messages and Codes

Database Maintenance and I/O Messages - ARI0900-ARI0949

which storage pools currently have DBSPACEs

ARI0929E Incorrect pool number {BLANK|value}

assigned to them.

on POOL statement.

Explanation: During database generation or the ADD

Note: You can specify an empty storage pool and then

DBEXTENT function, a POOL control statement with

follow the POOL control statement with a

an incorrect storage pool number was encountered. The

DBEXTENT control statement that assigns a

incorrect storage pool number is identified by BLANK

DBEXTENT to the storage pool.

or value in the message text. The storage pool number

System Action: The program ends.

was incorrect for one of the following reasons:

v It was omitted (BLANK in the message text).

Operator Response: Return the console output with

the output listing.

v It was not numeric.

v Its value was less than 2 (storage pool 1 cannot be

System Programmer Response: Supply the correct

specified, and numbers less than 1 are not valid

POOL control statement information and rerun the

storage pool numbers).

program.

v It was greater than the maximum number of storage

pools defined for the database (by the database

ARI0932E Number of DBEXTENTS exceeds

generation MAXPOOLS control statement). The

CUREXTNT value value.

SHOW DBCONFIG operator command will tell you

Explanation: During database generation one of the

how many storage pools are defined in an existing

following errors occurred:

database.

v The number of DBEXTENT control statements

System Action: The program ends.

exceeded the value (value in the message text)

Operator Response: Return the console output with

specified in the CUREXTNT control statement. The

the output listing.

CUREXTNT value specifies exactly how many

DBEXTENTs you must define during database

System Programmer Response: Supply the correct

generation.

POOL control statement information and rerun the

v The END delimiter control statement, which must

program.

follow the last DBEXTENT control statement (and

precede the DBSPACE control statements), was

ARI0930E Incorrect keyword keyword on POOL

omitted.

statement.

System Action: The program ends.

Explanation: During database generation or ADD

Operator Response: Return the console output with

DBEXTENT processing, an error was detected. The

the output listing.

second operand (keyword in message text) of the POOL

control statement was incorrectly specified. The second

System Programmer Response: Verify that the

operand of the POOL control statement can be either

CUREXTNT control statement was specified with the

LOG or NOLOG (or can be omitted).

correct value. Ensure that the correct number of

DBEXTENT control statements are specified and that

System Action: The program ends.

they are followed by an END delimiter control

Operator Response: Return the console output with

statement. Correct the error and rerun the program.

the output listing.

System Programmer Response: Supply the correct

ARI0933E DBEXTENT number extno specified as

POOL control statement information and rerun the

input to action. DBEXTENT is invalid.

program.

Reason Code = n.

Explanation: You have specified an invalid

ARI0931E Pool number n is not an empty storage

DBEXTENT number extno to add or delete. The type of

pool.

action is signified by action. The reason is signified by

the value n. For ADD DBEXTENT, n is one of the

Explanation: During ADD DBEXTENT processing, a

following:

POOL control statement specified a storage pool

number (n in message text) that already has either one

1. You did not enter a value.

or more DBEXTENTs, or one or more DBSPACEs

2. The value encountered a nonnumeric character.

assigned to it. You can specify only a storage pool that

3. You entered a value less than one.

does not yet have any DBEXTENTs or DBSPACEs

4. You did not enter a value that is exactly one greater

assigned to it. The SHOW DBEXTENT, or SHOW

than the number of DBEXTENTs currently defined

POOL operator command will tell you which storage

nor one of the previously deleted DBEXTENT

pools currently have DBEXTENTs assigned to them.

numbers.

Query the SYSDBSPACES catalog table to determine

Chapter 14. ARI0900-ARI0949 Database Maintenance and Database I/O Messages

221

Database Maintenance and I/O Messages - ARI0900-ARI0949

5. The deleted area is not large enough to hold the

does not have enough space, add DBEXTENTS to the

new DBEXTENT. Use the SHOW POOL command

same pool before invoking the deletion. (Ensure you

to determine the size of the deleted area.

have not exceeded the SOSLEVEL and there is enough

space in the storage pool. You may have to increase the

6. The free area at the end of the DBEXTENT control

SOSLEVEL to 95%.) For other errors, follow your

area in the directory is not large enough to hold the

installation’s problem determination procedure.

new DBEXTENT. Use the SHOW POOL command

to determine the size of this free area.

ARI0935E Archopt failed. Correct the cause of

For DELETE DBEXTENT, n is one of the following:

error. Do a normal SQLSTART to do the

1. You did not enter a value.

archive (or user archive).

2. The database manager encountered a nonnumeric

Explanation: Processing failed during the archive.

character.

Archopt is the type of archive the program is taking.

3. You entered a value less than one.

System Action: The program ends. All the

4. You entered a value that is greater that the

DBEXTENTs specified have been added or deleted

maximum number of DBEXTENTs allowed in the

successfully.

database.

System Programmer Response: Determine and correct

5. The DBEXTENT is in the database but not in the

the cause of the error. Do a normal SQLSTART of the

storage pool that you specified. Use the SHOW

application server and take the archive (or user

POOL command to determine the pool number or

archive).

use the default value by not inputting the pool

number.

ARI0936I

Warning: DBEXTENT number extno is

System Action: The program ends.

already in place. Program continues.

System Programmer Response: Rerun the program

Explanation: The DBEXTENT number extno that you

with the correct values.

wanted to add is already in the database.

System Action: The program continues.

ARI0934E Error occurred while deleting

DBEXTENT number extno. Reason Code

System Programmer Response: Ensure that the

= n.

DBEXTENT number is correct. If the DBEXTENT was

added in a previous run, no action is required. If you

Explanation: The ADD/DELETE DBEXTENT

want to move the DBEXTENT from one storage pool to

processing encountered an error. It occurred while the

another, delete the DBEXTENT in a separate run and

function was deleting DBEXTENT number extno. The

rerun the program.

function has added or deleted all DBEXTENT numbers

in the input file prior to extno. The function will not

process any DBEXTENT numbers in the input file after

ARI0937I

Warning: DBEXTENT number extno that

extno. The value of n signifies the error.

you want to delete is not found.

Program continues.

1. The storage pool has insufficient space to relocate

occupied pages in the DBEXTENT to be deleted.

Explanation: The DBEXTENT to be deleted was not

The function must copy all the occupied pages in

found in the database. A previous run of a program

the DBEXTENT to another location before deleting

may have deleted it.

the DBEXTENT. The storage pool does not have

enough space to accommodate them. (Ensure you

System Action: The program continues.

have not exceeded the SOSLEVEL and there is

System Programmer Response: Ensure that the

enough space in the storage pool.) Use the operator

DBEXTENT number is correct. If the DBEXTENT was

command SHOW POOL to determine the number

deleted in a previous run, no action is required.

of allocated pages on the DBEXTENT to be deleted.

Otherwise, rerun the program with the correct values.

2. The error occurred while the function was reading

the allocated pages.

ARI0938E You have specified DBEXTENT number

3. The error occurred while the function was locating

extno for deletion more than once.

a new page for relocation. This might be an I/O

Processing terminates.

error if the database manager was accessing the

directory blocks.

Explanation: You cannot delete a DBEXTENT more

than once in a single execution of the ADD or DELETE

System Action: The program ends. The DBEXTENT

DBEXTENT function, even though the DBEXTENT may

extno is not changed.

have been added back to the database in the interim.

System Programmer Response: Determine the cause

System Action: Processing ends.

of the error from the reason code. If the storage pool

222

Messages and Codes

Database Maintenance and I/O Messages - ARI0900-ARI0949

System Programmer Response: Rerun the program

System Action: The program ends.

with proper input.

System Programmer Response: Correct the error and

rerun the program.

ARI0939E Storage pool poolno contains the

INTERNAL DBSPACE and the

ARI0943I

Directory expansion was completed

DBEXTENT extno specified to be

successfully.

deleted is the only DBEXTENT in this

pool. DBEXTENT extno cannot be

Explanation: The directory has been expanded

deleted. Processing terminates.

successfully.

Explanation: Storage pool poolno contains the

System Action: The program ends.

INTERNAL DBSPACE, and the DBEXTENT extno that

you specified for deletion is the only DBEXTENT left in

ARI0945I

Expanded space will be used for

this pool. You cannot delete DBEXTENT extno.

DBSPACE pages.

System Action: Processing ends.

Explanation: You have requested to expand the

System Programmer Response: Move the INTERNAL

directory and to use the additional space to hold more

DBSPACE to another pool using the ADD DBSPACE

DBSPACE pages.

function or add more DBEXTENTs to the storage pool

System Action: Processing continues.

before you delete the DBEXTENT.

ARI0946I

Expanded space will be used for

ARI0940I

Additional 512-byte directory blocks

DBSPACE and DBEXTENT pages.

required: nnnnnnnnnn

Explanation: EXPAND = ALL was supplied in the

Explanation: The directory has been expanded

parameter list. The directory expansion process will

previously to allow more DBSPACE pages to be added.

expand the directory to allow more DBEXTENT and

To expand the directory again to allow both DBSPACE

DBSPACE pages to be added.

and DBEXTENT pages to be added, the new directory

must be large enough to hold both the previously

System Action: Processing continues.

expanded DBSPACE pages as well as the DBEXTENT

pages to be added. The new directory is not large

ARI0947I

Current|New maximum

enough. The message displays the additional number

DBEXTENT|DBSPACE pages:

of directory blocks that are required to expand the

nnnnnnnnnn

directory.

System Action: Processing ends.

Explanation: This message shows the (Current|New)

maximum number of (DBEXTENT|DBSPACE) pages

System Programmer Response: This message

that the directory can hold.

indicates how much additional space is required.

System Action: Processing continues.

Specify a larger VSAM Extent and re-run the job. Refer

to the DB2 Server for VSE System Administration manual

to determine the size of the new minidisk.

ARI0948I

DBEXTENT|DBSPACE pages added:

nnnnnnnnnn

ARI0941E Dataset for new directory is too small.

Explanation: This message shows the number of

additional (DBEXTENT|DBSPACE) pages that will be

Explanation: The output dataset must be at least as

available in the new directory.

large as the input dataset to hold the directory.

System Action: Processing continues.

System Action: The program ends.

System Programmer Response: Specify another

ARI0949I

(Current|New) directory size (blocks):

dataset of a larger size if one exists; otherwise, define

nnnnnnnnnn

one. Rerun the program.

Explanation: This message shows the size of the

(Current|New) directory in 512-byte pages.

ARI0942E Directory expansion failed.

System Action: Processing continues.

Explanation: An error occurred during the processing

of the directory expansion. The directory is not copied.

If this message is preceded by a VSAM ERROR display,

refer to the DB2 Server for VSE & VM Diagnosis Guide

and Reference manual for information on errors from

VSAM.

Chapter 14. ARI0900-ARI0949 Database Maintenance and Database I/O Messages

223

Chapter 15. ARI0950-ARI0974

Trace Formatter Messages

Explanation: The maximum number of parameters

ARI0950E INPUT keyword keyword is not valid.

used with the control statement keyword TRACENO is

Explanation: The submitted control statement

six.

keyword is unrecognized. The recognized trace

System Action: The program ends.

formatter control statement keywords are: AGENTNO,

COMP, DATE, DISK, DUMPALL, HEADER, RETCODE,

Programmer response: Reduce the number of

SUBCOMP, TIME, TRACENO, and USERID.

parameters to six or less. For more information about

TRACENO parameters, refer to the DB2 Server for VSE

System Action: The program ends.

& VM Operation manual.

Programmer response: Select the correct control

statement keyword. Each control statement can contain

ARI0955E Nondigit character in one of the

only one keyword.

TRACENO parameters.

Explanation: Syntax error. At least one of the

ARI0951E Number of parameters in user ID

parameters used with the control statement keyword

exceeds six.

TRACENO contains nonnumeric characters.

Explanation: The maximum number of parameters

System Action: The program ends.

used with the control statement keyword USER ID is

six.

Programmer response: Submit the parameters with

the correct syntax. For more information about

System Action: The program ends.

TRACENO parameters, refer to the DB2 Server for VSE

Programmer response: Reduce the number of

& VM Operation manual.

parameters to six or less. For more information about

USER ID parameters, refer to the DB2 Server for VSE &

ARI0956E Number of parameters in COMP

VM Operation manual.

exceeds one.

Explanation: The maximum number of parameters

ARI0952E Number of parameters in AGENTNO

used with the control statement keyword COMP is one.

exceeds six.

System Action: The program ends.

Explanation: The maximum number of parameters

used with the control statement keyword AGENTNO is

Programmer response: Enter only one of the allowed

six.

parameters: CONV, DBSS, DRRM DSC, RA, RDS,

WUM, or STG.

System Action: The program ends.

Programmer response: Reduce the number of

ARI0957E Parameter in COMP not valid.

parameters to six or less. For more information about

AGENTNO parameters, refer to the DB2 Server for VSE

Explanation: The parameter specified with the control

& VM Operation manual.

statement keyword COMP can be CONV, DBSS, DRRM

DSC, RA, RDS, WUM, or STG.

ARI0953E Nondigit character in one of the

System Action: The program ends.

AGENTNO parameters.

Programmer response: Submit the correct parameter:

Explanation: Syntax error. At least one of the

CONV, DBSS, DRRM, DSC, RA, RDS, WUM, or STG.

parameters used with the control statement keyword

AGENTNO contains nonnumeric characters.

ARI0958E Number of parameters in SUBCOMP

System Action: The program ends.

exceeds eight.

Programmer response: Submit the parameters with

Explanation: The maximum number of parameters

the correct syntax. For more information about

used with the control statement keyword SUBCOMP is

AGENTNO parameters, refer to the DB2 Server for VSE

eight.

& VM Operation manual.

System Action: The program ends.

Programmer response: Reduce the number of

ARI0954E Number of parameters in TRACENO

parameters to eight or less. For more information about

exceeds six.

225

Trace Formatter Messages - ARI0950-ARI0974

SUBCOMP parameters, refer to the DB2 Server for VSE

second date, if used, must be greater than the first date.

& VM Operation manual.

An example of correctly specified dates is: DATE

01/23/85 02/08/85.

ARI0959E Parameter in SUBCOMP not valid.

System Action: The program ends.

Explanation: At least one of the parameters used with

Programmer response: Submit the parameters with

the control statement keyword SUBCOMP is not valid.

the correct syntax.

The allowable parameters for the subcomponents DBSS,

DRRM, DSC, RA and RDS are:

ARI0963E Number of parameters in TIME exceeds

For RDS:

For DBSS:

For DSC:

For RA:

two.

AGENT

Explanation: The maximum number of parameters

COM

used with the control statement keyword TIME is two.

EXEC

ENTRY

INT

EXIT

System Action: The program ends.

OPT

INDEX

For DRRM:

Programmer response: Input the two parameters

LOCK

‘start-time’ and ‘end-time’ or the parameter

LOG

DICT

‘target-time’.

LUW

GEN

SORT

PARSE

STAT

RDIIN

ARI0964E Syntax error in one of the TIME

STOR

parameters.

System Action: The program ends.

Explanation: Syntax error. Each portion of the time

Programmer response: Submit the correct parameters.

must be specified as two digits; that is, a leading zero

For more information about SUBCOMP parameters,

must be entered where needed. The delimiter must be a

refer to the DB2 Server for VSE & VM Operation manual.

colon (:).

Note: The second time specified should be greater than

ARI0960E Number of parameters in DATE exceeds

the first time. For example, specifying TIME 23:45:00

two.

00:10:00 will cause no trace output to be selected (no

warning message will be issued). Consequently,

Explanation: The maximum number of parameters

specifying an interval that passes through midnight

used with the control statement keyword DATE is two.

must be done in two different runs of the trace

System Action: The program ends.

formatter. An example of correctly specified times is:

TIME 09:05:00 14:04:59. It is possible (but not very

Programmer response: Input the two parameters

useful) to specify only one time with the TIME

‘start-date’ and ‘end-date’ or the parameter

keyword. For example, TIME 12:00:00 specifies that

‘target-date’.

only the trace records created during that second of

time be formatted.

ARI0961E Syntax error in one of the DATE

System Action: The program ends.

parameters.

Programmer response: Submit the parameters with

Explanation: Syntax error. Each portion of the date

the correct syntax.

must be specified as two digits; that is, a leading zero

must be entered where needed. The delimiter must be

/. The second date, if used, must be greater than the

ARI0965E Nondigit character in one of the TIME

first date. An example of correctly specified dates is:

parameters.

DATE 01/23/85 02/08/85.

Explanation: Syntax error. At least one of the

System Action: The program ends.

parameters used with the control statement keyword

TIME contains nonnumeric characters. Each portion of

Programmer response: Submit the parameters with

the date must be specified as two digits; that is, a

the correct format.

leading zero must be entered where needed. The

delimiter must be ‘:’.

ARI0962E Nondigit character in one of the DATE

Note: The second time specified should be greater than

parameters.

the first time. For example, specifying TIME 23:45:00

Explanation: Syntax error. At least one of the

00:10:00 will cause no trace output to be selected (no

parameters used with the control statement keyword

warning message will be issued). Consequently,

DATE contains nonnumeric characters. Each portion of

specifying an interval that passes through midnight

the date must be specified as two digits; that is, a

must be done in two different runs of the trace

leading zero must be entered where needed. The

formatter. An example of correctly specified times is:

226

Messages and Codes

Trace Formatter Messages - ARI0950-ARI0974

TIME 09:05:00 14:04:59. It is possible (but not very

the trace formatter program.

useful) to specify only one time with the TIME

keyword. For example, TIME 12:00:00 specifies that

ARI0972E Storage allocation error. Return Code =

only the trace records created during that second of

nn.

time be formatted.

Explanation: In allocating virtual storage during trace

System Action: The program ends.

formatting, a VSE GETVIS macro failure occurred. The

Programmer response: Submit the parameters with

cause of the error is described by the Return Code

the correct syntax.

value nn (which is the return code from GETVIS).

System Action: The program ends.

ARI0966E Number of parameters in RETCODE

Programmer response: Report the problem to your

exceeds one.

system programmer.

Explanation: The maximum number of parameters

System Programmer Response:

used with the control statement keyword RETCODE is

one.

v Return Code = 12:

v Return Code = 32: This is a hardware storage failure.

System Action: The program ends.

Report the problem to your hardware service

Programmer response: Enter only one of the allowed

representative.

parameters (P, N, or *).

v For any other Return Code value: Make a record of

what went wrong and contact the designated

support group for your installation.

ARI0967E Parameter in RETCODE not valid.

Explanation: The submitted parameter used with the

ARI0973E Error releasing storage. Return Code =

control statement keyword RETCODE is not valid. The

nn.

parameter must be P, N, or *.

Explanation: In releasing virtual storage during trace

System Action: The program ends.

formatting, a CMS free storage macro failure occurred.

Programmer response: Enter one of the following as

The cause of the error is described by the Return Code

the RETCODE parameter:

value nn (which is the return code from the free storage

macro).

Positive (nonzero) return codes only

System Action: The program ends.

Negative return codes only

Operator Response: Report the problem to your

All nonzero return codes

system programmer.

System Programmer Response: Make a record of the

ARI0968E The trace file does not contain trace

return code and contact the designed support group for

data.

your installation.

Explanation: The mounted tape or disk file does not

contain the DB2 Server for VSE trace data. (The wrong

ARI0974E operation error on DDNAME xxxxxxxx.

tape may be mounted.)

Return Code = nn. EREASON=nn.

System Action: The program ends.

Explanation: An error occurred during a sequential

Programmer response: Ensure that the operator

input/output operation on the xxxxxxxx file.

mounted the correct tape and that the correct JCL was

The Return Code value is the Primary Error Code

submitted for the trace file. If the correct file is being

value. The EREASON value is the Secondary Error

accessed, it does not contain the trace data. (The tape is

Code value. For further explanation, look up the

probably empty or rewritten.)

displayed error codes under either Chapter 21,

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

ARI0969I

Trace file is empty.

ERRORS” in the HELP text.

Explanation: The DB2 Server for VSE trace formatter

System Action: The program ends.

program has detected that the DB2 Server for VSE trace

Operator Response: Return console output with the

file is empty. (It contains no records.) When database

output listing.

manager activity was being traced, no trace output data

was created.

System Programmer Response: For corrective action,

look up the displayed error codes under either

System Action: The program ends.

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

Programmer response: None required. You may want

“SEQ FILE ERRORS” in the HELP text.

to verify that the correct file was submitted as input to

Chapter 15. ARI0950-ARI0974 Trace Formatter Messages

227

Chapter 16. CICS/VSE Transaction Abend Codes

Notify your system programmer whenever one of

WHENEVER WARNING STOP,

these abend conditions occurs:

and because the resource adapter

detected either a positive

Code

Meaning

SQLCODE (not 100) or found the

ABE

The CISQ transaction abended

SQLWARN0 flag set to W.

during cleanup and termination

ASGN

An error has occurred on the

following a previous abend.

EXEC CICS ASSIGN command,

ADDR

An error has occurred on the

which is executed by the ISQL

EXEC CICS ADDRESS command,

transaction to get the terminal

which is executed by the ISQL

type, terminal screen dimensions,

transaction to get the addresses of

and CICS start code.

the TWA and the CSA.

ASP7

CICS or some subsystem failed

AEY9

An online application is trying to

during the CICS synchronization

access the database manager and

process.

the online resource adapter was

If the failing subsystem was the

not enabled or is terminating.

DB2 Server for VSE system, the

CICS has not been initialized

DB2 Server for VSE partition has

correctly. The DFHSIT must

a serious problem (such as log

contain the DBP parameter. In

full, media error, etc.); this

addition you must specify

problem must be corrected. The

DTB=YES on the DFHCSDUP

problem should be corrected in

entries for all transactions that

the database manager before

access the database manager.

trying online access.

For information about the CIRB

ASRA

A program check has occurred

and CIRT transactions, refer to the

while running under a user TCA.

DB2 Server for VSE System

The transaction that was

Administration manual.

attempting to access the

application server will be

AEIZ

The ISQL transaction has

abended.

attempted to write to temporary

storage and has exceeded the

ASRB

An ISQL print command has been

current CICS limitation for the

issued, but when CICS was

number of items allowed in a

started, logical unit SYS098 was

temporary storage queue.

not assigned to a VSE/Power

intercepted printer.

ARIE

The transaction was abended

because it coded EXEC SQL

ATSP

Temporary storage queues have

WHENEVER ERROR STOP, and

been defined as recoverable.

because the resource adapter

Recoverable temporary storage

detected a negative SQLCODE.

queues are incompatible with

ISQL.

ARIS

A serious error occurred in the

DB2 Server for VSE partition.

CICE

CICDAREA eyecatcher is missing

Normally, no further access to the

for the ISQL task common area.

database manager is possible. The

This is probably due to storage

problem in the database manager

overlay.

should be corrected before

ERR1

The ISQL transaction abended

continuing.

before a message could be sent to

ARIW

The transaction was abended

the terminal.

because it coded EXEC SQL

GCBE

Global control block eyecatcher is

229

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