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 (SC26-4379-02) Page Number: 2-9 Change Description: In SQL code -007, add the missing message text: STATEMENT CONTAINS THE ILLEGAL CHARACTER character =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 2-31 Change Description: In SQL code -614, change the reference in PROGRAMMER RESPONSE from Chapter 3 to Chapter 6 of the SQL Reference. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 3-41 Change Description: Add message DSNE952I: Explanation: This message is a part of normal DCLGEN output. It tells the name of the table for which the declaration was created. This message is issued by the following CSECT(s): DSNECP63 System Action: This message is included in the DCGLEN output. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 3-200 Change Description: To message DSNU314I, add the following sentence before the last sentence in the USER RESPONSE: This ensures that the rows are loaded back into the same object from which they were loaded. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 3-209 Change Description: For message DSNU402I, the severity is 4 (warning). =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 3-213 Change Description: In message DSNU501I, delete the following sentence from the SYSTEM ACTION: The faulty log record was not applied, but the log RBA in the page header is the RBA of this log record. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 3-296 Change Description: In message DSN1985I, replace the EXPLANATION with the following: EXPLANATION: One or more pages consisting of all zeros were encounteredwith valid data pages after them. The 'first zero page number' and the 'last zero page number' displayed in hexadecimal are the pages where zeros were first encountered and last encountered. In most cases, this is not an error condition. This is a normal condition for segmented table spaces and also for index spaces created with a FREEPAGE parameter not equal to zero. In addition, it is also normal for nonsegmented table spaces to contain zero pages after certain update scenarios terminated abnormally and data rollback was required. This message is issued by the following CSECT(s): DSN1COPY, DSN1PRNT, DSN1COMP Replace the SYSTEM PROGRAMMER RESPONSE with the following: SYSTEM PROGRAMMER RESPONSE: If the zero page is the result of segmenting, no action is necessary. Similarly, if the zero page is a valid zero page that was introduced by DB2, no action is necessary as this page is free space and is used by DB2 when needed. However, if the zero page was a valid zero page introduced by DB2 and you want to remove it from the table space, you can run the REORG utility. If the zero page was caused by something outside of DB2, you might need to run the RECOVER utility. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 4-178 Change Description: In abend reason code 00D94001, delete the following sentence from the EXPLANATION: For further information, see "IRLM Abend Reason Codes" on page 5-25. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 4-207 Change Description: In abend reason code 00E30302, add the following sentence after the first paragraph in the EXPLANATION: An unavailable database might also cause this problem. Replace the SYSTEM PROGRAMMER RESPONSE with the following: SYSTEM PROGRAMMER RESPONSE: Determine what made the plan not operational. Make sure the required database is available. Issue a REBIND subcommand for the plan. =============================================================== Book Title: Messages and Codes (SC26-4379-02) Page Number: 4-315 Change Description: Add the following abend reason codes: 00F30400, 00F30401, 00F30402, 00F30405, 00F30406, 00F30407 _______________________________________________________________ 00F30400 Explanation: This reason code is returned when a DB2 program makes a duplicate request to be called when a specific SSI function code is encountered on the SSI. This reason code is not normally visible to users or operators, but might appear in DB2 traces. This DB2 reason code is issued by the following CSECT(s): DSN3SSCN System Action: None by DSN3SSCN. The DB2 program that made the failing request probably produces diagnostics to report the failure. System Programmer Response: Collect the diagnostics produced by the application program reporting the failure, if any. Problem determination: Follow the instructions indicated by the diagnostics. _______________________________________________________________ 00F30401 Explanation: This reason code is returned when a DB2 program makes a request to no longer be called when a specific SSI function code is encountered on the SSI, but the control block representing the original request to be called is busy and cannot be deleted now. The request will be processed when the control block is no longer busy. This reason code is not normally visible to users or operators, but might appear in DB2 traces. This DB2 reason code is issued by the following CSECT(s): DSN3SSDI System Action: None by DSN3SSDI. The DB2 program that made the failing request might produce diagnostics to report the failure. System Programmer Response: Collect the diagnostics produced by the application program reporting the failure, if any. Problem Determination: Follow the instructions indicated by the diagnostics. _______________________________________________________________ 00F30402 Explanation: This reason code is returned when a DB2 program makes a request to no longer be called when a specific SSI function code is encountered on the SSI, but the control block representing the original request to be called cannot be found. This reason code is not normally visible to users or operators, but might appear in DB2 traces. This DB2 reason code is issued by the following CSECT(s): DSN3SSDI System Action: None by DSN3SSDI. The DB2 program that made the failing request might produce diagnostics to report the failure. System Programmer Response: Collect the diagnostics produced by the application program reporting the failure, if any. Problem Determination: Follow the instructions indicated by the diagnostics. _______________________________________________________________ 00F30405 Explanation: The DB2 subsystem was abended by module DSN3SSI1 because the system services address space's job-step task terminated. This abend reason code is issued by the following CSECT(s): DSN3SSI1 System Action: The DB2 subsystem is terminated with an SVC dump. Operator Response: You can start DB2 again after it terminates. System Programmer Response: At least one SVC dump and associated SYS1.LOGREC entries should be available. If you suspect an error in DB2, refer to Section 3 of Diagnosis Guide and Reference for information on identifying and reporting the problem. Problem Determination: This is usually caused by a previous error which should have recorded an entry in SYS1.LOGREC data set and requested an SVC dump. Examine the SYS1.LOGREC entries and SVC dumps to determine the actual cause of the error. Refer to "DB2 Abend Completion Codes" on page 1-6 for information on X'04F' and X'04E' abend completion codes. Collect the following diagnostic items listed in Appendix B. Problem Determination: 1, 2. _______________________________________________________________ 00F30406 Explanation: The DB2 subsystem was abended by module DSN3SSI1 because the system services address space was forced to an end-of-memory condition. This abend reason code is issued by the following CSECT(s): DSN3SSI1 System Action: The DB2 subsystem is terminated with an SVC dump. Operator Response: You can start DB2 again after it terminates. System Programmer Response: At least one SVC dump and associated SYS1.LOGREC entries should be available. If you suspect an error in DB2, refer to Section 3 of Diagnosis Guide and Reference for information on identifying and reporting the problem. Problem Determination: This is usually caused by a previous error that has recorded data on the SYS1.LOGREC data sets and requested an SVC dump. Examine the SYS1.LOGREC entries and SVC dumps to determine the actual cause of the error. Refer to "DB2 Abend Completion Codes" on page 1-6 for information on X'04F' and X'04E' abend completion codes. Collect the following diagnostic items listed in Appendix B. Problem Determination: 1, 2. _______________________________________________________________ 00F30407 Explanation: The DB2 subsystem was abended by module DSN3SSI1, because the job-step task in a resource manager address space terminated. This abend reason code is issued by the following CSECT(s): DSN3SSI1 System Action: The DB2 subsystem is terminated with an SVC dump. Operator Response: You can start DB2 again after it terminates. System Programmer Response: At least one SVC dump and associated SYS1.LOGREC entries should be available. If you suspect an error in DB2, refer to Section 3 of Diagnosis Guide and Reference for information on identifying and reporting the problem. Problem Determination: This is usually caused by a previous error that has recorded data on the SYS1.LOGREC data set and requested an SVC dump. Examine the SYS1.LOGREC entries and SVC dumps to determine the actual cause of the error. Refer to "DB2 Abend Completion Codes" on page 1-6 for information on X'04F' and X'04E' abend completion codes. Collect the following diagnostic items Appendix B. Problem Determination: 1, 2. =============================================================== Book Title: Messages and Codes Page Number: p. 4-275 For abend reason code 00E70005, replace the SYSTEM PROGRAMMER RESPONSE with the following: SYSTEM PROGRAMMER RESPONSE: This code generates an SVC dump and SYS1.LOGREC entries. Use the information from those two sources and from the Problem Determination section of this message to resolve the problem. If you suspect an error in DB2, refer to Section 3 of Diagnosis Guide and Reference for information on identifying and reporting the problem. Replace the second paragraph of PROBLEM DETERMINATION with: For information about finding the SQLCA, refer to Section 4 of Diagnosis Guide and Reference. ================================================================ Book Title: Messages and Codes Page Number: p. 4-315 Add abend reason code 00F30408 to page 4-315: 00F30408 EXPLANATION: The DB2 subsystem was terminated because a DB2 resource manager address space is in end-of-memory processing. This abend reason code is issued by the following CSECT(s): DSN3SST1 SYSTEM ACTION: The DB2 subsystem is terminated with an SVC dump OPERATOR RESPONSE: DB2 can be started again after it terminates. SYSTEM PROGRAMMER RESPONSE: At least one SVC dump and associated SYS1.LOGREC entries should be available. If you suspect an error in DB2, refer to Section 3 of Diagnosis Guide and Reference for information on identifying and reporting the problem. PROBLEM DETERMINATION: This is usually caused by a previous error that recorded data on the SYS1.LOGREC data set and requested an SVC dump. The SYS1.LOGREC entries and SVC dumps should be examined to determine the actual cause of the error. Refer to Appendix A, "CICS Transaction Abend/Dump Code" for information on X'04F' and X'04E' abend completion codes. Collect the following diagnostic items: o Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time spanning the failure o The SVC dump o Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II06784
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
1993-03-10
Closed date
1993-03-10
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