APAR status
Closed as canceled.
Error description
5740xyr00 DB2 R410 V4 This APAR documents changes to the DB2 Administration Guide Volume 1 SC26326500 which did not make Version 4.1 GA pubs. Continued from II09139. Continued in II11268. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 1-24, 1-25, 1-26, 1-27 Change Description: In the section titled data structures in the System Planning Concepts chapter, add more specific information on table space sizes and correct some index sizes. 1.In the first paragraph under "Table Spaces", modify as follows: "A table space is one or more data sets in which one or more tables are stored. A table space can consist of a number of VSAM data sets, which can together contain up to 64 gigabytes of data... 2.In the section "Partitioned table spaces" modify as follows: "...A partition can be 1, 2, or 4 gigabytes in length, depending on the number of partitions contained in the entire table space. The maximum number of partitions in a partitioned table space is 64. If less than 16 partitions are defined on the table space, then its maximum size is 4 gigabytes." 3.In the section "Simple Table Spaces", add the last sentence as follows: "The maximum size of a data set in the simple table space is 2 gigabytes. And so, the maximum size of a simple table space is 64 gigabytes (2 gigabytes multipled by 32 data sets)." 4.In the section "Indexes", modify as follows: "Each index occupies its own index space. A nonpartitioned index can contain from 1 to 32 VSAM linear data sets." 5.In the section "Partitioned Indexes" modify as follows: "A partitioned index is created on a table in a partitioned table space and is divided into multiple index spaces. A partitioned index consists of between 1 and 64 partitions, each of which has a one to one correspondence to a VSAM data set. Each partitioned table space always has one table and one partitioned index defined on it. The maximum size of a partitioned index is 1, 2, or 4 GB depending on the number of partitions. A partitioned index is always a clustering index. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 1-34 Change Description: Change the last paragraph on the page to this: To reduce the probability and duration of unplanned outages, you should periodically back up and reorganize your data. Because these affect the availability of the databases, you should limit your use of, and understand the options of, utilities such as COPY and REORG. The CONCURRENT and SHRLEVEL options of the COPY utility can minimize outages and improve availability of DB2 data during backup processing. If you use the SHRLEVEL CHANGE option, the data sets being copied are available during the entire copy operation. If you use SHRLEVEL REFERENCE, the availability of data sets depends on whether you also use the CONCURRENT option, which invokes DFSMS Concurrent Copy. - If you specify SHRLEVEL REFERENCE but not CONCURRENT, data sets are unavailable until the copy operation is complete. - If you specify SHRLEVEL REFERENCE and CONCURRENT, data is unavailable only until DFSMSdss finishes logical processing of the list of data sets to be copied. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 1-40 Change Description: Change the first full paragraph on the page to this: You can use DB2 with an extended recovery facility (XRF) to facilitate recovery from a CICS failure. To accomplish this, you must place all DB2 data sets on DASD shared between the primary and alternate XRF systems. This enables DB2 to be manually stopped on the primary system and started on the alternate system. You must then ensure that the DB2 data sets on the shared DASD cannot be updated at the same time by both the primary and alternate XRF systems. You might use a multi-system DASD serialization function, such as Global Resource Serialization (GRS), or any other means of shared DASD protection. For more information about XRF, see "Extended Recovery Facility (XRF) Toleration" in topic 4.7.5.1 and IMS/ESA Administration Guide: System. For more information on global resource serialization, see "MVS/ESA Planning: Global Resource Serialization." Change the index entry for global resource serialization to this: GRS (global resource serialization) for shared DASD and XRF ============================================================== Version 4 Book Title: Administration Guide, Volume 1 Pages: 2-85 Change Description: Change the second paragraph under "The CREATE STOGROUP Statement" to this: When DB2 processes the CREATE STOGROUP statement, it does not check the existence of the volumes in the VOLUMES clause or determine the types of devices that the volumes identify. Later, when the storage group is used to allocate data sets, DB2 passes the list of volumes in the order you specified to Data Facilities (DFSMSdfp), which does the data set allocation. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 2-85 and 2-124 Change Description: On page 2-85, remove the reference to a limit of 133 in the third paragraph under 'The CREATE STOGROUP Statement". Change the paragraph to read as follows: | All the volumes in a storage group must be of the same type. | If the volumes you name are not mounted, or not all of the same device type, a dynamic error allocation error occurs when you try to create a table space or index. On page 2-124, remove the reference to a limit of 133 in the second paragraph under 'Altering DB2 Storage Groups". Change the paragraph to read as follows: | All the volumes in a storage group must be of the same type; | and when a storage group is used to extend a data set, the volumes must have the same device type as the volumes used when the data set was defined. ============================================================ Version 4 Book Title: Administration Guide, Volume I Pages: 2-124 Change Description: Change the third paragraph of Altering DB2 Storage Groups. Add that changes to the volume list by ALTER STOGROUP also take effect when DB2 extends a dataset. (You are not required to REORG or RECOVER.) This is the new passage: The changes you make to the volume list by ALTER STOGROUP have no effect on existing storage. Changes take effect when new objects are defined, when a data set is extended, or when the REORG, RECOVER, or LOAD REPLACE utilities are used on those objects. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 2-148 Change Description: The last sentence in the first bullet now reads as follows: For instructions on using DSNTIAUL, see Section 2 of Installation Guide. ============================================================ Version 4 Book Title: Administration Guide Vol. 1 Pages: 4-9 Change Description: Correct typo. STOP PROCEDURE is the correct command name for function "Prevents DB2 from accespting SQL CALL statements for a stored procedure". ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 4-9 and 4-11 Change Description: under topic: Where DB2 Commands Are Entered, change first bullet to: - An MVS console or MVS application Program under topic: From an MVS console: - change title to: From an MVS console or MVS application program - change first paragraph to: You can enter all DB2 commands from an MVS console or MVS application program. The START DB2 command can be entered only from the MVS console. The command group authorization level must be SYS. under topic: From an APF-authorized Program: - change the command from MGCR to MGRCE - add new paragraph after the IEFSSNxx sentence.DB2 supports the MVS WTO Command And Response Token (CART) to route individual DB2 command response messages back to the invoking application program. The CART token is required if multiple DB2 commands are issued from a single application program. ============================================================ Version 4 Book Title: Administration Guide Vol. 1 Pages: 4-18 Change Description: Add the following sentence after ...IMS uses ASXBUSER field (if RACF or another security package is active). The ASXBUSER field is defined by MVS as 7 characters. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 4-31 Change Description: Add the following sentence to the paragraph beginning with "The AT(COMMIT) option of STOP...". The AT(COMMIT) option is required to interrupt threads that are bound with RELEASE(DEALLOCATE), especially in situations with high thread reuse. ============================================================ Version 4 Book Title: Adminstration Guide, Volume 1 Pages: 4-32 Replace the first two paragraphs in section Altering Buffer Pools with: DB2 maintains the buffer pool attributes that were defined during installation, such as buffer pool and hiperpool sizes, in the DB2 bootstrap data set. You use the ALTER BUFFERPOOL command to alter buffer pool attributes, including the buffer pool sizes, sequential steal thresholds, deferred write thresholds, parallel sequentional threshold, and hiperpool CASTOUT attributes for active or inactive buffer pools. Altered bufferpool values are stored and used until altered again. ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 4-174 Change Description: 2. Look ahead warning A look ahead warning occurs when 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 determines whether the data | set has enough available space. DB2 uses the following | values in this space calculation: | - the primary space quantity from the integrated catalog | facility (ICF) catalog | - the secondary space quantity from the ICF catalog | - the allocation unit size | If there is not enough space, DB2 tries to extend the | data set. If the extend request fails, DB2 issues the following message: DSNP001I - DSNPmmmm - data-set-name IS WITHIN nK BYTES of AVAILABLE SPACE. RC=rrrrrrrr CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy LUW-ID=logical-unit-of-work-id=token ============================================================ Version 4 Book Title: Administration Guide, Volume 1 Pages: 4-223 Change Description: Replace the first sentence under topic Total Loss of Log with: Even if all current copies of the BSDS and the active or archive log or both have been destroyed or lost, DB2 can still be restarted and data that belongs to that DB2 subsystem can still be accessed, provided that all system and user table spaces have remained intact and you have a recent copy of the BSDS. =============================================================== continued in II11268
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
CLOSE FOR INTERNET VIEWING
APAR Information
APAR number
II10229
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-07
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