| ARI0001E | An error occurred while attempting to obtain storage. |
Explanation: Either:
| Note: | The DB2 Server for VSE reason code is the VSE/Advanced Functions GETVIS macro return code. It is displayed in message ARI0042I. |
System Action: If SQLCODE -930 accompanies this message, the database manager continues and additional requests to obtain storage may result in the message being issued again. If the message is issued without SQLCODE -930, the database manager is ended.
Operator Response: If GETVIS storage has been exhausted (reason code = 12), restart the database manager after allocating a larger partition.
System Programmer Response: You may have to assist the operator in determining what partition size will be required if storage is exhausted. Contact the appropriate personnel for hardware service or the designated support group.
| ARI0002E | Unable to open the xxxxxxxx parameter data set. Reason Code = nn. Return Code=nn. |
Explanation: xxxxxxxx is the name of the parameter data set as specified in the PARMID parameter.
This parameter is specified in the job control to identify a library source statement member (in the "A" sublibrary).
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 21, Include File Access Errors, or "INCLUDE FILE ERRORS" in the HELP text.
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Either:
If the problem persists, for corrective action, look up the displayed error codes under either Chapter 21, Include File Access Errors or "INCLUDE FILE ERRORS" in the HELP text.
| ARI0003E | An error occurred reading the xxxxxxxx parameter data set. Reason Code = nn Return Code = nn. |
Explanation: xxxxxxxx is the name of the parameter data set as specified in the PARMID parameter. This parameter is specified in the job control to identify a library source statement member (in the "A" sublibrary).
The REASON value is the Primary Error Code. The CODE value is the Secondary Error Code. For further explanation, look up the displayed error codes under either Chapter 21, Include File Access Errors, or "INCLUDE FILE ERRORS" in the HELP text.
System Action: The database manager ends.
Operator Response: For further explanation, look up the displayed error codes under either Chapter 21, Include File Access Errors, or "INCLUDE FILE ERRORS" in the HELP text.
| ARI0004I | xxxxxxxx - The database manager ignores PARMID within a parameter data set. |
Explanation: xxxxxxxx is the name of the parameter data set which contains the PARMID initialization parameter. The PARMID parameter is ignored in a parameter data set.
System Action: Processing continues.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the parameter data set specification to eliminate this message.
| ARI0005E | {JCL|xxxxxxxx} - yyyyyyyy parameter is specified more than once. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
yyyyyyyy is the parameter keyword that was specified more than once in the initialization parameter input.
| Note: | The same parameter keyword can be specified once in the job control and once in the parameter data set. |
System Action: If this error occurs in the job control parameter processing, the database manager ends.
If this error occurs during parameter data set processing, the database manager ends unless the yyyyyyyy parameter is correctly specified in the job control. See System Programmer Response.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Remove the extra occurrences of the initialization parameter from either the job control or the parameter data set. If this parameter was specified more than once in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing.
| ARI0006E | {JCL|xxxxxxxx} - yyyyyyyy is an invalid parameter specification. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
yyyyyyyy is the initialization parameter keyword which is invalid (or misspelled). If the parameter keyword in error was greater than eight characters, only the first nine characters are printed.
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid initialization parameter specification in either the job control or the parameter data set.
| ARI0007E | {JCL|xxxxxxxx} error. A keyword is missing. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
System Action: The database manager is ended.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid initialization parameter specification in either the job control or the parameter data set. This error would be caused by coding ...,=value,... .
| ARI0008E | {JCL|OPER|xxxxxxxx} - yyyyyyyy = c is invalid. It must be d. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
OPER indicates that the parameter in error was specified during run time using the SET operator command.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
yyyyyyyy is the initialization parameter keyword which has the invalid parameter value. It must be one of the following keywords: ACCOUNT, DSPLYDEV, DSPSTATS, DUALLOG, DUMPTYPE, EXPAND, EXTEND, LOGMODE, STARTUP, SECALVER, SECTYPE, SYNCPNT, or SYSMODE.
c is the first (or only) character of the invalid parameter value. If no value was specified, a comma is substituted for the missing value. If more than one character is given for the parameter value, it will not be accepted even if the first character is valid.
d is a character string indicating the correct parameter value as follows:
yyyyyyyy d (default)
-------- --------------- ---------
ACCOUNT D, T, E, or N N
DSPLYDEV L, C, or B L
DSPSTATS 0, 1, or 2 0
DUALLOG N or Y N
DUMPTYPE P, F, or N F
EXPAND DBSPACE or ALL DBSPACE
EXTEND Y or N N
LOGMODE Y, A, L, or N Y
SECALVER N or Y N
SECTYPE DB2 DB2
STARTUP C, E, F, I, L, M, W
R, S, U, or W
SYNCPNT Y or N Y
SYSMODE M or S M
System Action: If this error occurs in the job control parameter processing, the database manager ends.
If this error occurs during parameter data set processing, the database manager ends unless the yyyyyyyy parameter is correctly specified in the job control. See System Programmer Response.
If this error occurs while processing the SET command, the command is ignored and processing continues.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid parameter value in the job control, the parameter data set, or the operator console. If the invalid parameter was specified in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing.
| ARI0009E | {JCL|OPER|xxxxxxxx} - yyyyyyyy = c is invalid. It must be in the range from n1 to n2. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
OPER indicates that the parameter in error was specified during run time using the SET operator command.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
yyyyyyyy is the parameter keyword which has the invalid parameter value. It must be one of the following keywords: ARCHPCT, CHKINTVL, DISPBIAS, LTIMEOUT, NCSCANS, NCUSERS, NDIRBUF, NLRBS, NLRBU, NPACKAGE, NPACKPCT, NPAGBUF, PROCMXAB, PTIMEOUT, RMTUSERS, SLOGCUSH, SOSLEVEL, or TRACEBUF.
c is the invalid parameter value. If no value was specified, a comma is substituted for the missing value. If the parameter is longer than eight characters, only the first eight characters are displayed. The parameter value can be up to eight characters. Leading zeros are suppressed.
n1 is the lower limit (or minimum) for the correct parameter value.
n2 is the upper limit (or maximum) for the correct parameter value.
yyyyyyyy n1 n2 (default)
-------- -- -------- ---------
ARCHPCT 10 99 80
CHKINTVL 1 99999999 10
DISPBIAS 1 10 7
LTIMEOUT 0 99999 0
NCSCANS 1 655 30
NCUSERS 1 252 5
NDIRBUF 10 400000 NPAGBUF
NLRBS Larger 583333 (2 x NCUSERS) +
of 50 or (NLRBU x NCUSERS)/2 +10
(2 x NCUSERS)
NLRBU 10 583233 1000
NPACKAGE 1 32766/NCUSERS 10
NPACKPCT 0 100 30
NPAGBUF 10 400000 (4 x NCUSERS) + 10
PROCMXAB 0 255 0
PTIMEOUT 0 99999 180
RMTUSERS 0 65535 0
SLOGCUSH 11 100 90
SOSLEVEL 1 100 10
TRACEBUF 0 99999 0
System Action: If this error occurs in the job control parameter processing or during parameter data set processing, the database manager ends.
If this error occurs while processing the SET operator command, the command is ignored and processing continues.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid parameter value in the job control, the parameter data set, or the operator console. If the invalid parameter was specified in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing.
| ARI0010E | {JCL|xxxxxxxx} - {TRACDBSS|TRACCONV|TRACRDS| TRACDSC|TRACWUM|TRACDRRM |TRACSTG} is invalid. The parameter value must be either {0, 1, or 2 | 0 or 1}. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
Specifying a parameter value other than 0, 1, or 2 for the TRACDBSS, TRACCONV, TRACRDS, TRACDSC, TRACWUM, or TRACDRRM initialization parameter is invalid. Specifying a parameter value other than 0 or 1 for the TRACSTG initialization parameter is invalid.
System Action: If this error occurs in the job control parameter processing, the database manager ends. If this error occurs during parameter data set processing, the database manager ends unless the TRACDBSS, TRACCONV, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG parameter is correctly specified in the job control. See System Programmer Response.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid initialization parameter value in either the job control or the parameter data set. If the invalid parameter was specified in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing.
| ARI0011E | {JCL|xxxxxxxx} - yyyyyyyy is invalid. The parameter string must be from 1 to n characters. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
yyyyyyyy is the initialization parameter keyword which has the invalid parameter string length. It must be one of the following keywords: CHARNAME, DBNAME, DBPSWD, DSPSTATS, PARMID, PROGNAME, TRACCONV, TRACDBSS, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG.
n is the maximum character string length of the value.
yyyyyyyy n --------- ----- CHARNAME 18 DBNAME 18 DBPSWD 8 DSPSTATS 2 PARMID 8 PROGNAME 8 TRACCONV 1 TRACDBSS 11 TRACRDS 6 TRACDSC 2 TRACWUM 1 TRACDRRM 4 TRACSTG 1
System Action: If this error occurs in the job control parameter processing, the database manager ends.
If this error occurs during parameter data set processing, the database manager ends unless the yyyyyyyy parameter is correctly specified in the job control. See System Programmer Response.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid initialization parameter value in either the job control or the parameter data set. If the invalid parameter was specified in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing. PARMID is valid only on the job control and, therefore, must always be corrected.
| ARI0012I | The database manager ignores yyyyyyyy = c when zzzzzzzz = d. |
Explanation: yyyyyyyy is the initialization parameter keyword of the value that is ignored.
c is the parameter value that was specified.
zzzzzzzz is the initialization parameter keyword that is used and causes the yyyyyyyy parameter to be ignored.
d is the parameter value specified for zzzzzzzz.
yyyyyyyy c zzzzzzzz d
-------- ------------- -------- -------------
ACCOUNT T, D, or E STARTUP C, E, I, L, M,
or S
ACCOUNT D, T, or E PROGNAME ARISEGB
ACCOUNT D, T, or E PROGNAME ARISRMG
ARCHPCT value LOGMODE Y or N
DISPBIAS value SYSMODE S
DUALLOG N or Y SYSMODE M
DUALLOG N or Y STARTUP E, F, I, M, R,
S, U, or W
NCUSERS value > 1 SYSMODE S
PROCMXAB non-zero value SYSMODE S
PROGNAME program-name SYSMODE M
PROGNAME program-name STARTUP C, E, I, L, M,
or S
PTIMEOUT non-zero value SYSMODE S
RMTUSERS non-zero value SYSMODE S
TRACDRRM non-zero value RMTUSERS 0
TRACWUM 1 or 2 RMTUSERS 0
SECALVER N or Y SYSMODE S
SECTYPE DB2 SYSMODE S
SYNCPNT Y RMTUSERS 0
LTIMEOUT non-zero value SYSMODE S
Notes:
System Action: Processing continues.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Remove the initialization parameter specification causing the message.
| ARI0013E | yyyyyyyy must be c when zzzzzzzz = d . |
Explanation: yyyyyyyy is the initialization parameter keyword of the value that is in conflict.
c is the parameter value that was specified.
zzzzzzzz is the initialization parameter keyword that is used and causes the yyyyyyyy parameter specification to be invalid.
d is the parameter value specified for zzzzzzzz.
yyyyyyyy c zzzzzzzz d
-------- ------- -------- --------
LOGMODE Y STARTUP L
LOGMODE Y, A, SYSMODE M
or L
STARTUP W, R, EXTEND Y
U, or F
STARTUP W, R, SYSMODE M
U, or F
System Action: If this error occurs in the job control parameter processing, the database manager ends.
If this error occurs during parameter data set processing, the database manager ends unless the yyyyyyyy parameter is correctly specified in the job control. See System Programmer Response.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid initialization parameter value in either the job control or the parameter data set. If the invalid parameter was specified in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing.
| ARI0014E | The database manager requires PROGNAME when SYSMODE = S AND STARTUP = {W|R}. |
Explanation: When SYSMODE=S and STARTUP=W (or STARTUP=R) is specified, the PROGNAME initialization parameter must be specified.
System Action: If this error occurs in the job control parameter processing, the database manager ends. If this error occurs during parameter data set processing, the database manager ends unless the PROGNAME or SYSMODE or STARTUP parameter is correctly specified in the job control. See System Programmer Response.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Either specify the PROGNAME initialization parameter or correct the invalid parameter value (SYSMODE or STARTUP) in either the job control or the parameter data set that is causing this message. If this parameter was specified more than once in the parameter data set, it may be overridden by a correct specification in the job control. However, the message will still be issued but may be ignored and the database manager will continue processing.
| ARI0015I | yyyyyyyy parameter value is c. |
Explanation: This message displays the final values used by the database manager as a result of the merging of job control, default parameter values.
yyyyyyyy is the initialization parameter keyword.
c is the parameter value to be used by the database manager.
yyyyyyyy c
--------- ------------------------
ACCOUNT D, T, E, or N
CHARNAME character-set-name
DBNAME database name, up to 18 characters
DSPLYDEV L, B, or C
DSPSTATS 0, 1, or 2
DUALLOG N or Y
DUMPTYPE P, F, or N
EXTEND Y or N
LOGMODE Y, A, L, or N
PARMID parameter-data-set-name
PROGNAME program-name
SECALVER Y or N
SECTYPE DB2
STARTUP C, E, F, I, L, M, R,
S, U, or W
SYSMODE M or S
TRACCONV 0, 1, or 2
RMTUSERS 0 - 65535
TRACDBSS 0, 1, or 2
TRACRDS 0, 1, or 2
TRACDSC 0, 1, or 2
TRACWUM 0, 1, or 2
TRACDRRM 0, 1, or 2
TRACSTG 0 or 1
System Action: Processing continues.
Notes:
System Programmer Response: You may want to verify that the initialization parameter values are correct.
| ARI0016I | yyyyyyyy parameter value is n. |
Explanation: This is an information message that displays the final values used by the database manager as a result of the merging of job control, parameter data set, and default parameter values.
yyyyyyyy is the initialization parameter keyword.
n is the parameter value to be used by the database manager.
yyyyyyyy n --------- -------------- ARCHPCT 10 to 99 CHKINTVL 1 to 99999999 DISPBIAS 1 to 10 NCSCANS 1 to 655 NCUSERS 1 to 252 NDIRBUF 10 to 400000 NLRBS 50 to 583333 NLRBU 10 to 583233 NPACKAGE 1 to 32766/NCUSERS NPACKPCT 0 to 100 NPAGBUF 10 to 400000 PROCMXAB 0 to 255 PTIMEOUT 0 to 99999 SLOGCUSH 11 to 100 SOSLEVEL 1 to 100 TRACEBUF 0 to 99999
System Action: Processing continues.
| Note: | The ARCHPCT parameter is displayed only if LOGMODE=A. |
System Programmer Response: You may want to verify that the initialization parameter values are correct.
| ARI0017E | An error occurred in the parameter specification. |
Explanation: One or more errors were found while processing the initialization parameters. Previous messages indicate the parameter in error and the correction.
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the invalid initialization parameter value in either the job control or the parameter data set. If the invalid parameter was specified in the parameter data set, it may be overridden by a correct specification in the job control.
| ARI0018I | {JCL|xxxxxxxx} - DBNAME parameter is ignored for VSE/AF. |
Explanation: JCL indicates that the parameter in error was specified in the job control.
xxxxxxxx is the name of the parameter data set which contains the parameter in error.
System Action: Processing continues. The specified keyword is ignored.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Remove the DBNAME specification.
| ARI0022E | Field procedure fieldproc-name has abnormally terminated. Please remove it from your installation. |
Explanation: The field procedure fieldproc-name has abended. You must remove the procedure from the system before restarting the system. Executing field procedures that contain errors can affect the security and integrity of the database. Thoroughly test the field procedure before reinstalling it on your system.
System Action: The application server will produce a mini-dump. When possible, processing will continue.
Operator Response: Save the console output for the system programmer.
System Programmer Response: Remove the field procedure from your system before restarting the database manager. Ensure that the field procedure is thoroughly tested before reinstalling it.
| ARI0023I | The program-name program will be invoked in AMODE amode. |
Explanation: The program-name program will be started in the addressing mode amode specified. This could be either 24-bit or 31-bit addressing. Note that this addressing mode corresponds to the addressing mode of the application program. If the application program is a DBS utility or a DB2 Server for VSE preprocessor, the addressing mode will always be AMODE 24. This message is issued before invoking the single-user-mode application program-name.
System Action: Processing continues.
System Programmer Response: If the amode is not what you want, refer to the appropriate application programming language manual.
| ARI0024E | DBCS conversion procedure transproc-name has abnormally terminated. Please remove it from your installation. |
Explanation: The DBCS conversion procedure transproc-name has abended. Thoroughly test the procedure before re-installing it on your system. If you want to replace or remove this procedure from your system, contact your system programmer.
System Action: The application server will produce a mini-dump. When possible, processing will continue.
Operator Response: Save the console output for the system programmer.
System Programmer Response: Determine the CCSID conversions that use this DBCS conversion procedure by checking the TRANSPROC column of the catalog table SYSTEM.SYSSTRINGS. Refer to the DB2 Server for VSE System Administration manual for information on updating these CCSID conversions to make use of another DBCS conversion routine.
| ARI0025I | The program program-name is loaded at load-address. |
Explanation: program-name is the name of the phase loaded by the database manager.
load-address is the storage address (expressed in hexadecimal) where the phase was loaded.
System Action: Processing continues.
System Programmer Response: You may want to note the address for use in any potential problem determination.
| ARI0026E | An error occurred in the attempt to load program xxxxxxxx. |
Explanation: xxxxxxxx is the name of the phase that the application server attempted to load.
The reason code is the system return code (from the CDLOAD macro):
| Note: | The reason codes are the VSE/Advanced Functions CDLOAD return codes. |
System Action: The database manager is ended.
Operator Response: If the reason code indicates insufficient storage, restart the application server after allocating a larger partition. For all other reason codes, notify your system programmer.
System Programmer Response: Catalog the phase in the library core image member if not found. You may have to assist the operator in determining what partition size will be needed if insufficient GETVIS storage is the problem.
If the problem is a hardware error, contact your installation hardware service representative. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0027E | A communication link error has occurred. |
Explanation: The database manager has violated the use of the CPC services. The most probable causes may be:
(See Chapter 19, DB2 Server for VSE Reason Codes.)
System Action: The database manager is ended.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0028I | The database manager is terminating. |
Explanation: This informational message is issued as acknowledgment when an SQLEND command (other than SQLEND QUICK) is first entered.
| Note: | SHUTDOWN is a valid synonym for SQLEND. |
System Action: The database manager will start termination procedures; all active users (DB2 Server for VSE agent structures) will be allowed to complete their processing. No new users will be allowed access to database services. After all active users have completed their processing, the database manager will perform any optional functions specified on the SQLEND command and end.
| ARI0029I | n communication links are still connected. |
Explanation: This informational message tells the operator how many users are active when the SQLEND command was entered. This number is the number of agent structures containing connected users.
This message is issued when an SQLEND command (other than SQLEND QUICK) is first issued. It is also issued with an updated number as each communication link is disconnected. This may allow the operator to determine how long it might take to complete the SQLEND process.
| Note: | SHUTDOWN is a valid synonym for SQLEND. |
System Action: Processing continues.
| ARI0030I | Database manager termination is already in progress. |
Explanation: This informational message is issued in response to a subsequent SQLEND command (other than SQLEND QUICK).
System Action: Processing continues and the command is ignored.
Operator Response: None unless an immediate shutdown is required, in which case an SQLEND QUICK command can be issued. If that command is issued, any logical units of work in progress will be resolved (either committed or backed out) the next time the database manager is brought up.
| Note: | SHUTDOWN is a valid synonym for SQLEND. |
| ARI0031E | Invalid SQLEND parameter. |
Explanation: The SQLEND command was entered with an invalid parameter. The operator should specify only a valid SQLEND command. For more information, refer to the DB2 Server for VSE & VM Operation manual.
| Note: | SHUTDOWN is a valid synonym for SQLEND. |
System Action: Operator command processing ends.
Operator Response: Reenter the command correctly.
| ARI0032I | The database manager has terminated. |
Explanation: This informational message is issued prior to closing any data sets and ending.
| Note: | The operator should not enter a CANCEL command after this message has been displayed. It will cause immediate termination of the database manager with the message ARI0034E being displayed. |
| Note: | If the database manager has ended abnormally, a DB2 Server for VSE mini-dump will be displayed. These dumps are described in the DB2 Server for VSE & VM Diagnosis Guide and Reference manual. |
System Action: The database manager is ended.
| ARI0033E | An error occurred while attempting to close SYSLST. |
Explanation: Termination could not properly close the printer file used for error and informational messages.
System Action: Database manager termination continues.
Operator Response: Notify your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0034E | An error occurred during termination. |
Explanation: This message is issued whenever database manager termination is in progress and an error (for example: a program check) occurs which causes the termination process to be invoked. This message is also issued if the operator enters a CANCEL command after message ARI0032I has been displayed.
| Note: | Tape files may not have been closed and may be missing the last buffer contents and have no tape mark (EOF indicator). |
System Action: The database manager ends immediately.
Operator Response: Notify your system programmer. You may wish to write a tapemark on any open tape files.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0035I | Application server cancel has been requested. |
Explanation: The operator has issued a CANCEL command or an I/O cancel has been issued by another VSE system component. The operator is allowed to request a dump if desired. See message ARI0044D.
System Action: The database manager ends.
| ARI0036E | No SAVEAREA found for ARIXRDS. |
Explanation: A program check interrupt occurred in the package. The database manager attempted to recover, but could not find the save area for the RDS recovery routine (ARIXEBR).
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0037E | The entry point for ARIXEBR1 cannot be found. |
Explanation: A program check interrupt occurred in the package. The database manager attempted to recover, but could not find the entry point to the RDS recovery routine (ARIXEBR1).
System Action: The database manager is ended.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0038E | Invalid return code from ARIxxxx. |
Explanation: An internal error has occurred.
ARIxxxx is the name of the module which returned an unexpected or invalid return code to the caller.
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0039E | Application server limit error occurred - ARIxxxx nn. |
Explanation: This message is usually due to causes such as:
Other messages issued prior to this message will identify the error condition and aid in the corrective action to be taken.
ARIxxxx is the name of the module which detected the limit error.
nn is the error detection point within that module. See Chapter 22, Limit Errors for a list of critical detection points and their related error conditions.
No DB2 Server for VSE dump or mini-dump will be displayed because a limit error occurred.
System Action: The database manager is ended.
Operator Response: If the error is due to insufficient GETVIS storage, restart the database manager after allocating a larger partition.
System Programmer Response: You may have to reallocate external storage space, catalog missing phases into the library core image member, or assist the operator in allocating a larger partition size.
| ARI0040E | A database manager system error occurred - ARIxxxx nn. |
Explanation: An internal error occurred within the database manager system. Usually a "should not occur" condition has occurred. A dump will be taken according to the DUMPTYPE initialization parameter. This is a system error.
ARIxxxx is the name of the module that detected the error.
nn is the error detection point within the module. See Chapter 23, System Errors for a list of communication link errors.
Notes:
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0041E | System hardware error occurred - ARIxxxx nn. |
Explanation: A hardware error was detected during a GETVIS, CDLOAD, I/O, etc. operation.
ARIxxxx is the name of the module that detected the error.
nn is the error detection point in the module.
A preceding message describes the cause of the hardware error. A dump or mini-dump will not be taken if a hardware error occurs.
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a hardware error is indicated, report this problem to the hardware service person at your installation. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0042I | Database manager reason code is n1 - X'n2'. |
Explanation: This code is a VSE system return code returned to the database manager. It can be used for problem determination.
n1 is the decimal representation of the reason code.
n2 is the hexadecimal representation of the reason code.
| Note: | A previous message should have been displayed related to the reason code. See Chapter 19, DB2 Server for VSE Reason Codes and Chapter 16, DBSS Return Codes for additional information about the reason codes. |
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Note the reason code for problem determination.
| ARI0043I | Database manager return code is n. |
Explanation: This return code is for informational purposes. Except for return code 0, it is related to any earlier DB2 Server for VSE messages that have been displayed. This return code is also returned to VSE upon return by the database manager.
n is one of the following:
For nonzero return codes, see previous database manager error messages.
| Note: | When the database manager is operating in single user mode: If this message is accompanied by message ARI0046I, the return code passed back to the system will be the code from the database system. |
System Action: Database manager termination continues.
| ARI0044D | If you want a dump, enter 1(Yes). Otherwise enter 0(No). |
Explanation: The abnormal termination routine has been entered due to an operator or I/O cancel request. If a dump is required, the operator must reply with a 1 or YES to the message. If 0 or NO is entered, no dump will be taken. Any other reply will cause message ARI0052E to be displayed. The dump to be taken is determined by the DUMPTYPE initialization parameter (DUMPTYPE=P, F, or N). If DUMPTYPE=N was specified, the default DUMPTYPE=F is assumed.
System Action: Processing continues as determined by the operator reply.
Operator Response: Reply 1 or YES if a dump is required. Reply 0 or NO if no dump is required.
| ARI0045I | Ready for operator communications. |
Explanation: This informational message is issued only in multiple user mode. It informs the system operator that the database manager is ready to accept DB2 Server for VSE operator commands.
Operator Response: Enter any operator commands desired.
| ARI0046I | xxxxxxxx return code is n1 - X'n2'. |
Explanation: This message occurs only when the database manager is operating in single user mode. It reports a nonzero application return code (passed back in register 15) when the application program returns to the database manager.
xxxxxxxx is the name of the application program (specified in the PROGNAME initialization parameter).
n1 is the decimal representation of the return code.
n2 is the hexadecimal representation of the return code.
Some application programs (such as those written in COBOL or FORTRAN) do not pass back a zero return code upon successful completion. If the application program does not make the return code zero, whatever value is in register 15 will be displayed as the return code. This value is normally the entry point address of the application program; it is typically a large value.
IBM-supplied DB2 Server for VSE programs (for example, a preprocessor or the DBS utility) that run in single user mode will also have their return codes displayed in this message.
If the name of the application program given in the message is one of the preprocessors:
the following return codes apply:
Return codes 12 and 16 are called preprocessor terminating errors. The preprocessor halts at the point of the error and performs its cleanup processing:
If the name of the application program given in the message is the DBS utility (ARIDBS), the following return codes apply:
When the database manager is started for database generation (STARTUP=C is specified), the program name is always ARIGCAT.
When the database manager is started for log reconfiguration (STARTUP=L is specified), the program name is always ARISEGB.
Unless the return code is 512 or greater, the application return code is passed back to the system.
System Action: Database manager termination continues.
Operator Response: None, unless otherwise requested by the application programmer.
System Programmer Response: None, unless otherwise requested by the application programmer or by preceding messages if the application program is the DB2 Server for VSE program.
| ARI0047E | CDLOAD - Reason Code = nnn. |
Explanation: This message only occurs with message ARI0026E. It is issued when an error other than "not found" or "insufficient storage" occurs while the database manager is trying to load the program indicated in message ARI0026E.
CDLOAD is the type of load operation being tried by the database manager when the error occurred.
nnn is the return code indicating the cause of the failure. Refer to the VSE manual that documents the load operation in question.
This message is accompanied by a DB2 Server for VSE dump (as specified by the DUMPTYPE initialization parameter) and message ARI0040E, except when the program identified is ARICMOD. The return code in message ARI0043I is 516.
System Action: The database manager ends.
Operator Response: Notify your system programmer.
System Programmer Response: Make a record of what went wrong and contact the designated support group for your installation.
| ARI0051E | Accounting support specified, but VSE job accounting support is not provided. |
Explanation: The DB2 Server for VSE accounting support uses the VSE GETFLD macro to collect CPU time on a user basis. This macro is supported only when the VSE job accounting support (JA) is provided. This means that the JA option is specified on the IPL SYS command.
System Action: If this condition occurs, DB2 Server for VSE accounting support is shut off, and the database manager is ended.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Re-IPL the system with the JA option specified on the IPL SYS command. Then restart the database manager.
| ARI0052E | response is incorrect. Please reenter the correct response. |
Explanation: An incorrect value (response in text) was entered in response to the previous message. If response is blank, a null response (no response or blanks) was entered.
System Action: The previous message will be re-displayed.
Operator Response: Determine the valid response to the previous message, and enter the valid response when the prompting message is re-displayed.
| ARI0053E | An unexpected error occurred accessing the application server at initialization. DBSS Return Code = code. |
Explanation: During the database manager startup, the RDS module ARIXERO encountered unexpected problems when attempting to access the application server.
code is the DBSS return code from the open. Refer to Chapter 16, DBSS Return Codes.
System Action: The database manager is ended.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Note the DBSS return code, make a record of what went wrong, and contact the designated support group for your installation.
| ARI0054E | Unable to do COMMIT. DBSS Return Code = return-code. |
Explanation: During the database manager startup, ARIXERO was unable to issue a COMMIT after opening the record catalog table RIDs, TIDs, and IIDs.
return-code is the DBSS return code from the open. Refer to Chapter 16, "DBSS Return Codes".
System Action: The database manager is ended.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Perform problem determination. If a database system error occurred, make a record of what went wrong and contact the designated support group for your installation.
| ARI0056I | Tracing terminates because of operator request. |
Explanation: During database initialization, you specified the parameters TRACCONV, TRACDBSS, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG (or any combination). The initialization dialog prompted the operator for the tape unit cuu or the reply DISK (output to disk) for the trace output file (message ARI0092A) and the operator responded with CANCEL to the prompting message. This message indicates that database initialization is continuing but with trace inactive ("output disabled").
System Action: Database initialization continues, but with the trace inactive, the TRACCONV, TRACDBSS, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG parameters are overridden.
| Note: | Since trace is "output disabled", the TRACE OFF operator command must be entered before the TRACE ON operator command can be entered. |
| ARI0057E | Message ARInnnn has formatting error. |
Explanation: This is a database error. The message identified by nnnn (that is, message prefix ARI) either:
For a multi-line message, the error may have occurred on any (or all) lines. The message in error precedes this message on the display terminal or printer.
System Action: Normal processing continues.
Operator Response: Save the message output (this message and the message identified by nnnn) and notify your system programmer.
Programmer Response: Same as Operator Response.
System Programmer Response: Save the message output and report this problem to the designated support group for your installation. If the application program using the database manager is known, save information about it so that the problem can be recreated if necessary.
| ARI0058E | Message editing error {MSG ID = nnnn | SQLCODE = nnnn}. Reason Code = nn. |
Explanation: This is a system error. A database component requested that a message be edited and displayed. If SQLCODE appears in the message text, the request was for the SQLCODE message associated with SQLCODE nnn. If MSG ID appears in the message text, the request was for the database message ARInnnn (nnnn from message text).
The exact cause of the message editing error is identified by the Reason Code=nn value in the message text where:
You may be able to identify the lost message from the displayed message number or SQLCODE and take appropriate action.
System Action: Processing continues as though the lost message had been displayed. Subsequent messages may clarify system activity.
User Response: If the reason code is 04 and the database machine is operating at a later release than your user machine, use the message number or SQLCODE in the message text to help you determine the release level of the database machine.
Operator Response: Save this message and, if possible, any additional information about the application program or the database manager program which was running and notify your system programmer.
Programmer Response: See Operator Response.
System Programmer Response: Save the message output and any other information given to you by the operator or programmer and report this problem to the designated support group for your installation. If the application program using the database manager is known, save information about it so that the problem can be recreated if necessary.
| ARI0059E | Program cancelled due to insufficient virtual storage. |
Explanation: An attempt to acquire partition virtual storage (using the VSE GETVIS macro) failed.
System Action: The program will be canceled because of insufficient virtual storage.
Operator Response: If the return code of 32 (X'20') from the GETVIS macro is displayed (see Note), a main storage hardware error was detected. Report this problem to your installation hardware service person.
Otherwise, assume that there is not enough virtual storage and proceed as follows. Either run the failing program in a larger partition or change the program parameters so that it requires less virtual storage. If you are running a program with the database manager in single user mode, you may be able to run it in a smaller partition while the database manager is running in multiple user mode. Consult with your database or VSE system programmer to help you.
| Note: | An attempt is made to provide information about: |
System Programmer Response: See Operator Response.
| ARI0060I | Database manager initialization complete. |
Explanation: The database manager has completed the initialization process in multiple user mode. It is ready to accept work requests from other partitions.
System Action: The database manager enters wait state, waiting for work requests from other partitions and for system operator requests to enter operator commands.
Operator Response: Database application programs including preprocessors, ISQL, and the Database Services Utility program may be started in other partitions.
Database operator commands may be entered from the system operator console.
| ARI0061E | The operator command value value is too long. |
Explanation: The system operator or ISQL terminal user has entered a database operator command which has a command name or parameter which exceeds eighteen characters in length. Database operator command names and parameters may not exceed eighteen characters. The first eighteen characters of the invalid value are displayed in the message. This error may be caused by misspelling an operator command name or parameter or by omitting the blank required between the parameters of the command or between the command name and the first parameter.
System Action: Operator command processing ends.
Operator Response: Use the VSE Attention routine to initiate communication with the database manager. Reenter the command with the correct value. For a description of the database operator commands, see the DB2 Server for VSE & VM Operation manual.
User Response: Reenter the command with the correct value. See the DB2 Server for VSE & VM Interactive SQL Guide and Reference manual.
| ARI0062A | dbname : Enter a DB2 Server for VSE operator command. |
Explanation: The dbname is the name of the application server started in the partition. The system operator has requested (using the VSE Attention facility) communication with the database manager. The database manager is prompting the operator to enter a database operator command.
System Action: The database manager will process the database operator command entered in response to this prompting message.
Operator Response: Enter the desired database operator command.
| Note: | If you do not wish to enter a command, respond to message ARI0062A by pressing only the Enter key. This will cause the database manager to end command processing until you again request communication with the database manager. |
| ARI0063I | You did not enter an operator command. |
Explanation: The system operator has entered a null line in response to a request to enter a database operator command, or ISQL has transmitted a blank line for database operator command processing. This should not occur for ISQL (ISQL internal error).
System Action: Operator command processing ends. To enter another database operator command, you must use the VSE Attention routine to initiate communication with the database manager.
User Response: You may enter a database operator command or an ISQL or SQL command. If you are in ISQL, this message indicates an internal error in ISQL. In this case, notify your system programmer.
System Programmer Response: If message ARI0063I is received by an ISQL terminal user, ISQL is malfunctioning. Determine the service level of the database manager and report this problem to the designated support group for your installation.
| ARI0064E | You entered an invalid operator command. |
Explanation: The operator or the ISQL terminal user has entered an operator command. Either:
Notes:
System Action: Operator command processing ends.
Operator Response: Initiate communication with the database manager (use the VSE Attention routine) and reenter the command with the correct name and operands. For the descriptions of the database operator commands, see the DB2 Server for VSE & VM Operation manual.
User Response: You may enter a database operator command or an ISQL or SQL command. This message indicates an internal error in ISQL. Notify your system programmer.
System Programmer Response: If message ARI0064E is received by an ISQL terminal user, ISQL is malfunctioning. Determine the service level of the database manager and report this problem to the designated support group for your installation.
| ARI0065I | Operator command processing is complete. |
Explanation: This message notifies the operator or the ISQL terminal user that a database operator command has successfully completed processing.
System Action: Normal processing continues. You can use the VSE Attention routine to start further communication with the database manager.
User Response: You may enter another database operator command or an ISQL or SQL command.
| ARI0066E | An error occurred processing the operator command. |
Explanation: A database operator command was routed to the module which processes the command. The module detected an error and ended command processing. If the error was an invalid command parameter, the module issued a message identifying the error. If the module invoked database services which detected an error (for example, I/O error), then the operator received an error message due to the error. Note that in the last case, the operator command may have come from an ISQL terminal but the specific error message is displayed to the operator.
System Action: Operator command processing ends.
Operator Response: Refer to the previous error message for the cause of the error and for corrective action.
User Response: If there is a previous error message indicating the cause of command failure, take the corrective action indicated by that message. If there is no previous error message, the command was not executed due to some error detected by the database manager (such as an I/O error) and the operator has been notified of the error. If the problem persists, you may wish to notify the system programmer of your problem.
System Programmer Response: Obtain the ISQL terminal user and operator error message output and take the corrective action recommended or suggested by the error messages.
| ARI0067E | Invalid SHOW command entered. |
Explanation: This message was caused by the operator or ISQL terminal entering:
System Action: Operator command processing ends.
Operator Response: Reenter the SHOW command with the correct operands. For a description of this command, refer to the DB2 Server for VSE & VM Operation manual.
User Response: Reenter the SHOW command with the correct operands. For the description of SHOW commands, refer to the DB2 Server for VSE & VM Operation manual. You may alternatively enter an ISQL or SQL command.
| ARI0068E | Invalid SET command entered. |
Explanation: The operator SET command operand was invalid or omitted.
System Action: Operator command processing ends.
Operator Response: Reenter the SET command with the correct operand. For the description of this command, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0069E | READ MEMBER sublibrary.membername FAILED, REASON=nn CODE=nn |
Explanation: During reading of the SYSIPT file, a READ MEMBER statement was encountered. (The READ MEMBER statement is described in the CHANGE TO PROGRAM DIRECTORY OR BOOK INFO WENT TO.) While attempting to access and read the VSE library source statement member specified in that statement, an error occurred.
sublibrary identifies the sublibrary containing the member.
membername identifies the library source statement member to be read. REASON is the Primary Error Code, and CODE is the Secondary Error Code.
For further explanation, look up the displayed error codes under either Chapter 21, Include File Access Errors, or "INCLUDE FILE ERRORS" in the HELP text.
System Action: See subsequent database messages. Normally this error condition causes the job to end.
User Response: Save this error message and give it to the job submittor or the system programmer for problem resolution.
System Programmer Response: Take action based on the REASON and CODE values.
| ARI0073E | Ready filename accounting output volume. Enter CUU or CANCEL. |
Explanation: The database manager is requesting the system operator to ready a tape unit for accounting output and to supply its cuu. The database accounting file will have the filename indicated by filename, which is either ARIACC1 or ARIACC2.
If this message is redisplayed after message ARI0075E (indicating an accounting file open error), the database manager is requesting corrective action for that message, plus the operator action for ARI0073E.
System Action: If the operator enters a cuu, the indicated tape unit is dynamically assigned and opened.
If the operator enters CANCEL, accounting support is shut off, and the database manager ends.
Operator Response: The database manager is requesting the system operator to:
| Note: | The selected tape unit must be currently unassigned. |
Reply CANCEL if no tape is available, or if accounting is not desired, or if the ARI0075E error condition cannot be corrected.
| ARI0074E | Invalid response {BLANK|value} to prompt message. |
Explanation: An incorrect value (value in message text) or no value (BLANK in message text) was entered in response to message ARI0073A.
System Action: The accounting prompting message ARI0073A (to which the invalid response was entered) is redisplayed.
Operator Response: Determine the valid response to the accounting prompting message, and enter the valid response when the prompting message is redisplayed.
| ARI0075E | {OPEN|CLOSE|GENCB} error on accounting file filename
[cuu].
Reason Code = reason-code. Return Code = return-code. [Error Code = error-code.] |
Explanation: In attempting to open or close the database accounting output file, or to generate the ACB/RPL for a VSAM ESDS accounting file, an error occurred. If accounting data is being written to tape, the cuu of the tape is provided in the message.
The file has the name indicated by filename, which is either ARIACC1 or ARIACC2.
If an error code is not displayed, the reason-code value is the primary error code and the return-code value is the secondary error code. For further explanation, look up the displayed reason code and return code under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
If an error code is displayed, the return-code is the contents of register 15 after VSAM processed the request macro. See the VSE/VSAM Messages and Codes manual for the possible cause of this error.
System Action: If the error condition is a dynamic assignment error on OPEN, message ARI0073A displays to allow the accounting output volume to be respecified. If the error condition is something other than a dynamic assignment error on an OPEN, the accounting support is shut off and the database manager ends.
Operator Response: Report the message to your system programmer. For corrective action, look up the displayed reason and return codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text. For VSAM errors, see the VSE/VSAM Messages and Codes manual for the possible cause of this error.
| ARI0076D | Write error on accounting file filename [cuu].
Reason Code = code Return Code = code [Error Code = code] Do you want to continue? No = terminate, Yes = continue without accounting, Alt = continue but use alternate file. Enter 0(No), 1(Yes), or 2(Alt). |
Explanation: In attempting to write database accounting data to the accounting output file, an access error occurred. All application server activity is halted until the reply to the prompt is given. If accounting data is being written to tape, the cuu is provided in the message. The database accounting file has the file name indicated by filename. This name will either be ARIACC1 or ARIACC2. If an error code is not displayed, the Reason Code value is the primary error code and the Return Code value is the secondary error code. See Chapter 20, Sequential File Errors for reason code and return code displayed. If an error code is displayed, the return code is the contents of register 15 after VSAM processed the request macro. See the VSE/VSAM Messages and Codes manual for the possible cause of this error.
The database manager is now asking whether you wish to: continue execution with the accounting support disabled, switch to the alternate accounting file, or terminate the database manager. The operator can reply No(0), Yes(1), or Alt(2).
System Action: All application server activity is halted until the operator replies to the prompt. If the operator replies Yes or No, accounting support is immediately disabled. This error condition prevents the accounting output file from being closed.
If the reply is Yes, execution continues with the accounting support disabled.
If the response is Alt, the database manager issues an OPEN for the alternate accounting file, and continues executing with accounting support enabled.
If the reply is No, the database manager immediately terminates. The condition is treated as a limit error.
If accounting is to tape, the tape unit identified in this error message will be dynamically unassigned. Therefore the tape unit will be available for any use, including the alternate accounting file (unless error message ARI112E is displayed). If this unit is used for the alternate accounting file, a new tape volume must be mounted.
Operator Response: Reply Yes(1), No(0), or Alt(2). Save this message and give it to your system programmer. Do not try to process the output file.
If accounting data is being written to tape, you can try to salvage the accounting data on the output tape by using the VSE job control MTC WTM,cuu statement.
System Programmer Response: For corrective action, see Chapter 20, Sequential File Errors for the reason code and return code displayed. For VSAM errors, refer to the VSE/VSAM Messages and Codes manual for the possible cause of this error.
| Note: | Although you may have partial accounting output, it may not be cleanly processed because the file was not closed. |
| ARI0077D | End of extents encountered on accounting file filename.
No = terminate, Yes = continue without accounting, Alt = continue but use alternate file. Enter 0(No), 1(Yes), or 2(Alt). |
Explanation: In attempting to write database accounting data to the accounting output DASD file, an end-of-extents condition occurred. The accounting DASD file is now full. Note that some accounting data has already been lost. All application server activity is halted until the reply to the prompting message is given. The database accounting file has the file name indicated by filename. This name will either be ARIACC1 or ARIACC2.
The database manager is now asking whether you wish to: continue execution with the accounting support disabled, switch to the alternate accounting file, or terminate the database manager. The operator can reply No(0), Yes(1), or Alt(2).
System Action: All application server activity is halted until the operator replies to the prompt. If the response is Yes or No, accounting support is immediately disabled.
If the reply is Yes(1), the database manager execution continues with accounting support disabled. Eventually, the actions described under System Programmer Response should be done.
If the response is Alt(2), the database manager issues an OPEN for the alternate accounting file and continues executing with accounting support enabled.
If the response is No(0), the database manager terminates immediately. The condition is treated as a limit error.
Operator Response: Reply Yes(1), Alt(2), or No(0). Save this message and give it to your system programmer.
System Programmer Response: You may need to allocate a larger space for the accounting file. Update the DLBL/EXTENT information accordingly in the job control for the accounting file. Ensure that the full accounting file is saved for later processing. If you are using database tables to store the accounting data, the full accounting file should be loaded (using DATALOAD) into the tables at the earliest opportunity.
| ARI0078E | Invalid response to accounting file error prompt message. |
Explanation: An invalid response was given to accounting file error prompt message ARI0076D.
System Action: Message ARI0076D is redisplayed.
User Response: Determine the valid response to message ARI0076D, and enter the valid response when the prompting message is redisplayed.
| ARI0079I | Accounting file filename {OPENED|CLOSED}. |
Explanation: The database accounting file has been opened or closed. This file has the name indicated by filename, which is either ARIACC1 or ARIACC2.
System Action: If the accounting file was opened, the system is writing accounting records to the opened file. If the accounting file was closed, it is available for any other processing.
User Response: None required.
| ARI0080E | Trace file end of extents encountered. Trace output is disabled. |
Explanation: In attempting to write database trace data to the trace output DASD file, an end-of-extents condition occurred. The trace DASD file is now full. Tracing is disabled.
System Action: The database manager continues without any further database trace output. This error condition prevents closing the trace output file during TRACE OFF command processing, database manager shutdown, or application termination.
User Response: Save this message and give it to your system programmer. Do not try to process the trace output file.
See the Operator Response for message ARI0097I for possible action to take to salvage the accumulated trace output data.
Operator Response: See User Response.
System Programmer Response: You may need to allocate a larger space for the trace file. Update the DLBL/EXTENT information accordingly in the job control for the trace file.
| ARI0081E | Write error trace file. Reason Code = nn. Error Code = nn. |
Explanation: When the system attempted to write trace data to the trace output file, an access error occurred. Trace status is now "output disabled". The trace file has the file name ARITRAC. The Reason Code value is the Primary Error Code. The Error 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: Any further database trace output is disabled. This error condition prevents closing the trace output file during TRACE OFF command processing, database manager shutdown, or application termination.
User Response: Save this message and give it to your system programmer. If a 0Pnn message was received for the trace tape or disk unit, also give a copy of this message to the system programmer. Do not try to process the trace output file.
See Operator Response for message ARI0097I for possible action to salvage the accumulated trace output data.
Operator Response: See User Response.
System Programmer 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. Note that although you may have partial trace output, it cannot be cleanly processed because the trace file has not been closed.
| ARI0082E | TRACE command parameter n [parameter] invalid or missing. |
Explanation: The TRACE operator command was entered and is being processed. One of the following conditions was detected:
Parameter n identifies which parameter was omitted or contains the invalid value. parameter, if present in the message text, identifies the invalid parameter value. If not present, it indicates that a required parameter was omitted.
System Action: TRACE command processing ends. There is no change in the status of the database trace facility.
Operator Response: Consult the TRACE command section of the DB2 Server for VSE & VM Operation manual, and compare the TRACE command description with the TRACE command that you entered and the text of this message. Determine which parameter was erroneously specified or omitted and reenter the TRACE command.
| ARI0083I | Trace command specified {ON|OFF}, but trace already {ON|OFF CLOSED}. |
Explanation: One of the following occurred:
TRACE ON cannot be validly specified unless trace is inactive (OFF). TRACE OFF cannot be validly specified unless trace is active (ON) or inactive but with the trace file open (OFF NOCLOSE).
System Action: TRACE command processing ends. There is no change in status of the database trace facility.
Operator Response: None is required since trace is already in the state specified by the TRACE command. If you want to specify new tracing (TRACE ON) parameters, you must first successfully enter the TRACE OFF command (the NOCLOSE option allows the trace file to be kept open for further output in the same trace file).
| ARI0084D | Enter one of userid, AGENT n, * (for all), or CANCEL. |
Explanation: The TRACE ON operator command is being processed. The database manager is prompting the operator to specify which database user ID or agent number (or * for all agent numbers) is to be traced.
System Action:
Operator Response: Enter one of the following:
In multiple user mode is Ready/Recovery Agent.
| Note: | On SHOW commands, user agents 4 through n are displayed as agents 1, 2, ..., NCUSERS initialization parameter value. |
| ARI0085E | Agent number [value] invalid or missing. |
Explanation: An incorrect or null (blank) agent number value was entered in response to TRACE ON command prompting message ARI0084D.
System Action: TRACE ON prompting message ARI0084D is re-displayed to allow the correct response to be entered.
Operator Response: Determine the valid agent number value you will enter in response to prompting message ARI0084D, and enter the valid response when the prompting message is re-displayed.
| ARI0086E | Invalid response {BLANK|value} to prompt. |
Explanation: An incorrect value (value in message text) or no value (BLANK in message text) was entered in response to a TRACE ON command or trace initialization prompting message.
System Action: The TRACE prompting message (to which the invalid response was entered) is redisplayed.
Operator Response: Determine the valid response to the trace prompting message, and enter the valid response when the prompting message is re-displayed.
| ARI0087D | Enter one or more component names or CANCEL. Valid component names are DBSS, RDS, [WUM, DRRM,] DSC, CONV, and STG. |
Explanation: The TRACE ON operator command is being processed. The database manager is prompting the operator to specify the major components (DBSS, RDS, WUM, DRRM, DSC, CONV, or STG) that are to be traced.
System Action:
Operator Response:
Enter any of DBSS, RDS, WUM, DRRM, DSC, CONV, or STG (with one or more blanks between them). You can enter them in any order.
| Note: | You can see this message in all environments. In environments where components are not active, however, the components tracing does not take place, even if the operator specifies them. |
| ARI0088D | Enter RDS function name and trace-level pairs.
Valid function names are *, EXEC, PA, OPT, AG, INT, AU, SG, and CANCEL. Valid trace-level values are 0, 1, and 2. |
Explanation: The TRACE ON command is being processed. The operator has responded RDS to prompting message ARI0087D. The database manager is prompting the operator to specify which functions of RDS to be traced and the desired trace level for each function.
System Action:
| Note: | If trace level 0 is entered for a function, it will not be traced (equivalent to not entering the function at all). Therefore, if you want to trace all RDS functions (at level 2, for example) except INT, you can enter * 2 INT 0. Since INT appears after the * specification, it overrides the implicit INT 2 implied by * 2. Likewise, entering : * 1 EXEC 2 will cause all RDS functions except EXEC to be traced at level 1 and EXEC to be traced at level 2. |
Operator Response:
| ARI0089E | Trace-level [value] for {RDS|CONV|DBSS |DSC|WUM|DRRM|STG} {*|function name} invalid or missing. |
Explanation: You entered one of the following:
Your entry was in response to one of the following TRACE ON command prompting messages:
{*|function name} in message text identifies the valid RDS, DBSS, DSC, or DRRM function name that precedes the omitted or incorrect trace-level value.
System Action: The TRACE ON prompting message (to which the incorrect response was entered) is re-displayed.
Operator Response: Determine the valid response to the trace prompting message (each function name must be followed by a valid trace-level value of 0, 1, or 2 with a blank between them) and enter the valid response when the prompting message is re-displayed.
| ARI0090D | Enter DBSS function name and trace-level pairs.
Valid function names are *, ENTRY, EXIT, LOG, LOCK, LUW, DC, DM, STOR, SORT, INDEX, STAT, and CANCEL. Valid trace-level values are 0, 1, and 2. |
Explanation: The TRACE ON command is being processed. The operator has responded DBSS to prompting message ARI0087D. The database manager is prompting the operator to specify which functions of DBSS are to be traced and the desired trace level for each function.
System Action:
| Note: | If trace level 0 is entered for a function, it will not be traced (equivalent to not entering the function at all). Therefore, if you want to trace all DBSS functions (at level 2, for example) except INDEX, you can enter: * 2 INDEX 0. Since INDEX appears after the * specification, it overrides the implicit INDEX 2 implied by * 2. Likewise, entering: * 1 ENTRY 2 will cause all DBSS functions except ENTRY to be traced at level 1 and ENTRY to be traced at level 2. |
Operator Response:
| ARI0091D | Enter the dump trace point number, or CANCEL to terminate trace command processing. |
Explanation: The TRACE ON command is being processed. The operator specified the DUMP parameter in the TRACE ON command. The database manager is prompting the operator to specify the CONV, DBSS, RDS, DSC, WUM, DRRM, or STG trace point number that is to cause a database snap dump to occur when the trace point is first activated. The snap dump will dump either all of the database partition (full dump), or only that part of the partition which does not contain database load modules (partial dump). The database initialization parameter DUMPTYPE will control whether a full dump is given (DUMPTYPE=F) or a partial dump is given (DUMPTYPE=P or N).
System Action: The entered trace point number is stored. When that trace point is first activated for tracing, a snap dump is produced on SYSLST. After the first activation, no more snap dumps are produced.
If CANCEL is entered, TRACE command processing ends.
Operator Response:
| ARI0092A | Ready trace output volume. Enter CUU, DISK, or CANCEL. |
Explanation: The operator specified one or more of the initialization parameters TRACCONV, TRACDBSS, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG. The initialization is requesting the system operator to:
If this message is redisplayed after message ARI0094E (indicating a trace file open error), the database manager is requesting corrective action for that message plus the operator action indicated above.
System Action: If the operator enters cuu, the indicated tape unit is dynamically assigned and opened. DB2 Server for VSE initialization continues with database trace active.
If the operator enters DISK, the trace disk file is opened. DB2 Server for VSE initialization continues with database trace active.
If the operator enters CANCEL, message ARI0056I is displayed. DB2 Server for VSE initialization continues with database trace inactive ("output disabled").
Operator Response: Database initialization is requesting the system operator to supply one of the following:
If trace output is to tape:
| Note: | The selected tape unit must be currently unassigned. |
You can reply CANCEL if no tape or disk file is available or tracing is not desired.
If this message is redisplayed after message ARI0094E (indicating a trace file open error), the database manager is requesting corrective action for that message plus the operator action indicated above. Reply CANCEL if the error condition cannot be corrected.
| ARI0093I | TRACE command terminated by request. |
Explanation: The TRACE ON command was being processed. The operator responded CANCEL to a prompting message.
System Action: TRACE command processing ends. There is no change in status to the database trace facility.
Operator Response: The operator may reenter the TRACE ON command.
| ARI0094E | Trace file {cuu|DISK} assign or open failed. Reason Code = nn. Return Code = nn. |
Explanation: The database manager is processing the TRACE ON command or initializing a database trace during database or Resource Adapter initialization. An error occurred while the Resource Adapter was attempting to dynamically assign (tape only) and open the trace output file on tape unit cuu (cuu is in the message text) or on a disk file (DISK is in the message text). 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 occurs in the database machine, then either:
If this error occurs in a user virtual machine, the application abends.
| Note: | If output is to tape, the tape volume has not been accessed. |
User 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.
Operator Response: See User Response.
System Programmer Response: See User Response.
| ARI0095I | Trace now on with output on unit {cuu|DISK}. |
Explanation: The TRACE ON command has been successfully processed, or database initialization has successfully initialized trace ON. Database trace is now active with trace output on tape unit cuu (cuu is in the message text) or to a disk file (DISK is in the message text).
System Action:
TRACE ON command processing is completed. Trace is active as specified by the values entered for the various TRACE ON command prompting messages, or initialization trace initialization is completed. The TRACCONV, TRACDBSS, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG initialization parameters specify how TRACE is active.
| ARI0096I | TRACE now OFF. Trace file remains open on unit {cuu|DISK}. |
Explanation: The TRACE OFF NOCLOSE command was successfully processed. Trace is inactive and the trace output file remains open for subsequent trace output (after using a TRACE ON command). If cuu is in the message text, it identifies the trace output file tape unit. If DISK is in the message text, the trace output file is a disk file. This message will occur if trace was active when the command was entered or if trace was already inactive but with the trace output file open (due to a prior TRACE OFF NOCLOSE command).
System Action: TRACE OFF command processing has completed. Trace is completely inactive.
Operator Response: None required. A TRACE ON command may now be entered. Note that a TRACE OFF command with the NOCLOSE parameter omitted (or database manager termination which closes the tape or disk file) must be executed before the trace output file can be processed.
| ARI0097I | TRACE was output disabled. TRACE is now OFF. It did not close unit {cuu|DISK|UA}. |
Explanation: The database manager is being normally or abnormally terminated, or the TRACE OFF command (with or without the CLOSE or NOCLOSE parameters) was processed. Trace was previously ON (active) due to the TRACE ON operator command or the initialization parameters TRACCONV, TRACDBSS, TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or TRACSTG.
Trace became "output disabled" (trace output suppressed) because of either:
The TRACE OFF command or database manager termination caused trace to be turned off (fully disabled), but the trace output file was not closed due to the previous problem (assign failure, open failure, or write error).
If cuu is in the message text, the trace output tape file was assigned and opened and may contain trace output data, but due to the write error and failure to close the file, the file may not be usable. Also, tape unit cuu remains assigned to the database partition until the partition goes to end of job step.
If DISK is in the message text, one of the following occurred:
If UA is in the message text, the trace output tape file was not successfully assigned and opened during database initialization.
System Action: Trace has been turned off (disabled).
| Note: | If cuu is in the message text, the tape unit cuu is no longer the trace output file. (A later TRACE ON command to another cuu will be accepted). |
Operator Response: None required. If the message was in response to the TRACE OFF command and output was to tape, a TRACE ON command may be entered (with a different cuu). If output was to tape, you may attempt to salvage the trace data on the output tape by using the VSE job control MTC WTM,cuu statement. In any case, you can attempt to run the DB2 Server for VSE Trace Formatter Utility Program (ARIMTRA). It will format and output all trace data or selected trace data up to the point of failure. At that point it will probably end due to invalid data or an I/O error on the tape.
| Note: | If output was to tape, tape unit cuu remains assigned to the database partition and cannot be used until the database manager ends. Therefore, if this condition occurred during the TRACE OFF command, you may have to shut down the database manager to unassign the tape unit. |
| ARI0098E | Trace file {cuu|DISK} unassigned or CLOSE failed. Reason Code = nn. Return Code = nn. TRACE OFF. Processing completed. |
Explanation: The TRACE OFF command (CLOSE is the default) is being processed or the database manager is being normally or abnormally ended. If cuu is in the message text, a terminating error occurred while trying to close and unassign the trace output tape file. If DISK is in the message text, a terminating error occurred while trying to close the trace output disk file. 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: TRACE OFF command processing or trace shutdown is completed. Trace is in the OFF state. Assume that the trace tape or disk file was not closed and is not fully processable (see below).
| Note: | If output was to tape, tape unit cuu remains assigned to the database partition and cannot be used until the database manager ends. Therefore, if this condition occurred during the TRACE OFF command, you may have to shut down the database manager to unassign the tape unit. |
Operator Response: Report the problem (message) to your system programmer.
You may attempt to run the DB2 Server for VSE Trace Formatter Utility Program (ARIMTRA). It will format and output all trace data up to the point of failure. At that point it may end due to lack of tape/disk CLOSE recording or an unreadable record on the tape/disk.
Notes:
System Programmer 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.
| ARI0099I | TRACE OFF. Output file closed on unit {cuu|DISK}. |
Explanation: Database trace has been successfully ended due to entry of the TRACE OFF CLOSE (CLOSE is the default) operator command or due to database manager normal or abnormal termination. Trace is off and the trace output file has been successfully closed. If cuu is in the message text, the trace file is on tape cuu and the tape unit has been unassigned. If DISK is in the message text, the trace file is a disk file.
System Action: TRACE OFF command processing or trace shutdown is completed. The trace file is closed.
Operator Response: None required. The trace output file is now available for print display by the DB2 Server for VSE Trace Formatter Utility Program (ARIMTRA).
Note for tracing to tape: Because the database manager does not rewind the tape, the operator should manually rewind the tape (unless more files are to be written on the tape) and, if desired, demount it.
| ARI0100E | Agent/user ID {agent-id | user-id} is not assigned. |
Explanation: A SHOW LOCK operator command could not be processed. Sources of the problem include:
System Action: The SHOW command processing is ended.
Operator Response: Be sure that the specified agent-id or user-id is valid and reenter the SHOW command.
| Note: | You may get the same result if the requested user-id does not occupy an agent at the time the command is reentered. |
| ARI0101E | DBSPACE dbspace-number does not exist. |
Explanation: The dbspace-number entered on the SHOW LOCK DBSPACE operator command was invalid:
System Action: The SHOW command processing is ended.
Operator Response: Correct the DBSPACE number (be sure that the DBSPACE number is between 1 and the maximum valid value for DBSPACE numbers) and reenter the command.
| ARI0102E | There is no lock contention for {any | this} {DBSPACE | agent/user}. |
Explanation: The database manager could not find a DBSPACE or an agent/user that had locking contention at the instant the SHOW command was entered. This message occurred as a result of entering a SHOW LOCK DBSPACE, SHOW LOCK USER, SHOW LOCK WANTLOCK, SHOW LOCK ACTIVE, or SHOW LOCK GRAPH command.
System Action: The SHOW command processing is ended.
Operator Response: Reenter the command.
| Note: | You may get the same result if the requested agent, user, or DBSPACE has no lock contention at the time the command is reentered. |
| ARI0103E | A column named name1 does not exist in the system catalog table named name2. |
Explanation: The row for the column name (name1) was not found in the system table name2. name1 is either TLABEL or CLABEL. The TLABEL column resides in SYSTEM.SYSCATALOG and contains correlation names. name2 is either SYSTEM.SYSCATALOG or SYSTEM.SYSCOLUMNS. The CLABEL column resides in SYSTEM.SYSCOLUMNS and contains column labels.
The database manager expects there to be a column named TLABEL in SYSTEM.SYSCATALOG and CLABEL in SYSTEM.SYSCOLUMNS when looking for a row describing those columns. It could find neither of them.
System Action: Processing continues.
Operator Response: Refer this message to your database administrator.
Database Administrator Response:
| ARI0104I | The row, where SQLOPTION = option1 does not exist, or has incorrect data in the VALUE column in the catalog table named SYSOPTIONS. The database manager will assume a value of option2. |
Explanation: You omitted a data type value or gave an incorrect value. The system assumed a value instead.
The SQLOPTION = option1 possibilities are:
System Action: Processing continues. The implied value of option2 is:
Operator Response: Refer this message to your database administrator.
Database Administrator Response: Display the SYSTEM.SYSOPTIONS catalog table and find out whether:
| ARI0105I | The row, where column = name, does not exist in the system catalog table table-name. The database manager assumes the internal default of charname. |
Explanation: The row for the character set, where column = name does not exist in the catalog table table-name. The character set specified in the CHARNAME parameter on SQLSTART is not correctly defined in all catalog tables.
System Action: Processing continues. The database manager uses the charname character set, which is usually be the last CHARNAME correctly specified.
Operator Response: Refer this message to your database administrator.
Database Administrator Response: Determine whether a wrong character set name is specified as the CHARNAME initialization parameter.
After inserting the row, restart the database manager, because some application programs may not run correctly when using another character set.
For more information, see the DB2 Server for VSE System Administration manual.
| ARI0106E | The database manager found an incompatibility in the application server at initialization. The expected FORMAT ID is format-id1. The FORMAT ID found in the application server is format-id2. |
Explanation: The code running on the database manager is incompatible with the release level of the database. format-id1 is the expected format ID, and format-id2 is the format ID of the current application server.
System Action: The database manager is terminated.
Operator Response: Refer this message to your system programmer.
System Programmer Response: The procedures for installing the database manager code and updating application servers are described in the DB2 Server for VSE Program Directory. Installations that are simultaneously using multiple application servers and different database manager releases may accidentally pair a release of the database manager with an incompatible application server.
Explanation: For the character set specified in the CHARNAME initialization parameter, the EBCDIC character set classification table or the EBCDIC character set translation table in SYSTEM.SYSCHARSETS contains invalid values.
In the strings following the message, the positions in error are marked by an E. These positions are represented in hexadecimal numbers.
System Action: Processing continues. If the application server default CHARNAME is being changed and the new CHARNAME is in error, the value of the current application server default CHARNAME is used. If the current application server default CHARNAME is in error, then INTERNATIONAL will be used as the CHARNAME value. Message ARI0143I indicates the value of the application server default CHARNAME.
Operator Response: Refer this message to your database administrator.
Database Administrator Response: Display the row for the specified EBCDIC character set in the SYSTEM.SYSCHARSETS catalog table. Determine the correct values and update the row with correct values.
After correcting the row, restart the database manager because some application programs may not run correctly using another character set.
| ARI0109E | DB2 Server for VSE accounting is not active. |
Explanation: The ALTACCT operator command was entered, but the database accounting support is not active.
System Action: The ALTACCT operator command processing ends.
Operator Response: None is required. Do not enter the ALTACCT operator command when DB2 Server for VSE accounting support is not active. If you were instructed to enter this command, notify your database system programmer.
System Programmer Response: Ensure that the ACCOUNT initialization parameter is properly specified and that the system operator is properly instructed when to enter the ALTACCT operator command.
| ARI0111I | Accounting disabled. |
Explanation: The DB2 Server for VSE accounting support has been disabled. This message is issued whenever the YES response is given in reply to either message ARI0076D or message ARI0077D.
System Action: Processing continues with accounting support disabled.
| ARI0112E | Dynamic UNASSIGN of accounting file filename cuu failed. Reason Code = X'nn'. |
Explanation: In attempting to dynamically unassign the tape unit identified in this error message, an error occurred. The Reason Code value is the return code (in hexadecimal) from the VSE ASSIGN macro. Refer to the IBM VSE/ESA System Macros Reference manual for an explanation of this code.
System Action: Processing continues. The tape unit identified in this error message remains assigned to the database partition until the database manager terminates and cannot be used until that time.
Operator Response: Save this message and give it to your system programmer.
System Programmer Response: Refer to the IBM VSE/ESA System Macros Reference manual for an explanation of the error code displayed.
| ARI0113I | {LUWID luwid-value | DBSPACE dbspace-number | USERID userid} has already been specified. |
Explanation: The specified LUWID, DBSPACE, or USERID was entered in a previous command of the same type (duplicate command) in the EXTEND input file.
System Action: The duplicate specification is ignored. Processing continues.
| ARI0114E | keyword was specified more than once in the same statement. |
Explanation: A single EXTEND input file command specified a control keyword more than once.
keyword is a control keyword--ALL, TO, DBSPACE, USERID, or LUWID.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Remove duplicate keywords in the EXTEND input file command, then restart extended database initialization.
| ARI0115E | Unexpected string string was found. |
Explanation: A line of an EXTEND input file command contains unrecognizable keywords, more than one control keyword, or extra input on a record.
string is an unrecognizable string, a keyword, or a control keyword found while parsing an EXTEND input file command.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file command. Restart extended database initialization.
| ARI0116E | string1 was expected but string2 was found. |
Explanation: While parsing EXTEND input file commands, one of the following caused an error:
For example, TIME or DATE was specified in a BYPASS UNDO WORK command, or ALL was specified in a ROLLBACK COMMITTED WORK command.
string1 is:
If string1 was either VALUE, UNDO, WORK, COMMITTED, or DBSPACE, string2 may be END OF RECORD because an incomplete command was entered. If string1 is either OPTION or WHERE, string2 may be END OF FILE because an incomplete command was entered.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0117E | Range error: number is greater than the maximum number of possible condition (max). |
Explanation: While parsing EXTEND input file commands, one of two conditions existed. condition identifies the condition.
number is the number of logical units of work included in the EXTEND input file.
max is 252, the maximum number of active logical units of work permitted at any one time.
number is the number of a DBSPACE.
max is the number of PUBLIC and PRIVATE DBSPACEs defined in the database.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0118E | {LUWID luwid-value | DBSPACE dbspace-number | USERID userid} contains invalid {HEX CHARACTERS | NUMBERS | ALPHANUMERICS} or is too long. |
Explanation: While parsing EXTEND input file commands, one of the following conditions occurred:
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0119E | Cannot {bypass | disable} DBSPACE 1. |
Explanation: DBSPACE 1 can be neither disabled nor bypassed. The database manager must be able to use the database catalog located in DBSPACE 1.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Modify the EXTEND input file so that DBSPACE 1 is not disabled or bypassed. Restart extended database initialization.
| ARI0120I | DBSPACE dbspace-number is already {ENABLED | DISABLED}. |
Explanation: A DISABLE or ENABLE DBSPACE command was specified for a DBSPACE that was previously disabled or enabled.
System Action: Initialization continues. The status of the specified DBSPACE is not changed.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Take note of the message.
| ARI0121I | DBSPACE nnn is disabled. |
Explanation: This message is issued for each disabled DBSPACE in the database. DBSPACEs are disabled by the DISABLE DBSPACE command.
System Action: Processing continues.
System Programmer Response: You may wish to take note of which DBSPACEs are disabled.
| ARI0122E | The time time-string and date date-string specified are later than the current time. |
Explanation: The starting date and time specified (or defaulted to) in the ROLLBACK COMMITTED WORK command are later than the current date and time. There can be nothing in the database log with such a date and time.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Determine the correct time and date. Correct the EXTEND input file. Restart extended database initialization.
| ARI0123E | The TO time and date combination is earlier than the FROM time and date combination. |
Explanation: In a ROLLBACK COMMITTED WORK command, the TO time and date (taken in combination) must be greater than the FROM time and date (taken in combination).
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0124E | {OPEN | GET | CLOSE} error input-file Reason Code = nn . Return Code = cc . |
Explanation: An error occurred in an attempt to access or close the EXTEND input file. 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 err Chapter 20, Sequential File Errors in this manual or SEQ FILE ERRORS in the HELP text.
input-file is SYSIPT, is the file with ddname ARIEXTND, the input file associated with the use of the EXTEND initialization parameter during database initialization.
System Action: For OPEN or GET errors, the database manager ends. For CLOSE errors, processing continues.
Operator Response: For OPEN or GET errors, look up displayed error codes to take corrective action. For CLOSE errors, no action is required.
System Programmer Response: Same as Operator Response.
| ARI0125E | The extend file is empty. |
Explanation: The input file, SYSIPT, associated with the use of the EXTEND initialization parameter during database initialization contains no commands.
System Action: The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: You must either provide the required file commands or restart database initialization with EXTEND=N.
| ARI0126E | DBSS termination during {FORWARD|ROLLBACK|UNDO| REDO} processing. |
Explanation:
| Note: | This failure can occur if a committed logical unit of work is rolled back by the ROLLBACK COMMITTED WORK command (refer to the DB2 Server for VSE & VM Diagnosis Guide and Reference manual for information about recovering from DBSS errors). |
| Note: | This message and its display output will always appear on the operator console. It will also appear in SYSLST output if the DSPLYDEV initialization parameter requests (or defaults to) SYSLST output. |
System Action: The database manager ends.
Operator Response: Save this message and the subsequent display output and contact your system programmer immediately.
System Programmer Response: Make note of the information given in the message and the following display output, and refer to the DB2 Server for VSE & VM Diagnosis Guide and Reference manual for information about recovery procedures for DBSS errors.
| ARI0127E | The {TIME | DATE} parameter string contains a syntax error. |
Explanation: The TIME or DATE parameter specified in a ROLLBACK COMMITTED WORK command contained a syntax error.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0128E | A nonnumeric or invalid character was found in the {TIME | DATE} parameter string. |
Explanation: An invalid character was found in the TIME or DATE parameter specified in a ROLLBACK COMMITTED WORK command.
| Note: | Value for day must be valid for the month or year specified. |
string is the invalid time or date string.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0129E | The combination of the ALL option with any other option is not valid. |
Explanation: One of two conditions occurred:
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the BYPASS UNDO WORK command. Restart extended database initialization.
| ARI0130I | The parameters specified are a subset of those used in a previous statement of the same type. |
Explanation: The parameters ANDed together in a BYPASS UNDO WORK or ROLLBACK COMMITTED WORK command are a subset of parameters specified in previous commands of the same type. For example, the following duplicate commands will cause this message to be issued:
BYPASS UNDO WORK WHERE USERID SMITH JONES DBSPACE 2 4 5 . . . BYPASS UNDO WORK WHERE USERID JONES DBSPACE 4
System Action: The duplicate specification is ignored. Processing continues.
| ARI0131E | The TO option was found but no starting time or date was specified. |
Explanation: A ROLLBACK COMMITTED WORK command was entered and the TO option was specified. No starting (from) TIME or DATE was specified.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0132E | DBSPACE dbspace-number has been selected for both enabling and disabling. |
Explanation: The EXTEND input file contained conflicting commands to enable and disable the same DBSPACE.
System Action: EXTEND input file parsing completes. The database manager ends.
Operator Response: Refer this message to your system programmer.
System Programmer Response: Correct the EXTEND input file. Restart extended database initialization.
| ARI0137I | Invalid installation defined date/time defaults on name. |
Explanation: The specified date/time default name contains an invalid value. During installation, four date/time values were stored into the SYSTEM.SYSOPTIONS table. Their names and supported values are as follows:
System Action: Processing continues with the default datetime values.
The default values supplied by the system are:
Operator Response: Refer this message to your system programmer.
System Programmer Response: Update the SYSTEM.SYSOPTIONS table with the correct datetime values.
| ARI0138E | Application Identifier SYSARI0x for the application server dbname has already been used by another database. |
Explanation: Another application server has been identified to XPCC with the same APPLID. Either there was an attempt to start the same application server in more than one partition, or the DBNAME Directory has more than one DBNAME mapping to the same APPLID.
System Action: Initialization of the database manager ends. The application server is not operational.
Operator Response: Ensure that the database name is correct, and that an application server with the same name has not been started in another partition. If the server name is correct, refer the problem to the system programmer.
System Programmer Response: Make sure that the DBNAME Directory entries are correct. An APPLID mapped onto by more than one DBNAME can result in this error. Also check the VSE IPL procedure to make sure that an XPCC SET command has not been issued for the same APPLID, as for VSE Guest Sharing.
| ARI0140D | Enter DRRM function name and trace-level pair. Valid function names are *, DICT, GEN, PARSE, RDIIN, and CANCEL. Valid trace-level values are 0, 1, and 2. |
Explanation: The TRACE ON command is being processed. The operator responded DRRM to prompting message ARI0087D. The database manager is prompting the operator to specify the functions of DRRM to be traced and the trace level for each function.
System Action:
| Note: | This message is displayed in all environments. In environments in which the DRRM component is not active, however, the operator's response to this message is ignored. |
Operator Response:
| ARI0141D | Enter WUM trace-level or CANCEL. Valid trace-level values are 0, 1, and 2. |
Explanation: The TRACE ON command is being processed. The operator has responded WUM to prompting message ARI0087D. The database manager is prompting the operator to specify the desired trace level for WUM.
System Action:
Notes:
Operator Response:
| ARI0142D | Enter DSC function name and trace-level pair. Valid function names are *, AGENT, COM, and CANCEL. Valid trace-level values are 0, 1, and 2. |
Explanation: The TRACE ON command is being processed. The operator responded DSC to prompting message ARI0087D. The database manager prompts the operator to specify the DSC function to trace and the desired trace level.
System Action:
| Note: | If you enter trace level 0 for a function, the function is not traced. Entering trace level 0 is equivalent to not specifying the function at all. |
Operator Response: If you want to terminate the TRACE command, enter CANCEL.
Explanation: The CHARNAME startup parameter (if specified) or the CHARNAME value used previously, and the values in SYSTEM.SYSOPTIONS for DBCS and CHARSUB, are used to initialize the values reported by this message. The values in SYSTEM.SYSOPTIONS are updated so that the next time the application server is started and the CHARNAME startup parameter is not specified, the values reported by this message are then similar to those received now.
System Action: Initialization continues.
| ARI0145E | DBSPACE name dbspace-number does not exist or is invalid. |
Explanation: The user failed to pass in a valid DBSPACE name (for example, System DBSPACE name) for processing.
System Action: The IDENTIFICATION process ends unsuccessfully.
User Response: Rerun the IDENTIFICATION process and provide a valid DBSPACE name as input.
| ARI0146I | Warning: The command line was truncated at column 80. |
Explanation: ARIYE04 only parses 80 characters. An operator command can only be 80 characters in VSE.
System Action: Process the truncated command.
Operator Response: Shorten the command line if valid data appears beyond column 80.
| ARI0150E | There is no connection for showid . |
Explanation: A connection to the application server for the specified showid that is an agent, user ID, or LUWID cannot be found. Sources of the problem include:
System Action: The SHOW command processing is ended.
Operator Response: Be sure that the specified agent, user ID, or LUWID is correct and then reenter the SHOW CONNECT command.
| Note: | You may receive the same result if the requested agent, user ID, or LUWID is not connected to the application server when the command is reentered. |
| ARI0153I | The database manager ignores TRACEBUF = size parameter when trace is not activated. |
Explanation: A nonzero size for the TRACEBUF startup parameter has been specified, and no subcomponent have been chosen to be traced (TRACxxxx startup parameters must indicate 1 or 2 for a specific subcomponent to be traced).
System Action: The system does not use the TRACEBUF parameter, and no trace buffer is allocated. The startup continues.
Operator Response: No response is required if the operator does not want any trace output. If trace output is expected, then the database manager must be restarted with the proper values of the TRACxxxx startup parameters. Alternatively, the TRACEBUF n parameter in the TRACE ON operator command can be used to start the trace in MUM.
| ARI0154I | A size kilobyte trace buffer has been allocated. Maximum contiguous memory left = amount kilobytes. |
Explanation: The trace buffer of the size as shown has been created.
System Action: The trace is started. Trace records are stored into the trace buffer.
Operator Response: If the amount maximum contiguous memory left is too small (see the note below) then the operator can consider one of the following actions:
| Note: | Even after the database manager has been started, the storage requirements are dynamic and workload dependent. See the DB2 Server for VSE System Administration manual for virtual storage requirements of the DB2 Server for VSE system. |
Explanation: The memory needed_storage required for the trace buffer allocation is not available.
System Action: If TRACEBUF was specified in the TRACE ON operator command, the trace is not started.
If TRACEBUF was specified as a database startup parameter, the database manager is ended.
Operator Response: There are several possible actions:
| ARI0156I | The trace buffer was written to the trace file. |
Explanation: The contents of the trace buffer was flushed out to the trace file. This can happen as a result of the TRACE OFF operator command or during a database system shutdown.
| ARI0157I | The trace buffer is empty. |
Explanation: An attempt to write the trace buffer into the trace file failed. The trace buffer is empty, because an incorrect TRACE specification (component, subcomponent, authorization ID, agent number or a level) was entered, or the workload that was run did not hit an activated trace point.
Operator Response: Reissue the TRACE ON command in MUM, or restart the database manager with the correct values of startup parameters. Repeat the workload to be traced.
| ARI0159D | The specified CHARNAME is different than the current system
CHARNAME.
This will force the system CCSID values to be changed. Do you wish to
change
the system CHARNAME?
Enter 0(No) to continue using the current CHARNAME of old-charname , or 1(Yes) to change the system CHARNAME to new-charname , or 111(Quit) to cancel your request and end SQLSTART processing. |
Explanation: The value of the CHARNAME parameter specified in SQLSTART is different from the current CHARNAME value. Changing the current CHARNAME will change the current default CCSID values. Also, the CCSID attribute of the character columns of the system catalog tables will be updated to the new default CCSID. The actual data stored in the system catalog tables will not be converted from the current default CCSID to the new default CCSID. Only the attribute of the character columns will change. The CCSID attribute of the character columns of any user tables will not be updated to the new default CCSID.
The default CHARNAME of a system should be changed only once: at installation or migration. If it is changed after system objects have been created in the system catalog tables, object names not conforming to the rules for ordinary identifiers may contain characters that do not have the same hexadecimal representation in the new CCSID and some data may be displayed incorrectly. For the rules about ordinary identifiers, see the DB2 Server for VSE & VM SQL Reference manual. For more information on the CHARNAME parameter, see the DB2 Server for VSE System Administration manual.
System Action:
Database Administrator Response: Unless you are installing or migrating a database or reconfiguring the database to work with different CCSIDs, enter 0(No) to continue database initialization using the current CHARNAME.
| ARI0160D | Enter CONV trace-level or CANCEL. Valid trace-level values are 0, 1, and 2. |
Explanation: The TRACE ON command is being processed. The operator has responded CONV to prompting message ARI0087D. The database manager is prompting the operator to specify the desired trace level for CONV.
System Action:
Operator Response: Enter the desired trace level. If TRACE command termination is desired, enter CANCEL.
| ARI0161E | RMTUSERS = value cannot be specified because the DRDA facility has not been installed for the application server. |
Explanation: RMTUSERS = value was specified as a database startup parameter. The DRDA facility was not installed for the application server, and it cannot process requests from DRDA application requesters.
System Action: The database manager is ended.
Operator Response: Refer this message to your database administrator.
Database Administrator Response: Determine whether or not you require your application server to service DRDA requesters. If so, install the DRDA facility following the steps in the DB2 Server for VSE System Administration manual.
| ARI0162D | Enter STG trace-level or CANCEL. Valid trace level values are 0 and 1. |
Explanation: The TRACE ON command is being processed. The operator responded STG to prompting message ARI0087D. The database manager is prompting the operator to specify the trace level for STG.
System Action:
Operator Response: Choose your response from "System Action", and enter 1 or 0 or CANCEL.
| ARI0163E | {SHOW CONNECT WAITING | DRDA facility} is not supported in this environment. |
Explanation:
System Action:
Operator Response:
Database Administrator Response: If your application server needs to service DRDA requesters, install the required VSE operating environment. If you do not need to service DRDA requesters, do not install the DRDA facility.
| ARI0165I | All parameters are ignored for string. |
Explanation: The command, statement, or operation that you entered, such as SHOW DBCONFIG, contained parameters, but none were required. The system does not use the parameters.
System Action: Processing continues, and all parameters are ignored.
| ARI0172E | A Sync Point Manager is not available. |
Explanation: The parameter "SYNCPNT=Y" was specified at startup; however, the CICS/VSE Sync Point Manager was not available. This message is following by message ARI0176I.
System Action: The database manager is unable to use CICS/VSE sync point manager for handling DRDA sync point operations. As a result, this database may not be a participant in DRDA logical units of work that update multiple remote databases. However, the database manager is still able to process SQLDS protocol requests and DRDA requests that do not involve a sync point manager (for example, DRDA logical units of work that only update a single remote database).
System Programmer Response: If this database manager is to be a participant in DRDA logical units of work that update multiple remote databases, the AXE transaction must be allowed to successfully autostart the DRDA TRUE support for this database, and the CICS Restart Resynchronization support must be installed. In addition, refer to System Programmer Response and Database Administrator Action of message ARI0190E.
| ARI0176I | The SYNCPNT parameter has been reset to N. |
Explanation: The AXE transaction was autostarting DRDA TRUE support and encountered an error. As a result, the AXE transaction instructed the database manager to change the SYNCPNT parameter from "Y" to "N".
System Action: The database manager is unable to use CICS/VSE sync point manager for handling DRDA sync point operations. As a result, this database may not be a participant in DRDA logical units of work that update multiple remote databases. However, the database manager is still able to process SQLDS protocol requests and DRDA requests that do not involve a sync point manager (for example, DRDA logical units of work that only update a single a single remote database).
System Programmer Response: This message is preceded by a message on the VSE console indicating the error that occurred. Fix the problem indicated in this prior message and restart the database.
| ARI0183E | The Sync Point Manager has asked to {COMMIT | ROLLBACK} this LUW but the database manager has no memory of it. |
Explanation: The CICS/VSE sync point manager is attempting to resynchronize the status of a logical unit of work with the database manager. It is asking the database to either commit or rollback this LUW. However the database manager could not find any indication that this unit of work needs resynchronization. This can happen when the operator used the database manager FORCE command and RESET INDBOUT command on this unit of work while the CICS/VSE sync point manager is resynchronizing with the database manager.
This message is followed by message ARI4019I to identify the unit of work.
System Action: The database manager sends back a normal completion reply to the CICS/VSE sync point manager.
Operator Response: Refer this message to your DB2 Server for VSE database administrator.
Database Administrator Action: Manual intervention is necessary to ensure that the LUW is in a consistent state at all sites where the LUW has been distributed. This may require intervention at this database manager, or possibly at other database managers. Manual intervention could mean manually fixing the data or possibly restoring an archive.
| ARI0184A | The Sync Point Manager has asked to {COMMIT | ROLLBACK} this LUW but the FORCE command was previously used to {ROLLBACK | COMMIT} it. |
Explanation: The CICS/VSE sync point manager is attempting to resynchronize the status of a logical unit of work with the database manager. It is asking the database to either commit or rollback this LUW. However the operator had previously used the database manager FORCE command to force the LUW into the opposite state.
This message is followed by message ARI0196I to identify the unit of work.
System Action: The LUW remains unsynchronized with the sync point manager. The LUW still appears when the SHOW INDOUBT command is issued.
Operator Response: Refer this message to your DB2 Server for VSE database administrator.
Database Administrator Action: In order to clear out this LUW from the SHOW INDOUBT display, it is necessary to use the RESET INDOUBT command.
In addition, manual intervention is necessary, before RESET INDOUBT is issued, to ensure that the LUW is in a consistent state at all sites where the LUW has been distributed. This may require intervention at this database manager, or possibly at other database managers. Manual intervention could mean manually fixing the data or possibly restoring an archive.
| ARI0185I | TRUE-name task-related user exit resynchronization between CICS and the database manager has started. |
Explanation: While autostarting DRDA TRUE support TRUE-name, the AXE transaction started resynchronization with the CICS/VSE sync point manager. Resynchronization occurs after two-phase commit processing has been interrupted by a resource failure. It involves passing a list of all in-doubt logical units of work to the CICS/VSE sync point manager. Using information stored in its log, the CICS/VSE sync point manager determines how the in-doubt logical units of work should be resolved and instructs the database manager to process each in-doubt logical unit of work accordingly.
TRUE-name is the name of the DRDA TRUE where resynchronization is taking place.
System Action: Resynchronization processing continues.
Database Administrator Action: Watch to make sure that no error messages appear between message ARI0185I and message ARI0186I.
| ARI0186I | TRUE-name task-related user exit resynchronization between CICS and the database manager has ended. |
Explanation: This is a signal to the database manager operator that the database manager has completed resynchronization of all in-doubt logical units of work with the CICS/VSE sync point manager.
TRUE-name is the name of the DRDA TRUE where resynchronization is taking place.
System Action: The CICS/VSE sync point manager and the database manager have resynchronized all possible in-doubt LUWs. In-doubt LUWs which have been resynchronized will no longer be displayed when the SHOW INDOUBT command is issued. In-doubt LUWs that remain unsynchronized will still be displayed.
Operator Response: Refer this message to your DB2 Server for VSE database administrator.
Database Administrator Action: Use the database manager SHOW INDOUBT command to find out if heuristic damage had occurred for any logical units of work. Manual intervention is necessary to ensure that these LUWs are in a consistent state at all sites where the LUW has been distributed. This may require intervention at this database manager, or possibly at other database managers. Manual intervention could mean manually fixing the data.
It is necessary to use the database manager RESET INDOUBT command to clear out these LUWs from the SHOW INDOUBT display. However, use the RESET INDOUBT command only after these logical units of work have been resolved.
| ARI0187I | TRUE-name is enabled for DRDA support. |
Explanation: The AXE transaction successfully completed autostarting DRDA TRUE support TRUE-name. This message is followed by message ARI0188I.
TRUE-name is the name of the DRDA TRUE support that was enabled.
System Action: The AXE transaction processing continues. The application server for which the DRDA TRUE support was autostarted can now be a participant in DRDA logical units of work that update multiple remote databases.
| ARI0188I | TRUE-name has an entry point of entry-point. |
Explanation: The AXE transaction successfully completed autostarting the DRDA TRUE TRUE-name.
TRUE-name is the name of the DRDA TRUE.
entry-point is the entry point of the DRDA TRUE.
System Action: The AXE transaction processing continues.
| ARI0189E | CICS restart resynchronization is not available. |
Explanation: While autostarting DRDA TRUE support, the AXE transaction detected that the CICS restart resynchronization transaction CRSY is not enabled.
System Action: The AXE transaction ends the enabling of the DRDA TRUE.
Operator Response: Enable the CICS restart resynchronization transaction CRSY.
System Programmer Response: Ensure that CICS restart resynchronization support has been installed properly. See the DB2 Server for VSE Program Directory for more details.
| ARI0190E | TRUE-name cannot be enabled for DRDA support. There is no DRDA TRUE support and processing will continue as if SYNCPNT=N is specified. |
Explanation: The AXE transaction failed in its attempt to autostart the DRDA TRUE support TRUE-name. An error message will have been displayed earlier that indicated the error that caused the failure.
TRUE-name is the name of the DRDA TRUE support the AXE transaction was autostarting.
System Action: This message is followed by messages ARI0172E and ARI0176I on the DB2 Server for VSE operator console. AXE transaction processing continues but the SYNCPNT parameter is reset from "Y" to "N". As a result, the database manager is unable to use the CICS/VSE sync point manager for handling DRDA sync point operations and this database may not be a participant in DRDA logical units of work that update multiple remote databases. However, the database manager is still able to process SQLDS protocol requests and DRDA requests that do not involve a sync point manager (for example, DRDA logical units of work that only update a single remote database).
Operator Response: Refer this message to your system programmer and database administrator.
System Programmer Response: An error message will have been displayed before this message that indicated the error. See the explanation for that message and resolve the error.
Database Administrator Action: After the error indicated by the error message displayed before this message has been resolved, restart the database with SYNCPNT = "Y". This will allow the next AXE transaction that is started by a DRDA2 application requester to autostart the DRDA TRUE support for this application server and will make this application server a participant in DRDA logical units of work that update multiple remote databases.
| ARI0191I | TRUE-name is disabled. |
Explanation: The DAXT transaction successfully completed the termination of the DRDA TRUE TRUE-name.
TRUE-name is the name of the DRDA TRUE support being terminated.
System Action: The DAXT transaction ends.
The DRDA TRUE TRUE-name will be autostarted when a DRDA2 application requester initiates a connection to a DB2 Server for VSE application server whose DRDA TRUE support is TRUE-name.
| ARI0192I | TRUE-name is not currently enabled for DRDA support. |
Explanation: The DAXT transaction was entered to disable the DRDA TRUE TRUE-name. However, the DRDA TRUE was not enabled. Either the DRDA TRUE was not enabled or a previous execution of DAXT terminated the DRDA TRUE.
TRUE-name is the name of the DRDA TRUE support being terminated.
System Action: The DAXT transaction ends.
| ARI0193E | The CICS log does not contain information for an in-doubt logical unit of work belonging to server server-name. |
Explanation: While autostarting DRDA TRUE support, the AXE transaction started TRUE resynchronization. During TRUE resynchronization, CICS/VSE was given a logical unit of work that the database manager indicated to be resolved. However, the information needed to resolve the logical unit of work was not on the CICS/VSE log. This generally results from a CICS/VSE coldstart following a system failure. If a CICS/VSE coldstart did not occur after the last system failure, the CICS/VSE log or the DB2 Server for VSE log data has been damaged.
This message is followed by messages ARI4018A and ARI4019I or messages ARI0195A and ARI0196I. ARI4018A and ARI4019I identify the in-doubt logical units of work (agents) that need to be resolved. These agents must be resolved (with the database manager FORCE command). ARI0195A identifies the in-doubt logical units of work (CICS/VSE recovery token) that had been FORCEd by the database manager FORCE command but had not been resolved with the CICS/VSE sync point manager.
server-name is the name of the application server which owns the in-doubt logical unit of work.
System Action: The logical unit of work remains unresolved. That is, it remains INDOUBT.
Resynchronization processing continues for other in-doubt LUWs.
Operator Response: If the message is followed by ARI4018A and ARI4019I, refer to the OPERATOR RESPONSE for messages ARI4018A and ARI4019I. If the message is followed by ARI0195A and ARI0196I, refer to the OPERATOR RESPONSE for messages ARI0195A and ARI0196I.
Database Administrator Action: If the message is followed by ARI4018A and ARI4019I, refer to the DATABASE ADMINISTRATOR ACTION for messages ARI4018A and ARI4019I. If the message is followed by ARI0195A and ARI0196I, refer to the DATABASE ADMINISTRATOR ACTION for messages ARI0195A and ARI0196I.
| ARI0194E | A logical unit of work that the database manager for server server-name indicated needed to be resolved was not identified by the CICS/VSE log as needing resolution. |
Explanation: While autostarting DRDA TRUE support, the AXE transaction started TRUE resynchronization. During TRUE resynchronization, CICS/VSE was given a logical unit of work that the database manager indicated needed to be resolved. However, information in the CICS/VSE log indicated that the logical unit of work did not need to be resolved. CICS/VSE cannot resolve the logical unit of work.
This condition can occur when an application program overlays a CICS/VSE log buffer, or when a DB2 Server for VSE log buffer is destroyed. Or, the CICS/VSE log or the DB2 Server for VSE log may have been damaged.
This message is followed by messages ARI4018A and ARI4019I or messages ARI0195A and ARI0196I. ARI4018A and ARI4019I identify the in-doubt logical units of work (agents) that need to be resolved. These agents must be resolved (with the database manager FORCE command). ARI0195A identifies the in-doubt logical units of work (CICS/VSE recovery token) that had been FORCEd by the database manager FORCE command but had not been resolved with the CICS/VSE sync point manager.
server-name is the name of the application server which owns the in-doubt logical unit of work.
System Action: The logical unit of work remains unresolved. That is, it remains INDOUBT.
Resynchronization processing continues for other in-doubt LUWs.
Operator Response: If the message is followed by ARI4018A and ARI4019I, refer to the OPERATOR RESPONSE for messages ARI4018A and ARI4019I. If the message is followed by ARI0195A and ARI0196I, refer to the OPERATOR RESPONSE for messages ARI0195A and ARI0196I.
System Programmer Response: Ensure that any newly installed application program are not overlaying CICS/VSE or DB2 Server for VSE storage. If the problem persists, make a record of what went wrong and contact the designated support group for your installation.
Database Administrator Action: If the message is followed by ARI4018A and ARI4019I, refer to the DATABASE ADMINISTRATOR ACTION for messages ARI4018A and ARI4019I. If the message is followed by ARI0195A and ARI0196I, refer to the DATABASE ADMINISTRATOR ACTION for messages ARI0195A and ARI0196I.
| ARI0195A | Use the database manager SHOW INDOUBT operator command to find the following units of work: |
| ARI0196I | SERVER_NAME = server-name. RECOVERY TOKEN = rectok. |
Explanation: While autostarting DRDA TRUE support and performing TRUE resynchronization, the AXE transaction was informed by CICS/VSE that a logical unit of work it is trying to resynchronize is lost due to CICS cold start or that a logical unit of work should not be resynchronized because it should not be in-doubt.
server-name is the name of the application server that owns the logical unit of work.
rectok is the unique CICS recovery token assigned to the logical unit of work.
System Action: The LUW remains unsynchronized with the sync point manager. The LUW still appears when SHOW INDOUBT command is issued.
Operator Response: Refer this message to your DB2 Server for VSE database administrator.
Database Administrator Action: Use the database manager SHOW INDOUBT command to obtain more information about the logical units of work. In order to clear this LUW from SHOW INDOUBT display, it is necessary to use the RESET INDOUBT command.
Manual intervention is necessary before the RESET INDOUBT command is issued to ensure that the LUW is in a consistent state at all sites where the LUW has been distributed. This may require intervention at this database manager, or possibly at other database managers.
| ARI0199I | DRDA TRUE TRUE-name is enabling for server server-name. |
Explanation: A DRDA2 application requester initiated a connection to a DB2 Server for VSE application server. The AXE transaction detected that the DRDA TRUE support for the application server was not enabled and so it autostarted the DRDA TRUE support for the application server.
TRUE-name is the name of the DRDA TRUE support the AXE transaction is autostarting.
server-name is the name of the application server for which the DRDA TRUE support was being autostarted.
System Action: The AXE transaction continues with the process of enabling the DRDA TRUE support.
Database Administrator Action: Watch to make sure that no
error messages appear after ARI0199I.