DB2 Server for VSE: Messages and Codes

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

ARI0200E Sizes of dual logs are unequal.

Explanation: During database generation (invoking the application server with initialization parameter STARTUP=C) or during log file redefinition/reformatting (invoking the application server with initialization parameter STARTUP=L), dual logging was defined (initialization parameter DUALLOG=Y). The database manager has determined that the two log data sets are not the same size. This is not permitted.

System Action: The application server is ended.

Operator Response: Return the console output with the output listing.

System Programmer Response: You can circumvent this problem by invoking the application server with a single log. To do so, either omit the DUALLOG parameter or specify it as DUALLOG=N.

You can correct this problem by proceeding as follows:

Redefine the VSAM clusters (ESDSs) for the logs so that they are equal in size. They are always equal in size if they are on the same device type and you specify the same primary allocation (CYLINDERS, TRACKS, or BLOCKS). Then reexecute the job.

ARI0201E Storage pool n is full.

Explanation: The physical storage in storage pool n has reached a level at which the system cannot function. If this error was the result of a DROP TABLE or DBSPACE command, then the storage pool did not contain enough shadow pages to process the DROP command.

System Action: In most cases, processing of the SQL statement ends. In some cases, the application server ends.

Operator Response: Return the console output with the output listing.

System Programmer Response: Define an additional VSAM cluster for a new DBEXTENT. Then run the ADD DBEXTENT function to add the DBEXTENT to the storage pool that is full.

Notes:

If ARI0201E occurred during DROP TABLE or DBSPACE processing and the application server ended, you need to check the catalog table SYSDROP after you warm start the application server. If there is an entry in SYSDROP for the table or dbspace that was being dropped when the application server was terminated, any subsequent drop commands may cause the application server to be terminated with message ARI0201E.
To correct this problem, you need either to add a DBEXTENT to the storage pool in which the table's DBSPACE resides, or to reorganize the DBSPACE.
When you add a DBEXTENT to correct this problem, you should next issue an ACQUIRE and then a DROP of any size DBSPACE. This will cause the database manager to clean up any entries in SYSTEM.SYSDROP that were left over during the original DROP TABLE or DBSPACE failure.
For information on how to reorganize the DBSPACE, see the DB2 Server for VSE & VM Database Administration manual.
You may not have to enlarge the storage pool. Under certain conditions, the message ARI0201E occurs when the processing of the current operation has used only half of the storage pool.
A bypass is possible if LOGMODE is not N and the failing operation is one of:

CREATE INDEX DROP TABLE
DROP DBSPACE UPDATE
INSERT DELETE
DATALOAD RELOAD TABLE
RELOAD DBSPACE RELOAD PROGRAM
RELOAD PACKAGE REORGANIZE INDEX
SCHEMA DROP INDEX

Try running the command in single user mode with LOGMODE=N.

ARI0202I Warning: Storage pool n is short of storage.

Explanation: Storage pool n has reached the cushion specified at startup using the database SOSLEVEL initialization parameter (SOSLEVEL x TOTAL PAGES IN POOL / 100). Either logging was inactive, or logging is active but further checkpoints will not correct this situation.

System Action: Processing continues.

Operator Response: Notify your system programmer.

System Programmer Response: Enter the SHOW DBEXTENT command to determine the amount of space left in the storage pool. You may need to add more DBEXTENTs to the storage pool specified in the message. (If needed, use the ADD DBEXTENT function.)

ARI0203E {PAGE|DIRECTORY} buffer pool is full.

Explanation: When running the database manager, more pages of data or DIRECTORY blocks were simultaneously required in the buffers than there were buffers in the pool.

System Action: The application server is ended.

Operator Response: Save the console output for the system programmer.

System Programmer Response: Increase the number specified for the initialization parameter NPAGBUF (for page buffers) or NDIRBUF (for directory buffers), and restart the application server.

ARI0204D Restore from archive has been invoked. Current database will be destroyed.
Enter RESTORE - to continue,
or CANCEL - to cancel.

Explanation: The application server was started with STARTUP=R or F. This causes the contents of the database to be replaced (restored) by the database copy on a database manager archive file. The restored database is then updated for any logging which has occurred since the last database archive.
Note: The database directory will be reformatted (and thus destroyed) before the restore process starts.

System Action: The system waits for your reply.

If the reply is RESTORE, the database manager continues and replaces the database with the database copy on the archive file.

If the reply is CANCEL, the application server is ended without modification to the database.

Any other reply causes the message to be reissued.

Operator Response: If the database is to be restored from a database manager archive file, reply RESTORE.

If the database is not to be restored from a database manager archive file, reply CANCEL to end the application server.

System Programmer Response: Inform the operator of your intentions when restoring a database, including any mounting of database manager archive tapes.

ARI0205I You must user-archive the directory and n DBEXTENT(S) but not the logs!

Explanation: The database operator has issued an SQLEND UARCHIVE command. This tells the database manager that you are shutting down normally and then backing up your database with the backup facility of your choosing.

n is the number of DBEXTENTs in your database. You are also warned not to backup your logs. Backing up and then restoring your logs would make it impossible to restore your database changes since the user-archive was taken.

System Action: The database manager will write a record on the log indicating that a user-archive is being attempted and then shut down normally.

Operator Response: After the application server terminates, backup your directory and n DBEXTENTs with any suitable backup facility. Take special care to note whether you have backed up successfully or not as you will be prompted with message ARI0206D at the next database startup.

ARI0206D Did the user-archive of the directory and n DBEXTENT(S) execute successfully? Enter 0(No) or 1(Yes).

Explanation: The SQLEND UARCHIVE command was used the last time the application server was shut down. You must tell the database manager if you have successfully archived your database. n is the number of DBEXTENTS in your database.

System Action: If you reply 1 for YES, the database manager records on the log that a user-archive was successfully done, and it frees log space. If you reply 0 for NO, the database manager will prompt you with message ARI0207D. If you do not reply 1 or 0, message ARI0052E will be displayed and message ARI0206D will be redisplayed.

Operator Response: Reply 1 if you are sure that you backed up your directory and n DBEXTENTs. Reply 0 if you are unsure about your archive and you will then be prompted with message ARI0207D.

ARI0207D Do you want to continue (without user-archive) or cancel (redo the user-archive)? Enter CONTINUE or CANCEL.

Explanation: You replied 0 to message ARI0206D. You may terminate the application server if you wish to redo your user-archive.

System Action: If you reply CONTINUE, the database manager will write a record to the log indicating that no user-archive was done and processing will continue.

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 terminate to allow you to redo your user-archive. At the next application server startup, you will be prompted with message ARI0206D.

If you do not reply CONTINUE or CANCEL, message ARI0052E is displayed and message ARI0207D is redisplayed.

Operator Response: Reply CONTINUE if you wish to continue using the database manager without user-archiving the database. Reply CANCEL if you wish to terminate and redo the user-archive.

ARI0208D Did the user-restore of the directory and n DBEXTENT(S) execute successfully? Enter 0(No) or 1(Yes).

Explanation: The application server was started with STARTUP=U to indicate that a user-restore of the database was done before startup. This message is issued to verify that you performed the restore.

System Action: If you reply 1, the database manager will reapply the log activity since the user-archive was taken. All committed logical units of work will be reflected in the database.

If you reply 0, the application server will terminate to allow you to redo the user-restore or startup with the correct STARTUP parameter.

If you do not reply 1 or 0, message ARI0052E is displayed and message ARI0208D is redisplayed.

Operator Response: Reply 1 if you are sure that your 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 parameter. If you are unsure of the user-restore, you may redo it after the application server ends and then restart the application server with STARTUP=U.

ARI0209E Since database archive was created, the size of the logs has changed. You must perform COLDLOG.

Explanation: The database restore has completed successfully. However, the size of the database logs has changed since the database archive was created. You must perform the COLDLOG process to:

Reflect the current size of the logs in the database directory, and
To create the log history area in a location known to the database manager. Refer to the information on "History Area" in the DB2 Server for VSE System Administration manual.

The database is at the level which existed when the database archive (just restored) was created.

System Action: The application server ends.

Operator Response: You must perform the following procedures:

You must COLDLOG the database manager using initialization parameters STARTUP=L, SYSMODE=S, DUALLOG=Y or N, and LOGMODE=A (or LOGMODE=Y if you do not plan to use archiving).
You should immediately startup the application server (using STARTUP=W and LOGMODE=A) and take a database archive using the SQLEND ARCHIVE or SQLEND UARCHIVE commands.
If you are using log archiving, you can then start the application server with LOGMODE=L. Otherwise, start the application server with LOGMODE=A.

ARI0210I The extend file input did not generate summary statistics.

Explanation: Either the control keywords specified in the EXTEND input file had no match in the log or the control keywords were matched but the logical units of work found were read-only (queries).

System Action: The database manager displays message ARI0213D.

Operator Response: Respond CANCEL to ARI0213D. Refer this message to your system programmer.

System Programmer Response: Check the control keywords in the EXTEND input file and adjust as needed. Restart extended database initialization.

ARI0211I The requested BYPASS or ROLLBACK operation may affect the following logical units of work:

Explanation: If the ROLLBACK COMMITTED WORK or BYPASS UNDO WORK operation completes, the specified logical units of work may operate on the same tables as did the rolled back or bypassed logical unit of work. Depending on which operation is performed on the DBSPACE or the table, this may lead to other problems such as updating a table or row which no longer exists.

System Action: The database manager displays message ARI0214I (impacted summary) and message ARI0213D (pause). Refer this message to your system programmer.

System Programmer Response: Use the summary information to determine if the specified action is to be done. Instruct the operator whether to reply CONTINUE or CANCEL to message ARI0213D.

Sample Output Sequence:

ARI0211I The requested BYPASS or ROLLBACK
         operation may affect the
         following logical units of work:
ARI0214I LUWID=7BA USER ID=JONES
         DBSPACE=8 TABLE ID=-32765(8003)

ARI0212I Summary information of the records to {be bypassed | roll back}:
LUWID = &2B. User ID = &3.
Date = &4. Time = &5.

Explanation: Summary information will be displayed for each logical unit of work bypassed or rolled back due to a BYPASS UNDO WORK or ROLLBACK COMMITTED WORK command. This message displays statistics for this logical unit of work. It is followed by message ARI0237I which displays the operations and the number of their occurrences which will be rolled back or bypassed if instructed to continue.

However, summary information will not be displayed for the logical units of work which have already been rolled back or bypassed due to a previous BYPASS UNDO WORK or ROLLBACK COMMITTED WORK command.
Note: The format of the displayed date is either mm-dd-yy or dd-mm-yy. The format is chosen when VSE is IPLed. The default format is mm-dd-yy.

System Action: The database manager issues:

Messages ARI0237I (operations performed), ARI0214I (affected logical units of work), and ARI0213D (operator decisions), or
Messages ARI0237I (operations performed) and ARI0213D (operator decisions).

Operator Response: Refer this message to your system programmer.

System Programmer Response: Use the summary information to determine if the specified action is to be done. Instruct the operator whether to reply CONTINUE or CANCEL to message ARI0213D.

Sample Output:

ARI0212I Summary information of the
         records to roll back:
         LUWID=7B9      User ID=SMITH
         Date=12-01-85  Time=13:12:45

ARI0213D Enter CONTINUE to continue initializing or CANCEL to end.

Explanation: Summary information, if any, has been displayed on the console concerning the logical units of work that will be bypassed or rolled back due to a BYPASS UNDO WORK or ROLLBACK COMMITTED WORK command if the database manager is instructed to continue.

System Action: The database manager waits for the operator reply. Message ARI0052E is displayed if you do not reply CONTINUE or CANCEL. This message displays the first 8 characters of the reply and states that the response was not valid. Message ARI0213D will be repeatedly displayed until CONTINUE or CANCEL is entered.

Operator Response: Analyze the summary information and respond accordingly. The response CONTINUE causes database initialization to continue with the specified EXTEND input file commands carried out. The effects of the commands will be written into the log before applying the records. They will remain in the log even if a failure occurs while applying the records. The response CANCEL causes application server termination, leaving the database as it was before startup.

If no summary information was displayed and an EXTEND input file was included, the EXTEND input file commands will not be executed. Something may be wrong with the EXTEND input file commands. In this case, respond CANCEL to bring down the application server and check the EXTEND input file commands. Refer the summary messages to your system programmer.

System Programmer Response: Analyze summary messages and decide whether the actions are what was expected. Determine whether to continue or cancel initialization.

ARI0214I LUWID=&1B. User ID=&2. DBSPACE=&3. TABLE ID=&4A. (&5B.)

Explanation: This message is displayed immediately after message ARI0211I. It displays the logical unit of work value, the user ID value, the DBSPACE number, and the table identification number (if applicable) of a logical unit of work which may be affected if the specified BYPASS UNDO WORK or ROLLBACK COMMITTED WORK command operation is continued.

The user ID value can be blank. For example, a logical unit of work was started after a system checkpoint. A second logical unit of work begins and commits before the first logical unit of work does. The first logical unit of work acts on the changes done by the second logical unit of work and commits. If the second logical unit of 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 checkpoint.

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

&2. is a user ID value or blank.

&3. is a DBSPACE number.

&4A. is a table identification number or 0 if the table identification number is not applicable (no table updated).

&5B. is a hexadecimal table identification number or 0 if the table identification number is not applicable (no table updated).

System Action: Message ARI0213D (operator decision) is displayed.

Operator Response: Refer this message to your system programmer.

System Programmer Response: Use the summary information to determine if the specified action is to be done. Instruct the operator whether to reply CONTINUE or CANCEL to message ARI0213D.

ARI0215E Operator command attempts to access a disabled DBSPACE.

Explanation: The operator or an ISQL user is issuing an operator command which is attempting to access a disabled DBSPACE. Disabled DBSPACEs cannot be accessed. The operator command that might cause this message is SHOW DBSPACE. DBSPACEs are disabled by DISABLE DBSPACE commands in an EXTEND input file.

System Action: Operator command processing ends.

Operator Response: Change the command so it does not attempt to access a disabled DBSPACE.

User Response: Same as Operator Response.

ARI0216I Directory verify function completed {with | without} discrepancies.

Explanation: This message is issued after the completion of the directory verify function (an SQLEND command option). This message will be preceded by specific error messages for each discrepancy found (if any).

System Action: Termination process continues.

Operator Response: If the directory verify function ended with discrepancies, refer this message and the preceding messages to your system programmer. If it completed without discrepancies, termination will continue and you will be prompted for operator action as needed.
Note: If ARCHIVE was specified and discrepancies were found, no database archive will be taken. If UARCHIVE was specified and discrepancies were found, a user-archive should not be taken. Any implicit log archives will be performed due to ARCHIVE or UARCHIVE. If LARCHIVE was specified, log archiving will be performed, but you should correct the discrepancies as soon as possible.

System Programmer Response: If the database directory verify function completed with discrepancies, note the information in the messages preceding this message and refer to directory verification in DB2 Server for VSE & VM Diagnosis Guide and Reference for recovery procedures. If it completed without discrepancies, no action is required of the system programmer.

ARI0217E Physical page X'n1' assigned to DBSPACE n2. Page X'n3' was not allocated in the allocation bit map.

Explanation: The directory verify function has detected that the physical page number identified by X'n1' that has been allocated to logical page X'n3' of DBSPACE number n2 is reflected as not being allocated in the allocation bit map. This is an internal database error.
Note: The DBSPACE number n2 corresponds to the DBSPACENO column in the catalog table SYSTEM.SYSDBSPACES.

System Action: The database manager will continue verifying all PUBLIC and PRIVATE DBSPACEs and end normally.

Operator Response: Refer this message to your system programmer.
Note: If ARCHIVE was specified, the DB2 Server for VSE database archive function will not be invoked. If UARCHIVE was specified, a user-archive should not be taken. Any implicit log archives will be performed due to ARCHIVE or UARCHIVE. If LARCHIVE was specified, the log will be archived, but you should correct the discrepancies as soon as possible.

System Programmer Response: Make note of the information given in this message and refer to directory verification in DB2 Server for VSE & VM Diagnosis Guide and Reference for recovery procedures.

ARI0218E DBSPACE n1, page X'n2' is allocated to physical page X'n3' of storage pool n4 instead of storage pool n5.

Explanation: The directory verify function has detected that physical page X'n3' of storage pool n4 was allocated to physical page X'n2' of DBSPACE n1, which belongs to storage pool n5. This is an internal database error.
Note: The DBSPACE number n1 corresponds to the DBSPACENO column in the catalog table SYSTEM.SYSDBSPACES.

System Action: The database manager will continue verifying all PUBLIC and PRIVATE DBSPACEs and end normally.

Operator Response: Refer this message to your system programmer.
Note: If ARCHIVE was specified, the archive function will not be invoked. If UARCHIVE was specified, a user-archive should not be taken. Any implicit log archives will be performed due to ARCHIVE or UARCHIVE. If LARCHIVE was specified, the log will be archived, but you should correct the discrepancies as soon as possible.

ARI0219E An unexpected internal error occurred during SYSDROP processing.

Explanation: The process which cleans up entries on the SYSDROP catalog table has been invoked. An unexpected error has occurred during this process, most likely a database error. This message is displayed on the system console.
Note: In addition to this error, ARI0504I and ARI0505I are also displayed to report error information in the SQLCA. See Chapter 16, DBSS Return Codes for definitions of the DBSS return codes.

System Action: The application server terminates the SYSDROP processing but continues executing.

Operator Response: Refer this message and its contents to your system programmer.

System Programmer Response: The SYSDROP process can be FORCEd by another logical unit of work which attempts to commit a DROP TABLE or DROP DBSPACE. If this failed to release the resources, report this message and its contents to the designated support group for your installation.

ARI0220E FORCE command has insufficient number of parameters.

Explanation: The database FORCE operator command was entered without parameters.

System Action: The command processing is ended.

Operator Response: Reenter the FORCE operator command with the appropriate operands.

ARI0221E {Agent|Rmtuser} identifier n in FORCE command is invalid.

Explanation: The identifier n is incorrect. It must both (1) be an integer value in the range 1 to the database initialization parameter NCUSERS or RMTUSERS, and (2) represent a valid user.

System Action: The command processing is ended.

Operator Response: Verify the agent or rmtuser identifier by using the SHOW ACTIVE or SHOW CONNECT operator command output. Then reenter the FORCE operator command with the correct agent or rmtuser identifier.

ARI0222E Parameter parm value in FORCE command is invalid.

Explanation: The parameter value identified by parm value specified in the FORCE operator command is not valid. Acceptable parameters are:

COMMIT

ROLLBACK

DISABLE

The DISABLE parameter is optional, but, if used, it must follow the ROLLBACK parameter (that is, ROLLBACK DISABLE).

System Action: The command processing is ended.

Operator Response: Check the specified parameter, and reenter the FORCE operator command with correct values.

For more information about the FORCE operator command, refer to the DB2 Server for VSE & VM Operation manual.

ARI0223I Agent n in FORCE command has no work to force.

Explanation: The agent identified by n does not now have any work to be forced off the system.
Note: The SHOW ACTIVE operator command may have indicated that there was work to force. However, the work ended before the FORCE operator command.

System Action: The command processing is ended.

Operator Response: Do a SHOW ACTIVE to verify the status of agent n. The agent will be either not in work (NIW) or active with a new logical unit of work.

ARI0224E FORCE COMMIT is not valid for agent n.

Explanation: The agent identified by n is not in a correct state for the COMMIT option. Only those agents which have been prepared for commit or rollback by a subsystem (such as CICS) and which are no longer connected to the subsystem may have the COMMIT option applied.

System Action: The command processing is ended.

ARI0225E System operator must issue SHOW ACTIVE, SHOW CONNECT or SHOW SYSTEM command prior to FORCE command.

Explanation: This message is issued for one of these reasons:

The database FORCE command was entered without first doing a SHOW ACTIVE, SHOW CONNECT or SHOW SYSTEM from the database operator console. One of these operator commands must be issued to obtain the correct agent numbers to specify in the FORCE command.
or
The FORCE command specified an agent that completed its LUW after the SHOW ACTIVE, SHOW CONNECT or SHOW SYSTEM command was entered.

Note that if parameters are used on the SHOW CONNECT command, they must result in the display of active agents to enable the FORCE command to work for the displayed agents.

System Action: The command processing is ended.

Operator Response: Enter the SHOW ACTIVE, SHOW CONNECT or SHOW SYSTEM command from the operator console to obtain the correct agent numbers, then reenter the FORCE command for those agents desired.

ARI0226I FORCE {ROLLBACK|COMMIT} is already scheduled for {agent|Rmtuser} n.

Explanation: The agent or Rmtuser identified by n is being rolled back or committed by the system. This action may have been scheduled because of an application request, a previous FORCE command, or system action.

System Action: The command processing is ended.

ARI0227E Agent n cannot be disabled because it is connected to the DB2 Server for VSE online support.

Explanation: The agent identified by n is now 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 while connected to this subsystem. To disable the connection between agents and a subsystem, request the subsystem to disconnect. For the DB2 Server for VSE Online Resource Adapter, this may be done by executing the CICS transaction CIRT.

System Action: Command processing ends.

Operator Response: Reenter the FORCE command without the DISABLE option or request a CICS terminal operator to enter the CIRT transaction.

ARI0228E DISABLE option not valid with COMMIT request.

Explanation: The FORCE command DISABLE option is only valid with ROLLBACK.
Note: The COMMIT option requires that there is no connection to be disabled. The COMMIT option is valid only for those agents that have been prepared for commit or rollback by a subsystem (such as CICS) and that are no longer connected to the subsystem.

System Action: The command processing is ended.

Operator Response: Reenter the FORCE command without the DISABLE option.

ARI0229E Too many FORCE command input parameters.

Explanation: The FORCE command was entered with more than three parameters.

System Action: The command processing is ended.

Operator Response: Reenter the FORCE command with correct number of parameters.

ARI0230I FORCE {ROLLBACK|COMMIT} {with|without} disable scheduled for agent n because of {log full|operator request|resynchronization recovery}.

Explanation: The database manager FORCE command was initiated for the agent identified by n due to the condition indicated by the message ("log full," "operator request," or "resynchronization recovery"). If the agent was in-doubt, the action could be COMMIT or ROLLBACK. Otherwise the action is ROLLBACK.

System Action: The COMMIT or ROLLBACK is scheduled. The actual COMMIT or ROLLBACK may not occur immediately. When the agent begins processing and detects that the FORCE was scheduled, it will then begin the requested process. DISABLE, if specified on the FORCE command, will cause the link to the application to be disconnected after the COMMIT or ROLLBACK process completes.

ARI0231E The database log contains unresolved units. Please start the database manager with NCUSERS = &1..

Explanation: The database recovery process detected some logical units of work which were prepared for COMMIT or ROLLBACK by a subsystem (for example, the DB2 Server for VSE Online Resource Adapter). Because of a system or subsystem failure, the subsystem did not COMMIT or ROLLBACK the logical units of work. These logical units of work cannot be recovered (committed or rolled back) because either:

The application server has been started in single user mode, or
The application server has been started in multiple user mode but the number of logical units of work is greater than the number of concurrent users (specified by the database initialization parameter NCUSERS).

&1. is the number of logical units of work prepared for COMMIT or ROLLBACK and is the minimum value required for initialization parameter NCUSERS.

System Action: The system ends with a limit error (message ARI0039E).

Operator Response: Restart the application server in multiple user mode (SYSMODE=M) and NCUSERS greater than or equal to &1..

ARI0232E The log contains unresolved work for user ID &1..

Explanation: The database recovery process detected that a logical unit of work for user ID &1. was prepared by a subsystem for COMMIT or ROLLBACK (for example, the DB2 Server for VSE Online Resource Adapter). The COMMIT or ROLLBACK request did not occur because of a system or subsystem failure. Operator intervention may be required to resolve the logical unit of work.

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

System Action: The database manager rebuilds the agent as it was prior to the system or subsystem failure. The agent is ready to be resolved by the FORCE command or by the DB2 Server for VSE online resource adapter restart resynchronization support. After the agent is resolved, it is made available for general use by applications or subsystems.

Operator Response: The agents requiring resolution will be resolved during the next execution of the DB2 Server for VSE online resource manager CIRA or CIRB transactions.

If restart resynchronization fails to resolve the agent, use the SHOW ACTIVE command to obtain more information about the logical unit of work. Check with the installation database administrator to determine whether a FORCE n COMMIT command or a FORCE n ROLLBACK command should be entered.

System Programmer Response: In general, a FORCE n COMMIT command should be entered. This is because the application declared its intent as commit either by 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 multiple resources (for example, the DB2 Server for VSE database and a DL/I database). In that case, the ROLLBACK option is available for when the update was not committed by another subsystem like DL/I.

To determine the nature of the application, the SHOW ACTIVE command displays the following information:

USERID = &1. is prepared for COMMIT OR ROLLBACK.
COORDINATOR is the CICS/VSE subsystem id.
RESOURCE ADAPTER is the DB2 Server for VSE resource adapter id.
TRANSACTION is the CICS/VSE TRANSID for the application.
CICS SIGNON is the CICS/VSE signon userid (if any).
TERMINAL is the CICS/VSE terminal id (if any).

If the TRANSACTION identifier is ISQL, only the DB2 Server for VSE database was being updated. Thus, FORCE COMMIT should be entered because the ISQL user requested COMMIT and ISQL updates only the DB2 Server for VSE database.

ARI0233E Invalid FREECLASS for page X'n1' of DBSPACE n2 (Block X'n3').

Explanation: The database manager has detected that the FREECLASS setting for page X'n1' of DBSPACE n2 is not within the valid range. This is an internal database error.
Note: The DBSPACE number n2 corresponds to the DBSPACENO column in catalog table SYSTEM.SYSDBSPACES.

Note: The BLOCK number n3 refers to the Page Map Table block that is being processed.

System Action: The database manager will continue verifying all PUBLIC and PRIVATE DBSPACEs and end normally.

Operator Response: Refer this message to your system programmer.
Note: If ARCHIVE was specified, the archive function will not be invoked. If UARCHIVE was specified, a user-archive should not be taken. Any implicit log archives are performed due to ARCHIVE or UARCHIVE. If LARCHIVE was specified, the log will be archived, but you should correct the discrepancies as soon as possible.

ARI0234E Invalid physical page X'n1' for page X'n2' of DBSPACE n3.

Explanation: The database manager has detected that physical page value X'n1' for logical page X'n2' of DBSPACE n3 is outside the currently defined physical pages of the database. This is an internal database error.
Note: The DBSPACE number n3 corresponds to the DBSPACENO column in catalog table SYSTEM.SYSDBSPACES.

System Action: The database manager will continue verifying all PUBLIC and PRIVATE DBSPACEs and end normally.

Operator Response: Refer this message to your system programmer.
Note: If ARCHIVE was specified, the archive function will not be invoked. If UARCHIVE was specified, a user-archive should not be taken. Any implicit log archives are performed due to ARCHIVE or UARCHIVE. If LARCHIVE was specified, the log will be archived, but you should correct the discrepancies as soon as possible.

ARI0235I LARCHIVE command rejected because a {log | database} archive is being taken.

Explanation: An LARCHIVE command was entered by the database operator while either a log archive or a database archive was being taken.

System Action: The log archive or database archive is completed and the LARCHIVE command is ignored.

ARI0236I The database manager rejects log archive request because log archiving is not enabled.

Explanation: An SQLEND LARCHIVE or an LARCHIVE command was entered by the operator, but the database manager is not running with LOGMODE=L.
Note: Although it is valid to enter SQLEND ARCHIVE if database archiving is not enabled (LOGMODE=Y), it is not valid to enter SQLEND LARCHIVE if log archiving is not enabled.

Note: SHUTDOWN is a valid synonym for SQLEND.

System Action: The database manager will process the SQLEND command ignoring the LARCHIVE request. If the LARCHIVE command was entered, command processing ends.

Operator Response: If you were instructed to enter the LARCHIVE command or SQLEND LARCHIVE, notify your system programmer. Otherwise, no action is required.

System Programmer Response: Ensure that the operator is not requested to log archive when LOGMODE is not L.

ARI0237I &1. &2.

Explanation: This message is issued after message ARI0212I. It specifies the affected DBSPACEs and the operations which will be bypassed or rolled back.

Sample Output:

ARI0237I  DBSPACE 7
ARI0237I   5 INSERTS
ARI0237I   2 CREATE TABLES
ARI0237I  DBSPACE 12
ARI0237I   10 UPDATES

System Action: Message ARI0214I (affected logical units) or message ARI0213D (operator decision) will be issued.

Operator Response: Refer this message to your system programmer.

System Programmer Response: Use the summary information to determine if the specified action is to be done. Instruct the operator whether to reply CONTINUE or CANCEL to message ARI0213D.

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

Explanation: The database manager is listing the restore set you should apply to the current database archive file. The message identifies the external labeling of the database archive file for the restore set.

Message ARI0239I displayed this information when the database archive file was created.
Note: The format of the displayed date is either mm-dd-yy or dd-mm-yy. The format is chosen when VSE is IPLed. The default format is mm-dd-yy.

System Action: ARI0261I is issued for each log archive to be applied to this database.

ARI0239I External labeling of this archive is: Type: {database|log} archive Timestamp: mm-dd-yy hh:mm:ss

Explanation: Because there are three different kinds of archives, and each may require multiple tape volumes, you should externally label the tapes for use in restoring the database. When the database manager requests the operator to mount the tapes to contain the archive, this message is displayed to help in this external labeling.

The database manager also uses the label internally to determine the log archives which follow a database archive.

This message is displayed at the following times:

When the database manager creates a database archive file
When the database manager creates a log archive file
When the application server is ending to allow the user to create a database archive (using the SQLEND UARCHIVE operator command)
When the database manager is ready to read the next log archive file during the restore process.

The database manager will display this same information to identify the database archive file and the required log archive files during the restore process. See messages ARI0238I and ARI0261I.
Note: The format of the displayed date is either mm-dd-yy or dd-mm-yy. The format is chosen when VSE is IPLed. The default format is mm-dd-yy.

System Action: The archive or restore process continues.

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 may want to record the archive details in an operational record book.

When restoring the database, use the displayed information to assist you in mounting the correct log archive tape. (This step is unnecessary if restoring a LOG ARCHIVE FROM DISK.)

ARI0240I Restoring log disk.

Explanation: The application server has been started with STARTUP=R, STARTUP=F, or STARTUP=U; the log archive input volume has been readied; and the log files are being restored.

System Action: The database manager proceeds with the restore process.

ARI0241E The log archive being read is not the log archive requested.

Explanation: The volume mounted after message ARI0239I was displayed is not the log archive tape file requested. Possible causes include:

The mounted (and opened) volume for file name ARILARC does not
The mounted (and opened) volume for file name ARILARC is a log

System Action:

The mounted (and opened) volume is closed. If the close fails, message ARI0298E is displayed and the application server is terminated. Otherwise, message ARI0295A is redisplayed to allow the operator to mount the required log archive file and continue the restore process.

Operator Response:

Determine why the correct volume was not mounted.
Ensure that the information given in message ARI0239I matches the information used to externally label the log archive volume at log archive creation time.
Note: This only applies if the operator labeled the archive tapes with the information displayed at archive creation time.
Ensure that the correct log archive volume is mounted. This is the log archive file identified by the previous message ARI0239I.
Reply with the correct cuu to message ARI0295A to continue the log archive restore process.

System Programmer Response: Ensure that your system operator follows procedures that allow proper identification of the log archive volume at creation time and proper log archive volume mounting at log archive restore time.

ARI0242E Previously LOGMODE was L and now LOGMODE is {Y|N}. To start with LOGMODE = {Y|N}, perform SQLEND with LARCHIVE, perform COLDLOG, and restart with LOGMODE = {Y|N}. Note: Only in a restore process do log archives taken up to the switch in LOGMODE from L to {Y|N} remain useful.

Explanation: If the operator wants to change from LOGMODE=L to LOGMODE=Y or N, this message outlines the procedure to follow. In this case, the message also alerts the operator that after SQLEND LARCHIVE archives the current log and the operator does a COLDLOG, a restore process that restores a database archive (which may include the log archive just taken in its restore set) cannot restore log archives taken past this log archive.

If the operator wants to continue running the database manager with LOGMODE=L, the operator can ignore the procedure outlined in this message and restart the application server with LOGMODE=L.

System Action: The application server is ended.

Operator Response: Either restart the application server with LOGMODE=L so that log archives continue to be useful in a restore process, or restart the application server with LOGMODE=Y or LOGMODE=N after performing the procedure outlined in the message. Note that COLDLOG is performed with the database initialization parameter STARTUP=L.

ARI0243I Previously LOGMODE was L and now LOGMODE=A. Note that log archives taken up to this point are useful until another database archive is taken.

Explanation: If the LOGMODE switch from L to A is desired, this message alerts the operator that once a database archive is taken with LOGMODE=A, a restore from a back-level database archive may only apply log archives up to the last log archive before this switch to LOGMODE=A.

System Action: Database initialization continues.

Operator Response: No action is required if the LOGMODE switch from L to A is desired. Otherwise, end the application server and restart it with the desired LOGMODE.

ARI0244E To continue with LOGMODE=L, you must first perform an initial database archive.

Explanation: You have been running with a LOGMODE other than L. If you want LOGMODE=L, you must first perform an initial database archive since the log indicates that there is no database archive upon which a log archive can be based. A cold log resets LOGMODE to Y because a COLDLOG ends all current restore sets.

System Action: The application server ends.

Operator Response: Start the application server with LOGMODE=Y and take a database archive. Then, restart the application server with LOGMODE=L.

ARI0245E Warning: Do not do a user-archive until you correct discrepancies in the directory.

Explanation: The SQLEND UARCHIVE command was entered with the DVERIFY parameter. The preceding messages display the discrepancies found in the directory.

System Action: The application server ends.

Operator Response: Refer the message to your system programmer.

System Programmer Response: Make note of the information given in the preceding messages and refer to the DB2 Server for VSE & VM Diagnosis Guide and Reference for recovery procedures for directory verification errors.

ARI0247D You are in the restore process. There are log archives that you could use in this process but LOGMODE=A. Do you want LOGMODE=L instead? Enter 1(Yes) to change LOGMODE to L, or 0(No) to keep LOGMODE=A.

Explanation: You have started the application server with STARTUP equal to R, U, or F and LOGMODE equal A. The database has been restored. There are log archives which could be applied to the database. The database manager is giving you the chance to switch the LOGMODE value to L so that the log archives may be applied.

System Action: If you reply 1(YES), the database manager will switch the LOGMODE to L and apply all applicable log archives as if you had started the application server with LOGMODE=L. If you reply 0(No), the database manager will issue message ARI0264D.

Operator Response: Reply 1(YES) if you want any log archives applied to the database just restored. Reply 0(No) if you do not want these log archives applied.

ARI0248E No operand on command.

Explanation: The operator or ISQL terminal user entered a COUNTER or RESET command without specifying either * or the counter names.

System Action: The command processing is ended.

User Response: Reenter the command and specify either * for all counters or specific counter names for the desired counters.

Operator Response: See User Response.

ARI0249E parameter is an invalid RESET or COUNTER parameter.

Explanation: The operator or ISQL terminal user entered a COUNTER command or RESET command with an operand value that was not a system counter name or a valid reset parameter.

System Action: The name is bypassed by the command processor. Any valid counters following the invalid name will be displayed or reset.

User Response: Check the spelling of the submitted name. Reenter the command with the correctly spelled counter name or reset parameter. Issue COUNTER * for a list of all acceptable counter names.

You cannot reset the DASDIO, DASDREAD, and DASDWRIT counters because they are sums of other counters.

To reset the values displayed by the SHOW STORAGE command, enter RESET HIGHSTOR. (HIGHSTOR is not a counter and is not reset by RESET *.)

Operator Response: See User Response.

ARI0250D The above information describes the next log archive to be used in the restore process. Enter either: CONTINUE to restore this log archive, STOP SYSTEM to interrupt this restore process or END RESTORE to end this restore process.

Explanation: Messages ARI0239I and ARI0252I contain a description of the next log archive file to be applied. This is the same information given at the time the log archive file was created. You are given three options with this message:

Reply CONTINUE: The log archive identified in message ARI0239I will be applied to the database. If the archive is on tape, and ARI0252I specifies a tape cuu, mount the tape before replying.
Reply STOP SYSTEM: The restore process is suspended and the application server stops. The restore process will start where it left off if you warm start the application server with STARTUP=W and LOGMODE=L.
Reply END RESTORE: The restore process is ended. Also, you will never be able to restore the remaining log archives to the database archive you have just restored. This is because the remaining log archives are no longer a part of the restore set for this database archive in the history area. However, if you go to a back level database archive, these log archives may be applied as usual.

System Action: One of the following actions will occur:

Reply was CONTINUE: The restore process continues.
Reply was STOP SYSTEM: The restore process is suspended. The application server stops.
Reply was END RESTORE: If you have not applied the first log archive file to your database archive file, you will receive message ARI0264D. If you have applied at least one log archive file to your database archive file, the database manager will complete initialization and begin application processing.

Operator Response: In all but very special cases, you will reply CONTINUE. As mentioned in the Explanation, you may need to mount a tape before making this reply. You may want to reply STOP SYSTEM if you are using an EXTEND input file and need to change the EXTEND commands. There is no danger in using STOP SYSTEM. The only case in which you may want to use END RESTORE is if you want to use the log archives up to a certain point and never restore the remaining log archives. END RESTORE should only be used in extreme cases as it could result in a permanent loss of data. Do not reply END RESTORE without consulting your system programmer.

System Programmer Response: Be sure that you understand the consequences of replying END RESTORE.

ARI0251D The database archive currently mounted is not the most recent database archive known to the database manager. Enter either: IGNORE to continue, or CANCEL to restart the restore process with the most recent database archive.

Explanation: The database archive that was just restored is not the latest database archive record in the history area. This prompt gives you the chance to terminate the database manager if you wish to mount a different database archive.

System Action: If you reply IGNORE and there are no log archive files that go with this database archive file, message ARI0264D is issued. If you reply IGNORE and there are log archive files to go with this database archive file, these log archive files are applied. If you reply CANCEL, the application server terminates to allow you to mount a different database archive file. Any other reply causes message ARI0052E to be displayed and message ARI0251D to be redisplayed.
Note: At this time, the database archive mounted has replaced your database files.

Operator Response: Reply IGNORE if you wish to continue with the restore of the database archive volume currently mounted. Reply CANCEL if you wish to terminate the application server and mount a different database archive to be used in the restore process.

ARI0252I Medium: Tape cuu

Explanation: ARI0252I follows ARI0239I. A log or database archive is about to be created, or the next log archive file is about to be read during the restore process.

During a log archive:

The address shown is the most recent tape address specified for ARILARC at startup, log restore, or log archive; if unspecified so far, it is "???".

During a log restore:

The address shown if the most recent tape address specified for ARILARC at startup, log restore, or log archive. If unspecified so far, it is "???".

System Action: The archive or restore process continues.

Operator Response: Respond to the messages following ARI0252I.

ARI0253D The database archive mounted is not known to the database manager. Enter either: IGNORE to continue, or CANCEL to restart the restore process.

Explanation: The database archive that was just restored does not have a record in the history area. This could be caused by:

The record of this database archive was written over. If it was your most current database archive, you should have gotten message ARI0258E as a warning of this. If it was a back level database archive, you would get no warning.
You did a COLDLOG (STARTUP=L) sometime after taking this database archive which destroyed the history area for this database.

This message gives you the chance to terminate the application server if you wish to mount a different database archive file.

System Action: If you reply IGNORE, message ARI0264D is issued. If you reply CANCEL, the application server terminates.

ARI0254I The database manager is initiating a log archive. When the log archive is complete, the database manager will process the database archive request.

Explanation: A database archive has been requested and LOGMODE=L but the current log has not been archived. Therefore, the database manager has initiated a log archive to ensure that log archives will remain useful in recovering to this point.
Note: This log archive will become the last archive in the restore set for the database archive taken prior to this database archive request.

System Action: The database manager has automatically initiated an on-line log archive operation. It will then process the database archive request.

ARI0255I The database manager is initiating a log archive. When it is completed, the restore process will continue.

Explanation: A database restore has been requested and LOGMODE=L but the current log has not been archived. Therefore, the database manager has initiated a log archive.
Note: This log archive will become the last log archive in the current restore set.

System Action: The database manager will automatically initiate an on-line log archive operation. The database manager will then resume restore processing.

ARI0256E You must specify ROLLBACK by DBSPACE dbspace-number in the extend file.

Explanation: A ROLLBACK COMMITTED WORK command was specified for a logical unit of work containing one or more DROP DBSPACE or DROP TABLE commands and one or more of the following occurred:

The DBSPACE control keyword was submitted but did not specify all of the DBSPACEs which are affected by the DROP commands.
The DBSPACE control keyword was not submitted with the command.
The ROLLBACK COMMITTED WORK command contained the DBSPACE control keyword with other ANDed control keywords (USERID, TIME, or DATE).

This message may be issued more than once for the same DBSPACE.
Note: DBSPACE 1 (catalog DBSPACE) need not be specified on the command although the DROP commands update the catalog.
dbspace-number is a DBSPACE number of the DBSPACE affected by a DROP DBSPACE or DROP TABLE command.

System Action: Processing of the log is completed and summary statistics are displayed. Message ARI0213D is not displayed and processing is ended.

Operator Response: Refer this message to your system programmer.

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 message (ARI0256E) in a ROLLBACK COMMITTED WORK command. Then, restart extended database initialization.

ARI0257I New LUWs and the log archive process cannot continue until n non-R/O active LUWs are completed.

Explanation: A log archive has been requested either through a command or due to the ARCHPCT value being exceeded. The log archive process requires that there be no logical units of work active at the time that the log archive begins. This is so that the logical units of work do not span log archives. The database manager displays this message to inform the operator of how many logical units of work are active at the time of the log archive request.

System Action: When a log archive is requested, the database manager prevents new logical units of work from starting. Users that try to start a new logical unit of work will be in a lock wait until the log archive begins. Logical units of work that are active when the log archive is requested are allowed to complete. In most cases, there is only a slight delay before the log archive begins. If, however, there are long running 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 manager will start log overflow processing and rollback the longest-running logical units of work to free log space.

Operator Response: If you find that a long running logical unit of work is holding up the log archive, you can use the SHOW operator commands to determine which user is delaying the start of the log archive. You may wish to use the FORCE command to end those logical units of work.

ARI0258E The log indicates that you are in danger of losing the record of your latest database archive. To prevent this, you must do a database archive.

Explanation: The database manager keeps track of information such as database archives, log archives, logmode switches, coldlogs, and restores. This is so that the database manager can be sure that the database and log archive files used for restore are valid and in the correct order. However, there is a limit on the number of records the database manager can store at any one time. When the limit is reached, the oldest records are lost. This is not a problem unless the record of the last database archive taken is lost. This message is issued when the latest database archive is within 10 records of being written over and every time a record is stored after that until the record of the latest database archive is actually written over. At this point, message ARI0262E is issued.

System Action: Processing continues.

Operator Response: Refer this message to your system programmer.

System Programmer Response: Be sure to take a database archive before receiving this message a total of 10 times. After a record of your latest database archive is lost, you will not be able to restore your database to its current state until you have taken a database archive.

ARI0259I No logical unit of work started at or after the time specified in the ROLLBACK command.

Explanation: This information message may be displayed when TIME is used as a control keyword in the EXTEND input file. It will be followed by message ARI0210I or message ARI0212I.

System Action: Processing continues.

System Programmer Response: Check the control keywords in the EXTEND input file and adjust if necessary. See message explanations for the accompanying messages.

ARI0260I The restore set for this database archive is as follows:

Explanation: This message is displayed every time a database restore completes. It is followed by messages ARI0238I and ARI0261I which identify the set of database archives and log archives to be used with the database archive just restored.

System Action: Message ARI0238I follows.

ARI0261I [-->] log archive - {tape file-ID mm-dd-yy hh:mm:ss}

Explanation: The message identifies the next log archive file in the restore set.

Message ARI0252I displayed this information when the log archive file was created. The information displayed should have been recorded externally on the tape. Message ARI0252I will display this information again when the restoration process is ready to read this log archive file.
Note: The format of the displayed date is either mm-dd-yy or dd-mm-yy. The format is chosen when VSE is IPLed. The default format is mm-dd-yy.

System Action: ARI0261I is issued for each log archive file to be applied to this database.

ARI0262E The record of your latest database archive has just been lost. You must archive the database to retore your database to its current state.

System Action: Processing continues.

Operator Response: Refer this message to your system programmer.

System Programmer Response: Take a database archive as soon as possible to ensure that if you need to restore the database that you will be able to.

ARI0263D To direct the log archive to tape, enter TAPE followed by the tape address and the catalog filename. (CAT.FILE-ID = catalog-file-ID).

Explanation: A log archive is being created and the operator is prompted to change, or has indicated a change is necessary, to the destination of the archive specified in ARI0252I. ARI0263D requests that this new destination be specified. The format of this identifier is described under ARI0252I.

System Action: If the operator response is valid, the database manager displays it in ARI0252I (preceded by ARI0239I), allowing the operator to confirm that this is the intended destination. If the response was invalid, an error message is displayed and ARI0263D is redisplayed.

Operator Response: To have the log archive written to tape, enter TAPE followed by the tape address (cuu).

The file identifier cannot have been used already for a log archive. It is recommended that you use the default naming convention.

ARI0264D If a COLDLOG was not performed immediately preceding this restore process, enter CANCEL, perform COLDLOG, and start the database manager with STARTUP=W. Otherwise, enter IGNORE.

Explanation:

You replied IGNORE to message ARI0251D or message ARI0253D, or
You replied END RESTORE to message ARI0250D before applying the first log archive file in your restore set, or
An end of restore set was found before the end of the current log.

Unless you executed a COLDLOG immediately preceding the STARTUP=R, your current log is out of synchronization with the database just restored. This message gives you a chance to COLDLOG before the log is applied to the database.

System Action: If you reply IGNORE, the database manager will assume that you have performed a COLDLOG prior to restore and log recovery, and the restore process will continue.

If you reply CANCEL, the application server will terminate.

Operator Response: If you have performed a COLDLOG immediately preceding the restore, then reply IGNORE. If you have not, then reply CANCEL, execute the COLDLOG function (STARTUP=L) and then start the application server with STARTUP=W. The COLDLOG function is performed by the SQLLOG EXEC. See the DB2 Server for VSE System Administration manual for more information on the SQLLOG EXEC.

ARI0273I Formatting directory disk.

Explanation: The application server has been started with STARTUP=R, and the directory disk is being formatted.

System Action: The restore process continues.

ARI0274I Implicit COMMIT failed for userid to avoid deadlock or because of system request. A ROLLBACK of the LUW will occur.

Explanation: User userid did not issue a commit work command before ending, and the database manager started implicit commit processing for that user. During this processing, it was found that the work performed by the user had to be rolled back due to a system request (such as log full, out of lock request blocks, etc.) or to avoid a deadlock situation.

System Action: All database changes for this logical unit of work have been rolled back.

Operator Response: Inform user user-id that the work has not been committed, but rolled back. User user-id should inform the application developer that this condition occurred.

User Response: Recover the work that had been rolled back. Also, it is strongly recommended that a commit work command be issued by applications prior to application termination. If this is done, the application could indicate to the user when a COMMIT WORK is actually completed.

ARI0276E Log is full.

Explanation: The database log is full. Overflow procedures, designed to prevent this from happening, have failed.

System Action: The application server is ended with a limit error. Logical units of work in progress at the time of the termination will be undone when the application server is warm started.

Operator Response: Notify your system programmer concerning the size of the log Also, it is possible that one logical unit of work has been started and has not been committed or rolled back; that is, it inadvertently remains active. This active logical unit of work prevents reuse of database log space.

You must always warm start the application server (initialization parameter STARTUP=W) to recover the logical units of work in progress when the system terminated. You can then, after a "clean" application server shutdown, redefine the logs and start the application server with the new log file definitions (initialization parameter STARTUP=L) to run with the larger logs.

System Programmer Response: You can minimize the space required in the log by running with LOGMODE=N or LOGMODE=Y (rather than LOGMODE=A). This is especially appropriate when loading or reloading the database (including DBS utility DATALOAD and RELOAD operations) and when running other applications that make mass updates to the database. If you are already doing this and are encountering this problem, consider redefining the logs with a larger size.

Switching log modes and redefining the logs are described in the DB2 Server for VSE System Administration manual.

ARI0277E Archive input file cuu does not contain a DB2 Server for VSE identifier.

Explanation: The volume mounted on tape unit cuu in response to message ARI0295A is not a DB2 Server for VSE database archive tape.

Possible causes include:

The mounted (and opened) volume for file name ARIARCH does not contain a DB2 Server for VSE database archive file.
The mounted (and opened) volume for file name ARIARCH is a DB2 Server for VSE database archive volume, but is not the first volume of a multi-volume archive file. This can occur only if you do not request VSE SAM open processing to check the file's volume sequence number.

Note: The database directory file has been reformatted. The database can only be recovered by a successful archive restoration or by rebuilding the database using the database generation process.

System Action: The archive file is closed and dynamically unassigned. Message ARI0295A is displayed again to allow the operator to mount the correct volume and continue the restore process. If the dynamic unassign fails, message ARI0298E is displayed and the application server terminates.
Note: The operator can mount the correct volume on the same or another tape unit and reply with its cuu to message ARI0295A.

Operator Response: Determine why the correct volume was not mounted, mount the correct volume, and reply to message ARI0295A with the tape unit cuu.

If you are unable to determine the cause of the problem, contact your system programmer.

System Programmer Response: Ensure that archive file volumes are properly identified so that you know which volumes belong to a database archive and the order in which they must be mounted. Ensure that your system operator follows procedures that allow proper identification at archive creation time and proper volume mounting at archive restore time. You should use extensive standard volume and file label checking and creation procedures to assist in this identification and verification process.

ARI0278E Unexpected EOF on archive input file [cuu].

Explanation: During a restore from archive, one of the following occurred:

The database manager encountered end-of-file on the database archive file before all data required to restore the database directory and DBEXTENTs was read.
The database manager encountered end-of-file on a log archive before all data required to restore the archived DB2 Server for VSE log was read.

cuu identifies the tape unit containing the database or log archive file. No cuu is specified for a log archive file being restored from disk. Possible causes include:

A DB2 Server for VSE or VSE system error occurred that caused database or log archive file records to be lost.
In mounting the volumes of a multi-volume archive file, the operator mounted the first volume correctly, but then mounted the last volume before mounting one or more of the intermediate volumes. This error can occur only if you omit the volume-sequence-number parameter from the ARIARCH (database archive) or ARILARC (log archive) TLBL Job Control statement, or if the operator was notified of a volume sequence number error and chose to ignore it.

System Action: The database or log archive file is closed and dynamically unassigned, and the application server stops. Note that the database has been only partially restored and is not usable.

Operator Response: If the error occurred while restoring a database archive file and you can determine the cause of the error, restart the application server with the STARTUP=R or F initialization parameter to redo the database restore process.

If the error occurred while restoring a log archive file and you can determine the cause of the error, warm start the application server (STARTUP=W). It will resume the restore process with the current log archive file (the one which encountered this error).

Otherwise, contact your system programmer.

System Programmer Response: Ensure that the system operator knows which database archive file volumes and log archive file volumes (if using log archiving) to mount and the order to mount them.

If the error occurred on a database archive file, ensure that the ARIARCH TLBL job control statement contains the volume-sequence-number parameter (to ensure that the volumes are not mounted out of sequence). Also ensure that the operator does not ignore volume sequence number error messages. You should retry the restore process. If the error persists, you will not be able to use this database archive file.

If the error occurred on a log archive file, ensure that the ARILARC TBL job control statement contains the volume-sequence-number parameter (to 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 resume the restore process with the current log archive file by warm starting the application server (STARTUP=W). If the error persists, you will not be able to use this log archive file.

Refer to the information about how to restart from a database restore operation in the DB2 Server for VSE System Administration manual for recovery procedures when a database or log archive file cannot be processed.

ARI0279E Archive input file is not current. No COLDLOG is issued.

Explanation: During a database restore from archive, the database manager determined from its log that:

The archive copy was not the most recent archive copy of the database, and
The COLDLOG function was not performed (COLDLOG is performed by starting the application server with the SYSMODE=S and STARTUP=L initialization parameters).

You cannot restore a database from an archive copy that is not the most recent archive copy of the database unless you immediately precede this task with the COLDLOG function. Refer to the DB2 Server for VSE System Administration manual for information on restoring a database.

System Action: The application server terminates. The 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.

Operator Response: Refer this message to your system programmer.

System Programmer Response: You have either:

Accidentally attempted to restore a database from an archive copy that is not the most recent archive copy, or
You have failed to execute the COLDLOG function before attempting to restore the database using a back-level archive copy.

You must either:

Rerun the database restore process using the most recent archive copy of the database, or
Run the COLDLOG function before running the database restore process using the back-level archive copy. If you intended to restore the database from a back level archive copy and forgot to perform the COLDLOG function, you can now perform the COLDLOG function and then restart the application server for normal processing (if you are sure that you have applied the correct back level archive copy).

ARI0280A Previously LOGMODE was A(ARCHIVE) and now LOGMODE=&1. To restart with LOGMODE=&1. perform shutdown with ARCHIVE unless an archive has just been taken, perform COLDLOG, and restart with LOGMODE=&1.

Explanation: This message is issued to protect against making a previous DB2 Server for VSE (or any type) of user archive useless. To run with LOGMODE=N or LOGMODE=Y, after running with LOGMODE=A, follow the procedure given in the message.
Note: This message can occur if:

You last ran the database manager with LOGMODE=Y and you issued an SQLEND ARCHIVE or SQLEND UARCHIVE command. These commands internally change the current LOGMODE to A if the current LOGMODE is Y.
Or
You last ran the database manager with LOGMODE=Y, issued an SQLEND, then ran SQLADBEX, specifying ARCHIVE or UARCHIVE, which internally changes the current LOGMODE to A if the current LOGMODE is Y.
You then restarted the application server with LOGMODE set to Y or N. Note that LOGMODE=Y is the default.

In both of the above circumstances, performing a shutdown with archive is not required to continue with LOGMODE=Y, since an archive has just been performed.

System Action: The application server is ended.

Operator Response: If you have started the application server with an incorrect LOGMODE value, correct the LOGMODE value and restart the application server. Otherwise, restart the database manager with 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 the two scenarios described in the above note. COLDLOG is performed by starting the database manager with the database initialization parameter STARTUP=L.

ARI0281I LUW REDO is completed.

Explanation: The logical units of work in the current log which required redoing at startup time have been redone by the recovery procedure.

System Action: Initialization continues.

ARI0282I LUW UNDO is completed.

Explanation: The logical units of work in the current log which required undoing at startup time have been undone by the recovery procedure.

System Action: Initialization continues.

ARI0283I Log analysis is complete.

Explanation: The current log has been scanned successfully by the recovery procedure to determine those logical units of work which require redoing or undoing at startup time.

System Action: Initialization continues.

ARI0284I SHOW LOG command is rejected because LOGMODE = N.

Explanation: A SHOW LOG command was entered by the system operator or the ISQL terminal user while running with LOGMODE=N.

System Action: The command is ignored.

ARI0285I Checkpoint interval is reduced to n.

Explanation: The checkpoint interval is the number of log pages which will be written between automatic checkpoints. This interval is specified by the database initialization parameter CHKINTVL. At database initialization, an analysis of the checkpoint interval and the size of the log is made to determine if at least one checkpoint will be taken before end of log or log wrap. If CHKINTVL will not cause one checkpoint, it is reduced by the required amount to cause one checkpoint to be taken.

System Action: Processing continues. The value n (in pages) is used to cause a checkpoint to be taken.

Operator Response: Unless this message is expected, give it to your system programmer.

System Programmer Response: You may wish to change the CHKINTVL database initialization parameter to avoid this message.

ARI0286I RESTORE cancelled by operator request.

Explanation: The operator replied CANCEL to message ARI0295A while restoring the database. Message ARI0295A is displayed (to ensure that the tape is mounted) before opening the database archive file or before opening a log archive file (restoring with LOGMODE=L) when the tape cuu to be used is unknown.

Unless STARTUP=F was specified and the database archive file cancelled, the database has been partially restored (or reformatted).

System Action: The application server ends.

Operator Response: Refer to message ARI0295A (where you replied CANCEL).

ARI0287I ARCHIVE command rejected because a {database | log} ARCHIVE is being performed.

Explanation: An ARCHIVE command was entered by the DB2 Server for VSE operator while either a log archive or a database archive was being taken.

System Action: The log archive or the database archive that is being taken will be completed, and the ARCHIVE command is ignored.

ARI0288I ARCHIVE command rejected because archiving is not enabled.

Explanation: An ARCHIVE command was entered by the system operator, but the database manager is not running with LOGMODE=A or LOGMODE=L.
Note: It is valid to enter SQLEND ARCHIVE if archiving is not enabled (LOGMODE=Y).

Note: SHUTDOWN is a valid synonym for SQLEND.
The ARCHIVE command requires a LOGMODE of A or L.

System Action: The database manager ignores the ARCHIVE command.

Operator Response: If you were instructed to enter the ARCHIVE command, notify your system programmer. Otherwise, no action is required.

System Programmer Response: Tell the operator not to enter the ARCHIVE command if LOGMODE is not A or L and do not enter the SQLEND ARCHIVE command if the LOGMODE is not Y, A, or L.

ARI0289I Restoring directory disk.

Explanation: This message occurs when the application server has been started with STARTUP=R, or F, the archive input volume has been readied, and the directory file is being restored.

System Action: The restore process continues.

ARI0290I Restoring data disk.

Explanation: The application server has been started with STARTUP=R or F, the archive input volume has been readied, the directory disk has been restored, and the restoring of the data disks (DBEXTENTs) is in process.

System Action: The database manager proceeds with the restore process.

ARI0291I System restore from directory and data disk(s) of database archive is completed.

Explanation: The application server has been started with STARTUP=R or F and the database disks restore process is complete. The database archive tape unit is now available for other purposes.

System Action: The database manager continues with initialization. The archive volumes can be removed from the system and stored until needed.

ARI0292I Archive is completed.

Explanation: A database or log archive has completed. If the archive was to tape, the archive tape unit is now available for other purposes.

System Action: Processing continues.

Operator Response: If the archive was to tape, the archive volumes can be removed from the system and stored until required for the restore process (or until they are no longer required).

ARI0293I Archive is starting.

Explanation: A database or log archive is beginning.

System Action: The database manager continues the archive process.

ARI0294A Archive file [cuu] {read|write} failed. Reason Code = nn. Return Code = nn.

Explanation: While attempting to read or write a DB2 Server for VSE database or log archive file, an access error occurred. cuu is the address of the tape device on which the error occurred; it is not displayed for an error on a disk device.

If the message text specifies WRITE, the database or log archive file has not been completed; it cannot be used. After the I/O error condition is corrected:

If this error occurred while creating a log archive during the database restore process, restart the restore process with the same STARTUP parameter value. If you user-restored the database, you do not have to repeat that process but you must restart with STARTUP=U.
If this error occurred while creating a log archive file with the LARCHIVE operator command, reenter the LARCHIVE operator command.
Otherwise, restart the application server and if applicable, reinitiate the archive process.

If the message text specifies READ, a database or log archive file was being used to restore the database. (The application server had been started with the initialization parameter STARTUP=R, F, or U for database recovery) The database is only partially restored; it can only be recovered by a successful archive restoration (described below) or by rebuilding the database (except for file definition) using the database generation process.

The Reason Code value is the Primary Error Code. The Return Code value is the Secondary Error Code. For further explanation, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.

System Action: If this error occurred due to a log archive initiated using the LARCHIVE operator command, the log archive process ends, but the database manager continues normal operation. For all other cases, the application server ends.

Operator Response: For corrective action, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.

If an archive file was being written, restart the application server or the LARCHIVE operator command according to the situation described under Explanation. This recovery action is described in the DB2 Server for VSE System Administration manual.

If an error occurred when reading a database archive file and if you are able to use the archive file which previously failed, start the application server with the initialization parameter STARTUP=R or F to restore the database and continue normal processing.

If an error occurred while reading a log archive file, warm start the application server. It will resume the restore process with the log archive that failed.

If a database or log archive file cannot be read (for example, uncorrectable media error), refer to the DB2 Server for VSE System Administration manual.

System Programmer Response: See Operator Response.

ARI0295A Ready archive input volume. Enter CANCEL or the cuu.

Explanation: Restoring a database from archive files has been begun by starting the application server with STARTUP=R, F, or U.

The database manager is prompting the operator to ensure that the correct database or log archive tape is mounted and readied on tape unit cuu. The operator is being requested to respond by entering the cuu on which the tape has been mounted or CANCEL to terminate.

If the archive file could not be dynamically assigned and opened successfully, message ARI0296A was displayed to indicate the error condition. This message was redisplayed to give the operator the opportunity to correct the error and restart the archive restore process.

If the cuu value entered in response to this message was not valid, message ARI0297A was displayed to indicate the error condition. This message was redisplayed to give the operator the opportunity to enter a valid cuu.

If the database archive file did not contain a DB2 Server for VSE database archive, message ARI0277E was displayed and the file was closed and dynamically unassigned. This message was redisplayed to correct the error and restart the database restore process.
Note: Unless STARTUP=F was specified and the request was for a database archive file, the database has been partially restored (or reformatted).

System Action: If the operator responds with CANCEL, the restore is canceled and the application server is ended.

If the operator responds with cuu, tape unit cuu is dynamically assigned to the archive input file; it is opened (with rewind) for archive restore input and the restore process proceeds.

Operator Response: If this message was redisplayed after message ARI0277E, ARI0296A, or ARI0297A, take the corrective action suggested by that error message.

Select an available unassigned tape unit. Mount and ready the first (or only) volume of the archive file. Enter the cuu of the selected tape unit.

If a tape unit is not available or if the error condition from message ARI0277E or ARI0296A cannot be corrected, enter CANCEL to end the restore process and the application server.

If you reply CANCEL for a database archive file, you must restart with STARTUP= R or F for database recovery.

If you reply CANCEL for a log archive file, you should 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 were requested to mount.

ARI0296A Archive file [cuu] ASSIGN or OPEN failed. Reason Code = nn. Return Code = nn.

Explanation: A DB2 Server for VSE database archive or restore from archive is in progress. An error occurred while attempting to dynamically assign and open the archive output file or restore input file on tape unit cuu.

The Reason Code value is the primary error code. The Return Code value is the secondary error code. For further explanation, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
Note: Unless STARTUP=F was specified and the request was for a database archive file, the database has been partially restored (or reformatted).

System Action:

If REASON = 36 and CODE = 8, 12, 16, 48, or 52: Message ARI0297A is displayed. The system reissues the archive or restore mount message (either ARI0295A or ARI0299A).
All other REASON and CODE combinations: For restore, message ARI0295A is reissued. For a log archive initiated by the LARCHIVE operator command, the log archive ends and the database manager continues normal operation. For all other archive output files, the application server ends.

Operator Response: For corrective action, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.

If the application server stops while creating a log archive during the restore process, restart the process after taking corrective action for the error.

If the application server stops while creating a normal database or log archive, warm start the application server (STARTUP=W) after taking corrective action for the error. Then, take the action you took previously to initiate the database or log archive. If the archive was initiated by the database manager, it will be initiated again.

If an LARCHIVE operator command request failed and the database manager continued operating, you can retry the LARCHIVE command after correcting the cause of this error message.

ARI0297A Response to archive prompt is not valid.

Explanation: An archive prompt message has been issued, but the operator's reply was not valid.

If ARI0263D has been issued, the response has a syntax error. Possible causes:

No reply was entered.
For ARI0246D, CHANGE or CONTINUE was misspelled.
For ARI0263D, TAPE was misspelled.

System Action: The database manager issues the prompt message again and asks for valid input.

Operator Response: Ensure that the input being entered is valid, and enter it in response to the prompt message.

ARI0298E Archive file [cuu] CLOSE failed. Reason Code = nn. Return Code = nn.

Explanation: The database manager was creating or reading a database or log archive file. An error occurred when the database manager attempted to close the database or log archive file.

cuu is the address of the tape device on which the error occurred; the address will not be displayed for an error on a disk device.

Note: Due to this error, tape unit cuu has not been dynamically unassigned. The tape unit cannot be used by the database manager or any other partition until the system ends. You may want to shutdown the application server if you need to re-use the tape unit.

System Action: If a log archive file was being created with the LARCHIVE operator command, the log archive ends and the database manager continues normal operation. If a database or log archive file was being created for any other reason, the application server ends. The database or log archive file cannot be used. The system log indicates that the archive was not successful.

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).

If the entire database was being restored from a database archive and message ARI0277E was not displayed, normal processing continues.

If a log archive was being read during the restore process, normal processing continues.

Operator Response: For corrective action, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.

Then, if a log archive was being created during the restore process, restart the process.

Then, if this error occurred due to a log archive initiated by the LARCHIVE operator command, reenter the LARCHIVE operator command to re-initiate the log archive process.

Then, if a database or log archive was being created, warm start the application server, If desired, reschedule the archive creation by using the ARCHIVE, LARCHIVE, SQLEND ARCHIVE, SQLEND LARCHIVE, or SQLEND UARCHIVE operator command. This recovery action is described in the DB2 Server for VSE System Administration manual. If the database manager implicitly initiated the database or log archive due to the ARCHPCT initialization parameter, it will do so again when you warm start the application server.
Note: SHUTDOWN is a valid synonym for SQLEND.
If the database was being restored from a database archive and message ARI0277E precedes this message, take the corrective action as implied by these two messages. Restart the database archive process.

If the database was being restored from a database archive and message ARI0277E does not precede this message, you can proceed with whatever activity you had planned. The database has been successfully restored from the archive copy.

No further action is required if the error occurred while closing a database or log archive input file during the restore process. If there are subsequent log archives to be read, you will have to use a different tape unit because this tape unit has not been dynamically unassigned. Alternatively, you can reply STOP SYSTEM to subsequent message ARI0250D for the next log archive to stop the application server (and get the tape unit unassigned) and then warm start the application server to resume the restore process with the next log archive.

System Programmer Response: See Operator Response.

ARI0299A Ready archive output volume. Enter the cuu for dynamic or 1 for static tape device.

Explanation: A database or log archive is being created for one of the following reasons:

You entered the ARCHIVE operator command.
You entered the SQLEND ARCHIVE operator command.
The database manager has implicitly initiated the creation of a database archive due to the ARCHPCT initialization parameter.

The database manager is prompting the operator to ensure that a tape is mounted and readied on tape unit cuu, or on the tape unit assigned to SYS005. The operator is being requested to respond by entering either the cuu number or 1.

If the cuu entered in response to this message was not valid, message ARI0297A was displayed to indicate the error condition.

If 1 was specified, and the logical device SYS005 was not assigned, message ARI2036I was displayed to indicate the error condition.

System Action: When the operator responds with cuu, tape unit cuu is dynamically assigned to the archive output file; it is opened (with rewind) for archive output and the archive process proceeds.

If the operator responds with 1, logical device SYS005 is opened (with rewind) for archive output and the archive process proceeds.

Operator Response: If the archive is to be written to logical device SYS005, mount and ready a scratch tape volume on SYS005 and respond 1 to this message. Otherwise, select an available unassigned tape unit. Mount and ready a scratch tape volume. Enter the cuu of the selected tape unit.

If you have one or more tape units assigned to SYS005 for this purpose, mount and ready the required scratch tape volumes, and enter SYS005.

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

ARI2000E Index index-id in DBSPACE dbspace-no has been marked invalid.

Explanation: One of the following may have happened during ROLLBACK, UNDO, or REDO processing:

The system cannot obtain a logical index page. This can result from the ROLLBACK or UNDO of either a DROP INDEX, a REORGANIZE INDEX, a deletion of a row, or an update of a row. It can also result from the REDO of either a CREATE INDEX, an insertion of a row, or an update of a row.
The system cannot obtain a physical index page. This can result from the ROLLBACK or UNDO of a DROP INDEX, a REORGANIZE INDEX, a deletion of a row, or an update of a row. It can also result from the REDO of either a CREATE INDEX, an insertion of a row, or an update of a row.
Not enough virtual storage or room in a temporary DBSPACE exists to recreate an index. The shortage can result from the ROLLBACK or UNDO of either a DROP INDEX or REORGANIZE INDEX, or from the REDO of a CREATE INDEX or REORGANIZE INDEX.

System Action: The database manager continues to process the ROLLBACK, UNDO, or REDO command without updating the index and marks the index invalid.

Operator Response: Notify your system programmer.

System Programmer Response: Contact the owner of the invalid index. The owner must drop and recreate the index. The system has a limit of 16 invalid indexes. You can find the index name by using the following SELECT statement:

 SELECT A.DBSPACENO, B.IID, B.INAME, B.ICREATOR, 
       A.TNAME FROM SYSTEM.SYSCATALOG A, 
       SYSTEM.SYSINDEXES B
       WHERE A.TNAME = B.TNAME AND 
             A.CREATOR = B.CREATOR
             AND A.DBSPACENO = dbspace-no
             AND B.IID = index-id
       ORDER BY A.DBSPACENO, B.IID   ;

ARI2001I Warning: The following entities are invalid.

Explanation: This is a message heading for a list of invalid entities found during system start up. It is followed by the output of the SHOW INVALID command. For more information refer to the SHOW INVALID operator command.

System Action: Processing continues.

Operator Response: Notify and give your console output to your system programmer.

System Programmer Response: Notify the owners of the invalid indexes and have them drop and recreate the indexes.

ARI2002I Index pages are being reclaimed for DBSPACE &1.

Explanation: A free index page is required for a ROLLBACK, UNDO, or REDO work, but there are no free pages available. An attempt is being made to reclaim empty or partially empty pages from existing indexes.

System Action: If pages are reclaimed successfully processing will continue. If no pages are reclaimed the index will be marked invalid and processing will continue. Message ARI2003I will be issued when the page reclaim processing is complete.

Operator Response: Refer this message to your system programmer.

System Programmer Response: Refer to message ARI2003I.

ARI2003I The index page reclaim processing is finished.

Explanation: A free index page was required for a ROLLBACK, UNDO, or REDO work, but there were no free pages available. An attempt to reclaim empty or partially empty index pages has completed.

System Action: If pages were reclaimed successfully processing will continue. If no pages were reclaimed the index will be marked invalid and processing will continue.

Operator Response: Refer this message to your system programmer.

System Programmer Response: This message indicates that the DBSPACE specified is running short of index pages. Index page reclaiming may adversely 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 pages, then action should be taken to free some pages.

For more information, refer to the DB2 Server for VSE & VM Database Administration manual.

ARI2008I Archive is about to be started.

Explanation: The operator or database administrator requested a database or log archive with one of the following commands:

LARCHIVE
SQLEND LARCHIVE
ARCHIVE
SQLEND ARCHIVE

This message follows message ARI0065I. It informs the user that although the operator or database administrator requested an archive, the actual archive process has not started.

System Action: As soon as the system is ready, the database or log archive begins.

ARI2009E To continue with LOGMODE=A, you must first perform an initial database archive.

Explanation: You have been running with LOGMODE Y or N. If you want LOGMODE=A, you must first perform an initial database archive because the log indicates that no database archive exists.

System Action: The application server ends.

Operator Response: Start the application server with LOGMODE=Y and take a database archive. Next, restart the application server with LOGMODE=A.

ARI2010I WARNING: The database manager terminated abnormally. The log contents is required for recovery. Continuing with the COLDLOG will erase all log records and may cause the next startup to terminate during UNDO/REDO processing.

Explanation: The last time the application server started up, it terminated abnormally. The current log is required to recover the system to the point of failure, either by warmstarting the database or by restoring the last database archive.

System Action: Processing continues. The user will be given an opportunity to cancel the COLDLOG by message ARI0920D.

User Response: If you have not redefined the log datasets, cancel the coldlog in response to message ARI0920D. Warm start the database to recover up to the point of failure, or restore the database from a previous archive.

ARI2011I Formatting data disk(s).

Explanation: The application server has been started with STARTUP=R and the directory has been restored. The DB2 Server for VSE data disks are being formatted.

System Action: The restore process continues.

ARI2036I Logical device has not been statically assigned for a DB2 Server for VSE archive.

Explanation: The operator entered 1 in response to message ARI0299A. Logical device SYS005 is either not assigned or assigned to a non-tape device. It cannot be used for a database manager archive.

System Action: Message ARI0299A will be redisplayed.

Operator Response: Respond to message ARI0299A.

ARI2037D Restoring the database with LOGMODE=Y or N. Enter 0 to CANCEL and restart with logmode A or L, or enter 1 to CONTINUE.

Explanation: The restore process is started with LOGMODE=Y or N. You can enter 0 to cancel the restore process and restart with logmode A or L. If you enter 1 to continue, the restore process will continue to restore the Directory and the DBEXTENTs. The restore set for this database archive will also be displayed if there are log archives to be restored. Message ARI0280A will then be issued and the application server terminated. Also, the current log could be lost.

System Action: Processing continues.

Operator Response: Enter 0 to cancel the restore, and restart the restore process with logmode A or L, or enter 1 to continue.

Attention: The current log could be lost.

ARI2038E Archive being restored is from a different release of DB2 Server for VSE. The restore has failed.

Explanation: The system has determined that the archive being restored was not taken with the current release of DB2 Server for VSE.

System Action: The restore process ends. Note that the directory has been restored and the database is unusable.

Operator Response: Restore an archive taken with the current release of DB2 Server for VSE.

ARI2039E CHKINTVL = newval is invalid. Maximum valid CHKINTVL value is maxval.

Explanation: The checkpoint interval is the number of log pages which will be written between automatic checkpoints. When this value is changed during run time, an analysis of the checkpoint interval and the size of the log is made to determine if at least one checkpoint will be taken before end of log or log wrap. This message is generated if the CHKINTVL specified will not cause at least one checkpoint to be taken.

System Action: The checkpoint interval is not changed and processing continues.

Operator Response: Refer this message to your system programmer.

System Programmer Response: Correct the invalid CHKINTVL value. maxval represents the highest allowable checkpoint interval value based on the size of the log.

ARI2040E Pool Recovery is in progress, STARTUP=startup is not allowed.

Explanation: The Data Restore storage pool recovery process was initiated, but has not yet been completed by starting the database manager with STARTUP=U. Storage Pool recovery must be completed before the database can be started with STARTUP=startup.

System Action: The requested function is not performed.

Operator Response: Complete the storage pool recovery process by starting the database with STARTUP=U.

ARI2041I Pool Recovery processing continues.

Explanation: The Data Restore storage pool recovery process was initiated and completed successfully. The database is being started with STARTUP=U, which will complete the storage pool recovery process.

System Action: Storage pool recovery processing continues.

ARI2042E Pool Recovery cannot continue.

Explanation: The Data Restore storage pool recovery process was initiated, but did not complete successfully. The database cannot be started with STARTUP=U to complete the storage pool recovery process until the Data Restore pool recovery process is successfully completed. The database is currently in an inconsistent state. One of the following must be done before the database can be restarted.

Use the RESTORE POOL command of the Data Restore feature to complete the initial phase of storage pool recovery successfully. Then, start the database with STARTUP=U to complete storage pool recovery.
Restore the entire database from a database archive. This can be either a database manager archive or a user archive.

System Action: Processing terminates.

ARI2043E During Pool Recovery, END RESTORE will not be accepted.

Explanation: The message displayed before ARI2043E indicates that END RESTORE is an acceptable reply to the message. However, during Pool Recovery, END RESTORE will be rejected as an invalid response.

System Action: The system is waiting for an operator response.

Operator Response: Enter a response to the previous message. If END RESTORE is entered, it will not be accepted as a valid response.

ARI2044D Agent identifier n in the FORCE command was using DRDA Two Phase Commit protocol. Forcing this agent may lead to heuristic damage. Do you want to force this agent? Enter 0(No) or 1(Yes).

Explanation: The in-doubt agent n was using the DRDA two phase commit protocol. Forcing this agent's work could cause data on other databases to be inconsistent with data at this database.

System Action: If you reply 1 for YES, the agent will be forced to commit or rollback its work as indicated on the FORCE command. If you reply 0 for NO, the in-doubt agent will not be forced and will remain in-doubt. If you do not reply 1 or 0, message ARI0052E will be displayed and message ARI2044D will be redisplayed.

Operator Response: Reply 1 if you are sure that you want to force this in-doubt agent. Reply 0 if you are unsure. If you need to force the in-doubt agent, the FORCE command can be reentered.

Database Administrator Action:

The database administrator must understand the application and the status of this unit of work on all of the involved application servers before forcing an in-doubt agent that was using DRDA two phase commit protocol. It is most desirable to let the systems resolve the in-doubt agents automatically during resynchronization recovery. The database administrator of the DRDA2 requester should be contacted to help determine the impact of forcing the in-doubt agent.

ARI2045E RESET INDOUBT command has insufficient number of parameters.

Explanation: The RESET INDOUBT operator command was entered without parameters.

System Action: The command processing is ended.

Operator Response: Reenter the RESET INDOUBT operator command with the appropriate operands.

ARI2046E Too many RESET INDOUBT command input parameters.

Explanation: The RESET INDOUBT * operator command was entered with extra parameters. When * is specified, no other parameters are allowed.

System Action: The command processing is ended.

Operator Response: Reenter the RESET INDOUBT operator command with the appropriate operands.

ARI2047E Transaction identifier n in RESET INDOUBT command is invalid.

Explanation: The transaction identifier n does not exist in the system.

System Action: The command processing is ended.

Operator Response: Enter the SHOW INDOUBT operator command to find out the valid, existing transaction identifiers. Then reenter the RESET INDOUBT operator command with the appropriate operands.

ARI2048D In-doubt n was forced. Are you sure you want to reset this in-doubt? Enter 0(No) or 1(Yes).

Explanation: The transaction identifier n was in-doubt and was resolved by using the FORCE operator command. The action taken by the FORCE command could be different than the action that resynchronization recovery would have done. This unit of work might still be in-doubt on the other participating application servers.

System Action: If you reply 1 for YES, the in-doubt entry will be removed from the system. If you reply 0 for NO, the in-doubt entry will not be removed from the system. If you do not reply 1 or 0, message ARI0052E will be displayed and message ARI2048D will be redisplayed.

Operator Response: Reply 1 if you are sure that you want to remove this in-doubt entry. Reply 0 if you are unsure. If you need to remove the in-doubt entry, the RESET INDOUBT command can be reentered.

Database Administrator Action:

The database administrator must understand the application and the status of this unit of work on all of the involved application servers before removing an in-doubt entry that was forced. It is most desirable to let the systems resolve the in-doubt agents automatically during resynchronization recovery. The database administrator of the DRDA2 requester should be contacted to help determine the impact of forcing the in-doubt agent.

ARI2052I FORMAT 1
A checkpoint was taken.
Scheduled: sctime
Started: sttime
Ended: etime
FORMAT 2
A checkpoint was taken.
Type = type.
Scheduled: sctime
Started: sttime
Ended: etime
DIRREAD = drd
DIRWRITE = dwr
PAGEREAD = prd
PAGWRITE = pwr
DSREAD = dsr
DSWRITE = dsw
Time spent waiting to
start: wst seconds
Time spent executing: ext seconds
Log pages filled since last
checkpoint: logused

Explanation: Format 1 of the message is displayed if DSPSTATS=1. Format 2 of the message is displayed if DSPSTATS=2. The DSREAD and DSWRITE values are only displayed if the VM data spaces feature is installed and is being used.

type is the reason the checkpoint was performed. The type is only displayed if DSPSTATS=2. Valid types are:

COLDLOG: Log just formatted.
Warm Start: System just recovered (that is, warm start).
Periodic: Periodic system checkpoint taken. Periodic checkpoints can occur for various reasons, including, CHKINTVL was reached, SLOGCUSH was reached, SOSLEVEL was reached, and a DROP DBSPACE was issued. See the DB2 Server for VSE & VM Performance Tuning Handbook manual for more details.
Database Archive Started: Archive of the database started.
Database Archive Completed: Archive of database completed.
Log Archive Started: Archive of the log started.
Log Archive Completed: Archive of the log completed.
Shutdown: System being shutdown.
Shutdown with User archive: Shutdown with user archive.
User Archive Done: User archive done and verified.
Logmode=N: System checkpoint when LOGMODE=N.

sctime is the time of day the checkpoint was scheduled.

sttime is the time of day the checkpoint started execution.

etime is the time of day the checkpoint ended execution.

drd is the number of directory buffer reads that were done by the checkpoint processing.

dwr is the number of directory buffer writes that were done by the checkpoint processing.

prd is the number of page buffer reads that were done by the checkpoint processing.

pwr is the number of page buffer writes that were done by the checkpoint processing.

dsr is the number of data space reads that were done by the checkpoint processing. This is only displayed if the VM data spaces feature is being used.

dsw is the number of data space writes that were done by the checkpoint processing. This is only displayed if the VM data spaces feature is being used.

wst is the time that the checkpoint was waiting to begin processing. This is only displayed if DSPSTATS=2.

ext is the time that the checkpoint was processing. This is only displayed if DSPSTATS=2.

logused is the number of log pages filled since the last checkpoint was taken.

System Action: System processing continues.

User Response: Use the SET DSPSTATS command to disable these messages if they are not desired, or to change which format of the message appears.

ARI2053E The mandatory COLDLOG during migration was not done. A COLDLOG must be performed before continuing.

Explanation: The database startup has detected that a COLDLOG was not performed during migration. Failure to COLDLOG the database will prevent restoring database archives. The database cannot be started until a COLDLOG has been performed.

System Action: Database startup has terminated.

Operator Response: Refer this message to your system programmer.

System Programmer Response: You must perform a COLDLOG before the database manager will allow the database to finish startup.

ARI2054I Database manager has taken a FULL archive.

Explanation: The database manager has completed taken a FULL archive. Either an implicit archive was initiated by the database manager, or the ARCHIVE operator command was used with the FULL parameter.

System Action: Processing continues.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

CREATE INDEX	DROP TABLE
DROP DBSPACE	UPDATE
INSERT	DELETE
DATALOAD	RELOAD TABLE
RELOAD DBSPACE	RELOAD PROGRAM
RELOAD PACKAGE	REORGANIZE INDEX
SCHEMA	DROP INDEX