APAR status
Closed as canceled.
Error description
This APAR documents changes to the DB2 Administration Guide Volume 2 SC26-4888-00 which did not make Version 3 GA pubs. 5740xyr00 R310 Continuation of II07836, continued in II08714. ================================================================ Version 3 Book Title: DB2 Administration Guide, Volume 2 Pages: 5-81 and 5-82 Change Description: Replace the entire contents of Figure 165 with the following: //* //* REASSEMBLE AND LINKEDIT THE RACF STARTED PROCEDURES //* TABLE ICHRIN03 TO INCLUDE USERIDS AND GROUP NAMES //* FOR EACH DB2 CATALOGED PROCEDURE. OPTIONALLY, ENTRIES //* FOR AN IMS OR CICS SYSTEM MIGHT BE INCLUDED. //* //* AN IPL WITH A CLPA (OR AN MLPA SPECIFYING THE LOAD //* MODULE) IS REQUIRED FOR THESE CHANGES TO TAKE EFFECT. //* ENTCOUNT DC AL2(((ENDTABLE-BEGTABLE)/ENTLNGTH)+32768) * NUMBER OF ENTRIES AND INDICATE RACF FORMAT * * PROVIDE THREE ENTRIES FOR EACH DB2 SUBSYSTEM NAME. * BEGTABLE DS 0H * ENTRIES FOR SUBSYSTEM NAME "DSN" DC CL8'DSNMSTR' SYSTEM SERVICES PROCEDURE DC CL8'SYSDSP' USERID DC CL8'DB2SYS' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES ENTLNGTH EQU *-BEGTABLE CALCULATE LENGTH OF EACH ENTRY DC CL8'DSNDBM1' DATABASE SERVICES PROCEDURE DC CL8'SYSDSP' USERID DC CL8'DB2SYS' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES DC CL8'DSNDIST' DDF PROCEDURE DC CL8'SYSDSP' USERID DC CL8'DB2SYS' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES * ENTRIES FOR SUBSYSTEM NAME "DB2T" DC CL8'DB2TMSTR' SYSTEM SERVICES PROCEDURE DC CL8'SYSDSPT' USERID DC CL8'DB2TEST' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES DC CL8'DB2TDBM1' DATABASE SERVICES PROCEDURE DC CL8'SYSDSPT' USERID DC CL8'DB2TEST' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES DC CL8'DB2TDIST' DDF PROCEDURE DC CL8'SYSDSPT' USERID DC CL8'DB2TEST' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES * ENTRIES FOR SUBSYSTEM NAME "DB2P" DC CL8'DB2PMSTR' SYSTEM SERVICES PROCEDURE DC CL8'SYSDSPD' USERID DC CL8'DB2PROD' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES DC CL8'DB2PDBM1' DATABASE SERVICES PROCEDURE DC CL8'SYSDSPD' USERID DC CL8'DB2PROD' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES DC CL8'DB2PDIST' DDF PROCEDURE * OPTIONAL ENTRIES FOR CICS AND IMS CONTROL REGION DC CL8'CICSSYS' CICS PROCEDURE NAME DC CL8'CICS' USERID DC CL8'CICSGRP' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES DC CL8'IMSCNTL' IMS CONTROL REGION PROCEDURE DC CL8'IMS' USERID DC CL8'IMSGRP' GROUP NAME DC X'00' NO PRIVILEGED ATTRIBUTE DC XL7'00' RESERVED BYTES ENDTABLE DS 0D END =============================================================== Book Title: Operations and Recovery Page Number: 6-18 Change Description: In the section "Running TSO Application Programs" change the RUN statement to read: RUN PROGRAM (DSN8BC3) PLAN(DSN8BH31) LIB ('DSN310.RUNLIB.LOAD') =============================================================== Version 3 Book Title: Administration Guide, Volume II Pages: 6-100 Change Description: 1. Change the heading 'Deferring Recovery of an Object' to 'Deferring Restart and Recovery of an Object'. Also change the paragraph following this heading: 'Usually, restarting DB2 also restarts the resources that were available when DB2 terminated. However, if some specific object is causing problems, you should consider deferring its restart and restarting | DB2 without it. If the deferred object needs to | go through restart recovery, the recovery is deferred | until you restart it. (See 'Restarting Deferred | Objects' on page 6-101 for more information.) In addition to your intentionally deferring the restart and recovery of particular objects, DB2 defers recovery of any object with certain problems, such as an open or I/O error during restart.' 2. Change the heading 'How to Defer Recovery' to 'How to Defer Restart'. Also change the first bullet after this heading: 'Stop the object before stopping DB2. If you stop an object with the -STOP command before DB2 stops, | that object: | - is not started automatically when DB2 restarts | - does not need to go through recovery when you | restart it' ================================================================ Book Title: Operations and Recovery Page Number: 6-101 Change Description: Add the following as a new last paragraph in the section "Running Utilities on Deferred Objects:" When RECOVER, LOAD REPLACE, RECOVER INDEX or REPAIR are run on a deferred page set, that page set is implicitly started with utility-only access (UT). If you need to change the access mode after the utility processing is complete, use the -START DATABASE command with option ACCESS(RW) or ACCESS(RO). For page sets which belong to a shared read-only database (ROSHARE OWNER), the -STOP DATABASE command must be issued before changing the start access mode. =============================================================== Version 3 Book Title: DB2 Administration Guide Pages: 6-144 Change Description: Revise step 1 under the section "To obtain a consistent offline backup" to read: 1. If the backup mechanism requires an EXCLUSIVE ENQ on the data set (for example, DFSMShsm), stop the DB2 objects being backed up by issuing the following command: -STOP DATABASE(database name) SPACENAM(tablespace-name) Otherwise start the DB2 objects being backed up for read- only access by issuing the following command: -START DATABASE(database name) SPACENAM(tablespace-name) ACCESS(RO) This is necessary to ensure that no updates to data occur during this procedure. =============================================================== Version 3 Book Title: Administration Guide, Volume 2 Pages: 6-146 Change Description: Change number 12 under 'Order of Recovering Catalog and Directory' as follows: o Other catalog and directory table spaces and indexes. DSNDB06.SYSUSER has two indexes that have not yet been recovered. The remaining catalog table spaces, in database DSNDB06, are SYSGROUP, SYSGPAUT, SYSPLAN, SYSPKAGE, SYSSTATS, SYSSTR, and SYSVIEWS. | Most indexes are listed in SQL Reference. | SYSVIEWS has one additional index that is not listed in | that publication: DSNVTH01. There are two remaining directory table spaces, DSNDB01.SCT02, which has indexes SYSIBM.DSNSCT02, and DSNDB01.SPT01, which has indexes SYSIBM.DSNSPT01 and SYSIBM.DSNSPT02. ================================================================ Book Title: Operations and Recovery Page Number: 6-179 Change Description: In the section "Manually Recovering CICS Indoubt Units of Recovery," Step 2, second paragraph, change the wording of the first sentence to: Locating the prepare log record in the ... =============================================================== Version 3 Book Title: DB2 Administration Guide, Volume II Pages: 6-188, 6-189, 6-191 Change Description: On page 6-188, under 'BSDS Failure', remove the sentence that says 'This requires stopping DB2.' On page 6-189, remove 'at startup' from the first sentence. (Problem 1 can happen while DB2 is up.) On page 6-191, rename the section titled 'BSDS Recovery' to 'Recovering the BSDS from a Backup Copy'. Also remove the first paragraph, and the 3 numbered steps below it. =============================================================== Book Title: Operations and Recovery Page Number: 6-198 Change Description: In the section "VSAM Volume Data Set (VVDS) Destroyed," under the heading "Operator action," add the following sentence to Step 3: If you are recovering objects created in an ROSHARE OWNER database that are STOGROUP defined, and the physical VSAM data set does not exist, the -STOP DATABASE command cannot be used. In this case, stop the DB2 subsystem. =============================================================== Book Title: Operations and Recovery Page Number: 6-199 Change Description: In the section "VSAM Volume Data Set (VVDS) Destroyed," under the heading "Operator action," revise Step 6 to read: Use access method services DELETE and DEFINE commands to delete and redefine the data sets for all user-defined table spaces and DB2-defined data sets for shared read-only data (when the physical data set has been destroyed). DB2 automatically deletes and redefines all other STOGROUP defined table spaces. =============================================================== Version 3 Book Title: DB2 Administration Guide, Volume 2 Pages: 6-199 The paragraph following the DSNP001I message on page 6-199 of the DB2 Version 3 Administration Guide now reads: In that case, there is enough space for a few inserts and updates, but the index space or table space is almost full. On an insert or update at the end of a page set, DB2 compares the amount of space available with a hedge value. The hedge value is half of the secondary space quantity obtained from the integrated catalog facility catalog. If the amount of space available is less than the hedge value,then DB2 tries to extend the data set. If the extend request fails, then DB2 issues message DSNP001I. ================================================================ Version 3 Book Title: Administration Guide, Volume II Pages: 6-200 Change Description: The following sentence should be added to the first paragraph under 'Procedure 1. Extend a Data Set': If you use ALTER ADDVOLUMES, you should stop the table space and restart it after adding the new volumes. ================================================================ Book Title: Operations and Recovery Page Number: 6-207 Change Description: In the section "Remote Site Recovery from Disaster at a Local Site," change Step 4 to read: Use the access method services DEFINE CLUSTER command with the REUSE option to allocate the catalog, directory, user-defined table spaces, indexes, logs and any DB2-defined data sets created for shared read-only databases where the physical data sets do not exist. =============================================================== This APAR is continued in APAR II08714.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for internet viewing
APAR Information
APAR number
II08064
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
1994-07-20
Closed date
1997-10-24
Last modified date
1997-10-24
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:
14 December 2020