APAR status
Closed as canceled.
Error description
5740xyr00 DB2 R410 V4 Continued in II09155, II10803 This APAR documents changes to the DB2 Messages and Codes SC26326800 which did not make Version 4.1 GA pubs. ============================================================ Version 4 Book Title: Messages and Codes Pages: 2-66 Change Description: Within the explanation for SQLCODE -30073, the following paragraph is changed as an introduction to the list of common code points: "The "parameter" is a 2-byte hexadecimal DDM code point. See "Distributed Data Management Architecture Reference Manual for a definition of the validcode points. Common values for "parameter include: " The following code point is added to the list: X'1144' DRDA servers return this code point when a DB2 client specifies a version for a package and the DRDA server does not support versions. ============================================================ Version 4 Book Title: Messages and Codes Page: 3-105 Change Description: In the operator response section of message DSNJ110E, modify the first sentence in the 2nd paragraph as follows: Execute an MVS Display System Requests command (D R,L for example) to determine the outstanding requests related to the log off-load process. ============================================================ Version 4 Book Title: Messages and Codes Pages: 3-181 Change Description: Message DSNR007I will be changed from: At the end of the first phase, it shows the status of any URs that require processing. At the end of the second (forward recovery) and third (backout) phases, it shows the status of only those URs which needed processing but were not processed. to: At the end of the current status rebuild phase, it shows the status of any URs that require processing. At the end of the forward recovery and backout phases, it shows the status of only those URs which needed processing but were not processed. ============================================================ Version 4 Book Title: Messages and Codes Pages: 3-255,256 Change Description: The utility message DSNU335 will be modified to more completely describe the differences in the LOAD utility with fixed record lengths. DSNU335I Explanation: The LOAD utility found that the input field 'ffffffff' extends beyond the end of the input record. If DISCARDS processing is active, the message severity is 4 (warning). ... System Action: For fixed length records, with no VARCHARs included, the length needed by the LOAD utility can be calculated before processing. In this case, when the LOAD utility determines that no records can be loaded because ALL of the INTO TABLE statements require input longer than the defined lengths, the LOAD job terminates on the first record without discarding any records. ============================================================ Version 4 Book Title: Messages and Codes Pages: 3-301 Change Description: The type and action parameters are irrelevant for these message types. However, DSNU659E is incorrect and should be DSNU659I. This message is issued for the REPAIR LEVELID utility in 2 circumstances: 1. The target dataset is in use, or, 2.there is outstanding log apply activity for the target pageset. Neither of these situations is an error condition. Therefore, the message will be changed to DSNU659I. ============================================================ Version 4 Book Title: Messages and Codes Pages: 3-327 Change Description: the following is added to the explanation for message DSNW133I: -The hexadecimal return code from the OPn request. 04 - No OPn buffer is assigned to an application to collect data. the following is added to the OPX return codes: 04 - No OPX buffer is assigned to an application to collect data. ============================================================ Version 4 Book Title: Messages & Codes Pages: 3-345 Messages DSNZ002I, DSNZ003I, and DSNZ004I will be modified to match the actual message that is generated. The messages will appear as follows: DSNZ002I src DSNZINIT SUBSYSTEM ssnm SYSTEM PARAMETERS LOAD MODULE NAME IS dsnzparm-name DSNZ003I csect-name DSNZINIT CSECT parm-csect NOT FOUND IN SYSTEM PARAMETERS DSNZ004I csect-name DSNZINIT INCORRECT LEVEL wrong-level FOUND IN parm-csect SYSTEM PARAMETERS. LEVEL correct-level IS REQUIRED ============================================================ Version 4 Book Title: Messages and Codes Pages: 3-369 Change Description: A pointer to the "MVS/DFP Diagnosis Guide" is added in the System Programmer Response for message DSN1995I and other messages that have the line "Follow standard VSAM diagnostic procedures." Specifically, the addition will say: See also MVS/DFP V3R3 Diagnosis Guide for more information on the standard VSAM procedures. ============================================================= Version 4 Book Title: Messages and Codes Pages: 4-218 Change Description: The message for 00D900F7 will be changed as follows: Explanation: DB2 received an error while attempting to acquire a lock. System Action: Standard DB2 diagnostic information is recorded in SYS1.LOGREC and an SVC dump might be requested. Depending on the error, DB2 might initiate subsystem termination. ============================================================ Version 4 Book Title: Messages and Codes Pages: 4-305 Change Description: The information about SYS1.LOGREC has already been added to reason code 00E60805 in a previous DB2BOOKS append (1379). However, an additional user response will be added to the message as follows: Refer to the IFCABM field in the IFCA (the number of bytes moved to the return area) to determine if partial information was returned. ============================================================ Version 4 Book Title: Messages and Codes Pages: 4-320 The wording for Message 00E7009E is changed as follows: 00E7009E Object depends on facilities of a release of DB2 that is later than you are currently running. This abend reason code is issued by the following CSECTs: DSNXIAIX DSNXIATB DSNXIATS DSNXICIX DSNXICTB DSNXIDIX DSNXIDTB DSNXIDTS DSNXOCA DSNXOLV The operation is not allowed. Notify the system programmer. In order to perform the operation on the object, you must use the release of DB2 that supports the new facilities. The requested operation is not performed. An SQLCODE -904 and/or message DSNT501I is issued. Message DSNT501I describes which object has the release dependency. ============================================================ Version 4 Book Title: Messages and Codes Pages: 5-5 Change Description: The following message is added: DXR100I irlmnm STORAGE IRLMID=pi Explanation: This message is issued in response to the following command: F <irlmproc>,STATUS,STOR A brief summary of selected storage usage is displayed where: CUR: xxxK is the CURRENT E/CSA usage HWM: xxxK is the High Water Mark or greatest amount of E/CSA allocated by IRLM during this initialization period POOL: RHB Resource Hash Block (RHB) RLB Resource Lock Block (RLB) If parameter PC=YES, then RHB and RLB are located in the IRLM PRIVATE region. If parameter PC=NO, the storage is in ECSA. Other-A Other ECSA storage allocated to IRLM Other-B Other CSA storage allocated to IRLM SEGS: n the number of storage segments allocated K-MEM: xxx Storage amount in 1000 byte units PC: YES/NO PC parmameter as specified in the "irlmproc" MAXCSA: xxxK the value displayed if parameter PC=NO. This represents the value of MAXCSA specified in the irlmproc, in units of 1000 bytes. N/A the value displayed if parameter PC=YES. The following is sample output for PC=NO: DXR100I IR21 STORAGE IRLMID=233 253 CSA STORAGE STATUS. CUR: 325K HWM: 325K POOL SEGS K-MEM - PC: NO MAXCSA: 1000K RHB 1 64 RLB 1 64 OTH-A 9 184 OTH-B 4 13 The following is sample output for PC=YES: DXR100I JR21 STORAGE IRLMID=032 262 CSA STORAGE STATUS. CUR: 193K HWM: 193K POOL SEGS K-MEM - PC: YES MAXCSA: N/A RHB 1 64 RLB 1 64 OTH-A 8 180 OTH-B 4 13 Message DXR121I is modified as follows: DXR121I irlmnm END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA 325K Explanation: The IRLM end-of-task routine released all of the MVS common storage that was used by the terminating IRLM. The HI-CSA is the highest amount of CSA + ECSA allocated to the IRLM during this initialization, represented in units of 1000 bytes. ============================================================== Version 4 Book Title: DB2 Messages & Code Pages: 5-12 Change Description: Add two new IRLM messages: DXR164E and DXR166E DXR164E irlmnm CANNOT RECOVER FOR A FAILED MEMBER DUE TO LOSS OF CONNECTIVITY TO THE LOCK STRUCTURE Explanation: IRLM detects loss of connectivity to the lock structure during member recovery or global initialization. IRLM is longer able to support data sharing without the retained lock information. System Action: Disconnect from the data sharing group. User Response: Notify the system programmer to correct the problem with the coupling facility. Problem Determination: See IXC messages to determine the root cause of the failure and the appropriate corrective action. DXR166E irlmnm CONNECT TO LOCK STRUCTURE FAILED FOR GLOBAL INITIALIZATION Explanation: IRLM detects loss of connectivity to the lock structure during member recovery or global initialization. IRLM is longer able to support data sharing without the retained lock information. System Action: Disconnect from the data sharing group. User Response: Notify the system programmer to correct the problem with the coupling facility. Problem Determination: See IXC messages to determine the root cause of the failure and the appropriate corrective action. ============================================================ This APAR is continued in II10803.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for INTERNET viewing
APAR Information
APAR number
II10225
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
1997-02-06
Closed date
1997-10-31
Last modified date
1999-06-08
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:
08 June 1999