APAR status
Closed as canceled.
Error description
5740xyr00 DB2 R410 V4 continued in II10645. This APAR documents changes to the DB2 Utility Guide and Reference SC26-3395-00 which did not make Version 4.1 GA pubs. =============================================================== Version 4 Book Title: Utility Guide and Reference Pages: 2-19, 2-180 Change Description: On page 2-19, "Sample DSNUPROC Listing," change the second line under SIZE to read: THE DEFAULT REGION SIZE IS 4096K. On page 2-180, add a new first paragraph under "Before Running REORG": REORG may require a larger reqion size for Version 4 than for Version 3. The recommended minimum is 4096K. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-64 Change Description: Replace this statement: "If you issue TERM UTILITY while COPY is in the active or stopped state, the table space is put in copy pending status." With this statement: "If you issue TERM UTILITY while COPY is in the active or stopped state, a "T" record is inserted in SYSIBM.SYSCOPY. When you run COPY, it does not allow an incremental image copy if the "T" record exists. You must take a full image copy." ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-66 Change Description: Add a new sentence after "To run on DSNDB01.SYSUTILX, COPY must be the only utility in the job step.": If SHRLEVEL REFERENCE is specified, COPY for DSNDB01.SYSUTILX must be the only utility running in the sysplex. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-74 Change Description: Under the heading, "Forcing a Utility Abend with DIAGNOSE", delete the following sentence: The DIAGNOSE utility does not force an abend on message DSNU399I,"LOAD UTILITY ERROR SUMMARY REPORT." (This sentence is removed due to PTF PL72949 (V3). Users can force an abend when DSNU399I is issued from the LOAD utility using DIAGNOSE.) ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-91 Change Description: Under "Compressing Data," and a new paragraph after the first paragraph: The data is not compressed until the dictionary is built. You must use LOAD REPLACE or RESUME NO to build the dictionary. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-133, 2-135, 2-172, 2-181, 2-182 Change Description: p. 2-133, MODIFY: Change the first sentence of the first paragraph to "The MODIFY RECOVERY online utility deletes records from the SYSIBM.SYSCOPY catalog table, related log records from the SYSIBM.SYSLGRNG directory table, and entries from the DBD." p. 2-172, "Keyword and Parameter Descriptions": Second paragraph under TABLESPACE, add the sentence: "You cannot recover catalog or directory table spaces in a list." p. 2-181-2, "Reclaiming Space from Dropped Tables": First paragraph: add "See "Reclaiming Space in the DBD" on page 2-135 for actions to take when you drop a table." Delete the second paragraph, including the list. p. 2-135, "Instructions for Specific Tasks," add two new notes: Reclaiming Space in the DBD ___________________________ To reclaim space in the DBD when you drop a table, use the following procedure: 1. Commit the drop 2. Run the REORG utility on the tablespace 3. Run the COPY utility to make a full image copy of the table space 4. Run MODIFY with the DELETE option to delete all previous image copies. MODIFY reclaims space only if there are SYSCOPY rows to delete. Improving REORG Performance after Adding a Column _________________________________________________ If you add a column to a table space and the record was previously fixed-length, DB2 treats the record as variable-length. As a result, the REORG utility decompresses the rows of the table space during the UNLOAD phase and then compresses them again during the RELOAD phase. To remedy this, use the following procedure: 1. Run the REORG utility on the tablespace 2. Run the COPY utility to make a full image copy of the table space 3. Run MODIFY with the DELETE option to delete all previous image copies. MODIFY will return the record to fixed-length status only if there are SYSCOPY rows to delete. ================================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-141 Change Description: Under "Considerations for Running QUIESCE," add a new paragraph as follows: If Too Many Table Spaces Are Specified -------------------------------------- If QUIESCE is run on a list of more than 1165 table spaces, it terminates with a return code of 8 as shown: DSNU000I DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = QUIESCE DSNU046I DSNUGPSP - UTILITY STATEMENT IS TOO LONG OR TOO COMPLEX DSNU012I DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-148 Change Description: In Table 33, change the Required column for the Work Data Set to "No." In the paragraph on "Creating the Work Data Set," change "requires" to "can use." ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-158 Change Description: The paragraph beginning "For a multiple data set table space" will be deleted. The following paragraph presents the same information more clearly. ============================================================= Version 4 Book Title: Utility Guide and Reference Pages: 2-173 Change Description: Replace the first paragraph under the TORBA keyword to the following: Is used in a non-data-sharing environment to specify a point on the log to recover to. TORBA must be used when recovering to a point before Version 4. In a data sharing environment, TORBA must be used only when recovering to a point before the originating member joined the data sharing group. If you specify an RBA after this point, the recovery fails. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-182 Change Description: Add a new paragraph under "Reorganizing the Catalog and Directory": Attention: You should take a full image copy before and after reorganizing any catalog or directory object. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-182 Change Description: Change the first bullent under "Limitations for Reorganizing the Catalog and Directory" to the following: * You cannot reorganize DSNDB01.SYSUTILX. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-208 Change Description: Add a table space spec entry similar to the one in the diagram on p. 2-209 to the syntax diagram on p. 2-208. ============================================================ Version 4 Book Title: Utility Guide and Reference Page: 2-208 Change description: In the following section, the first item will be removed. You cannot use LEVELID with: - An open table space or partition - A table space or partition with outstanding indoubt log records or pages in the logical page list (LPL). The section will now read as follows: You cannot use LEVELID with a table space or partition with outstanding indoubt log records or pages in the logical page list (LPL). ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-217 to 2-218 Change Description: Example 1, line 3 is changed to: VERIFY OFFSET 50 DATA X'A00' Example 1, line 4 is changed to: REPLACE OFFSET 50 DATA X'D11' Example 5, step 1, line 3 is changed to: VERIFY OFFSET X'0A' DATA X'00002422' Example 5, step 1, line 4 is changed to: REPLACE OFFSET X'0A' DATA X'00000000' Example 5, step 2, line 3 is changed to: VERIFY OFFSET X'06' DATA X'00002521' ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-222 Change Description: Under "Report Recovery Output," change the second paragraph under the first bullet to the following: For a description of the fields in the SYSCOPY rows, see the table describing SYSIBM.SYSCOPY in Appendix D of SQL Reference. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 2-235 Change Description: The following is added after the second paragraph that ends with 'See the description following FAROFFPOS.' NEAROFFPOS is incremented if the current indexed row is not on the same or the next page of the previous indexed row, and the distance between the two pages does not qualify for FAROFFPOS. In the last paragraph after the sentence that ends with 'less than segsize * 2', add the following: A nonzero value in the NEAROFFPOS field after a REORG could be attributed to the number of space map pages contained in the segmented table space. The last sentence in this paragraph will be deleted: A page is also considered near-off the present page if it immediately precedes the present page. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 3-23, 3-24, 3-30 Change Description: On page 3-23, add the following paragraph after the bulleted list in the introduction: In a data sharing environment, the DSNJU004 utility can list information from any or all BSDSs in a data sharing group. On page 3-24, change the heading "Required Data Sets" to "Required and Optional Data Sets." Add the entries for SYSIN, GROUP, and MxxBSDS from pp 244-5 of Data Sharing: Planning and Administration. On page 3-30, under a new heading "Syntax and Options of the Control Statement," add an introductory paragraph: Using the SYSIN data set allows you to list information from any or all BSDSs of a data sharing group. After the introductory paragraph, add the Control Statement Syntax and Option Descriptions from page 244 of Data Sharing: Planning and Administration. ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 3-32 Change Description: Add a new third paragraph under Example 1: "The RIDs in Step 5 of the example are for example purposes only. Using them results in a error message. Change them to the actual RIDs to be checked." ============================================================ Version 4 Book Title: Utility Guide and Reference Pages: 3-38 Change Description: Under "Considerations for Running DSN1COMP, include the following paragraph under a new subheading: Running DSN1COMP on a Table Space with Identical Data _____________________________________________________ If you run DSN1COMP on a table space in which the data is the same for all rows, message DSN1941I is issued and DSN1COMP does not compute any statistics. ============================================================ This APAR is continued in II10645.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
closed for db2info retention
APAR Information
APAR number
II09160
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
1995-12-28
Closed date
1997-10-23
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