APAR status
Closed as canceled.
Error description
This apar documents changes to the DB2 Messages and Codes manual that did not make the r230 ga pubs. 5740xyr00 sc26-4379-02 sc26437902
Local fix
Problem summary
================================================================ Book Title: Messages and Codes Page Number: p. 2-4 For SQL code +203, the SQLSTATE is wrong. It should be: SQLSTATE: 01552 ================================================================ Book Title: Messages and Codes Page Number: p. 2-14 For SQL code -151, add the following bullet after the second bullet in the EXPLANATION: o The object table is a catalog table with no updateable columns. In addition, replace the PROGRAMMER RESPONSE with the following: PROGRAMMER RESPONSE: The requested function is not supported by DB2. Refer to the description of the UPDATE statement in Chapter 6 of SQL Reference for information regarding restrictions on the ability to update columns in partitioned tables and views. ================================================================ Book Title: Messages and Codes Page Number: p. 2-47 Replace SQL code -908 with the following: -908 bind-type ERROR USING auth-id AUTHORITY BIND, REBIND OR AUTO-REBIND OPERATION IS NOT ALLOWED EXPLANATION: For BIND and REBIND, the indicated authorization ID is not allowed to perform the indicated bind-type against a plan or package. An entry in the Resource Limit Specification Table (RLST) prohibits binding and rebinding by this authorization ID, or all authorization IDs. For AUTO-REBIND, the system parameter controlling AUTO-REBIND operations is set to disallow AUTO-REBIND. bind-type Type of bind operation (BIND, REBIND or AUTO-REBIND). auth-id Authorization ID of the invoker of the BIND subcommand or primary authorization ID of the invoker of the plan for AUTO-REBIND operations. SYSTEM ACTION: The plan or package is not bound. SYSTEM PROGRAMMER RESPONSE: If the indicated authorization id should be allowed to bind, change the entry in the active RLST table. If AUTO-REBIND operations are disabled, rebind the package before reexecuting the package. ============================================================ In the Messages and Codes on page 3-73, add the following message: DSNE626I MAXIMUM OUTPUT LINES FOR SELECT STATEMENT REACHED (NUMBER), PROCESSING FOR CURRENT SELECT STATEMENT TERMINATED EXPLANATION: The maximum number of output lines to be displayed for a select statement, '(number)' has been reached, and processing of the current select statement is terminated. The maximum number to display is specified by the SPUFI user on the CURRENT SPUFI DEFAULTS panel. This message appears in the SPUFI output file. This message is issued by the following CSECT(s): DSNESM20 SYSTEM ACTION: Processing of subsequent SQL statements in the input file continues. USER RESPONSE: If the number of lines displayed is insufficient, you can increase the maximum number of lines to be displayed for SELECT statements on the CURRENT SPUFI DEFAULTS panel and re-execute the SELECT statement. ============================================================ In the Messages and Codes on page 3-73, under message DSNH792I, remove the following references: o SQL89 Section 8.4 Syntax Rule: 1 o SQL89 Section 8.5 Syntax Rule: 1 o SQL89 Section 8.7 Syntax Rule: 1 o SQL89 Section 8.11 Syntax Rule: 1 o SQL89 Section 8.12 Syntax Rule: 1 ============================================================ In the Messages and Codes on page 3-155, under message DSNT376I, change the message text to the following: DSNT376I PLAN plan-id1 WITH CORRELATION-ID id1 CONNECTION-ID id2 LUW-ID id3 IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN plan-id2 WITH CORRELATION-ID Id4 CONNECTION-ID id5 LUW-ID id6 ============================================================ Book Title: Messages and Codes Page Number: p. 3-164 For DSNT429I, replace the message text for DSNT429I with the following: DSNT429I THE SUM OF MAX USERS AND MAX REMOTE MUST BE LESS THAN OR EQUAL TO 2000 ================================================================ Book Title: Messages and Codes Page Number: p. 3-187 For DSNU058I, after the first sentence in the EXPLANATION, add this sentence: The object in recovery pending state might be a parent object. In the Messages and Codes on page 3-187, under message DSNU062I, change the message text to the following: DSNU062I csect-name util-name UTILITY MAY NOT BE RUN ON OBJECT qualifier.object-name Change the explanation to the following: EXPLANATION: An attempt was made to execute a utility 'util-name' against an object 'qualifier.object-name' which is not allowed. The named object cannot be processed by the named DB2 utility. ============================================================ In the Messages and Codes on page 3-200, this message replaces the existing message by the same name. DSNU544I csect-name - UNABLE TO OPEN THE COPY DATASET dataset-name, RC= reason-code Explanation: RECOVER was unable to open the dataset 'dataset-name' with 'reason-code' from the open abend. The reason code is taken from field SDWAABCC in the SDWA. This message is issued by the following CSECT(s): DSNUBCR3 Severity:0 (informational) System Action:The RECOVER utility continues processing, searching for the prior image copy or applying log records. ================================================================ Book Title: Messages and Codes Page Number: p. 3-202 For DSNU333I, replace the USER RESPONSE with the following: USER RESPONSE: Correct the input data and resubmit the job. Make sure that the 'field specification' on the LOAD statement is consistent with the table definition and the input data. This might mean changing: o The table definition o The LOAD statement o The input data Refer to Chapter 3 of Command and Utility Reference to determine input constraints. Refer to Section 4 (Volume 2) of Administration Guide for information on resubmitting a partially completed LOAD step. ================================================================ Book Title: Messages and Codes Page Number: p. 3-203 For DSNU335I, after the first paragraph in the EXPLANATION, add this sentence: If DISCARDS processing is active, the message severity is 4 (warning). Replace the SEVERITY and USER RESPONSE, as follows: SEVERITY: 4 (warning) or 8 (error) USER RESPONSE: Correct the input data and resubmit the job. Make sure that the 'field specification' on the LOAD statement is consistent with the definition and the input data. This might mean changing: o The table definition o The LOAD statement o The input data Refer to Chapter 3 of Command and Utility Reference to determine input constraints. Refer to Section 4 (Volume 2) of Administration Guide for information on resubmitting a a partially completed LOAD step. ================================================================ Book Title: Messages and Codes Page Number: p. 3-208 For DSNU400I, in the third paragraph of the EXPLANATION, replace the sentence, "The percentage of changed pages is..." with the following sentence: The percentage of changed pages is obtained by dividing the number of changed pages by the number of pages in the table space. ============================================================ In the Messages and Codes on page 3-212, add the following message: DSNU470I DSNDB01.SYSUTIL CANNOT BE INCLUDED IN A LIST OF TABLE SPACES TO BE QUIESCED EXPLANATION: This message is issued by the QUIESCE utility when DSNDB01.SYSUTIL is found in a table space list of a QUIESCE statement. This Message is issued by the following CSECT(s): DSNUQUIA SEVERITY: 8(error) SYSTEM ACTION: The utility job terminates. USER RESPONSE: Remove DSNDB01.SYSUTIL from the tablespace- list and quiesce it separately. ================================================================ Book Title: Messages and Codes Page Number: p. 3-222 For message DSNU575I, change the SEVERITY to: SEVERITY: 0 (informational) ================================================================ Book Title: Messages and Codes Page Number: p. 3-231 Change Description: For message DSNU656I, replace the SYSTEM ACTION with the following SYSTEM ACTION and PROGRAMMER RESPONSE. SYSTEM ACTION: The REPAIR utility located the indicated record, performed all the requested verifications, and replaced the data in the record at the indicated offset with the new data as defined by the REPLACE control statement. SYSTEM PROGRAMMER RESPONSE: If a changed record is recovered before an image copy is made, and the REPAIR utility was run wit LOG NO, the repair must be reapplied. If the REPAIR utility was run with LOG YES, no image copy is required before recovering the data after the repair. ================================================================ Book Title: Messages and Codes Page Number: p. 4-33 For abend reason code 00C90088, replace the second paragraph of the PROBLEM DETERMINATION with the following: If statistics trace class 3 is active, IFCID 172 contains diagnostic information. For a discussion of the effects of locking, see Section 7 (Volume 3) of Administration Guide. If you suspect an error in DB2, refer to Section 3 of Diagnosis Guide and Reference for information on identifying and reporting the problem. ============================================================ In the Messages and Codes on page 4-36, under reason code 00C90094, add the following after system action: USER RESPONSE: If the code was received while processing a user table, DB2 has determined that the dataset is empty, so a DROP TABLESPACE statement followed by a CREATE TABLESPACE statement will define the table to DB2. If it was received while processing a DB2 catalog or directory then job DSNTIJID should be rerun in order to get the table into a state where DB2 recognizes it (see DB2 Administration Guide, Planning and Installing DB2, installation step 13). ================================================================ Book Title: Messages and Codes Page Number: p. 4-37 For abend reason code 00C90099, add this information to the USER RESPONSE: If you receive this code during a reorganization, query the catalog to check the PCTFREE and FREEPAGE values. You might be able to decrease the amount of freespace to allow the REORG utility to complete successfully. ============================================================ In the Messages and Codes on page 4-74, add the following reason code: 00D10332 EXPLANATION: A log read completed unsuccessfully because a link RBA pointed to a log record with a different URID. This This is an internal error. This abend reason code is issued by the following CSECTS(s): DSNJR103 SYSTEM ACTION: A record is written to SYS1.LOGREC and an SVC DUMP is requested. The requesting execution unit is abnormally terminated. USER RESPONSE: None required. OPERATOR RESPONSE: Collect the SYS1.LOGREC and SVC dump. Notify the system programmer. SYSTEM PROGRAMMER RESPONSE: While reading the log backwards via the LRHLINK RBA's, a log record was encountered that contained a different URID. A link read is normally done when processing a rollback or an abort. This abend is to prevent a rollback of the wrong transaction and if this occurs during abort processing, the subsystem will be brought down. If the abend reoccurs on the subsequent restart of DB2, a conditional restart will be necessary to bypass the invalid log record. Refer to Section 6 (Volume 2) of the Administration Guide for information on recovering from a log failure during restart and resolving inconsistencies resulting from conditional restart. PROBLEM DETERMINATION: RLM standard diagnostic information is provided in "Recovery Log Manager Reason Codes (X'D1')". In addition, register 6 contains the address of the execution block (EB). All log read cursors reside in a recovery log manager storage pool whose header address is in the log manager block (LMB) at LMBRCPHB. The LMB is pointed to by register 5 an described in the DSNDLMB macro. ============================================================
Problem conclusion
Temporary fix
Comments
This is for doc changes that occured after the GA pubs
APAR Information
APAR number
II05810
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1992-03-09
Closed date
1992-03-17
Last modified date
1994-11-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
13 December 2020