IBM(R) DB2(R) !DB/SMU Version 510 and 610 APAR PK00722 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 2.0 PREREQUISITES 2.1 Hardware requirements 2.2 Software requirements 3.0 INSTALLATION INSTRUCTIONS 4.0 CUSTOMIZATION INSTRUCTIONS 5.0 CORRECTIONS TO DOCUMENTATION 6.0 HOW TO GET HELP 7.0 NOTICES 7.1 Use of Evaluation Program 7.1 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 !DB/SMU Version 510 and 610 APAR PK00722 README file. This README file contains information about installing the fix for !DB/SMU APAR PK00722. The fix for APAR PK00722 has been tested and validated up to PSP level 0440-1 on version 510 of !DB/SMU. This fix will be included at the next PSP. APAR PK00722 reports that the !DB/SMU check/fix function, program @SMCKFX was not purging enough data from the SYSTEM PDS. This fix improves the validation edits and results in better space management of the SYSTEM PDS. 1.1 Evaluation code This is not evaluation code. Please contact your IBM account representative to set up an evaluation of !DB/SMU. This code does not deliver the full product. This code delivers a fix for a specific APAR against !DB/SMU. 2.0 PREREQUISITES !DB/SMU has hardware and software requirements. 2.1 Hardware requirements Application of this APAR can be performed on any hardware system upon which !DB/SMU can run. -Approximately 50 tracks of free disk space are needed to implement this APAR fix. 2.2 Software requirements To apply this fix you must: Be running IBM DB2 !DB/SMU at version 510. Be able to run the binder or linkage editor, IEWL or equivalent Have Security System authority to update the product loadlib 3.0 INSTALLATION INSTRUCTIONS To install this APAR fix, complete the following tasks: 1. Download fix 2. Allocate receiving dataset on host 3. Transfer files to host 4. Allocate backup loadlib 5. Back-up load module 6. Apply fix 7. Run the check/fix program 8. Confirm fix results 1. Download fix This APAR fix will either arrive as a ZIP file attached to an email or will be downloaded from an FTP site. Please create a directory on the PC in which to receive the file. Either detach from the email to this directory or FTP the ZIP file in binary to this directory. 2. Allocate receiving dataset on host - hilev.PK00722 Allocate PDS on the host with the following attributes Organization . . . : PO Record format . . . : FB Record length . . . : 80 Block size . . . . : 27920 Space TRACKS 20,10,10 3. Transfer files to host FTP the files from the PC to the host PDS File OBJECT should be transfered in BINARY mode All other files can be transferred in ASCII 4. Allocate backup loadlib - hilev.PK00722.BKUPLOAD Allocate a PDS to backup the load module effected by this APAR Organization . . . : PO Record format . . . : U Record length . . . : 0 Block size . . . . : 32760 Space TRACKS 5,5,5 5. Back-up load module Copy load module @SMCKFX from the product load library to hilev.PK00722.BKUPLOAD 6. Apply fix Member LINK is the JCL to execute to link the object module replacement to the product load library. Modify the JCL as follows: For DD SYSLMOD, change hilev.LOAD to point to your product load library For DD SYSLIN, point to the hilev.PK00722 dataset allocated earlier Add appropriate JOBCARD for your site Submit job Confirm that job completed successfully 7. Run the check/fix program Member EXEC is the JCL to execute program @SMCKFX. This job has 2 steps. The first step is intended to delete the new SYSTEM PDS if it already exists. This facilitates easy re-runs of the job. The second is the purge program fixed by this APAR. Modify the JCL as follows: For DD PDSOUT provide a valid dataset name for the new !DB/SMU SYSTEM PDS. PDSOUT appears in 2 places. For PDSOUT in STEP010 the space allocation does not need to be changed. For PDSOUT in STEP020 insure that adequate DISK space is allocated. The amount of disk space needed should be less than the amount used by the current SYSTEM PDS. The size of the new SYSTEM PDS should be smaller, but because the amount of data that will be purged is dependent on the date and frequency of SCANs or SPACEMAPs and the PDATE value set in the PARM, it is not possible to predict how much smaller. For DD PDSIN, provide the name of the current SYSTEM PDS. This value should also be set for the DCB= value for PDSOUT in STEP020. Add a jobcard appropriate for your site Set the PDATE value on the PARM for STEP020. This value is the purge date. Members created prior to this date will be deleted. The format of the date field is YYDDD. Submit the job and confirm that it completes successfully. 8. Confirm fix results Using ISPF 3.4 you can determine how many members were purged and how much less DASD space is used by the new SYSTEM PDS. You can view the effect of the purge on the SYSTEM PDS in one of two ways. You can either reconfigure !DB/SMU to use the new SYSTEM PDS or you can perform renames. Reconfigure Enter !DB/SMU Select H for Housekeeping Select 0 Profile Data Administration. Select 4 Configuration Information Change the SYSTEM PDS to point to the new SYSTEM PDS PF 3 out Exit the product Reenter the product Follow instructions under Validation Rename Rename the SYSTEM PDS Rename the new SYSTEM PDS to the name of the original Validation Enter !DB/SMU Select H for Housekeeping Select 4 Display Members of the System PDS. On this display you can determine how many database members remain in the SYSTEM PDS and how many SCAN/SPACEMAP members remain for a given database. 4.0 CUSTOMIZATION INSTRUCTIONS This APAR fix does not affect customization. 5.0 CORRECTIONS TO DOCUMENTATION The following sections describe corrections to documentation after the book was published. The !DB/SMU Check/FIX function is not currently documented in the manuals. Section <7. Run the check/fix program> above describes how to run the program. This program provides facilities for managing the SYSTEM PDS. Over a period of time, the !DB/SMU SYSTEM PDS can become quite large if frequent SCANs or SPACEMAPs are run against all databases. The Check/Fix program can be used to manage the size of the SYSTEM PDS. In Housekeeping, by using option 0 Profile Data Administration and option 4 Configuration Information, you can set the value for Max Reports. By reducing this number, fewer report members will be kept for each database. However, this number only takes affect at the next SCAN, at which time older members beyond this threshhold are purged. Data members for objects that are no longer being scanned are not affected by changing the Max Reports value. By running @SMCKFX and setting the purge date (PDATE PARM value) members created prior to the PDATE will be purged. 6.0 HOW TO GET HELP For a complete and up-to-date source of DB2 Tools information, including information on issues discovered after this README was published, go to the following Web site: !DB/SMU Online Support: http://www.ibm.com/software/data/db2imstools/support.html !DB/SMU manuals can be downloaded from http://www-306.ibm.com/software/data/db2imstools/db2tools-library.html If you are not able to find your answer searching the listed URL, call 1-800-IBM-SERV to speak to an IBM representative for assistance. 7.0 NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the a pplication programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. 7.1 Use of Evaluation Program If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement terms that apply to the use of evaluation code. 7.2 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries or both: DB2 IBM iSeries z/OS zSeries IBM DB2 !DB/SMU (C) Copyright IBM Corporation 2001, 2002, 2003,2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.