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

DB2 Server for VSE System Control - ARI0001-ARI0199

System Programmer Response: Refer to the IBM

v An invalid keyword-option combination was found.

VSE/ESA System Macros Reference manual for an

For example, TIME or DATE was specified in a

explanation of the error code displayed.

BYPASS UNDO WORK command, or ALL was

specified in a ROLLBACK COMMITTED WORK

command.

ARI0113I

{LUWID luwid-value | DBSPACE

dbspace-number | USERID userid} has

already been specified.

string1 is:

Explanation: The specified LUWID, DBSPACE, or

KEYWORD One of the following keywords was

USERID was entered in a previous command of the

expected: BYPASS, ROLLBACK,

same type (duplicate command) in the EXTEND input

DISABLE, or ENABLE.

file.

OPTION

One of the following options was

System Action: The duplicate specification is ignored.

expected: ALL, LUWID, TIME, DATE,

Processing continues.

DBSPACE, or USERID.

VALUE

One of the following values was

ARI0114E keyword was specified more than once in

expected: LUWID value, TIME value,

the same statement.

DATE value, DBSPACE value, or

USERID value.

Explanation: A single EXTEND input file command

specified a control keyword more than once.

reserved word One of the following reserved words

was expected: WHERE, UNDO,

keyword is a control keyword—ALL, TO, DBSPACE,

WORK, COMMITTED, DBSPACE.

USERID, or LUWID.

System Action: EXTEND input file parsing completes.

If string1 was either VALUE, UNDO, WORK,

The database manager ends.

COMMITTED, or DBSPACE, string2 may be END OF

RECORD because an incomplete command was

Operator Response: Refer this message to your

entered. If string1 is either OPTION or WHERE, string2

system programmer.

may be END OF FILE because an incomplete command

was entered.

System Programmer Response: Remove duplicate

keywords in the EXTEND input file command, then

System Action: EXTEND input file parsing completes.

restart extended database initialization.

The database manager ends.

Operator Response: Refer this message to your

ARI0115E Unexpected string string was found.

system programmer.

Explanation: A line of an EXTEND input file

System Programmer Response: Correct the EXTEND

command contains unrecognizable keywords, more

input file. Restart extended database initialization.

than one control keyword, or extra input on a record.

string is an unrecognizable string, a keyword, or a

ARI0117E Range error: number is greater than the

control keyword found while parsing an EXTEND

maximum number of possible condition

input file command.

(max).

System Action: EXTEND input file parsing completes.

Explanation: While parsing EXTEND input file

The database manager ends.

commands, one of two conditions existed. condition

identifies the condition.

Operator Response: Refer this message to your

system programmer.

v condition is LUWIDS. The total number of logical

units of work included in the EXTEND input file (a

System Programmer Response: Correct the EXTEND

composite of all commands) exceeded the maximum.

input file command. Restart extended database

Since BYPASS UNDO WORK affects log recovery,

initialization.

only 252 logical units of work are allowed.

number is the number of logical units of work

ARI0116E string1 was expected but string2 was

included in the EXTEND input file.

found.

max is 252, the maximum number of active logical

Explanation: While parsing EXTEND input file

units of work permitted at any one time.

commands, one of the following caused an error:

v condition is DBSPACES. The number of DBSPACEs

v An unexpected string was found where a keyword,

exceeded the maximum number of PUBLIC and

option, or reserved word should have been found.

PRIVATE DBSPACEs in the database.

v An end of record was expected and a string was

number is the number of a DBSPACE.

found.

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

max is the number of PUBLIC and PRIVATE

System Programmer Response: Take note of the

DBSPACEs defined in the database.

message.

System Action: EXTEND input file parsing completes.

The database manager ends.

ARI0121I

DBSPACE nnn is disabled.

Operator Response: Refer this message to your

Explanation: This message is issued for each disabled

system programmer.

DBSPACE in the database. DBSPACEs are disabled by

the DISABLE DBSPACE command.

System Programmer Response: Correct the EXTEND

input file. Restart extended database initialization.

System Action: Processing continues.

System Programmer Response: You may wish to take

ARI0118E

{LUWID luwid-value | DBSPACE

note of which DBSPACEs are disabled.

dbspace-number | USERID userid}

contains invalid {HEX CHARACTERS |

ARI0122E The time time-string and date date-string

NUMBERS | ALPHANUMERICS} or is

specified are later than the current time.

too long.

Explanation: The starting date and time specified (or

Explanation: While parsing EXTEND input file

defaulted to) in the ROLLBACK COMMITTED WORK

commands, one of the following conditions occurred:

command are later than the current date and time.

v A logical unit of work (luwid-value is the logical unit

There can be nothing in the database log with such a

of work identifier) contains invalid hexadecimal

date and time.

characters.

System Action: EXTEND input file parsing completes.

v A DBSPACE value contains characters other than

The database manager ends.

positive numbers or zero.

v The logical unit of work, DBSPACE, or user ID value

Operator Response: Refer this message to your

was too long.

system programmer.

System Action: EXTEND input file parsing completes.

System Programmer Response: Determine the correct

The database manager ends.

time and date. Correct the EXTEND input file. Restart

extended database initialization.

Operator Response: Refer this message to your

system programmer.

ARI0123E The TO time and date combination is

System Programmer Response: Correct the EXTEND

earlier than the FROM time and date

input file. Restart extended database initialization.

combination.

Explanation: In a ROLLBACK COMMITTED WORK

ARI0119E Cannot {bypass | disable} DBSPACE 1.

command, the TO time and date (taken in combination)

must be greater than the FROM time and date (taken in

Explanation: DBSPACE 1 can be neither disabled nor

combination).

bypassed. The database manager must be able to use

the database catalog located in DBSPACE 1.

System Action: EXTEND input file parsing completes.

The database manager ends.

System Action: EXTEND input file parsing completes.

The database manager ends.

Operator Response: Refer this message to your

system programmer.

Operator Response: Refer this message to your

system programmer.

System Programmer Response: Correct the EXTEND

input file. Restart extended database initialization.

System Programmer Response: Modify the EXTEND

input file so that DBSPACE 1 is not disabled or

bypassed. Restart extended database initialization.

ARI0124E

{OPEN | GET | CLOSE} error input-file

Reason Code = nn. Return Code = cc.

ARI0120I

DBSPACE dbspace-number is already

Explanation: An error occurred in an attempt to

{ENABLED | DISABLED}.

access or close the EXTEND input file. The Reason

Code value is the primary error code; the Return Code

Explanation: A DISABLE or ENABLE DBSPACE

value is the secondary error code. For further

command was specified for a DBSPACE that was

explanation, look up the displayed err Chapter 21,

previously disabled or enabled.

“Sequential File Errors,” on page 361 in this manual or

System Action: Initialization continues. The status of

SEQ FILE ERRORS in the HELP text.

the specified DBSPACE is not changed.

input-file is SYSIPT, is the file with ddname ARIEXTND,

Operator Response: Refer this message to your

the input file associated with the use of the EXTEND

system programmer.

initialization parameter during database initialization.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

System Action: For OPEN or GET errors, the database

COMMITTED WORK command (refer to the

manager ends. For CLOSE errors, processing continues.

DB2 Server for VSE & VM Diagnosis Guide and

Reference manual for information about

Operator Response: For OPEN or GET errors, look up

recovering from DBSS errors).

displayed error codes to take corrective action. For

v If REDO appears in the message, the database

CLOSE errors, no action is required.

manager has failed in the DBSS during the log

System Programmer Response: Same as Operator

recovery phase of warm start or restore from archive

Response.

while trying to “redo” a database update previously

made by the committed logical unit of work

identified in the following display output. The

ARI0125E The extend file is empty.

following display output provides more information

Explanation: The input file, SYSIPT, associated with

about the failing DBSS operation and identifies the

the use of the EXTEND initialization parameter during

database user who requested the operation.

database initialization contains no commands.

Note: This message and its display output will always

System Action: The database manager ends.

appear on the operator console. It will also

Operator Response: Refer this message to your

appear in SYSLST output if the DSPLYDEV

system programmer.

initialization parameter requests (or defaults to)

SYSLST output.

System Programmer Response: You must either

provide the required file commands or restart database

System Action: The database manager ends.

initialization with EXTEND=N.

Operator Response: Save this message and the

subsequent display output and contact your system

ARI0126E DBSS termination during

programmer immediately.

{FORWARD|ROLLBACK|UNDO|

System Programmer Response: Make note of the

REDO} processing.

information given in the message and the following

Explanation:

display output, and refer to the DB2 Server for VSE &

If FORWARD appears in the message, the database

VM Diagnosis Guide and Reference manual for

manager failed in the DBSS while accessing data in

information about recovery procedures for DBSS errors.

the database (DBSPACE data). The database manager

was performing normal database activity for an

ARI0127E The {TIME | DATE} parameter string

application program or a terminal user. The

contains a syntax error.

following display output provides more information

about the failing DBSS operation and identifies the

Explanation: The TIME or DATE parameter specified

database user who requested the operation.

in a ROLLBACK COMMITTED WORK command

contained a syntax error.

If ROLLBACK appears in the message, the database

manager failed in the DBSS while trying to undo a

TIME Must be a total of 8 characters (hh:mm:ss). You

database update previously made by the logical unit

must have two digits each for hour, minutes,

of work identified in the following display output.

and seconds with a delimiter (:) between each.

The database manager is performing log recovery for

Add leading zeros if necessary.

a logical unit of work that failed because the

DATE Must be a total of 8 characters (mm-dd-yy or

application, the terminal user, or the database

dd-mm-yy). The correct format is specified

manager initiated the ROLLBACK WORK process.

when VSE is IPLed. You must have two digits

The following display output provides more

each for month, day, and year with a delimiter

information about the failing DBSS operation and

(-) between each. Add leading zeros if

identifies the database user who requested the

necessary.

operation.

If UNDO appears in the message, the database

string is the incorrect time or date character string.

manager has failed in the DBSS during log recovery

phase of warm start or restore from archive while

System Action: EXTEND input file parsing completes.

trying to undo a database update previously made

The database manager ends.

by the uncommitted logical unit of work identified in

Operator Response: Refer this message to your

the following display output. The following display

system programmer.

output provides more information about the failing

DBSS operation and identifies the database user who

System Programmer Response: Correct the EXTEND

requested the operation.

input file. Restart extended database initialization.

Note: This failure can occur if a committed logical

unit of work is rolled back by the ROLLBACK

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

ARI0128E A nonnumeric or invalid character was

ARI0130I

The parameters specified are a subset of

found in the {TIME | DATE} parameter

those used in a previous statement of

string.

the same type.

Explanation: An invalid character was found in the

Explanation: The parameters ANDed together in a

TIME or DATE parameter specified in a ROLLBACK

BYPASS UNDO WORK or ROLLBACK COMMITTED

COMMITTED WORK command.

WORK command are a subset of parameters specified

in previous commands of the same type. For example,

TIME A non-numeric value for the hour, minutes, or

the following duplicate commands will cause this

seconds was specified. Or, an incorrect

message to be issued:

numeric value was specified. Valid numeric

BYPASS UNDO WORK WHERE

ranges for time are:

USERID SMITH JONES

DBSPACE 2 4 5

hh 00-23

mm 00-59

ss 00-59

DATE A non-numeric value for the month, day, or

year was specified. Or, an incorrect numeric

BYPASS UNDO WORK WHERE

value was specified. Valid numeric ranges for

USERID JONES

date are:

DBSPACE 4

mm 01-12

dd 01-31

yy 00-99

System Action: The duplicate specification is ignored.

Processing continues.

Note: Value for day must be valid for the

month or year specified.

ARI0131E The TO option was found but no

starting time or date was specified.

string is the invalid time or date string.

Explanation: A ROLLBACK COMMITTED WORK

System Action: EXTEND input file parsing completes.

command was entered and the TO option was

The database manager ends.

specified. No starting (from) TIME or DATE was

specified.

Operator Response: Refer this message to your

system programmer.

System Action: EXTEND input file parsing completes.

The database manager ends.

System Programmer Response: Correct the EXTEND

input file. Restart extended database initialization.

Operator Response: Refer this message to your

system programmer.

ARI0129E The combination of the ALL option

System Programmer Response: Correct the EXTEND

with any other option is not valid.

input file. Restart extended database initialization.

Explanation: One of two conditions occurred:

v The ALL option and some other option (LUWID,

ARI0132E DBSPACE dbspace-number has been

USERID, or DBSPACE), were specified in the same

selected for both enabling and

BYPASS UNDO WORK command. No other option

disabling.

can be specified with ALL.

Explanation: The EXTEND input file contained

v More than one BYPASS UNDO WORK command

conflicting commands to enable and disable the same

was specified in the same EXTEND input file and

DBSPACE.

one of these commands specified the ALL option. If

System Action: EXTEND input file parsing completes.

ALL is used, only one BYPASS UNDO WORK

The database manager ends.

command is allowed in the EXTEND input file.

Operator Response: Refer this message to your

System Action: EXTEND input file parsing completes.

system programmer.

The database manager ends.

System Programmer Response: Correct the EXTEND

Operator Response: Refer this message to your

input file. Restart extended database initialization.

system programmer.

System Programmer Response: Correct the BYPASS

ARI0137I

Invalid installation defined date/time

UNDO WORK command. Restart extended database

defaults on name.

initialization.

Explanation: The specified date/time default name

contains an invalid value. During installation, four

date/time values were stored into the

SYSTEM.SYSOPTIONS table. Their names and

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

supported values are as follows:

ARI0140D Enter DRRM function name and

DATE

trace-level pair. Valid function names

The date format. One of the following must be

are *, DICT, GEN, PARSE, RDIIN, and

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

CANCEL. Valid trace-level values are 0,

1, and 2.

TIME

The time format. One of the following must be

Explanation: The TRACE ON command is being

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

processed. The operator responded DRRM to

prompting message ARI0087D. The database manager

LDATELEN

is prompting the operator to specify the functions of

The local date length. It must be 0, or a number

DRRM to be traced and the trace level for each

greater than 9 and less than 255.

function.

LTIMELEN

System Action:

The local time length. It must be 0, or a number

v If * n is entered, where n is one of 0, 1, or 2, all

greater than 7 and less than 255.

DRRM functions will be traced at trace-level n.

System Action: Processing continues with the default

v If any or all of DICT n, GEN n, PARSE n, RDIIN n

datetime values.

are entered, the specified functions of DRRM will be

The default values supplied by the system are:

traced at the specified trace-level n (where n is 1 or

2).

DATE

ISO

v If trace-level 0 is entered for a function it will not be

TIME

ISO

traced (equivalent to not entering the function at all).

v If CANCEL is entered, TRACE command processing

LDATELEN

ends.

LTIMELEN

Note: This message is displayed in all environments. In

Operator Response: Refer this message to your

environments in which the DRRM component is

system programmer.

not active, however, the operator’s response to

System Programmer Response: Update the

this message is ignored.

SYSTEM.SYSOPTIONS table with the correct datetime

Operator Response:

values.

v If all DRRM functions are to be traced, enter * plus 1

or 2 for the trace level that you want (with a blank

ARI0138E Application Identifier SYSARI0x for the

between * and number). For example, enter

application server dbname has already

1 PARSE 2 to trace all DRRM functions except

been used by another database.

PARSE at level 1 and traces PARSE at level 2.

Explanation: Another application server has been

v If only selected DRRM functions are to be traced,

identified to XPCC with the same APPLID. Either there

enter first a function name followed by its trace-level

was an attempt to start the same application server in

value, and then a second function name, if you want

more than one partition, or the DBNAME Directory has

one, with its trace-level value. One or more blanks

more than one DBNAME mapping to the same

must be keyed between each function name and each

APPLID.

trace-level value entered. If you enter a function

name more than once, only the last entry is effective.

System Action: Initialization of the database manager

If you want to terminate the TRACE command, enter

ends. The application server is not operational.

CANCEL.

Operator Response: Ensure that the database name is

correct, and that an application server with the same

ARI0141D Enter WUM trace-level or CANCEL.

name has not been started in another partition. If the

Valid trace-level values are 0, 1, and 2.

server name is correct, refer the problem to the system

programmer.

Explanation: The TRACE ON command is being

processed. The operator has responded WUM to

System Programmer Response: Make sure that the

prompting message ARI0087D. The database manager

DBNAME Directory entries are correct. An APPLID

is prompting the operator to specify the desired trace

mapped onto by more than one DBNAME can result in

level for WUM.

this error. Also check the VSE IPL procedure to make

sure that an XPCC SET command has not been issued

System Action:

for the same APPLID, as for VSE

Guest Sharing.

v If n is entered, where n is 1 or 2, the WUM

component will be traced at trace-level n.

v If CANCEL is entered, TRACE command processing

ends.

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

Notes:

ARI0143I

The application server has been

1. This message is displayed in all environments. In

initialized with the following values:

environments where the WUM component is

CHARNAME = option1, DBCS = option2,

inactive, however, the operator’s response to this

CHARSUB = option3, CCSIDSBCS =

message is not used.

option4, CCSIDMIXED = option5, and

2. If trace level 0 is added for this component, it

CCSIDGRAPHIC = option6.

will not be traced (equivalent to not entering the

Explanation: The CHARNAME startup parameter (if

function at all). For example, to trace the WUM

specified) or the CHARNAME value used previously,

component at level 2, enter 2.

and the values in SYSTEM.SYSOPTIONS for DBCS and

Operator Response:

CHARSUB, are used to initialize the values reported by

this message. The values in SYSTEM.SYSOPTIONS are

v Enter the desired trace level.

updated so that the next time the application server is

v If all WUM functions are to be traced, enter * plus 1

started and the CHARNAME startup parameter is not

or 2 for the trace level (with blank between * and

specified, the values reported by this message are then

number).

similar to those received now.

v If only selected WUM functions are to be traced,

System Action: Initialization continues.

enter a function name, its trace-level value, and then

optionally a second function name, with its

trace-level value. One or more blanks must be

ARI0145E

between each function name and each trace level

value entered. If you enter a function name more

Format 1: DBSPACE dbspace-number does

than once, the last entry is effective.

not exist or is invalid.

v See "Notes" for this message for the use of the *

Format 2: DBSPACE dbspace-name does

symbol with other function names.

not exist or is invalid.

v If TRACE command termination is desired, enter

Explanation: The user failed to provide a valid

CANCEL.

DBSPACE name or number.

System Action: Processing ends.

ARI0142D Enter DSC function name and

trace-level pair. Valid function names

User Response: Verify the name or number of the

are *, AGENT, COM, and CANCEL.

dbspace that you want to process, and run the utility

Valid trace-level values are 0, 1, and 2.

again.

Explanation: The TRACE ON command is being

processed. The operator responded DSC to prompting

ARI0146I

Warning: The command line was

message ARI0087D. The database manager prompts the

truncated at column 80.

operator to specify the DSC function to trace and the

Explanation: ARIYE04 only parses 80 characters. An

desired trace level.

operator command can only be 80 characters in VSE.

System Action:

System Action: Process the truncated command.

v If you enter AGENT, the agent handling function of

Operator Response: Shorten the command line if

the database manager is traced at the specified trace

valid data appears beyond column 80.

level (n).

v If you enter COM, the communications function of

the database manager is traced at the specified trace

ARI0150E There is no connection for showid.

level (n).

Explanation: A connection to the application server

v If you enter CANCEL, TRACE command processing

for the specified showid that is an agent, user ID, or

ends.

LUWID cannot be found. Sources of the problem

include:

Note: If you enter trace level 0 for a function, the

v An incorrect user ID was entered.

function is not traced. Entering trace level 0 is

v An incorrect agent number was entered (not numeric

equivalent to not specifying the function at all.

or not in the range 1 through NCUSERS).

Operator Response: If you want to terminate the

v An incorrect LUWID was entered.

TRACE command, enter CANCEL.

v The agent, user ID, or LUWID is not connected to

the application server at the instant the SHOW

CONNECT command was entered.

System Action: The SHOW command processing is

ended.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

Operator Response: Be sure that the specified agent,

VSE System Administration manual for virtual

user ID, or LUWID is correct and then reenter the

storage requirements of the DB2 Server for VSE

SHOW CONNECT command.

system.

Note: You may receive the same result if the requested

ARI0155E There is not enough memory for trace

agent, user ID, or LUWID is not connected to the

buffer allocation. Contiguous memory

application server when the command is

requested = needed_storage kilobytes.

reentered.

Maximum contiguous memory available

at this time = available_storage kilobytes.

ARI0153I

The database manager ignores

Trace is not started.

TRACEBUF = size parameter when trace

Explanation: The memory needed_storage required for

is not activated.

the trace buffer allocation is not available.

Explanation: A nonzero size for the TRACEBUF

System Action: If TRACEBUF was specified in the

startup parameter has been specified, and no

TRACE ON operator command, the trace is not started.

subcomponent have been chosen to be traced

(TRACxxxx startup parameters must indicate 1 or 2 for

If TRACEBUF was specified as a database startup

a specific subcomponent to be traced).

parameter, the database manager is ended.

System Action: The system does not use the

Operator Response: There are several possible actions:

TRACEBUF parameter, and no trace buffer is allocated.

v Reissue the TRACE ON command with smaller

The startup continues.

amount of storage specified for the TRACEBUF

parameter.

Operator Response: No response is required if the

operator does not want any trace output. If trace

v Reissue the TRACE ON command with TRACEBUF

output is expected, then the database manager must be

= 0 (the trace buffer is not used and the trace records

restarted with the proper values of the TRACxxxx

are written directly into the trace file).

startup parameters. Alternatively, the TRACEBUF n

v Start the database manager with more memory

parameter in the TRACE ON operator command can be

available.

used to start the trace in MUM.

v If TRACEBUF was specified as a database startup

parameter, start the database manager with a smaller

ARI0154I

A size kilobyte trace buffer has been

amount of storage specified for TRACEBUF, or

allocated. Maximum contiguous memory

remove TRACEBUF from the parameter list.

left = amount kilobytes.

Explanation: The trace buffer of the size as shown has

ARI0156I

The trace buffer was written to the trace

been created.

file.

System Action: The trace is started. Trace records are

Explanation: The contents of the trace buffer was

stored into the trace buffer.

flushed out to the trace file. This can happen as a result

of the TRACE OFF operator command or during a

Operator Response: If the amount maximum

database system shutdown.

contiguous memory left is too small (see the note

below) then the operator can consider one of the

following actions:

ARI0157I

The trace buffer is empty.

v Turn the trace off using the TRACE OFF command

Explanation: An attempt to write the trace buffer into

and then reissue the TRACE ON with a smaller

the trace file failed. The trace buffer is empty, because

amount of storage specified for the TRACEBUF

an incorrect TRACE specification (component,

parameter.

subcomponent, authorization ID, agent number or a

v Turn the trace off using the TRACE OFF command

level) was entered, or the workload that was run did

and then reissue the TRACE ON with TRACEBUF =

not hit an activated trace point.

0 or without TRACEBUF (the trace buffer is not used

Operator Response: Reissue the TRACE ON

and the trace records are written directly into the

command in MUM, or restart the database manager

trace file).

with the correct values of startup parameters. Repeat

v Start the database manager with more memory

the workload to be traced.

available.

Note: Even after the database manager has been

started, the storage requirements are dynamic

and workload dependent. See the DB2 Server for

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

database to work with different CCSIDs, enter 0(No) to

ARI0159D The specified CHARNAME is different

continue database initialization using the current

than the current system CHARNAME.

CHARNAME.

This will force the system CCSID values

to be changed. Do you wish to change

the system CHARNAME?

ARI0160D Enter CONV trace-level or CANCEL.

Valid trace-level values are 0, 1, and 2.

Enter 0(No) to continue using the

Explanation: The TRACE ON command is being

current CHARNAME of

processed. The operator has responded CONV to

old-charname, or

prompting message ARI0087D. The database manager

1(Yes) to change the system

is prompting the operator to specify the desired trace

CHARNAME

level for CONV.

to new-charname, or

111(Quit) to cancel your request

System Action:

and end SQLSTART

v If n is entered, where n is 1 or 2, the CONV

processing.

component will be traced at trace-level n.

Explanation: The value of the CHARNAME parameter

v If trace-level 0 is entered for the component, it will

specified in SQLSTART is different from the current

not be traced (equivalent to not entering CONV in

CHARNAME value. Changing the current

response to the message ARI0087D).

CHARNAME will change the current default CCSID

v If CANCEL is entered, TRACE command processing

values. Also, the CCSID attribute of the character

ends.

columns of the system catalog tables will be updated to

the new default CCSID. The actual data stored in the

Operator Response: Enter the desired trace level. If

system catalog tables will not be converted from the

TRACE command termination is desired, enter

current default CCSID to the new default CCSID. Only

CANCEL.

the attribute of the character columns will change. The

CCSID attribute of the character columns of any user

ARI0161E RMTUSERS = value cannot be specified

tables will not be updated to the new default CCSID.

because the DRDA facility has not been

The default CHARNAME of a system should be

installed for the application server.

changed only once: at installation or migration. If it is

Explanation: RMTUSERS = value was specified as a

changed after system objects have been created in the

database startup parameter. The DRDA facility was not

system catalog tables, object names not conforming to

installed for the application server, and it cannot

the rules for ordinary identifiers may contain characters

process requests from DRDA application requesters.

that do not have the same hexadecimal representation

in the new CCSID and some data may be displayed

System Action: The database manager is ended.

incorrectly. For the rules about ordinary identifiers, see

Operator Response: Refer this message to your

the DB2 Server for VSE & VM SQL Reference manual.

database administrator.

For more information on the CHARNAME parameter,

see the DB2 Server for VSE System Administration

Database Administrator Response: Determine

manual.

whether or not you require your application server to

service DRDA requesters. If so, install the DRDA

System Action:

facility following the steps in the DB2 Server for VSE

v If you answer 0 (No), the current default

System Administration manual.

CHARNAME and CCSID values are used and

SQLSTART processing continues.

ARI0162D Enter STG trace-level or CANCEL. Valid

v If you answer 1 (Yes), the default CHARNAME will

trace level values are 0 and 1.

change. CCSID values associated with the new

CHARNAME will:

Explanation: The TRACE ON command is being

- Become the new default CCSID values for the

processed. The operator responded STG to prompting

database manager

message ARI0087D. The database manager is

prompting the operator to specify the trace level for

- Replace the current CCSID attribute for the

STG.

character columns in the system catalog tables.

v If you answer 111(Quit), SQLSTART processing ends,

System Action:

and no changes are made.

v If 1 is entered, the STG component is traced at level

v If 0 is entered, the STG component is not traced.

Database Administrator Response: Unless you are

v If CANCEL is entered, TRACE command processing

installing or migrating a database or reconfiguring the

ends.

Operator Response: Choose your response from

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

"System Action", and enter 1 or 0 or CANCEL.

installed. In addition, refer to System Programmer

Response and Database Administrator Action of

message ARI0190E.

ARI0163E

{SHOW CONNECT WAITING | DRDA

facility} is not supported in this

environment.

ARI0176I

The SYNCPNT parameter has been reset

to N.

Explanation:

v If it says SHOW CONNECT WAITING, the SHOW

Explanation: The AXE transaction was autostarting

CONNECT WAITING command cannot be used in

DRDA TRUE support and encountered an error. As a

this operating system environment.

result, the AXE transaction instructed the database

manager to change the SYNCPNT parameter from "Y"

System Action:

to "N".

v If it says SHOW CONNECT WAITING, the

command processing is ended.

System Action: The database manager is unable to

v If it says DRDA facility, the database manager is

use CICS/VSE sync point manager for handling DRDA

ended.

sync point operations. As a result, this database may

not be a participant in DRDA logical units of work that

Operator Response:

update multiple remote databases. However, the

v If it says SHOW CONNECT WAITING, check the

database manager is still able to process SQLDS

correctness of the syntax of the SHOW CONNECT

protocol requests and DRDA requests that do not

command in this operating environment.

involve a sync point manager (for example, DRDA

v If it says DRDA facility, refer this message to your

logical units of work that only update a single a single

Database Administrator.

remote database).

Database Administrator Response: If your application

System Programmer Response: This message is

server needs to service DRDA requesters, install the

preceded by a message on the VSE console indicating

required VSE operating environment. If you do not

the error that occurred. Fix the problem indicated in

need to service DRDA requesters, do not install the

this prior message and restart the database.

DRDA facility.

ARI0183E The Sync Point Manager has asked to

ARI0165I

All parameters are ignored for string.

{COMMIT | ROLLBACK} this LUW but

Explanation: The command, statement, or operation

the database manager has no memory of

that you entered, such as SHOW DBCONFIG,

it.

contained parameters, but none were required. The

Explanation: The CICS/VSE sync point manager is

system does not use the parameters.

attempting to resynchronize the status of a logical unit

System Action: Processing continues, and all

of work with the database manager. It is asking the

parameters are ignored.

database to either commit or rollback this LUW.

However the database manager could not find any

indication that this unit of work needs

ARI0172E A Sync Point Manager is not available.

resynchronization. This can happen when the operator

Explanation: The parameter "SYNCPNT=Y" was

used the database manager FORCE command and

specified at startup; however, the CICS/VSE Sync Point

RESET INDBOUT command on this unit of work while

Manager was not available. This message is following

the CICS/VSE sync point manager is resynchronizing

by message ARI0176I.

with the database manager.

System Action: The database manager is unable to

This message is followed by message ARI4019I to

use CICS/VSE sync point manager for handling DRDA

identify the unit of work.

sync point operations. As a result, this database may

System Action: The database manager sends back a

not be a participant in DRDA logical units of work that

normal completion reply to the CICS/VSE sync point

update multiple remote databases. However, the

manager.

database manager is still able to process SQLDS

protocol requests and DRDA requests that do not

Operator Response: Refer this message to your DB2

involve a sync point manager (for example, DRDA

Server for VSE database administrator.

logical units of work that only update a single remote

Database Administrator Action: Manual intervention is

database).

necessary to ensure that the LUW is in a consistent

System Programmer Response: If this database

state at all sites where the LUW has been distributed.

manager is to be a participant in DRDA logical units of

This may require intervention at this database manager,

work that update multiple remote databases, the AXE

or possibly at other database managers. Manual

transaction must be allowed to successfully autostart

intervention could mean manually fixing the data or

the DRDA TRUE support for this database, and the

possibly restoring an archive.

CICS Restart Resynchronization support must be

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

ARI0184A The Sync Point Manager has asked to

ARI0186I

TRUE-name task-related user exit

{COMMIT | ROLLBACK} this LUW but

resynchronization between CICS and

the FORCE command was previously

the database manager has ended.

used to {ROLLBACK | COMMIT} it.

Explanation: This is a signal to the database manager

Explanation: The CICS/VSE sync point manager is

operator that the database manager has completed

attempting to resynchronize the status of a logical unit

resynchronization of all in-doubt logical units of work

of work with the database manager. It is asking the

with the CICS/VSE sync point manager.

database to either commit or rollback this LUW.

TRUE-name is the name of the DRDA TRUE where

However the operator had previously used the

resynchronization is taking place.

database manager FORCE command to force the LUW

into the opposite state.

System Action: The CICS/VSE sync point manager

and the database manager have resynchronized all

This message is followed by message ARI0196I to

possible in-doubt LUWs. In-doubt LUWs which have

identify the unit of work.

been resynchronized will no longer be displayed when

System Action: The LUW remains unsynchronized

the SHOW INDOUBT command is issued. In-doubt

with the sync point manager. The LUW still appears

LUWs that remain unsynchronized will still be

when the SHOW INDOUBT command is issued.

displayed.

Operator Response: Refer this message to your DB2

Server for VSE database administrator.

Database Administrator Action: In order to clear out

Database Administrator Action: Use the database

this LUW from the SHOW INDOUBT display, it is

manager SHOW INDOUBT command to find out if

necessary to use the RESET INDOUBT command.

heuristic damage had occurred for any logical units of

work. Manual intervention is necessary to ensure that

In addition, manual intervention is necessary, before

these LUWs are in a consistent state at all sites where

RESET INDOUBT is issued, to ensure that the LUW is

the LUW has been distributed. This may require

in a consistent state at all sites where the LUW has

intervention at this database manager, or possibly at

been distributed. This may require intervention at this

other database managers. Manual intervention could

database manager, or possibly at other database

mean manually fixing the data.

managers. Manual intervention could mean manually

fixing the data or possibly restoring an archive.

It is necessary to use the database manager RESET

INDOUBT command to clear out these LUWs from the

SHOW INDOUBT display. However, use the RESET

ARI0185I

TRUE-name task-related user exit

INDOUBT command only after these logical units of

resynchronization between CICS and

work have been resolved.

the database manager has started.

Explanation: While autostarting DRDA TRUE support

ARI0187I

TRUE-name is enabled for DRDA

TRUE-name, the AXE transaction started

support.

resynchronization with the CICS/VSE sync point

manager. Resynchronization occurs after two-phase

Explanation: The AXE transaction successfully

commit processing has been interrupted by a resource

completed autostarting DRDA TRUE support

failure. It involves passing a list of all in-doubt logical

TRUE-name. This message is followed by message

units of work to the CICS/VSE sync point manager.

ARI0188I.

Using information stored in its log, the CICS/VSE sync

TRUE-name is the name of the DRDA TRUE support

point manager determines how the in-doubt logical

that was enabled.

units of work should be resolved and instructs the

database manager to process each in-doubt logical unit

System Action: The AXE transaction processing

of work accordingly.

continues. The application server for which the DRDA

TRUE support was autostarted can now be a

TRUE-name is the name of the DRDA TRUE where

participant in DRDA logical units of work that update

resynchronization is taking place.

multiple remote databases.

System Action: Resynchronization processing

continues.

ARI0188I

TRUE-name has an entry point of

Database Administrator Action: Watch to make sure

entry-point.

that no error messages appear between message

Explanation: The AXE transaction successfully

ARI0185I and message ARI0186I.

completed autostarting the DRDA TRUE TRUE-name.

TRUE-name is the name of the DRDA TRUE.

entry-point is the entry point of the DRDA TRUE.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

System Action: The AXE transaction processing

ARI0191I

TRUE-name is disabled.

continues.

Explanation: The DAXT transaction successfully

completed the termination of the DRDA TRUE

ARI0189E CICS restart resynchronization is not

TRUE-name.

available.

TRUE-name is the name of the DRDA TRUE support

Explanation: While autostarting DRDA TRUE support,

being terminated.

the AXE transaction detected that the CICS restart

resynchronization transaction CRSY is not enabled.

System Action: The DAXT transaction ends.

System Action: The AXE transaction ends the

The DRDA TRUE TRUE-name will be autostarted when

enabling of the DRDA TRUE.

a DRDA2 application requester initiates a connection to

a DB2 Server for VSE application server whose DRDA

Operator Response: Enable the CICS restart

TRUE support is TRUE-name.

resynchronization transaction CRSY.

System Programmer Response: Ensure that CICS

ARI0192I

TRUE-name is not currently enabled for

restart resynchronization support has been installed

DRDA support.

properly. See the DB2 Server for VSE Program Directory

for more details.

Explanation: The DAXT transaction was entered to

disable the DRDA TRUE TRUE-name. However, the

DRDA TRUE was not enabled. Either the DRDA TRUE

ARI0190E TRUE-name cannot be enabled for

was not enabled or a previous execution of DAXT

DRDA support. There is no DRDA

terminated the DRDA TRUE.

TRUE support and processing will

continue as if SYNCPNT=N is specified.

TRUE-name is the name of the DRDA TRUE support

being terminated.

Explanation: The AXE transaction failed in its attempt

to autostart the DRDA TRUE support TRUE-name. An

System Action: The DAXT transaction ends.

error message will have been displayed earlier that

indicated the error that caused the failure.

ARI0193E The CICS log does not contain

TRUE-name is the name of the DRDA TRUE support

information for an in-doubt logical unit

the AXE transaction was autostarting.

of work belonging to server server-name.

System Action: This message is followed by messages

Explanation: While autostarting DRDA TRUE support,

ARI0172E and ARI0176I on the DB2 Server for VSE

the AXE transaction started TRUE resynchronization.

operator console. AXE transaction processing continues

During TRUE resynchronization, CICS/VSE was given

but the SYNCPNT parameter is reset from "Y" to "N".

a logical unit of work that the database manager

As a result, the database manager is unable to use the

indicated to be resolved. However, the information

CICS/VSE sync point manager for handling DRDA

needed to resolve the logical unit of work was not on

sync point operations and this database may not be a

the CICS/VSE log. This generally results from a

participant in DRDA logical units of work that update

CICS/VSE coldstart following a system failure. If a

multiple remote databases. However, the database

CICS/VSE coldstart did not occur after the last system

manager is still able to process SQLDS protocol

failure, the CICS/VSE log or the DB2 Server for VSE

requests and DRDA requests that do not involve a sync

log data has been damaged.

point manager (for example, DRDA logical units of

This message is followed by messages ARI4018A and

work that only update a single remote database).

ARI4019I or messages ARI0195A and ARI0196I.

Operator Response: Refer this message to your

ARI4018A and ARI4019I identify the in-doubt logical

system programmer and database administrator.

units of work (agents) that need to be resolved. These

agents must be resolved (with the database manager

System Programmer Response: An error message will

FORCE command). ARI0195A identifies the in-doubt

have been displayed before this message that indicated

logical units of work (CICS/VSE recovery token) that

the error. See the explanation for that message and

had been FORCEd by the database manager FORCE

resolve the error.

command but had not been resolved with the

Database Administrator Action: After the error

CICS/VSE sync point manager.

indicated by the error message displayed before this

server-name is the name of the application server which

message has been resolved, restart the database with

owns the in-doubt logical unit of work.

SYNCPNT = "Y". This will allow the next AXE

transaction that is started by a DRDA2 application

System Action: The logical unit of work remains

requester to autostart the DRDA TRUE support for this

unresolved. That is, it remains INDOUBT.

application server and will make this application server

Resynchronization processing continues for other

a participant in DRDA logical units of work that

in-doubt LUWs.

update multiple remote databases.

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

Operator Response: If the message is followed by

CICS/VSE or DB2 Server for VSE storage. If the

ARI4018A and ARI4019I, refer to the OPERATOR

problem persists, make a record of what went wrong

RESPONSE for messages ARI4018A and ARI4019I. If

and contact the designated support group for your

the message is followed by ARI0195A and ARI0196I,

installation.

refer to the OPERATOR RESPONSE for messages

Database Administrator Action: If the message is

ARI0195A and ARI0196I.

followed by ARI4018A and ARI4019I, refer to the

Database Administrator Action: If the message is

DATABASE ADMINISTRATOR ACTION for messages

followed by ARI4018A and ARI4019I, refer to the

ARI4018A and ARI4019I. If the message is followed by

DATABASE ADMINISTRATOR ACTION for messages

ARI0195A and ARI0196I, refer to the DATABASE

ARI4018A and ARI4019I. If the message is followed by

ADMINISTRATOR ACTION for messages ARI0195A

ARI0195A and ARI0196I, refer to the DATABASE

and ARI0196I.

ADMINISTRATOR ACTION for messages ARI0195A

and ARI0196I.

ARI0195A

Use the database manager SHOW

INDOUBT operator command to find

ARI0194E A logical unit of work that the database

the following units of work:

manager for server server-name indicated

needed to be resolved was not

ARI0196I

SERVER_NAME = server-name.

identified by the CICS/VSE log as

RECOVERY TOKEN = rectok.

needing resolution.

Explanation: While autostarting DRDA TRUE support

Explanation: While autostarting DRDA TRUE support,

and performing TRUE resynchronization, the AXE

the AXE transaction started TRUE resynchronization.

transaction was informed by CICS/VSE that a logical

During TRUE resynchronization, CICS/VSE was given

unit of work it is trying to resynchronize is lost due to

a logical unit of work that the database manager

CICS cold start or that a logical unit of work should

indicated needed to be resolved. However, information

not be resynchronized because it should not be

in the CICS/VSE log indicated that the logical unit of

in-doubt.

work did not need to be resolved. CICS/VSE cannot

resolve the logical unit of work.

server-name is the name of the application server that

owns the logical unit of work.

This condition can occur when an application program

overlays a CICS/VSE log buffer, or when a DB2 Server

rectok is the unique CICS recovery token assigned to the

for VSE log buffer is destroyed. Or, the CICS/VSE log

logical unit of work.

or the DB2 Server for VSE log may have been

System Action: The LUW remains unsynchronized

damaged.

with the sync point manager. The LUW still appears

This message is followed by messages ARI4018A and

when SHOW INDOUBT command is issued.

ARI4019I or messages ARI0195A and ARI0196I.

Operator Response: Refer this message to your DB2

ARI4018A and ARI4019I identify the in-doubt logical

Server for VSE database administrator.

units of work (agents) that need to be resolved. These

agents must be resolved (with the database manager

Database Administrator Action: Use the database

FORCE command). ARI0195A identifies the in-doubt

manager SHOW INDOUBT command to obtain more

logical units of work (CICS/VSE recovery token) that

information about the logical units of work. In order to

had been FORCEd by the database manager FORCE

clear this LUW from SHOW INDOUBT display, it is

command but had not been resolved with the

necessary to use the RESET INDOUBT command.

CICS/VSE sync point manager.

Manual intervention is necessary before the RESET

server-name is the name of the application server which

INDOUBT command is issued to ensure that the LUW

owns the in-doubt logical unit of work.

is in a consistent state at all sites where the LUW has

been distributed. This may require intervention at this

System Action: The logical unit of work remains

database manager, or possibly at other database

unresolved. That is, it remains INDOUBT.

managers.

Resynchronization processing continues for other

in-doubt LUWs.

ARI0199I

DRDA TRUE TRUE-name is enabling for

Operator Response: If the message is followed by

server server-name.

ARI4018A and ARI4019I, refer to the OPERATOR

Explanation: A DRDA2 application requester initiated

RESPONSE for messages ARI4018A and ARI4019I. If

a connection to a DB2 Server for VSE application

the message is followed by ARI0195A and ARI0196I,

server. The AXE transaction detected that the DRDA

refer to the OPERATOR RESPONSE for messages

TRUE support for the application server was not

ARI0195A and ARI0196I.

enabled and so it autostarted the DRDA TRUE support

System Programmer Response: Ensure that any newly

for the application server.

installed application program are not overlaying

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS

Messages

server. If there is an entry in SYSDROP for the table

ARI0200E Sizes of logs are unequal.

or dbspace that was being dropped when the

Explanation: During database generation (invoking

application server was terminated, any subsequent

the application server with initialization parameter

drop commands may cause the application server to

STARTUP=C) or during log file redefinition/

be terminated with message ARI0201E.

reformatting (invoking the application server with

To correct this problem, you need either to add a

initialization parameter STARTUP=L), dual logging was

DBEXTENT to the storage pool in which the table’s

defined (initialization parameter DUALLOG=Y) or

DBSPACE resides, or to reorganize the DBSPACE.

alternate logging (initialization parameter ALTLOG=Y)

When you add a DBEXTENT to correct this

was defined. The database manager has determined

problem, you should next issue an ACQUIRE and

that the log data sets are not the same size. This is not

then a DROP of any size DBSPACE. This will cause

permitted.

the database manager to clean up any entries in

System Action: The application server is ended.

SYSTEM.SYSDROP that were left over during the

original DROP TABLE or DBSPACE failure.

Operator Response: Return the console output with

For information on how to reorganize the

the output listing.

DBSPACE, see the DB2 Server for VSE & VM

System Programmer Response: You can circumvent

Database Administration manual.

this problem by invoking the application server with a

2. You may not have to enlarge the storage pool.

single log. To do so, either omit the DUALLOG and

Under certain conditions, the message ARI0201E

ALTLOG parameters or specify DUALLOG=N and

occurs when the processing of the current operation

ALTLOG=N.

has used only half of the storage pool.

You can correct this problem by proceeding as follows:

A bypass is possible if LOGMODE is not N and the

failing operation is one of:

Redefine the VSAM clusters (ESDSs) for the logs so

that they are equal in size. They are always equal in

CREATE INDEX

DROP TABLE

size if they are on the same device type and you

DROP DBSPACE

UPDATE

specify the same primary allocation (CYLINDERS,

INSERT

DELETE

TRACKS, or BLOCKS). Then reexecute the job.

DATALOAD

RELOAD TABLE

RELOAD DBSPACE

RELOAD PROGRAM

ARI0201E Storage pool n is full.

RELOAD PACKAGE

REORGANIZE INDEX

Explanation: The physical storage in storage pool n

SCHEMA

DROP INDEX

has reached a level at which the system cannot

function. If this error was the result of a DROP TABLE

Try running the command in single user mode with

or DBSPACE command, then the storage pool did not

LOGMODE=N.

contain enough shadow pages to process the DROP

command.

ARI0202I

Warning: Storage pool n is short of

System Action: In most cases, processing of the SQL

storage.

statement ends. In some cases, the application server

Explanation: Storage pool n has reached the cushion

ends.

specified at startup using the database SOSLEVEL

Operator Response: Return the console output with

initialization parameter (SOSLEVEL x TOTAL PAGES

the output listing.

IN POOL / 100). Either logging was inactive, or

logging is active but further checkpoints will not

System Programmer Response: Define an additional

correct this situation.

VSAM cluster for a new DBEXTENT. Then run the

ADD DBEXTENT function to add the DBEXTENT to

System Action: Processing continues.

the storage pool that is full.

Operator Response: Notify your system programmer.

Notes:

System Programmer Response: Enter the SHOW

1. If ARI0201E occurred during DROP TABLE or

DBEXTENT command to determine the amount of

DBSPACE processing and the application server

space left in the storage pool. You may need to add

ended, you need to check the catalog table

more DBEXTENTs to the storage pool specified in the

SYSDROP after you warm start the application

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

message. (If needed, use the ADD DBEXTENT

backing up your database with the backup facility of

function.)

your choosing.

n is the number of DBEXTENTs in your database. You

ARI0203E

{PAGE|DIRECTORY} buffer pool is

are also warned not to backup your logs. Backing up

full.

and then restoring your logs would make it impossible

to restore your database changes since the user-archive

Explanation: When running the database manager,

was taken.

more pages of data or DIRECTORY blocks were

simultaneously required in the buffers than there were

System Action: The database manager will write a

buffers in the pool.

record on the log indicating that a user-archive is being

attempted and then shut down normally.

System Action: The application server is ended.

Operator Response: After the application server

Operator Response: Save the console output for the

terminates, backup your directory and n DBEXTENTs

system programmer.

with any suitable backup facility. Take special care to

System Programmer Response: Increase the number

note whether you have backed up successfully or not

specified for the initialization parameter NPAGBUF (for

as you will be prompted with message ARI0206D at the

page buffers) or NDIRBUF (for directory buffers), and

next database startup.

restart the application server.

ARI0206D Did the user-archive of the directory

ARI0204D Restore from archive has been invoked.

and n DBEXTENT(S) execute

Current database will be destroyed.

successfully? Enter 0(No) or 1(Yes).

Explanation: The SQLEND UARCHIVE command

Enter RESTORE - to continue,

was used the last time the application server was shut

or CANCEL - to cancel.

down. You must tell the database manager if you have

Explanation: The application server was started with

successfully archived your database. n is the number of

STARTUP=R or F. This causes the contents of the

DBEXTENTS in your database.

database to be replaced (restored) by the database copy

System Action: If you reply 1 for YES, the database

on a database manager archive file. The restored

manager records on the log that a user-archive was

database is then updated for any logging which has

successfully done, and it frees log space. If you reply 0

occurred since the last database archive.

for NO, the database manager will prompt you with

message ARI0207D. If you do not reply 1 or 0, message

Note: The database directory will be reformatted (and

ARI0052E will be displayed and message ARI0206D

thus destroyed) before the restore process starts.

will be redisplayed.

System Action: The system waits for your reply.

Operator Response: Reply 1 if you are sure that you

backed up your directory and n DBEXTENTs. Reply 0

If the reply is RESTORE, the database manager

if you are unsure about your archive and you will then

continues and replaces the database with the database

be prompted with message ARI0207D.

copy on the archive file.

If the reply is CANCEL, the application server is ended

ARI0207D Do you want to continue (without

without modification to the database.

user-archive) or cancel (redo the

Any other reply causes the message to be reissued.

user-archive)? Enter CONTINUE or

CANCEL.

Operator Response: If the database is to be restored

from a database manager archive file, reply RESTORE.

Explanation: You replied 0 to message ARI0206D. You

may terminate the application server if you wish to

If the database is not to be restored from a database

redo your user-archive.

manager archive file, reply CANCEL to end the

application server.

System Action: If you reply CONTINUE, the database

manager will write a record to the log indicating that

System Programmer Response: Inform the operator of

no user-archive was done and processing will continue.

your intentions when restoring a database, including

any mounting of database manager archive tapes.

If you reply CANCEL, the database manager will not

write any record to the log. The last user-archive log

record is still in effect. The application server will

ARI0205I

You must user-archive the directory and

terminate to allow you to redo your user-archive. At

n DBEXTENT(S) but not the logs!

the next application server startup, you will be

Explanation: The database operator has issued an

prompted with message ARI0206D.

SQLEND UARCHIVE command. This tells the database

If you do not reply CONTINUE or CANCEL, message

manager that you are shutting down normally and then

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

ARI0052E is displayed and message ARI0207D is

DUALLOG=Y or N, ALTLOG=Y or N, and

redisplayed.

LOGMODE=A (or LOGMODE=Y if you do not plan

to use archiving).

Operator Response: Reply CONTINUE if you wish to

2. You should immediately startup the application

continue using the database manager without

server (using STARTUP=W and LOGMODE=A) and

user-archiving the database. Reply CANCEL if you

take a database archive using the SQLEND

wish to terminate and redo the user-archive.

ARCHIVE or SQLEND UARCHIVE commands.

3. If you are using log archiving, you can then start

ARI0208D Did the user-restore of the directory and

the application server with LOGMODE=L.

n DBEXTENT(S) execute successfully?

Otherwise, start the application server with

Enter 0(No) or 1(Yes).

LOGMODE=A.

Explanation: The application server was started with

STARTUP=U to indicate that a user-restore of the

ARI0210I

The extend file input did not generate

database was done before startup. This message is

summary statistics.

issued to verify that you performed the restore.

Explanation: Either the control keywords specified in

System Action: If you reply 1, the database manager

the EXTEND input file had no match in the log or the

will reapply the log activity since the user-archive was

control keywords were matched but the logical units of

taken. All committed logical units of work will be

work found were read-only (queries).

reflected in the database.

System Action: The database manager displays

If you reply 0, the application server will terminate to

message ARI0213D.

allow you to redo the user-restore or startup with the

correct STARTUP parameter.

Operator Response: Respond CANCEL to ARI0213D.

Refer this message to your system programmer.

If you do not reply 1 or 0, message ARI0052E is

displayed and message ARI0208D is redisplayed.

System Programmer Response: Check the control

keywords in the EXTEND input file and adjust as

Operator Response: Reply 1 if you are sure that your

needed. Restart extended database initialization.

user-restore was successful. Otherwise, reply 0. If the

STARTUP parameter was incorrectly set to U, simply

restart the application server with the correct STARTUP

ARI0211I

The requested BYPASS or ROLLBACK

parameter. If you are unsure of the user-restore, you

operation may affect the following

may redo it after the application server ends and then

logical units of work:

restart the application server with STARTUP=U.

Explanation: If the ROLLBACK COMMITTED WORK

or BYPASS UNDO WORK operation completes, the

ARI0209E Since database archive was created, the

specified logical units of work may operate on the

size of the logs has changed. You must

same tables as did the rolled back or bypassed logical

perform COLDLOG.

unit of work. Depending on which operation is

performed on the DBSPACE or the table, this may lead

Explanation: The database restore has completed

to other problems such as updating a table or row

successfully. However, the size of the database logs has

which no longer exists.

changed since the database archive was created. You

must perform the COLDLOG process to:

System Action: The database manager displays

message ARI0214I (impacted summary) and message

v Reflect the current size of the logs in the database

ARI0213D (pause). Refer this message to your system

directory, and

programmer.

v To create the log history area in a location known to

the database manager. Refer to the information on

System Programmer Response: Use the summary

"History Area" in the DB2 Server for VSE System

information to determine if the specified action is to be

Administration manual.

done. Instruct the operator whether to reply

CONTINUE or CANCEL to message ARI0213D.

The database is at the level which existed when the

Sample Output Sequence:

database archive (just restored) was created.

ARI0211I The requested BYPASS or ROLLBACK

System Action: The application server ends.

operation may affect the

following logical units of work:

Operator Response: You must perform the following

ARI0214I LUWID=7BA USER ID=JONES

procedures:

DBSPACE=8 TABLE ID=-32765(8003)

1. You must COLDLOG the database manager using

initialization parameters STARTUP=L, SYSMODE=S,

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

will be repeatedly displayed until CONTINUE or

ARI0212I

Summary information of the records to

CANCEL is entered.

{be bypassed | roll back}:

Operator Response: Analyze the summary

LUWID = &2B. User ID = &3.

information and respond accordingly. The response

Date = &4.

Time = &5.

CONTINUE causes database initialization to continue

with the specified EXTEND input file commands

Explanation: Summary information will be displayed

carried out. The effects of the commands will be

for each logical unit of work bypassed or rolled back

written into the log before applying the records. They

due to a BYPASS UNDO WORK or ROLLBACK

will remain in the log even if a failure occurs while

COMMITTED WORK command. This message displays

applying the records. The response CANCEL causes

statistics for this logical unit of work. It is followed by

application server termination, leaving the database as

message ARI0237I which displays the operations and

it was before startup.

the number of their occurrences which will be rolled

back or bypassed if instructed to continue.

If no summary information was displayed and an

EXTEND input file was included, the EXTEND input

However, summary information will not be displayed

file commands will not be executed. Something may be

for the logical units of work which have already been

wrong with the EXTEND input file commands. In this

rolled back or bypassed due to a previous BYPASS

case, respond CANCEL to bring down the application

UNDO WORK or ROLLBACK COMMITTED WORK

server and check the EXTEND input file commands.

command.

Refer the summary messages to your system

programmer.

Note: The format of the displayed date is either

mm-dd-yy or dd-mm-yy. The format is chosen

System Programmer Response: Analyze summary

when VSE is IPLed. The default format is

messages and decide whether the actions are what was

mm-dd-yy.

expected. Determine whether to continue or cancel

initialization.

System Action: The database manager issues:

v Messages ARI0237I (operations performed), ARI0214I

ARI0214I

LUWID=&1B. User ID=&2.

(affected logical units of work), and ARI0213D

DBSPACE=&3. TABLE ID=&4A. (&5B.)

(operator decisions), or

v Messages ARI0237I (operations performed) and

Explanation: This message is displayed immediately

ARI0213D (operator decisions).

after message ARI0211I. It displays the logical unit of

work value, the user ID value, the DBSPACE number,

Operator Response: Refer this message to your

and the table identification number (if applicable) of a

system programmer.

logical unit of work which may be affected if the

System Programmer Response: Use the summary

specified BYPASS UNDO WORK or ROLLBACK

information to determine if the specified action is to be

COMMITTED WORK command operation is continued.

done. Instruct the operator whether to reply

The user ID value can be blank. For example, a logical

CONTINUE or CANCEL to message ARI0213D.

unit of work was started after a system checkpoint. A

Sample Output:

second logical unit of work begins and commits before

the first logical unit of work does. The first logical unit

ARI0212I Summary information of the

of work acts on the changes done by the second logical

records to roll back:

unit of work and commits. If the second logical unit of

LUWID=7B9

User ID=SMITH

Date=12-01-85

Time=13:12:45

work is rolled back for any reason, the first logical unit

of work will be affected and USERID will be blank

because the logical unit of work started after the

ARI0213D Enter CONTINUE to continue

checkpoint.

initializing or CANCEL to end.

&1B. is a logical unit of work value.

Explanation: Summary information, if any, has been

displayed on the console concerning the logical units of

&2. is a user ID value or blank.

work that will be bypassed or rolled back due to a

&3. is a DBSPACE number.

BYPASS UNDO WORK or ROLLBACK COMMITTED

WORK command if the database manager is instructed

&4A. is a table identification number or 0 if the table

to continue.

identification number is not applicable (no table

updated).

System Action: The database manager waits for the

operator reply. Message ARI0052E is displayed if you

&5B. is a hexadecimal table identification number or 0

do not reply CONTINUE or CANCEL. This message

if the table identification number is not applicable (no

displays the first 8 characters of the reply and states

table updated).

that the response was not valid. Message ARI0213D

System Action: Message ARI0213D (operator decision)

is displayed.

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

Operator Response: Refer this message to your

ARI0217E Physical page X'n1' assigned to

system programmer.

DBSPACE n2. Page X'n3' was not

System Programmer Response: Use the summary

allocated in the allocation bit map.

information to determine if the specified action is to be

Explanation: The directory verify function has

done. Instruct the operator whether to reply

detected that the physical page number identified by

CONTINUE or CANCEL to message ARI0213D.

X'n1' that has been allocated to logical page X'n3' of

DBSPACE number n2 is reflected as not being allocated

ARI0215E Operator command attempts to access a

in the allocation bit map. This is an internal database

disabled DBSPACE.

error.

Explanation: The operator or an ISQL user is issuing

Note: The DBSPACE number n2 corresponds to the

an operator command which is attempting to access a

DBSPACENO column in the catalog table

disabled DBSPACE. Disabled DBSPACEs cannot be

SYSTEM.SYSDBSPACES.

accessed. The operator command that might cause this

message is SHOW DBSPACE. DBSPACEs are disabled

System Action: The database manager will continue

by DISABLE DBSPACE commands in an EXTEND

verifying all PUBLIC and PRIVATE DBSPACEs and end

input file.

normally.

System Action: Operator command processing ends.

Operator Response: Refer this message to your

system programmer.

Operator Response: Change the command so it does

not attempt to access a disabled DBSPACE.

Note: If ARCHIVE was specified, the DB2 Server for

User Response: Same as Operator Response.

VSE database archive function will not be

invoked. If UARCHIVE was specified, a

user-archive should not be taken. Any implicit

ARI0216I

Directory verify function completed

log archives will be performed due to ARCHIVE

{with | without} discrepancies.

or UARCHIVE. If LARCHIVE was specified, the

Explanation: This message is issued after the

log will be archived, but you should correct the

completion of the directory verify function (an

discrepancies as soon as possible.

SQLEND command option). This message will be

System Programmer Response: Make note of the

preceded by specific error messages for each

information given in this message and refer to directory

discrepancy found (if any).

verification in DB2 Server for VSE & VM Diagnosis

System Action: Termination process continues.

Guide and Reference for recovery procedures.

Operator Response: If the directory verify function

ended with discrepancies, refer this message and the

ARI0218E DBSPACE n1, page X'n2' is allocated to

preceding messages to your system programmer. If it

physical page X'n3' of storage pool n4

completed without discrepancies, termination will

instead of storage pool n5.

continue and you will be prompted for operator action

Explanation: The directory verify function has

as needed.

detected that physical page X'n3' of storage pool n4

was allocated to physical page X'n2' of DBSPACE n1,

Note: If ARCHIVE was specified and discrepancies

which belongs to storage pool n5. This is an internal

were found, no database archive will be taken. If

database error.

UARCHIVE was specified and discrepancies

were found, a user-archive should not be taken.

Note: The DBSPACE number n1 corresponds to the

Any implicit log archives will be performed due

DBSPACENO column in the catalog table

to ARCHIVE or UARCHIVE. If LARCHIVE was

SYSTEM.SYSDBSPACES.

specified, log archiving will be performed, but

you should correct the discrepancies as soon as

System Action: The database manager will continue

possible.

verifying all PUBLIC and PRIVATE DBSPACEs and end

normally.

System Programmer Response: If the database

directory verify function completed with discrepancies,

Operator Response: Refer this message to your

note the information in the messages preceding this

system programmer.

message and refer to directory verification in DB2

Server for VSE & VM Diagnosis Guide and Reference for

Note: If ARCHIVE was specified, the archive function

recovery procedures. If it completed without

will not be invoked. If UARCHIVE was

discrepancies, no action is required of the system

specified, a user-archive should not be taken.

programmer.

Any implicit log archives will be performed due

to ARCHIVE or UARCHIVE. If LARCHIVE was

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

specified, the log will be archived, but you

ARI0222E Parameter parm value in FORCE

should correct the discrepancies as soon as

command is invalid.

possible.

Explanation: The parameter value identified by parm

System Programmer Response: Make note of the

value specified in the FORCE operator command is not

information given in this message and refer to directory

valid. Acceptable parameters are:

verification in DB2 Server for VSE & VM Diagnosis

COMMIT

Guide and Reference for recovery procedures.

ROLLBACK

DISABLE

ARI0219E An unexpected internal error occurred

during SYSDROP processing.

The DISABLE parameter is optional, but, if used, it

must follow the ROLLBACK parameter (that is,

Explanation: The process which cleans up entries on

ROLLBACK DISABLE).

the SYSDROP catalog table has been invoked. An

unexpected error has occurred during this process,

System Action: The command processing is ended.

most likely a database error. This message is displayed

Operator Response: Check the specified parameter,

on the system console.

and reenter the FORCE operator command with correct

values.

Note: In addition to this error, ARI0504I and ARI0505I

are also displayed to report error information in

For more information about the FORCE operator

the SQLCA. See Chapter 17, “DBSS Return

command, refer to the DB2 Server for VSE & VM

Codes,” on page 231 for definitions of the DBSS

Operation manual.

return codes.

System Action: The application server terminates the

ARI0223I

Agent n in FORCE command has no

SYSDROP processing but continues executing.

work to force.

Operator Response: Refer this message and its

Explanation: The agent identified by n does not now

contents to your system programmer.

have any work to be forced off the system.

System Programmer Response: The SYSDROP process

Note: The SHOW ACTIVE operator command may

can be FORCEd by another logical unit of work which

have indicated that there was work to force.

attempts to commit a DROP TABLE or DROP

However, the work ended before the FORCE

DBSPACE. If this failed to release the resources, report

operator command.

this message and its contents to the designated support

group for your installation.

System Action: The command processing is ended.

Operator Response: Do a SHOW ACTIVE to verify

ARI0220E FORCE command has insufficient

the status of agent n. The agent will be either not in

number of parameters.

work (NIW) or active with a new logical unit of work.

Explanation: The database FORCE operator command

was entered without parameters.

ARI0224E FORCE COMMIT is not valid for agent

System Action: The command processing is ended.

Explanation: The agent identified by n is not in a

Operator Response: Reenter the FORCE operator

correct state for the COMMIT option. Only those agents

command with the appropriate operands.

which have been prepared for commit or rollback by a

subsystem (such as CICS) and which are no longer

ARI0221E

{Agent|Rmtuser} identifier n in FORCE

connected to the subsystem may have the COMMIT

command is invalid.

option applied.

Explanation: The identifier n is incorrect. It must both

System Action: The command processing is ended.

(1) be an integer value in the range 1 to the database

initialization parameter NCUSERS or RMTUSERS, and

ARI0225E System operator must issue SHOW

(2) represent a valid user.

ACTIVE, SHOW CONNECT or SHOW

System Action: The command processing is ended.

SYSTEM command prior to FORCE

command.

Operator Response: Verify the agent or rmtuser

identifier by using the SHOW ACTIVE or SHOW

Explanation: This message is issued for one of these

CONNECT operator command output. Then reenter the

reasons:

FORCE operator command with the correct agent or

v The database FORCE command was entered without

rmtuser identifier.

first doing a SHOW ACTIVE, SHOW CONNECT or

SHOW SYSTEM from the database operator console.

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

One of these operator commands must be issued to

prepared for commit or rollback by a subsystem

obtain the correct agent numbers to specify in the

(such as CICS) and that are no longer connected

FORCE command.

to the subsystem.

v The FORCE command specified an agent that

System Action: The command processing is ended.

completed its LUW after the SHOW ACTIVE, SHOW

CONNECT or SHOW SYSTEM command was

Operator Response: Reenter the FORCE command

entered.

without the DISABLE option.

Note that if parameters are used on the SHOW

ARI0229E Too many FORCE command input

CONNECT command, they must result in the display

parameters.

of active agents to enable the FORCE command to

work for the displayed agents.

Explanation: The FORCE command was entered with

more than three parameters.

System Action: The command processing is ended.

Operator Response: Enter the SHOW ACTIVE, SHOW

CONNECT or SHOW SYSTEM command from the

Operator Response: Reenter the FORCE command

operator console to obtain the correct agent numbers,

with correct number of parameters.

then reenter the FORCE command for those agents

desired.

ARI0230I

FORCE {ROLLBACK|COMMIT}

{with|without} disable scheduled for

ARI0226I

FORCE {ROLLBACK|COMMIT} is

agent n because of {log full|operator

already scheduled for {agent|Rmtuser}

request|resynchronization recovery}.

Explanation: The database manager FORCE command

Explanation: The agent or Rmtuser identified by n is

was initiated for the agent identified by n due to the

being rolled back or committed by the system. This

condition indicated by the message ("log full," "operator

action may have been scheduled because of an

request," or "resynchronization recovery"). If the agent

application request, a previous FORCE command, or

was in-doubt, the action could be COMMIT or

system action.

ROLLBACK. Otherwise the action is ROLLBACK.

System Action: The command processing is ended.

System Action: The COMMIT or ROLLBACK is

scheduled. The actual COMMIT or ROLLBACK may

not occur immediately. When the agent begins

ARI0227E Agent n cannot be disabled because it is

processing and detects that the FORCE was scheduled,

connected to the DB2 Server for VSE

it will then begin the requested process. DISABLE, if

online support.

specified on the FORCE command, will cause the link

to the application to be disconnected after the

Explanation: The agent identified by n is now

COMMIT or ROLLBACK process completes.

connected to a subsystem (for example, the DB2 Server

for VSE Online Resource Adapter). The agent’s

resources cannot be freed up using the DISABLE option

ARI0231E The database log contains unresolved

while connected to this subsystem. To disable the

units. Please start the database manager

connection between agents and a subsystem, request

with NCUSERS = &1..

the subsystem to disconnect. For the DB2 Server for

VSE Online Resource Adapter, this may be done by

Explanation: The database recovery process detected

executing the CICS transaction CIRT.

some logical units of work which were prepared for

COMMIT or ROLLBACK by a subsystem (for example,

System Action: Command processing ends.

the DB2 Server for VSE Online Resource Adapter).

Because of a system or subsystem failure, the

Operator Response: Reenter the FORCE command

subsystem did not COMMIT or ROLLBACK the logical

without the DISABLE option or request a CICS

units of work. These logical units of work cannot be

terminal operator to enter the CIRT transaction.

recovered (committed or rolled back) because either:

v The application server has been started in single user

ARI0228E DISABLE option not valid with

mode, or

COMMIT request.

v The application server has been started in multiple

Explanation: The FORCE command DISABLE option

user mode but the number of logical units of work is

is only valid with ROLLBACK.

greater than the number of concurrent users

(specified by the database initialization parameter

Note: The COMMIT option requires that there is no

NCUSERS).

connection to be disabled. The COMMIT option

is valid only for those agents that have been

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

&1. is the number of logical units of work prepared for

v TRANSACTION is the CICS/VSE TRANSID for the

COMMIT or ROLLBACK and is the minimum value

application.

required for initialization parameter NCUSERS.

v CICS SIGNON is the CICS/VSE signon userid (if

any).

System Action: The system ends with a limit error

(message ARI0039E).

v TERMINAL is the CICS/VSE terminal id (if any).

Operator Response: Restart the application server in

If the TRANSACTION identifier is ISQL, only the DB2

multiple user mode (SYSMODE=M) and NCUSERS

Server for VSE database was being updated. Thus,

greater than or equal to &1..

FORCE COMMIT should be entered because the ISQL

user requested COMMIT and ISQL updates only the

ARI0232E The log contains unresolved work for

DB2 Server for VSE database.

user ID &1..

Explanation: The database recovery process detected

ARI0233E Invalid FREECLASS for page X'n1' of

that a logical unit of work for user ID &1. was

DBSPACE n2 (Block X'n3').

prepared by a subsystem for COMMIT or ROLLBACK

Explanation: The database manager has detected that

(for example, the DB2 Server for VSE Online Resource

the FREECLASS setting for page X'n1' of DBSPACE n2

Adapter). The COMMIT or ROLLBACK request did not

is not within the valid range. This is an internal

occur because of a system or subsystem failure.

database error.

Operator intervention may be required to resolve the

logical unit of work.

Note: The DBSPACE number n2 corresponds to the

&1. is the user ID which was established for the logical

DBSPACENO column in catalog table

unit of work.

SYSTEM.SYSDBSPACES.

System Action: The database manager rebuilds the

Note: The BLOCK number n3 refers to the Page Map

agent as it was prior to the system or subsystem

Table block that is being processed.

failure. The agent is ready to be resolved by the FORCE

command or by the DB2 Server for VSE online resource

System Action: The database manager will continue

adapter restart resynchronization support. After the

verifying all PUBLIC and PRIVATE DBSPACEs and end

agent is resolved, it is made available for general use

normally.

by applications or subsystems.

Operator Response: Refer this message to your

Operator Response: The agents requiring resolution

system programmer.

will be resolved during the next execution of the DB2

Server for VSE online resource manager CIRA or CIRB

Note: If ARCHIVE was specified, the archive function

transactions.

will not be invoked. If UARCHIVE was

specified, a user-archive should not be taken.

If restart resynchronization fails to resolve the agent,

Any implicit log archives are performed due to

use the SHOW ACTIVE command to obtain more

ARCHIVE or UARCHIVE. If LARCHIVE was

information about the logical unit of work. Check with

specified, the log will be archived, but you

the installation database administrator to determine

should correct the discrepancies as soon as

whether a FORCE n COMMIT command or a FORCE n

possible.

ROLLBACK command should be entered.

System Programmer Response: Make note of the

System Programmer Response: In general, a FORCE n

information given in this message and refer to directory

COMMIT command should be entered. This is because

verification in DB2 Server for VSE & VM Diagnosis

the application declared its intent as commit either by

Guide and Reference for recovery procedures.

an SQL COMMIT WORK or by a CICS/VSE

SYNCPOINT (no ROLLBACK). The only exception to

the general rule is if the application was updating

ARI0234E Invalid physical page X'n1' for page

multiple resources (for example, the DB2 Server for

X'n2' of DBSPACE n3.

VSE database and a DL/I database). In that case, the

ROLLBACK option is available for when the update

Explanation: The database manager has detected that

was not committed by another subsystem like DL/I.

physical page value X'n1' for logical page X'n2' of

DBSPACE n3 is outside the currently defined physical

To determine the nature of the application, the SHOW

pages of the database. This is an internal database

ACTIVE command displays the following information:

error.

v USERID = &1. is prepared for COMMIT OR

ROLLBACK.

Note: The DBSPACE number n3 corresponds to the

v COORDINATOR is the CICS/VSE subsystem id.

DBSPACENO column in catalog table

SYSTEM.SYSDBSPACES.

v RESOURCE ADAPTER is the DB2 Server for VSE

resource adapter id.

System Action: The database manager will continue

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

verifying all PUBLIC and PRIVATE DBSPACEs and end

ARI0237I

&1. &2.

normally.

Explanation: This message is issued after message

Operator Response: Refer this message to your

ARI0212I. It specifies the affected DBSPACEs and the

system programmer.

operations which will be bypassed or rolled back.

Note: If ARCHIVE was specified, the archive function

Sample Output:

will not be invoked. If UARCHIVE was

ARI0237I DBSPACE 7

specified, a user-archive should not be taken.

ARI0237I

5 INSERTS

Any implicit log archives are performed due to

ARI0237I

2 CREATE TABLES

ARCHIVE or UARCHIVE. If LARCHIVE was

ARI0237I DBSPACE 12

specified, the log will be archived, but you

ARI0237I

10 UPDATES

should correct the discrepancies as soon as

System Action: Message ARI0214I (affected logical

possible.

units) or message ARI0213D (operator decision) will be

System Programmer Response: Make note of the

issued.

information given in this message and refer to directory

Operator Response: Refer this message to your

verification in DB2 Server for VSE & VM Diagnosis

system programmer.

Guide and Reference for recovery procedures.

System Programmer Response: Use the summary

information to determine if the specified action is to be

ARI0235I

LARCHIVE command rejected because a

done. Instruct the operator whether to reply

{log | database} archive is being taken.

CONTINUE or CANCEL to message ARI0213D.

Explanation: An LARCHIVE command was entered

by the database operator while either a log archive or a

ARI0238I

database archive mm-dd-yy hh:mm:ss

database archive was being taken.

Explanation: The database manager is listing the

System Action: The log archive or database archive is

restore set you should apply to the current database

completed and the LARCHIVE command is ignored.

archive file. The message identifies the external labeling

of the database archive file for the restore set.

ARI0236I

The database manager rejects log

Message ARI0239I displayed this information when the

archive request because log archiving is

database archive file was created.

not enabled.

Explanation: An SQLEND LARCHIVE or an

Note: The format of the displayed date is either

LARCHIVE command was entered by the operator, but

mm-dd-yy or dd-mm-yy. The format is chosen

the database manager is not running with

when VSE is IPLed. The default format is

LOGMODE=L.

mm-dd-yy.

System Action: ARI0261I is issued for each log

Note: Although it is valid to enter SQLEND ARCHIVE

archive to be applied to this database.

if database archiving is not enabled

(LOGMODE=Y), it is not valid to enter SQLEND

LARCHIVE if log archiving is not enabled.

ARI0239I

External labeling of this archive is:

Type: {database|log} archive Timestamp:

Note: SHUTDOWN is a valid synonym for SQLEND.

mm-dd-yy hh:mm:ss

System Action: The database manager will process the

Explanation: Because there are three different kinds of

SQLEND command ignoring the LARCHIVE request. If

archives, and each may require multiple tape volumes,

the LARCHIVE command was entered, command

you should externally label the tapes for use in

processing ends.

restoring the database. When the database manager

requests the operator to mount the tapes to contain the

Operator Response: If you were instructed to enter

archive, this message is displayed to help in this

the LARCHIVE command or SQLEND LARCHIVE,

external labeling.

notify your system programmer. Otherwise, no action is

required.

The database manager also uses the label internally to

determine the log archives which follow a database

System Programmer Response: Ensure that the

archive.

operator is not requested to log archive when

LOGMODE is not L.

This message is displayed at the following times:

v When the database manager creates a database

archive file

v When the database manager creates a log archive file

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

v When the application server is ending to allow the

2. Ensure that the information given in message

user to create a database archive (using the SQLEND

ARI0239I matches the information used to

UARCHIVE operator command)

externally label the log archive volume at log

archive creation time.

v When the database manager is ready to read the next

log archive file during the restore process.

Note: This only applies if the operator labeled the

archive tapes with the information displayed

The database manager will display this same

at archive creation time.

information to identify the database archive file and the

required log archive files during the restore process.

3. Ensure that the correct log archive volume is

See messages ARI0238I and ARI0261I.

mounted. This is the log archive file identified by

the previous message ARI0239I.

Note: The format of the displayed date is either

4. Reply with the correct cuu to message ARI0295A to

mm-dd-yy or dd-mm-yy. The format is chosen

continue the log archive restore process.

when VSE is IPLed. The default format is

System Programmer Response: Ensure that your

mm-dd-yy.

system operator follows procedures that allow proper

System Action: The archive or restore process

identification of the log archive volume at creation time

continues.

and proper log archive volume mounting at log archive

restore time.

Operator Response: When creating archives, use the

displayed information to externally label the archive

tapes. If you are doing a LOG ARCHIVE TO DISK, you

ARI0242E Previously LOGMODE was L and now

may want to record the archive details in an

LOGMODE is {Y|N}. To start with

operational record book.

LOGMODE = {Y|N}, perform SQLEND

with LARCHIVE, perform COLDLOG,

When restoring the database, use the displayed

and restart with LOGMODE = {Y|N}.

information to assist you in mounting the correct log

Note: Only in a restore process do log

archive tape. (This step is unnecessary if restoring a

archives taken up to the switch in

LOG ARCHIVE FROM DISK.)

LOGMODE from L to {Y|N} remain

useful.

ARI0240I

Restoring log disk.

Explanation: If the operator wants to change from

Explanation: The application server has been started

LOGMODE=L to LOGMODE=Y or N, this message

with STARTUP=R, STARTUP=F, or STARTUP=U; the

outlines the procedure to follow. In this case, the

log archive input volume has been readied; and the log

message also alerts the operator that after SQLEND

files are being restored.

LARCHIVE archives the active log (and the inactive log

if alternate logging is enabled and it was not archived

System Action: The database manager proceeds with

before) and the operator does a COLDLOG, a restore

the restore process.

process that restores a database archive (which may

include the log archive just taken in its restore set)

ARI0241E The log archive being read is not the log

cannot restore log archives taken past this log archive.

archive requested.

If the operator wants to continue running the database

Explanation: The volume mounted after message

manager with LOGMODE=L, the operator can ignore

ARI0239I was displayed is not the log archive tape file

the procedure outlined in this message and restart the

requested. Possible causes include:

application server with LOGMODE=L.

v The mounted (and opened) volume for file name

System Action: The application server is ended.

ARILARC does not

Operator Response: Either restart the application

v The mounted (and opened) volume for file name

server with LOGMODE=L so that log archives continue

ARILARC is a log

to be useful in a restore process, or restart the

System Action:

application server with LOGMODE=Y or

LOGMODE=N after performing the procedure outlined

The mounted (and opened) volume is closed. If the

in the message. Note that COLDLOG is performed

close fails, message ARI0298E is displayed and the

with the database initialization parameter STARTUP=L.

application server is terminated. Otherwise, message

ARI0295A is redisplayed to allow the operator to

mount the required log archive file and continue the

ARI0243I

Previously LOGMODE was L and now

restore process.

LOGMODE=A. Note that log archives

taken up to this point are useful until

Operator Response:

another database archive is taken.

1. Determine why the correct volume was not

Explanation: If the LOGMODE switch from L to A is

mounted.

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

desired, this message alerts the operator that once a

the LOGMODE value to L so that the log archives may

database archive is taken with LOGMODE=A, a restore

be applied.

from a back-level database archive may only apply log

System Action: If you reply 1(YES), the database

archives up to the last log archive before this switch to

manager will switch the LOGMODE to L and apply all

LOGMODE=A.

applicable log archives as if you had started the

System Action: Database initialization continues.

application server with LOGMODE=L. If you reply

0(No), the database manager will issue message

Operator Response: No action is required if the

ARI0264D.

LOGMODE switch from L to A is desired. Otherwise,

end the application server and restart it with the

Operator Response: Reply 1(YES) if you want any log

desired LOGMODE.

archives applied to the database just restored. Reply

0(No) if you do not want these log archives applied.

ARI0244E To continue with LOGMODE=L, you

must first perform an initial database

ARI0248E No operand on command.

archive.

Explanation: The operator or ISQL terminal user

Explanation: You have been running with a

entered a COUNTER or RESET command without

LOGMODE other than L. If you want LOGMODE=L,

specifying either * or the counter names.

you must first perform an initial database archive since

System Action: The command processing is ended.

the log indicates that there is no database archive upon

which a log archive can be based. A cold log resets

User Response: Reenter the command and specify

LOGMODE to Y because a COLDLOG ends all current

either * for all counters or specific counter names for

restore sets.

the desired counters.

System Action: The application server ends.

Operator Response: See User Response.

Operator Response: Start the application server with

LOGMODE=Y and take a database archive. Then,

ARI0249E parameter is an invalid RESET or

restart the application server with LOGMODE=L.

COUNTER parameter.

Explanation: The operator or ISQL terminal user

ARI0245E Warning: Do not do a user-archive until

entered a COUNTER command or RESET command

you correct discrepancies in the

with an operand value that was not a system counter

directory.

name or a valid reset parameter.

Explanation: The SQLEND UARCHIVE command

System Action: The name is bypassed by the

was entered with the DVERIFY parameter. The

command processor. Any valid counters following the

preceding messages display the discrepancies found in

invalid name will be displayed or reset.

the directory.

User Response: Check the spelling of the submitted

System Action: The application server ends.

name. Reenter the command with the correctly spelled

counter name or reset parameter. Issue COUNTER * for

Operator Response: Refer the message to your system

a list of all acceptable counter names.

programmer.

You cannot reset the DASDIO, DASDREAD, and

System Programmer Response: Make note of the

DASDWRIT counters because they are sums of other

information given in the preceding messages and refer

counters.

to the DB2 Server for VSE & VM Diagnosis Guide and

Reference for recovery procedures for directory

To reset the values displayed by the SHOW STORAGE

verification errors.

command, enter RESET HIGHSTOR. (HIGHSTOR is not a

counter and is not reset by RESET *.)

ARI0247D You are in the restore process. There are

Operator Response: See User Response.

log archives that you could use in this

process but LOGMODE=A. Do you

ARI0250D The above information describes the

want LOGMODE=L instead? Enter

next log archive to be used in the

1(Yes) to change LOGMODE to L, or

restore process. Enter either:

0(No) to keep LOGMODE=A.

CONTINUE to restore this log archive,

Explanation: You have started the application server

STOP SYSTEM to interrupt this restore

with STARTUP equal to R, U, or F and LOGMODE

process or END RESTORE to end this

equal A. The database has been restored. There are log

restore process.

archives which could be applied to the database. The

Explanation: Messages ARI0239I and ARI0252I contain

database manager is giving you the chance to switch

a description of the next log archive file to be applied.

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

This is the same information given at the time the log

history area. This prompt gives you the chance to

archive file was created. You are given three options

terminate the database manager if you wish to mount a

with this message:

different database archive.

1. Reply CONTINUE: The log archive identified in

System Action: If you reply IGNORE and there are no

message ARI0239I will be applied to the database. If

log archive files that go with this database archive file,

the archive is on tape, and ARI0252I specifies a tape

message ARI0264D is issued. If you reply IGNORE and

cuu, mount the tape before replying.

there are log archive files to go with this database

2. Reply STOP SYSTEM: The restore process is

archive file, these log archive files are applied. If you

suspended and the application server stops. The

reply CANCEL, the application server terminates to

restore process will start where it left off if you

allow you to mount a different database archive file.

warm start the application server with

Any other reply causes message ARI0052E to be

STARTUP=W and LOGMODE=L.

displayed and message ARI0251D to be redisplayed.

3. Reply END RESTORE: The restore process is ended.

Also, you will never be able to restore the

Note: At this time, the database archive mounted has

remaining log archives to the database archive you

replaced your database files.

have just restored. This is because the remaining log

Operator Response: Reply IGNORE if you wish to

archives are no longer a part of the restore set for

continue with the restore of the database archive

this database archive in the history area. However,

volume currently mounted. Reply CANCEL if you wish

if you go to a back level database archive, these log

to terminate the application server and mount a

archives may be applied as usual.

different database archive to be used in the restore

System Action: One of the following actions will

process.

occur:

v Reply was CONTINUE: The restore process

ARI0252I

Medium: Tape cuu

continues.

Explanation: ARI0252I follows ARI0239I. A log or

v Reply was STOP SYSTEM: The restore process is

database archive is about to be created, or the next log

suspended. The application server stops.

archive file is about to be read during the restore

v Reply was END RESTORE: If you have not applied

process.

the first log archive file to your database archive file,

During a log archive:

you will receive message ARI0264D. If you have

applied at least one log archive file to your database

The address shown is the most recent tape address

archive file, the database manager will complete

specified for ARILARC or ARILALT at startup, log

initialization and begin application processing.

restore, or log archive; if unspecified so far, it is "???".

Operator Response: In all but very special cases, you

During a log restore:

will reply CONTINUE. As mentioned in the

The address shown if the most recent tape address

Explanation, you may need to mount a tape before

specified for ARILARC or ARILALT at startup, log

making this reply. You may want to reply STOP

restore, or log archive. If unspecified so far, it is "???".

SYSTEM if you are using an EXTEND input file and

need to change the EXTEND commands. There is no

System Action: The archive or restore process

danger in using STOP SYSTEM. The only case in which

continues.

you may want to use END RESTORE is if you want to

use the log archives up to a certain point and never

Operator Response: Respond to the messages

restore the remaining log archives. END RESTORE

following ARI0252I.

should only be used in extreme cases as it could result

in a permanent loss of data. Do not reply END

ARI0253D The database archive mounted is not

RESTORE without consulting your system programmer.

known to the database manager. Enter

System Programmer Response: Be sure that you

either: IGNORE to continue, or

understand the consequences of replying END

CANCEL to restart the restore process.

RESTORE.

Explanation: The database archive that was just

restored does not have a record in the history area. This

ARI0251D The database archive currently mounted

could be caused by:

is not the most recent database archive

1. The record of this database archive was written

known to the database manager. Enter

over. If it was your most current database archive,

either: IGNORE to continue, or

you should have gotten message ARI0258E as a

CANCEL to restart the restore process

warning of this. If it was a back level database

with the most recent database archive.

archive, you would get no warning.

Explanation: The database archive that was just

restored is not the latest database archive record in the

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

2. You did a COLDLOG (STARTUP=L) sometime after

ARI0256E You must specify ROLLBACK by

taking this database archive which destroyed the

DBSPACE dbspace-number in the extend

history area for this database.

file.

This message gives you the chance to terminate the

Explanation: A ROLLBACK COMMITTED WORK

application server if you wish to mount a different

command was specified for a logical unit of work

database archive file.

containing one or more DROP DBSPACE or DROP

TABLE commands and one or more of the following

System Action: If you reply IGNORE, message

occurred:

ARI0264D is issued. If you reply CANCEL, the

v The DBSPACE control keyword was submitted but

application server terminates.

did not specify all of the DBSPACEs which are

Operator Response: Reply IGNORE if you wish to

affected by the DROP commands.

continue with the restore of the database archive

v The DBSPACE control keyword was not submitted

volume currently mounted. Reply CANCEL if you wish

with the command.

to terminate the application server and mount a

v The ROLLBACK COMMITTED WORK command

different database archive to be used in the restore

contained the DBSPACE control keyword with other

process.

ANDed control keywords (USERID, TIME, or DATE).

ARI0254I

The database manager is initiating a log

This message may be issued more than once for the

archive of the active log. When the log

same DBSPACE.

archive is complete, the database

manager will process the database

Note: DBSPACE 1 (catalog DBSPACE) need not be

archive request.

specified on the command although the DROP

commands update the catalog.

Explanation: A database archive has been requested

and LOGMODE=L but the active log has not been

archived. Therefore, the database manager has initiated

dbspace-number is a DBSPACE number of the DBSPACE

a log archive to ensure that log archives will remain

affected by a DROP DBSPACE or DROP TABLE

useful in recovering to this point.

command.

System Action: Processing of the log is completed and

Note: This log archive will become the last archive in

summary statistics are displayed. Message ARI0213D is

the restore set for the database archive taken

not displayed and processing is ended.

prior to this database archive request.

Operator Response: Refer this message to your

System Action: The database manager has

system programmer.

automatically initiated an on-line log archive operation.

It will then process the database archive request.

System Programmer Response: Use the summary

information to determine if the specified actions are to

be done. If so, include each DBSPACE specified in this

ARI0255I

The database manager is initiating a log

message (ARI0256E) in a ROLLBACK COMMITTED

archive of the active log. When it is

WORK command. Then, restart extended database

completed, the restore process will

initialization.

continue.

Explanation: A database restore has been requested

ARI0257I

Format 1:

and LOGMODE=L but the active log has not been

New LUWs and the log archive of the

archived. Therefore, the database manager has initiated

active log cannot continue until n

a log archive.

non-R/O active LUWs are completed.

Format 2:

Note: This log archive will become the last log archive

New LUWs and the switch to the

in the current restore set.

inactive log cannot continue until n

non-R/O active LUWs are completed.

System Action: The database manager will

automatically initiate an on-line log archive operation.

Explanation: Format 1 is displayed when a log archive

The database manager will then resume restore

of the active log has been requested either through a

processing.

command or due to the ARCHPCT value being

exceeded. Format 2 is displayed when alternate logging

is enabled and the ARCHPCT value is exceeded. Both

the log archive of the active log and the switch to the

inactive log require that there be no logical units of

work active at the time that the log archive or the

switch to the inactive log completes. This is so that the

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

logical units of work do not span log archives. The

database to its current state until you have taken a

database manager displays this message to inform the

database archive.

operator of how many logical units of work are active

at the time of the log archive or log switch request.

ARI0259I

No logical unit of work started at or

System Action: When a log archive of the active log is

after the time specified in the

requested, or when an attempt is made to switch to the

ROLLBACK command.

inactive log, the database manager prevents new logical

Explanation: This information message may be

units of work from starting. Users that try to start a

displayed when TIME is used as a control keyword in

new logical unit of work will be in a lock wait until the

the EXTEND input file. It will be followed by message

log archive begins or until the switch to the inactive log

ARI0210I or message ARI0212I.

is completed. Logical units of work that are active

when the log archive is requested or when an attempt

System Action: Processing continues.

is made to switch to the alternate log are allowed to

System Programmer Response: Check the control

complete. In most cases, there is only a slight delay

keywords in the EXTEND input file and adjust if

before the log archive begins or the switch to the

necessary. See message explanations for the

inactive log begins. If, however, there are long running

accompanying messages.

logical units of work, the delay will be longer. A logical

unit of work may be long enough so that the

SLOGCUSH value is reached. In this case, the database

ARI0260I

The restore set for this database archive

manager will start log overflow processing and rollback

is as follows:

the longest-running logical units of work to free log

Explanation: This message is displayed every time a

space.

database restore completes. It is followed by messages

Operator Response: If you find that a long running

ARI0238I and ARI0261I which identify the set of

logical unit of work is holding up the log archive or

database archives and log archives to be used with the

switch to the inactive log, you can use the SHOW

database archive just restored.

operator commands to determine which user is

System Action: Message ARI0238I follows.

delaying the start of the log archive. You may wish to

use the FORCE command to end those logical units of

work.

ARI0261I

[-->] log archive - {tape file-ID mm-dd-yy

hh:mm:ss}

ARI0258E The log indicates that you are in danger

Explanation: The message identifies the next log

of losing the record of your latest

archive file in the restore set.

database archive. To prevent this, you

must do a database archive.

Message ARI0252I displayed this information when the

log archive file was created. The information displayed

Explanation: The database manager keeps track of

should have been recorded externally on the tape.

information such as database archives, log archives,

Message ARI0252I will display this information again

logmode switches, coldlogs, switching from an active to

when the restoration process is ready to read this log

inactive log, and restores. This is so that the database

archive file.

manager can be sure that the database and log archive

files used for restore are valid and in the correct order.

Note: The format of the displayed date is either

However, there is a limit on the number of records the

mm-dd-yy or dd-mm-yy. The format is chosen

database manager can store at any one time. When the

when VSE is IPLed. The default format is

limit is reached, the oldest records are lost. This is not a

mm-dd-yy.

problem unless the record of the last database archive

taken is lost. This message is issued when the latest

System Action: ARI0261I is issued for each log

database archive is within 10 records of being written

archive file to be applied to this database.

over and every time a record is stored after that until

the record of the latest database archive is actually

ARI0262E The record of your latest database

written over. At this point, message ARI0262E is issued.

archive has just been lost. You must

System Action: Processing continues.

archive the database to restore your

database to its current state.

Operator Response: Refer this message to your

system programmer.

Explanation: The database manager keeps track of

information such as database archives, log archives,

System Programmer Response: Be sure to take a

logmode switches, coldlogs, switching from an active to

database archive before receiving this message a total

inactive log, and restores. This is so that the database

of 10 times. After a record of your latest database

manager can be sure that the database and log archive

archive is lost, you will not be able to restore your

files used for restore are valid and in the correct order.

However, there is a limit on the number of records the

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

database manager can store at any one time. When the

System Action: If you reply IGNORE, the database

limit is reached, the oldest records are lost. This is not a

manager will assume that you have performed a

problem unless the record of the last database archive

COLDLOG prior to restore and log recovery, and the

taken is lost. This message is issued when the latest

restore process will continue.

database archive has been written over.

If you reply CANCEL, the application server will

System Action: Processing continues.

terminate.

Operator Response: Refer this message to your

Operator Response: If you have performed a

system programmer.

COLDLOG immediately preceding the restore, then

reply IGNORE. If you have not, then reply CANCEL,

System Programmer Response: Take a database

execute the COLDLOG function (STARTUP=L) and

archive as soon as possible to ensure that if you need

then start the application server with STARTUP=W. The

to restore the database that you will be able to.

COLDLOG function is performed by the SQLLOG

EXEC. See the DB2 Server for VSE System Administration

ARI0263D To direct the log archive to tape, enter

manual for more information on the SQLLOG EXEC.

TAPE followed by the tape address and

the catalog filename. (CAT.FILE-ID =

ARI0273I

Formatting directory disk.

catalog-file-ID).

Explanation: The application server has been started

Explanation: A log archive is being created and the

with STARTUP=R, and the directory disk is being

operator is prompted to change, or has indicated a

formatted.

change is necessary, to the destination of the archive

specified in ARI0252I. ARI0263D requests that this new

System Action: The restore process continues.

destination be specified. The format of this identifier is

described under ARI0252I.

ARI0274I

Implicit COMMIT failed for userid to

System Action: If the operator response is valid, the

avoid deadlock or because of system

database manager displays it in ARI0252I (preceded by

request. A ROLLBACK of the LUW will

ARI0239I), allowing the operator to confirm that this is

occur.

the intended destination. If the response was invalid,

Explanation: User userid did not issue a commit work

an error message is displayed and ARI0263D is

command before ending, and the database manager

redisplayed.

started implicit commit processing for that user. During

Operator Response: To have the log archive written to

this processing, it was found that the work performed

tape, enter TAPE followed by the tape address (cuu).

by the user had to be rolled back due to a system

request (such as log full, out of lock request blocks,

The file identifier cannot have been used already for a

etc.) or to avoid a deadlock situation.

log archive. It is recommended that you use the default

naming convention.

System Action: All database changes for this logical

unit of work have been rolled back.

ARI0264D If a COLDLOG was not performed

Operator Response: Inform user user-id that the work

immediately preceding this restore

has not been committed, but rolled back. User user-id

process, enter CANCEL, perform

should inform the application developer that this

COLDLOG, and start the database

condition occurred.

manager with STARTUP=W. Otherwise,

User Response: Recover the work that had been rolled

enter IGNORE.

back. Also, it is strongly recommended that a commit

Explanation:

work command be issued by applications prior to

application termination. If this is done, the application

v You replied IGNORE to message ARI0251D or

could indicate to the user when a COMMIT WORK is

message ARI0253D, or

actually completed.

v You replied END RESTORE to message ARI0250D

before applying the first log archive file in your

restore set, or

ARI0276E Log is full.

v An end of restore set was found before the end of

Explanation: The database log is full. Overflow

the active log.

procedures, designed to prevent this from happening,

have failed.

Unless you executed a COLDLOG immediately

System Action: The application server is ended with a

preceding the STARTUP=R, your current log is out of

limit error. Logical units of work in progress at the time

synchronization with the database just restored. This

of the termination will be undone when the application

message gives you a chance to COLDLOG before the

server is warm started.

log is applied to the database.

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

Operator Response: Notify your system programmer

Note: The operator can mount the correct volume on

concerning the size of the log Also, it is possible that

the same or another tape unit and reply with its

one logical unit of work has been started and has not

cuu to message ARI0295A.

been committed or rolled back; that is, it inadvertently

Operator Response: Determine why the correct

remains active. This active logical unit of work prevents

volume was not mounted, mount the correct volume,

reuse of database log space.

and reply to message ARI0295A with the tape unit cuu.

You must always warm start the application server

If you are unable to determine the cause of the

(initialization parameter STARTUP=W) to recover the

problem, contact your system programmer.

logical units of work in progress when the system

terminated. You can then, after a "clean" application

System Programmer Response: Ensure that archive

server shutdown, redefine the logs and start the

file volumes are properly identified so that you know

application server with the new log file definitions

which volumes belong to a database archive and the

(initialization parameter STARTUP=L) to run with the

order in which they must be mounted. Ensure that

larger logs.

your system operator follows procedures that allow

proper identification at archive creation time and

System Programmer Response: You can minimize the

proper volume mounting at archive restore time. You

space required in the log by running with

should use extensive standard volume and file label

LOGMODE=N or LOGMODE=Y (rather than

checking and creation procedures to assist in this

LOGMODE=A). This is especially appropriate when

identification and verification process.

loading or reloading the database (including DBS utility

DATALOAD and RELOAD operations) and when

running other applications that make mass updates to

ARI0278E Unexpected EOF on archive input file

the database. If you are already doing this and are

[cuu].

encountering this problem, consider redefining the logs

Explanation: During a restore from archive, one of the

with a larger size.

following occurred:

Switching log modes and redefining the logs are

v The database manager encountered end-of-file on the

described in the DB2 Server for VSE System

database archive file before all data required to

Administration manual.

restore the database directory and DBEXTENTs was

read.

ARI0277E Archive input file cuu does not contain

v The database manager encountered end-of-file on a

a DB2 Server for VSE identifier.

log archive before all data required to restore the

archived DB2 Server for VSE log was read.

Explanation: The volume mounted on tape unit cuu in

response to message ARI0295A is not a DB2 Server for

cuu identifies the tape unit containing the database or

VSE database archive tape.

log archive file. No cuu is specified for a log archive file

being restored from disk. Possible causes include:

Possible causes include:

v A DB2 Server for VSE or VSE system error occurred

v The mounted (and opened) volume for file name

that caused database or log archive file records to be

ARIARCH does not contain a DB2 Server for VSE

lost.

database archive file.

v In mounting the volumes of a multi-volume archive

v The mounted (and opened) volume for file name

file, the operator mounted the first volume correctly,

ARIARCH is a DB2 Server for VSE database archive

but then mounted the last volume before mounting

volume, but is not the first volume of a multi-volume

one or more of the intermediate volumes. This error

archive file. This can occur only if you do not request

can occur only if you omit the volume-sequence-

VSE SAM open processing to check the file’s volume

number parameter from the ARIARCH (database

sequence number.

archive) or ARILARC/ARILALT (log archive) TLBL

Job Control statement, or if the operator was notified

Note: The database directory file has been reformatted.

of a volume sequence number error and chose to

The database can only be recovered by a

ignore it.

successful archive restoration or by rebuilding

the database using the database generation

System Action: The database or log archive file is

process.

closed and dynamically unassigned, and the

application server stops. Note that the database has

System Action: The archive file is closed and

been only partially restored and is not usable.

dynamically unassigned. Message ARI0295A is

displayed again to allow the operator to mount the

Operator Response: If the error occurred while

correct volume and continue the restore process. If the

restoring a database archive file and you can determine

dynamic unassign fails, message ARI0298E is displayed

the cause of the error, restart the application server

and the application server terminates.

with the STARTUP=R or F initialization parameter to

redo the database restore process.

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

If the error occurred while restoring a log archive file

Operator Response: Refer this message to your

and you can determine the cause of the error, warm

system programmer.

start the application server (STARTUP=W). It will

System Programmer Response: You have either:

resume the restore process with the current log archive

file (the one which encountered this error).

v Accidentally attempted to restore a database from an

archive copy that is not the most recent archive copy,

Otherwise, contact your system programmer.

System Programmer Response: Ensure that the

v You have failed to execute the COLDLOG function

system operator knows which database archive file

before attempting to restore the database using a

volumes and log archive file volumes (if using log

back-level archive copy.

archiving) to mount and the order to mount them.

You must either:

If the error occurred on a database archive file, ensure

that the ARIARCH TLBL job control statement contains

v Rerun the database restore process using the most

the volume-sequence-number parameter (to ensure that

recent archive copy of the database, or

the volumes are not mounted out of sequence). Also

v Run the COLDLOG function before running the

ensure that the operator does not ignore volume

database restore process using the back-level archive

sequence number error messages. You should retry the

copy. If you intended to restore the database from a

restore process. If the error persists, you will not be

back level archive copy and forgot to perform the

able to use this database archive file.

COLDLOG function, you can now perform the

COLDLOG function and then restart the application

If the error occurred on a log archive file, ensure that

server for normal processing (if you are sure that

the ARILARC and ARILALT TBL job control statement

you have applied the correct back level archive

contains the volume-sequence-number parameter (to

copy).

ensure that volumes are not mounted out of sequence).

Also, ensure that the operator does not ignore volume

sequence number error messages. You should try to

ARI0280A Previously LOGMODE was

resume the restore process with the current log archive

A(ARCHIVE) and now LOGMODE=&1.

file by warm starting the application server

To restart with LOGMODE=&1. perform

(STARTUP=W). If the error persists, you will not be

shutdown with ARCHIVE unless an

able to use this log archive file.

archive has just been taken, perform

COLDLOG, and restart with

Refer to the information about how to restart from a

LOGMODE=&1.

database restore operation in the DB2 Server for VSE

System Administration manual for recovery procedures

Explanation: This message is issued to protect against

when a database or log archive file cannot be

making a previous DB2 Server for VSE (or any type) of

processed.

user archive useless. To run with LOGMODE=N or

LOGMODE=Y, after running with LOGMODE=A,

follow the procedure given in the message.

ARI0279E Archive input file is not current. No

COLDLOG is issued.

Note: This message can occur if:

Explanation: During a database restore from archive,

1. You last ran the database manager with

the database manager determined from its log that:

LOGMODE=Y and you issued an SQLEND

v The archive copy was not the most recent archive

ARCHIVE or SQLEND UARCHIVE

copy of the database, and

command. These commands internally

v The COLDLOG function was not performed

change the current LOGMODE to A if the

(COLDLOG is performed by starting the application

current LOGMODE is Y.

server with the SYSMODE=S and STARTUP=L

initialization parameters).

You last ran the database manager with

LOGMODE=Y, issued an SQLEND, then ran

You cannot restore a database from an archive copy

SQLADBEX, specifying ARCHIVE or

that is not the most recent archive copy of the database

UARCHIVE, which internally changes the

unless you immediately precede this task with the

current LOGMODE to A if the current

COLDLOG function. Refer to the DB2 Server for VSE

LOGMODE is Y.

System Administration manual for information on

2. You then restarted the application server with

restoring a database.

LOGMODE set to Y or N. Note that

System Action: The application server terminates. The

LOGMODE=Y is the default.

database has been updated to reflect the contents of the

archive file, but it may not be in a “current and

consistent state” because the updates in the DB2 Server

for VSE log have not been applied to the database.

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

In both of the above circumstances, performing a

reduced by the required amount to cause one

shutdown with archive is not required to continue with

checkpoint to be taken.

LOGMODE=Y, since an archive has just been

System Action: Processing continues. The value n (in

performed.

pages) is used to cause a checkpoint to be taken.

System Action: The application server is ended.

Operator Response: Unless this message is expected,

Operator Response: If you have started the

give it to your system programmer.

application server with an incorrect LOGMODE value,

System Programmer Response: You may wish to

correct the LOGMODE value and restart the application

change the CHKINTVL database initialization

server. Otherwise, restart the database manager with

parameter to avoid this message.

LOGMODE=N or LOGMODE=Y after performing the

procedure outlined in the message. The archive step

may be skipped if this message is caused by either of

ARI0286I

RESTORE cancelled by operator

the two scenarios described in the above note.

request.

COLDLOG is performed by starting the database

Explanation: The operator replied CANCEL to

manager with the database initialization parameter

message ARI0295A while restoring the database.

STARTUP=L.

Message ARI0295A is displayed (to ensure that the tape

is mounted) before opening the database archive file or

ARI0281I

LUW REDO is completed.

before opening a log archive file (restoring with

LOGMODE=L) when the tape cuu to be used is

Explanation: The logical units of work in the current

unknown.

log which required redoing at startup time have been

redone by the recovery procedure.

Unless STARTUP=F was specified and the database

archive file cancelled, the database has been partially

System Action: Initialization continues.

restored (or reformatted).

System Action: The application server ends.

ARI0282I

LUW UNDO is completed.

Operator Response: Refer to message ARI0295A

Explanation: The logical units of work in the current

(where you replied CANCEL).

log which required undoing at startup time have been

undone by the recovery procedure.

ARI0287I

ARCHIVE command rejected because a

System Action: Initialization continues.

{database | log} ARCHIVE is being

performed.

ARI0283I

Log analysis is complete.

Explanation: An ARCHIVE command was entered by

Explanation: The current log has been scanned

the DB2 Server for VSE operator while either a log

successfully by the recovery procedure to determine

archive or a database archive was being taken.

those logical units of work which require redoing or

System Action: The log archive or the database

undoing at startup time.

archive that is being taken will be completed, and the

System Action: Initialization continues.

ARCHIVE command is ignored.

ARI0284I

SHOW LOG command is rejected

ARI0288I

ARCHIVE command rejected because

because LOGMODE = N.

archiving is not enabled.

Explanation: A SHOW LOG command was entered by

Explanation: An ARCHIVE command was entered by

the system operator or the ISQL terminal user while

the system operator, but the database manager is not

running with LOGMODE=N.

running with LOGMODE=A or LOGMODE=L.

System Action: The command is ignored.

Note: It is valid to enter SQLEND ARCHIVE if

archiving is not enabled (LOGMODE=Y).

ARI0285I

Checkpoint interval is reduced to n.

Note: SHUTDOWN is a valid synonym for SQLEND.

Explanation: The checkpoint interval is the number of

log pages which will be written between automatic

The ARCHIVE command requires a LOGMODE of A or

checkpoints. This interval is specified by the database

initialization parameter CHKINTVL. At database

initialization, an analysis of the checkpoint interval and

System Action: The database manager ignores the

the size of the log is made to determine if at least one

ARCHIVE command.

checkpoint will be taken before end of log or log wrap.

Operator Response: If you were instructed to enter

If CHKINTVL will not cause one checkpoint, it is

the ARCHIVE command, notify your system

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

programmer. Otherwise, no action is required.

ARI0293I

Archive is starting.

System Programmer Response: Tell the operator not

Explanation: A database or log archive is beginning.

to enter the ARCHIVE command if LOGMODE is not

A or L and do not enter the SQLEND ARCHIVE

System Action: The database manager continues the

command if the LOGMODE is not Y, A, or L.

archive process.

ARI0289I

Restoring directory disk.

ARI0294A Archive file [cuu] {read|write} failed.

Reason Code = nn. Return Code = nn.

Explanation: This message occurs when the

application server has been started with STARTUP=R,

Explanation: While attempting to read or write a DB2

or F, the archive input volume has been readied, and

Server for VSE database or log archive file, an access

the directory file is being restored.

error occurred. cuu is the address of the tape device on

which the error occurred; it is not displayed for an

System Action: The restore process continues.

error on a disk device.

If the message text specifies WRITE, the database or log

ARI0290I

Format 1:

archive file has not been completed; it cannot be used.

Restoring data disk.

After the I/O error condition is corrected:

Format 2:

v If this error occurred while creating a log archive

Restoring dbextent <extent-number> of

during the database restore process, restart the

<total-extents>.

restore process with the same STARTUP parameter

Format 3:

value. If you user-restored the database, you do not

Extent <extent-number> of <total-extents>

have to repeat that process but you must restart with

is a deleted dbextent. No action taken.

STARTUP=U.

Explanation: The application server has been started

v If this error occurred while creating a log archive file

with STARTUP=R or F, the archive input volume has

with the LARCHIVE operator command, reenter the

been readied, the directory disk has been restored, and:

LARCHIVE operator command.

v FORMAT 1: the restoring of the data disks

v Otherwise, restart the application server and if

(DBEXTENTs) is in process.

applicable, reinitiate the archive process.

v FORMAT 2: the restoring of DBEXTENT

<extent-number> of <max-extent> is in progress.

If the message text specifies READ, a database or log

v FORMAT 3: dbextent <extent-number> of

archive file was being used to restore the database.

<max-extents> was previously deleted and will not be

(The application server had been started with the

restored.

initialization parameter STARTUP=R, F, or U for

database recovery) The database is only partially

System Action: The database manager proceeds with

restored; it can only be recovered by a successful

the restore process.

archive restoration (described below) or by rebuilding

the database (except for file definition) using the

ARI0291I

System restore from directory and data

database generation process.

disk(s) of database archive is completed.

The Reason Code value is the Primary Error Code. The

Explanation: The application server has been started

Return Code value is the Secondary Error Code. For

with STARTUP=R or F and the database disks restore

further explanation, look up the displayed error codes

process is complete. The database archive tape unit is

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

now available for other purposes.

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

System Action: The database manager continues with

System Action: If this error occurred due to a log

initialization. The archive volumes can be removed

archive initiated using the LARCHIVE operator

from the system and stored until needed.

command, the log archive process ends, but the

database manager continues normal operation. For all

ARI0292I

Archive is completed.

other cases, the application server ends.

Explanation: A database or log archive has completed.

Operator Response: For corrective action, look up the

If the archive was to tape, the archive tape unit is now

displayed error codes under either Chapter 21,

available for other purposes.

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

ERRORS” in the HELP text.

System Action: Processing continues.

If an archive file was being written, restart the

Operator Response: If the archive was to tape, the

application server or the LARCHIVE operator

archive volumes can be removed from the system and

command according to the situation described under

stored until required for the restore process (or until

Explanation. This recovery action is described in the

they are no longer required).

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

DB2 Server for VSE System Administration manual.

after message ARI0277E, ARI0296A, or ARI0297A, take

the corrective action suggested by that error message.

If an error occurred when reading a database archive

file and if you are able to use the archive file which

Select an available unassigned tape unit. Mount and

previously failed, start the application server with the

ready the first (or only) volume of the archive file.

initialization parameter STARTUP=R or F to restore the

Enter the cuu of the selected tape unit.

database and continue normal processing.

If a tape unit is not available or if the error condition

If an error occurred while reading a log archive file,

from message ARI0277E or ARI0296A cannot be

warm start the application server. It will resume the

corrected, enter CANCEL to end the restore process

restore process with the log archive that failed.

and the application server.

If a database or log archive file cannot be read (for

If you reply CANCEL for a database archive file, you

example, uncorrectable media error), refer to the DB2

must restart with STARTUP= R or F for database

Server for VSE System Administration manual.

recovery.

System Programmer Response: See Operator

If you reply CANCEL for a log archive file, you should

Response.

warm start the application server (STARTUP=W) and

continue the restore process with the current log

archive file. The current log archive file is the one you

ARI0295A Ready archive input volume. Enter

were requested to mount.

CANCEL or the cuu.

Explanation: Restoring a database from archive files

ARI0296A Archive file [cuu] ASSIGN or OPEN

has been begun by starting the application server with

failed. Reason Code = nn. Return Code

STARTUP=R, F, or U.

= nn.

The database manager is prompting the operator to

Explanation: A DB2 Server for VSE database archive

ensure that the correct database or log archive tape is

or restore from archive is in progress. An error

mounted and readied on tape unit cuu. The operator is

occurred while attempting to dynamically assign and

being requested to respond by entering the cuu on

open the archive output file or restore input file on tape

which the tape has been mounted or CANCEL to

unit cuu.

terminate.

The Reason Code value is the primary error code. The

If the archive file could not be dynamically assigned

Return Code value is the secondary error code. For

and opened successfully, message ARI0296A was

further explanation, look up the displayed error codes

displayed to indicate the error condition. This message

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

was redisplayed to give the operator the opportunity to

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

correct the error and restart the archive restore process.

If the cuu value entered in response to this message

Note: Unless STARTUP=F was specified and the

was not valid, message ARI0297A was displayed to

request was for a database archive file, the

indicate the error condition. This message was

database has been partially restored (or

redisplayed to give the operator the opportunity to

reformatted).

enter a valid cuu.

System Action:

If the database archive file did not contain a DB2

v If REASON = 36 and CODE = 8, 12, 16, 48, or 52:

Server for VSE database archive, message ARI0277E

Message ARI0297A is displayed. The system reissues

was displayed and the file was closed and dynamically

the archive or restore mount message (either

unassigned. This message was redisplayed to correct

ARI0295A or ARI0299A).

the error and restart the database restore process.

v All other REASON and CODE combinations: For

restore, message ARI0295A is reissued. For a log

Note: Unless STARTUP=F was specified and the

archive initiated by the LARCHIVE operator

request was for a database archive file, the

command, the log archive ends and the database

database has been partially restored (or

manager continues normal operation. For all other

reformatted).

archive output files, the application server ends.

System Action: If the operator responds with

Operator Response: For corrective action, look up the

CANCEL, the restore is canceled and the application

displayed error codes under either Chapter 21,

server is ended.

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

If the operator responds with cuu, tape unit cuu is

ERRORS” in the HELP text.

dynamically assigned to the archive input file; it is

If the application server stops while creating a log

opened (with rewind) for archive restore input and the

archive during the restore process, restart the process

restore process proceeds.

after taking corrective action for the error.

Operator Response: If this message was redisplayed

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

If the application server stops while creating a normal

If the entire database was being restored from a

database or log archive, warm start the application

database archive and message ARI0277E was not

server (STARTUP=W) after taking corrective action for

displayed, normal processing continues.

the error. Then, take the action you took previously to

If a log archive was being read during the restore

initiate the database or log archive. If the archive was

process, normal processing continues.

initiated by the database manager, it will be initiated

again.

Operator Response: For corrective action, look up the

displayed error codes under either Chapter 21,

If an LARCHIVE operator command request failed and

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

the database manager continued operating, you can

ERRORS” in the HELP text.

retry the LARCHIVE command after correcting the

cause of this error message.

Then, if a log archive was being created during the

restore process, restart the process.

ARI0297A Response to archive prompt is not valid.

Then, if this error occurred due to a log archive

initiated by the LARCHIVE operator command, reenter

Explanation: An archive prompt message has been

the LARCHIVE operator command to re-initiate the log

issued, but the operator’s reply was not valid.

archive process.

If ARI0263D has been issued, the response has a syntax

Then, if a database or log archive was being created,

error. Possible causes:

warm start the application server, If desired, reschedule

v No reply was entered.

the archive creation by using the ARCHIVE,

v For ARI0246D, CHANGE or CONTINUE was

LARCHIVE, SQLEND ARCHIVE, SQLEND

misspelled.

LARCHIVE, or SQLEND UARCHIVE operator

v For ARI0263D, TAPE was misspelled.

command. This recovery action is described in the DB2

System Action: The database manager issues the

Server for VSE System Administration manual. If the

prompt message again and asks for valid input.

database manager implicitly initiated the database or

log archive due to the ARCHPCT initialization

Operator Response: Ensure that the input being

parameter, it will do so again when you warm start the

entered is valid, and enter it in response to the prompt

application server.

message.

Note: SHUTDOWN is a valid synonym for SQLEND.

ARI0298E Archive file [cuu] CLOSE failed. Reason

Code = nn. Return Code = nn.

If the database was being restored from a database

archive and message ARI0277E precedes this message,

Explanation: The database manager was creating or

take the corrective action as implied by these two

reading a database or log archive file. An error

messages. Restart the database archive process.

occurred when the database manager attempted to

close the database or log archive file.

If the database was being restored from a database

cuu is the address of the tape device on which the error

archive and message ARI0277E does not precede this

occurred; the address will not be displayed for an error

message, you can proceed with whatever activity you

on a disk device.

had planned. The database has been successfully

restored from the archive copy.

Note: Due to this error, tape unit cuu has not been

dynamically unassigned. The tape unit cannot be

No further action is required if the error occurred while

used by the database manager or any other

closing a database or log archive input file during the

partition until the system ends. You may want to

restore process. If there are subsequent log archives to

shutdown the application server if you need to

be read, you will have to use a different tape unit

re-use the tape unit.

because this tape unit has not been dynamically

unassigned. Alternatively, you can reply STOP SYSTEM

System Action: If a log archive file was being created

to subsequent message ARI0250D for the next log

with the LARCHIVE operator command, the log

archive to stop the application server (and get the tape

archive ends and the database manager continues

unit unassigned) and then warm start the application

normal operation. If a database or log archive file was

server to resume the restore process with the next log

being created for any other reason, the application

archive.

server ends. The database or log archive file cannot be

used. The system log indicates that the archive was not

System Programmer Response: See Operator

successful.

Response.

If the database was being restored from a database

archive and message ARI0277E precedes this message,

the application server stops. The database directory file

has been reformatted (the database is not usable).

Chapter 3. ARI0200-ARI0299, ARI2000- ARI2069 DBSS Messages

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

v The system cannot obtain a physical index page. This

ARI0299A Ready archive output volume. Enter the

can result from the ROLLBACK or UNDO of a

cuu for dynamic or 1 for static tape

DROP INDEX, a REORGANIZE INDEX, a deletion

device.

of a row, or an update of a row. It can also result

Explanation: A database or log archive is being

from the REDO of either a CREATE INDEX, an

created for one of the following reasons:

insertion of a row, or an update of a row.

v You entered the ARCHIVE operator command.

v Not enough virtual storage or room in a temporary

DBSPACE exists to recreate an index. The shortage

v You entered the SQLEND ARCHIVE operator

can result from the ROLLBACK or UNDO of either a

command.

DROP INDEX or REORGANIZE INDEX, or from the

v The database manager has implicitly initiated the

REDO of a CREATE INDEX or REORGANIZE

creation of a database archive due to the ARCHPCT

INDEX.

initialization parameter.

System Action: The database manager continues to

The database manager is prompting the operator to

process the ROLLBACK, UNDO, or REDO command

ensure that a tape is mounted and readied on tape unit

without updating the index and marks the index

cuu, or on the tape unit assigned to SYS005. The

invalid.

operator is being requested to respond by entering

Operator Response: Notify your system programmer.

either the cuu number or 1.

System Programmer Response: Contact the owner of

If the cuu entered in response to this message was not

the invalid index. The owner must drop and recreate

valid, message ARI0297A was displayed to indicate the

the index. The system has a limit of 16 invalid indexes.

error condition.

You can find the index name by using the following

SELECT statement:

If 1 was specified, and the logical device SYS005 was

SELECT A.DBSPACENO, B.IID, B.INAME, B.ICREATOR,

not assigned, message ARI2036I was displayed to

A.TNAME FROM SYSTEM.SYSCATALOG A,

indicate the error condition.

SYSTEM.SYSINDEXES B

WHERE A.TNAME = B.TNAME AND

System Action: When the operator responds with cuu,

A.CREATOR = B.CREATOR

tape unit cuu is dynamically assigned to the archive

AND A.DBSPACENO = dbspace-no

output file; it is opened (with rewind) for archive

AND B.IID = index-id

output and the archive process proceeds.

ORDER BY A.DBSPACENO, B.IID

;

If the operator responds with 1, logical device SYS005

is opened (with rewind) for archive output and the

ARI2001I

Warning: The following entities are

archive process proceeds.

invalid.

Operator Response: If the archive is to be written to

Explanation: This is a message heading for a list of

logical device SYS005, mount and ready a scratch tape

invalid entities found during system start up. It is

volume on SYS005 and respond 1 to this message.

followed by the output of the SHOW INVALID

Otherwise, select an available unassigned tape unit.

command. For more information refer to the SHOW

Mount and ready a scratch tape volume. Enter the cuu

INVALID operator command.

of the selected tape unit.

System Action: Processing continues.

If you have one or more tape units assigned to SYS005

Operator Response: Notify and give your console

for this purpose, mount and ready the required scratch

output to your system programmer.

tape volumes, and enter SYS005.

System Programmer Response: Notify the owners of

If SYS005 has no tape unit assigned to it, use the CUU

the invalid indexes and have them drop and recreate

option.

the indexes.

ARI2000E Index index-id in DBSPACE dbspace-no

ARI2002I

Index pages are being reclaimed for

has been marked invalid.

DBSPACE &1.

Explanation: One of the following may have

Explanation: A free index page is required for a

happened during ROLLBACK, UNDO, or REDO

ROLLBACK, UNDO, or REDO work, but there are no

processing:

free pages available. An attempt is being made to

v The system cannot obtain a logical index page. This

reclaim empty or partially empty pages from existing

can result from the ROLLBACK or UNDO of either a

indexes.

DROP INDEX, a REORGANIZE INDEX, a deletion

System Action: If pages are reclaimed successfully

of a row, or an update of a row. It can also result

processing will continue. If no pages are reclaimed the

from the REDO of either a CREATE INDEX, an

index will be marked invalid and processing will

insertion of a row, or an update of a row.

Messages and Codes

DBSS Messages - ARI0200-ARI0299, ARI2000- ARI2069

continue. Message ARI2003I will be issued when the

Operator Response: Start the application server with

page reclaim processing is complete.

LOGMODE=Y and take a database archive. Next,

restart the application server with LOGMODE=A.

Operator Response: Refer this message to your

system programmer.

ARI2010I

WARNING: The database manager

System Programmer Response: Refer to message

terminated abnormally. The log contents

ARI2003I.

is required for recovery. Continuing

with the COLDLOG will erase all log

ARI2003I

The index page reclaim processing is

records and may cause the next startup

finished.

to terminate during UNDO/REDO

processing.

Explanation: A free index page was required for a

ROLLBACK, UNDO, or REDO work, but there were no

Explanation: The last time the application server

free pages available. An attempt to reclaim empty or

started up, it terminated abnormally. The current log is

partially empty index pages has completed.

required to recover the system to the point of failure,

either by warmstarting the database or by restoring the

System Action: If pages were reclaimed successfully

last database archive.

processing will continue. If no pages were reclaimed

the index will be marked invalid and processing will

System Action: Processing continues. The user will be

continue.

given an opportunity to cancel the COLDLOG by

message ARI0920D.

Operator Response: Refer this message to your

system programmer.

User Response: If you have not redefined the log

datasets, cancel the coldlog in response to message

System Programmer Response: This message

ARI0920D. Warm start the database to recover up to

indicates that the DBSPACE specified is running short

the point of failure, or restore the database from a

of index pages. Index page reclaiming may adversely

previous archive.

affect performance. At this time the SHOW DBSPACE

command should be issued to monitor index page

consumption. If there are still relatively few free index

ARI2011I

Formatting data disk(s).

pages, then action should be taken to free some pages.

Explanation: The application server has been started

For more information, refer to the DB2 Server for VSE &

with STARTUP=R and the directory has been restored.

VM Database Administration manual.

The DB2 Server for VSE data disks are being formatted.

System Action: The restore process continues.

ARI2008I

Archive is about to be started.

Explanation: The operator or database administrator

ARI2036I

Logical device has not been statically

requested a database or log archive with one of the

assigned for a DB2 Server for VSE

following commands:

archive.

LARCHIVE

Explanation: The operator entered 1 in response to

SQLEND LARCHIVE

message ARI0299A. Logical device SYS005 is either not

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