APAR status
Closed as canceled.
Error description
5740xyr00 DB2 R410 V4 This APAR documents changes to the DB2 Installation Guide SC26345600 which did not make Version 4.1 GA pubs. continued in II09154, II09481, II10228, II10827. =============================================================== Version 4 Book Title: Installation Guide Pages: 1-37 Change Description: The following statement is removed from the Version 4 and Version 5 Installation Guide: "The subsystem command prefix is built from the subsystem recognition character concatenated with the DB2 subsystem name." ============================================================ Version 4 Book Title: Installation Guide Pages: 2-24, 2-240, 2-255 Change Description: p.2-24: The paragraph under heading "DASD Requirements for the Work File Database" now contains a cross reference to the migration chapter: "For additional migration considerations when running DSNTIJTC please refer to "Migrating the DB2 Subsystem". This chapter deals with specific migration considerations that you need for calculating the size of your workfile database." p.2-240: The heading is changed from "New Indexes" to "Workfile Database Size Calculations". The paragraph under this heading has been changed to: "The migration job DSNTIJTC creates 10 new indexes and updates one index on catalog tables. These indexes are created "sequentially" during migration. The work file database is used for the sort. The migration fails if you do not have enough storage, so ensure that you have enough space before you begin. See "DASD Requirements for the Work File Database" for information about space requirements." A new table has been added, "Index changed using the work file database". This lists DSNATX02 and its columns that are updated during migration. The title of the table showing the new indexes has been modified to stress that the indexes are added sequentially during migration. The new table title is: "Indexes added sequentially the work file database". p.2-255: The paragraph under Migration Step 18 has been modified to reference the tables on page 2-240 showing the new and changed indexes during migration that might affect workfile database space needs. The last sentence in the paragraph has been changed and a new sentence added: "Then the utility creates new catalog tables, adds columns to existing catalog tables and creates and updates indexes on the catalog tables to accommodate new Version 4 objects. All the indexes are created or updated sequentially during the execution of DSNTIJTC." ============================================================== Version 4 Book Title: Installation Guide Pages: 2-31 Change Description: Records per page=FLOOR(3870 / 8)=48 is changed to FLOOR(3870 / 80)=48 ============================================================ Version 4 Book Title: Installation Guide Pages: 2-35 Change Description: The following paragraph will be added to the section titled "Virtual Storage for Address Spaces", p.2-35. You might notice that the samples jobs sometimes use a region size of 0K. This region size is meant to simplify the installation process in those particular cases. In the following sections, there are some recommendations from DB2 on region sizes. These recommendations are based on "average" use under "normal" circumstances on "typical" systems. Your requirements might be quite different. In the section on "DB2 Distributed Data Facility Address Space" on page 2-35, change "We recommend you specify 5000KB but plan to use 2000KB" to "We recommend you use the default region size of 0KB." ============================================================ Version 4 Book Title: Installation Guide Pages: 2-45 Change Description: Under the heading DATA SET CONTROL BLOCK STORAGE SIZE CALCULATION, change the 3rd bullet to: Let "indexes" be the number of indexes per table. The installation CLIST sets this variable to 2. ============================================================ Version 4 Book Title: Installation Guide Pages: 2-68 Change Description: The section titled "Using Navigation Aids from the GoTo Pull-down" is deleted. ============================================================ Version 4 Book Title: Installation Guide Pages: 2-76 Change Description: The following paragraph is added after the discussion of upward and downward compatibility: Please be aware that some early code modules contain SQLSTATEs. In DB2 V4R1, some SQLSTATE values were changed or added to conform to ANSI/ISO SQL standard of 1992. You might need to modify any application programs that reference old SQLSTATE values. See MESSAGES AND CODES for a list of SQL codes that are changed or added. As mentioned earlier, it is a good idea to check monthly for PSP updates to get the most current information about DB2. ============================================================ Version 4 Book Title: Installation Guide Pages: 2-123 Change Description: The sentence will be changed to: "If COBOL is not installed on your system, do not run jobs DSNTEJ2C, DSNTEJ3C, DSNTEJ4C, DSNTEJ5C, OR DSNTEJ6." ============================================================ Version 4 Book Title: Installation Guide Pages: 2-133, 2-363 Change Description: p.2-133: an emphasis added to the word "not" "Fields 6-11 might NOT be required". p.2-363: If you are migrating and you use the CICS attachment facility, you must assemble and link-edit the RCT. This is optional, however, if you are using CICS version 4 or above. ============================================================ Version 4 Book Title: Installation Guide Pages: 2-140 Change Description: Panel DSNTIPE will be updated to reflect changes that were made in PN76627, as follows: 8 UTILITY CACHE OPTION ===> NO 9 DEFAULT INDEX TYPE ===> 2 The detail for field 8 will be as follows: Specify whether utilities that do a scan of a nonpartitioned index followed by an update of a subset of the pages in the index allow data to remain in 3990 cache longer when reading data. If you specify YES, these DB2 utilityprefetch reads remain in cache longer, possibly improving performance of subsequent writes in the following cases for a table with very large nonpartitioned indexes: -LOAD PART integer RESUME -REORG TABLESPACE PART This option is useful only with RAMAC DASD attached to the 3990 Model 6. If you specify NO, DB2 utilities use the 3990 cache the same way as any other application (as you specified in the SEQUENTIAL CACHE option). ============================================================ Version 4 Book Title: Installation Guide Pages: 2-182 Change Description: A new paragraph is added following the paragraph that ends "Specify YES if you want the data to be compacted": If you use compression or auto-blocking on the tape unit, you will need to ensure that you do not read backwards on the tape unit. You can do this by increasing the size and number of active log data sets and by monitoring long running units of recovery withthe UR CHECK FREQ (panel DSNTIPN) or another monitor. The alternative to monitoring the units of work and increasing active log space is archiving to disk and then using another facility, such as DFSMShsm to archive the archive log from disk to tape. Be aware that data compressed to tape can only be read using a device that supports the IDRC feature... ============================================================ Version 4 Book Title: Installation Guide Pages: 2-206 Change Description: An asterisk will be added following option 20 MVS PARMLIB UPDATES. The documentation now matches the actual panel. ============================================================ Version 4 Book Title: Installation Guide Pages: 2-240 Change Description: The title of Table 62 is changed to "New indexes added sequentially by using the workfile database." ============================================================ Version 4 Book Title: Installation Guide Pages: 2-255 Change Description: The following sentence is added in Migration Step 16, bullet number 2, following the example: -DSN1 DISPLAY DATABASE(*) SPACENAM(*) RESTRICT "The above command might also produce message DSNT501I with reason code C900A6." ============================================================= Version 4 Book Title: Installation Guide Pages: 2-261 Change Description: Under the first bullet which talks about using ALTER INDEX with option CONVERT TO TYPE 2, change the numbered bullets to: 1. Please be aware that Type 2 indexes require more space than Type 1 indexes. Before you convert to Type 2 indexes with the ALTER INDEX command, determine if you need to allocate more space for these indexes. Refer to "Calculating the Space Required for a Type 2 Index" on page 2-32. Based on these calculations, if your index space is not large enough, delete and re-define your data sets with a larger allocation. You can use DFSMSdfp to manage your data sets. For more information on increasing your data set allocations, see "DFSMS/MVS: Storage Administration Reference for DFSMSdfp 2. Issue ALTER INDEX... for EACH index. 3. You must run the utility RECOVER INDEX for EACH index. Under the second bullet which talks about using CATMAINT utility with CONVERT TO TYPE 2 option, change the numbered bullets to: 1. Please be aware that Type 2 indexes require more space than Type 1 indexes. Before you convert to Type 2 indexes with the ALTER INDEX command, determine if you need to allocate more space for these indexes. Refer to "Calculating the Space Required for a Type 2 Index" on page 2-32. Based on these calculations, if your index space is not large enough,delete and re-define your data sets with a larger allocation. You can use DFSMSdfp to manage your data sets. For more information on increasing your data set allocations, see "DFSMS/MVS: Storage Administration Reference for DFSMSdfp". 2. Invoke the CATMAINT utility with theCONVERT TO TYPE 2 option. This utility takes care of both the ALTER and RECOVER INDEX steps for you. ============================================================ Version 4 Book Title: Installation Guide Pages: 2-271 Change Description: The following documentation change is made for version 4 only under the heading "Remigrating", following the current second paragraph: Please note that after fallback, DB2 uses DSNDB01.SYSLGRNX instead of DSNDB01.SYSLGRNG. You must be sure that actions are against DSNDB01.SYSLGRNX during remigration. ============================================================ Version 4 Book Title: Installation Guide Pages: 3-19 Change Description: The following sentences have been added under Step 5: Populate the Communications Database: "You do not need to populate table SYSIBM.SYSLULIST unless DB2 is acting as a requester of data in a data sharing group. See Data Sharing Administration and Planning Guide for more information. ============================================================ Apar is continued in II10827.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
CLOSE FOR INTERNET VIEWING
APAR Information
APAR number
II10228
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