Transcription
IBM IMS Library Integrity Utilities for z/OSVersion 2 Release 2User's GuideIBMSC19-3979-05
IBM IMS Library Integrity Utilities for z/OSVersion 2 Release 2User's GuideIBMSC19-3979-05
Note:Before using this information and the product it supports, read the "Notices" topic at the end of this information.Sixth Edition (August 2019)This edition applies to Version 2 Release 2 of IBM IMS Library Integrity Utilities for z/OS (program number5655-U08) and to all subsequent releases and modifications until otherwise indicated in new editions.This edition replaces SC19-3979-04. Copyright IBM Corporation 2003, 2015; Copyright Rocket Software Inc., 2015, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.
ContentsAbout this information . . . . . . . . viiChapter 1. IMS Library Integrity Utilitiesoverview . . . . . . . . . . . . . . 1What's new in IMS Library Integrity Utilities . .IMS Library Integrity Utilities terminology . . .What does IMS Library Integrity Utilities do? . .IMS Library Integrity Utilities solutions . . . .Functional enhancements in IMS Library IntegrityUtilities Version 2 . . . . . . . . . . .Functional enhancements in Version 2 Release 2Functional enhancements in Version 2 Release 1Service updates and support information . . .Product documentation and updates . . . . .Accessibility features for IMS Library IntegrityUtilities. . . . . . . . . . . . . . . 2. 7. 9. 15. 171719. 22. 23. 25Chapter 2. Configuring IMS LibraryIntegrity Utilities . . . . . . . . . . 27Hardware and software prerequisites . . . . .Configuring for initial installation . . . . . .Setting up security for Consistency Checker andMultiple Resource Checker . . . . . . .Migration procedures . . . . . . . . . .Migrating Integrity Checker . . . . . . .Migrating Advanced ACBGEN . . . . . . 28. 29.29303035Chapter 3. Integrity Checker utility . . . 37Integrity Checker overview . . . . . . . . .Planning for Integrity Checker configuration . . .LIU load module library customization . . . .LICON data sets and global option modules . .Integrity Checker configuration requirements . .Runtime options and environments . . . . .Historical data maintained in LICON data setsConsiderations for activating Integrity CheckerActivating Integrity Checker . . . . . . . . .Setting up the global option modules . . . . .Setting up the LICON data sets. . . . . . .Setting up RACF security. . . . . . . . .Customizing LIU load modules. . . . . . .Configuring for a BPE-based DBRC environmentVerifying that Integrity Checker is activated . .Restarting IMS online and running IMS batchapplication, IMS utility, and IMS Tools jobs . . .Maintaining Integrity Checker . . . . . . . .Maintaining RDEs . . . . . . . . . . .Maintaining global option modules . . . . .Maintaining LICON data sets . . . . . . .Restarting Integrity Checker after an abend. . .Applying PTFs to IMS Library Integrity Utilitiesand to IMS . . . . . . . . . . . . .Preventing database corruption with IntegrityChecker . . . . . . . . . . . . . . trictions: Cases where DMB verification is notdone. . . . . . . . . . . . . . . . 81DMB mismatch in IMS online environment orapplication jobs . . . . . . . . . . . . 82DMB mismatch during database maintenanceand operation . . . . . . . . . . . . 85Addressing a DMB mismatch . . . . . . . 86Deactivating Integrity Checker . . . . . . . . 88Deactivating Integrity Checker when IMS LibraryIntegrity Checker is installed as a stand-aloneproduct. . . . . . . . . . . . . . . 88Deactivating Integrity Checker when IMS LibraryIntegrity Utilities is installed as a component ofan IMS tools solution pack . . . . . . . . 89Output from Integrity Checker . . . . . . . . 91FABLPRNT data set . . . . . . . . . . 91FABLSNAP data set . . . . . . . . . . 92Global option module generation macro . . . . . 93Creating global option modules . . . . . . 93JCL requirements for the FABLPGEN program . 94LICON utility reference . . . . . . . . . . 100JCL requirements for the LICON utility . . . 100Input for the LICON utility. . . . . . . . 102INIT.DB command . . . . . . . . . . 103INIT.LICON command . . . . . . . . . 108CHANGE.DB command . . . . . . . . . 108DELETE.DB command . . . . . . . . . 112EXPIRE.DB command . . . . . . . . . 114LIST.DB command. . . . . . . . . . . 115LIST.LICON command . . . . . . . . . 116RECOVER.DB command . . . . . . . . 117VERIFY.DB command . . . . . . . . . 118Output from the LICON utility . . . . . . 120Chapter 4. Consistency Checker utility 127Consistency Checker utility overview . . . . .Restriction for Consistency Checker . . . . . .Checking the consistency of definitions . . . . .JCL requirements for the Consistency Checkerutility . . . . . . . . . . . . . . . .Control statements for the Consistency Checkerutility . . . . . . . . . . . . . . . .JCL examples for the Consistency Checker utilityExample: Checking the consistency of DBDs . .Example: Checking the consistency of PSBs . .Example: Checking the consistency of DBDs andPSBs . . . . . . . . . . . . . . .Output from the Consistency Checker utility . . .SYSOUT data set . . . . . . . . . . .SYSPRINT data set . . . . . . . . . .128131132133136139139140141142142142Chapter 5. Multiple Resource Checkerutility . . . . . . . . . . . . . . . 159Multiple Resource Checker utility overview . 160iii
Checking consistencies with the Multiple ResourceChecker utility . . . . . . . . . . . . .Checking the consistency of multiple resourcesChecking the consistency of multiple sets ofRECON data sets . . . . . . . . . . .Checking the consistency across two resourcetypes . . . . . . . . . . . . . . .Checking the consistency of same resource-typemembers in multiple libraries . . . . . . .JCL requirements for the Multiple ResourceChecker utility . . . . . . . . . . . . .Control statements for the Multiple ResourceChecker utility . . . . . . . . . . . . .Fields compared in RECON data sets . . . . .JCL examples for the Multiple Resource CheckerExamples: Checking the consistency of multipleresources . . . . . . . . . . . . . .Example: Comparing the database definitionsacross multiple sets of RECON data sets . . .Output from the Multiple Resource Checker utilityFABWOUT data set . . . . . . . . . .FABWSUMM data set . . . . . . . . .FABWRRPT data set . . . . . . . . . ter 6. DBD/PSB/ACB Compareutility . . . . . . . . . . . . . . . 203DBD/PSB/ACB Compare utility overview . . .Restrictions and considerations for theDBD/PSB/ACB Compare utility . . . . . . .Comparing IMS control blocks . . . . . . .JCL requirements for the DBD/PSB/ACB Compareutility . . . . . . . . . . . . . . . .Control statements for the DBD/PSB/ACBCompare utility. . . . . . . . . . . . .DBD, PSB, ACB control statements . . . . .REPORT control statement . . . . . . . .NOCOMP control statement . . . . . . .JCL examples for the DBD/PSB/ACB Compareutility . . . . . . . . . . . . . . . .Example: Comparing two DBDs . . . . . .Example: Comparing two DBDs that havedifferent names. . . . . . . . . . . .Example: Comparing a DBD with a DBD-typeACB . . . . . . . . . . . . . . .Example: Comparing two PSBs . . . . . .Example: Comparing a PSB with a PSB-typeACB . . . . . . . . . . . . . . .Example: Comparing two ACBs . . . . . .Example: Comparing ACBs with DBDs andPSBs . . . . . . . . . . . . . . .Example: Comparing DBDs, PSBs, and ACBsOutput from the DBD/PSB/ACB Compare utilitySYSOUT data set . . . . . . . . . . .SYSPRINT data set . . . . . . . . . 30231231231Chapter 7. DBD/PSB/ACB Mapperutility . . . . . . . . . . . . . . . 247DBD/PSB/ACB Mapper utility overview . . . . 248Restrictions for the DBD/PSB/ACB Mapper utility 250Printing hierarchical structure of databases . . . 251ivIMS Library Integrity Utilities User's GuideJCL requirements for the DBD/PSB/ACB Mapperutility . . . . . . . . . . . . . . . .Control statements for the DBD/PSB/ACB Mapperutility . . . . . . . . . . . . . . . .JCL examples for the DBD/PSB/ACB Mapperutility . . . . . . . . . . . . . . . .Example: Generating DBD maps . . . . . .Example: Generating PSB maps . . . . . .Example: Generating ACB maps . . . . . .Example: Generating DBD, PSB, ACB maps . .Example: Creating a DBD and generating aDBD map . . . . . . . . . . . . .Example: Creating a PSB and generating a PSBmap . . . . . . . . . . . . . . .Output from the DBD/PSB/ACB Mapper utilitySYSOUT data set . . . . . . . . . . .SYSPRINT data set . . . . . . . . . .252254257257258259260261262263263263Chapter 8. DBD/PSB/ACB Reversalutility . . . . . . . . . . . . . . . 283DBD/PSB/ACB Reversal utility overview . . . .Restrictions for the DBD/PSB/ACB Reversal utilityConverting IMS control blocks to controlstatements . . . . . . . . . . . . . .JCL requirements for the DBD/PSB/ACB Reversalutility . . . . . . . . . . . . . . . .Control statements for the DBD/PSB/ACBReversal utility . . . . . . . . . . . . .JCL examples for the DBD/PSB/ACB Reversalutility . . . . . . . . . . . . . . . .Example: Re-creating the sources from DBDsand PSBs . . . . . . . . . . . . . .Example: Re-creating the sources from ACBsExample: Obtaining DBD library informationExample: Obtaining PSB library information . .Example: Obtaining control statement sourceand Mapper input . . . . . . . . . . .Output from the DBD/PSB/ACB Reversal utilitySYSOUT data set . . . . . . . . . . .SYSPUNCH data set . . . . . . . . . .DBDSRC data set . . . . . . . . . . .PSBSRC data set . . . . . . . . . . .SYSPRINT data set . . . . . . . . . .MAPOUT data set. . . . . . . . . . .OPTPRT data set . . . . . . . . . . .DBD/PSB/ACB Reversal Site Default Generationutility . . . . . . . . . . . . . . . .Reversal Site Default Generation utilityoverview . . . . . . . . . . . . . .Setting site default values for theDBD/PSB/ACB Reversal utility . . . . . .JCL requirements for the Reversal Site DefaultGeneration utility . . . . . . . . . . .Control statements for the Reversal Site DefaultGeneration utility . . . . . . . . . . .Output from the DBD/PSB/ACB Reversal SiteDefault Generation utility . . . . . . . .Chapter 9. MDA Reversal utilityMDA Reversal utility 9312312312329329330330330333334335. . . 337. 338
MDA Reversal utility restrictions . . . . . . .Converting DFSMDA members back into DFSMDAmacros . . . . . . . . . . . . . . .JCL requirements for the MDA Reversal utility . .Control statements for the MDA Reversal utilityJCL examples for the MDA Reversal utility . . .Output from the MDA Reversal utility . . . . .FABXMSRC data set . . . . . . . . . .MDASRC data set . . . . . . . . . . .FABXMOUT data set . . . . . . . . . .FABXMRPT data set . . . . . . . . . .Chapter 10. Catalog Manager utility340341342344347348348351352352355Catalog Manager utility overview . . . . . .Catalog Manager utility restrictions . . . . . .Validating IMS control blocks in the IMS catalogComparing IMS control blocks . . . . . . .Converting IMS control blocks to controlstatements . . . . . . . . . . . . . .JCL requirements for the Catalog Manager utilityControl statements for the Catalog Manager utilityControl statements for the validate function . .Control statements for the compare function . .Control statements for the convert function . .JCL examples for the Catalog Manager utility . .Example: Validating DBDs and PSBs . . . .Example: Comparing IMS control blocks . . .Example: Converting IMS control blocks tocontrol statements . . . . . . . . . . .Output from the Catalog Manager utility . . . .Output from the validate function . . . . .Output from the compare function . . . . .Output from the convert function . . . . 91396Chapter 11. Advanced ApplicationControl Block Generator utility . . . . 401Advanced ACBGEN utility overview . . . .Generating application control blocks . . . .Merging Advanced ACBGEN load modules intothe IMS SDFSRESL library . . . . . . . .Using the Advanced ACBGEN utility in an ACBGeneration and Catalog Populate utility job . .JCL requirements for the Advanced ACBGENutility . . . . . . . . . . . . . . .Control statements for the Advanced ACBGENutility . . . . . . . . . . . . . . .SYSIN control statements . . . . . . .ACBSYSIN control statements . . . . . .Output from the Advanced ACBGEN utility . .SYSPRINT data set . . . . . . . . .DFSPRINT data set . . . . . . . . .MVS console and the JES job listing . . . . 402. 403. 404. 406. 407.411411411415415429429Chapter 12. ACBLIB Analyzer utility431ACBLIB Analyzer utility overview . . .Analyzing ACB libraries . . . . . . .JCL requirements for the ACBLIB AnalyzerACBSYSIN control statements . . . . .Output from the ACBLIB Analyzer utility .Input Specifications report . . . . . 432. 433434. 436. 438. 438. . .utility. . . .Library Information report . . . . . .Library Contents report . . . . . . .Distribution of Member Sizes report . . .Distribution of PSB Workarea Sizes report .Chronological History of ACBGENs reportWarning Messages report . . . . . .439440444444445446Chapter 13. MFS Reversal utility . . . 449MFS Reversal utility overview. . . . . .Restrictions and considerations for the MFSReversal utility . . . . . . . . . . .Converting MFS control blocks to controlstatements . . . . . . . . . . . .JCL requirements for the MFS Reversal utilityControl statements for the MFS Reversal utilityOutput from the MFS Reversal utility . . .SYSOUT data set . . . . . . . . .SYSPRINT data set . . . . . . . .MFSSRCE data set. . . . . . . . .COPYFMT data set . . . . . . . .COPYPRT data set . . . . . . . .Important notes about the generated source . 450. 451.452453455459459459462465466468Chapter 14. MFS Compare utility . . . 471MFS Compare utility overview . . . . . .Considerations for the MFS Compare utility . .Keywords used in comparisons . . . . . .Comparing MFS control blocks . . . . . .JCL requirements for the MFS Compare utility .Control statements for the MFS Compare utilityOutput from the MFS Compare utility . . . .SYSOUT data set . . . . . . . . . .SYSPRINT data set . . . . . . . . .472474475480481483. 485. 485. 485Chapter 15. Troubleshooting . . . . . 489IMS Library Integrity Utilities return codes .Integrity Checker and LICON utility returncodes . . . . . . . . . . . . .Consistency Checker return codes . . .Multiple Resource Checker return codes .DBD/PSB/ACB Compare, Mapper, andReversal return codes. . . . . . . .MDA Reversal return codes . . . . .Catalog Manager return codes . . . . .Advanced ACB Generator return codes. .MFS Reversal return codes . . . . . .MFS Compare return codes. . . . . .IMS Library Integrity Utilities return codesunder IMS Administration Tool . . . .IMS Library Integrity Utilities abend codes .Integrity Checker abend codes. . . . .Consistency Checker abend codes . . .Multiple Resource Checker abend codes .DBD/PSB/ACB Compare abend codes . .DBD/PSB/ACB Mapper abend codes . .DBD/PSB/ACB Reversal abend codes . .MFS Reversal abend codes . . . . . .IMS messages . . . . . . . . . . .IMS Library Integrity Utilities messages . .FABL messages . . . . . . . . . . 490. 490. 490. 497498499Contentsv
FABM messages . . . . . . . .FABN messages . . . . . . . .FABQ messages . . . . . . . .FABV messages . . . . . . . .FABW messages . . . . . . . .FABX messages. . . . . . . . .How to look up message explanations . .Gathering diagnostic information . . . .Diagnostics Aid . . . . . . . . .How to run Diagnostics Aid with JCL .Load Module/Macro APAR Status reportviIMS Library Integrity Utilities User's Guide.529534547557563566579580581581582Diagnostic Aid messages and codes . 583Chapter 16. References . . . . . . . 587Device and feature code tablesSample library members. . .How to read syntax diagrams . 588. 590. 592Notices . . . . . . . . . . . . . . 595Index . . . . . . . . . . . . . . . 599
About this informationIBM IMS Library Integrity Utilities for z/OS (also referred to as IMS LibraryIntegrity Utilities or IMS LIU) is a tool that helps you in managing data for thelibraries, such as the DBD libraries, PSB libraries, ACB libraries, and RECON datasets that you use when referring to the IMS database.These topics are designed for system programmers, application programmers,system analysts, database administrators, and computer operators perform thesetasks:v Understand the functions and utilities of IMS Library Integrity Utilitiesv Run and use IMS Library Integrity Utilities after it is installedv Interpret IMS Library Integrity Utilities reportsv Diagnose and recover from IMS Library Integrity Utilities problemsTo use these topics, you should have a working knowledge of:v The z/OS operating systemv ISPFv SMP/EAlways refer to the IMS Tools Product Documentation web page for completeproduct documentation id swg27020942The IMS Tools Product Documentation web page includes:v Links to IBM Knowledge Center for the user guides ("HTML")v PDF versions of the user guides ("PDF")v Program Directories for IMS Tools productsv Recent updates to the user guides, referred to as "Tech docs" ("See updates tothis information!")v Technical notes from IBM Software Support, referred to as "Tech notes"v White papers that describe product business scenarios and solutionsvii
viiiIMS Library Integrity Utilities User's Guide
Chapter 1. IMS Library Integrity Utilities overviewIBM IMS Library Integrity Utilities for z/OS (also referred to as IMS LibraryIntegrity Utilities or IMS LIU) aids you in managing data for the libraries, such asDBD libraries, PSB libraries, ACB libraries, RECON data sets, IMS catalog, IMSdirectory, and libraries containing DFSMDA members that you use when referringto IMS databases.Topics:v “What's new in IMS Library Integrity Utilities” on page 2v “IMS Library Integrity Utilities terminology” on page 7v “What does IMS Library Integrity Utilities do?” on page 9v “IMS Library Integrity Utilities solutions” on page 15v “Functional enhancements in IMS Library Integrity Utilities Version 2” on page17v “Service updates and support information” on page 22v “Product documentation and updates” on page 23v “Accessibility features for IMS Library Integrity Utilities” on page 251
What's new in IMS Library Integrity UtilitiesThis topic summarizes the technical changes for this edition.New and changed information is indicated by a vertical bar ( ) to the left of achange. Editorial changes that have no technical significance are not noted. SC19-3979-05 (August 2019) Catalog Manager utilityv The utility has been enhanced to support BMP regions (APAR PH04670).For more information, see “DD statements” on page 366.v The function to validate IMS control blocks in the IMS catalog and theIMS directory has been enhanced to support the IMS directory stagingdata set (APAR PH09134). By this enhancement, the algorithm forvalidating the time stamps of ACBs in the ACB libraries and in the IMSdirectory and instances in the IMS catalog database has changed. Also,the format of the IMS Catalog Validation report has been changed. For more information, see the following topics: – “Catalog Manager utility overview” on page 356 – “Output from the validate function” on page 384SC19-3979-04 (October 2018) MDA Reversal utilityA new utility, MDA Reversal, is added. The utility converts DFSMDAmembers to DFSMDA macros (APAR PI98748). The utility can alsogenerate a report that lists information about all the DFSMDA membersfound in libraries that you specify. For more information, see Chapter 9,“MDA Reversal utility,” on page 337.Catalog Manager utilityThe utility supports the following new functions (APAR PI95272).v Compare IMS control blocks in the IMS directory with those in ACBlibraries, DBD libraries, or PSB libraries.v Convert ACBs in the IMS directory into IMS DBDGEN controlstatements or into IMS PSBGEN control statements.The utility has also been enhanced to compare IMS control blocks in theIMS directory (APAR PH00141).For more information, see Chapter 10, “Catalog Manager utility,” on page355.SC19-3979-03 (September 2017)DBD/PSB/ACB Compare utilityv The utility supports a new parameter, METADATA, for the NOCOMPstatement (APAR PI67745). This parameter indicates that the metadatafields in DBD, PSB, or ACB are not compared. The behavior of thisparameter is the same as NOCOMP CATALOG. For more information,see “NOCOMP control statement” on page 217.v The utility supports new parameters for the NOCOMP statement (APARPI71280). The new parameters are LANG, LIST, PROCOPT, PROCSEQ,PROCSEQD, PSB ACCESS, and PSB PSELOPT. For more information,see “NOCOMP control statement” on page 217.2IMS Library Integrity Utilities User's Guide
IMS Administration Tool supportIMS Library Integrity Utilities extends the functions of IBM IMSAdministration Tool for z/OS (APAR PI67745). If IMS Library IntegrityUtilities is configured for IMS Administration Tool, IMS Library IntegrityUtilities enables the following functions of IMS Administration Tool:v View IMS databases (DBDs) and program views (PSBs) of Database andApplication administrationv IMS Catalog Managementv Program View of IMS SPUFIFor more information, see the IMS Administration Tool User's Guide andReference.Explanations of return codes and messages that you might receive usingIMS Library Integrity Utilities under IMS Administration Tool are providedin Chapter 15, “Troubleshooting,” on page 489.SC19-3979-02 (March 2016)DBD/PSB/ACB Compare utilityThe utility supports a new control statement, CTLSTMT. Use this controlstatement to echo the SYSIN control statements and selected runtimeoptions to the SYSPRINT data set (APAR PI35148). For more information,see “Control statements for the DBD/PSB/ACB Compare utility” on page211.DBD/PSB/ACB Mapper utilityThe utility prints the version of IMS that was used to generate the controlblock in the SYSPRINT data set (APAR PI33159). For more information, seethe reports in “SYSPRINT data set” on page 263.DBD/PSB/ACB Reversal utilityv The following new control statements are supported (APAR PI47105):– ACB REFENRECED option to decode DBD-type ACBs that are notreferenced by any PSB-type ACBs.– PGM COBOL option to set LANG COBOL instead of LANG ASSEMin the decoded PSB source.– DECOPT PCB LABEL option to print the PCBNAME in the labelinstead of printing the PCBNAME parameter in the decoded PSBsource.– DECOPT SENSEG PROCOPT option to always print the SENSEGPROCOPT value in the decoded PSB source.This APAR also adds a new function control statement, UNREF ACB.Use this control statement to generate the Unreferenced ACB(DBD)report in the SYSPRINT data set.For more information, see the following topics:– “Control statements for the DBD/PSB/ACB Reversal utility” on page292– “Unreferenced ACB(DBD) report” on page 327v LISTLIB DBD and LISTLIB PSB control statements generate DBD andPSB library member list reports in the SYSPRINT data set (APARPI53117). The report contains information about the members in the datasets that are concatenated to DBDLIB DD or PSBLIB DD. For moreinformation, see the following topics:Chapter 1. IMS Library Integrity Utilities overview3
– “Control statements for the DBD/PSB/ACB Reversal utility” on page292– “Library member list report for DBD or PSB” on page 327Catalog Manager utilityThe utility provides the function to check the time stamp of DBD-typeACB and PSB-type ACB members in the IMS catalog directory (APARPI36550). For more information, see “Catalog Manager utility overview” onpage 356.DBD/PSB Map ViewerThe following capabilities have been added to the DBD/PSB Map Viewerfor Management Console (APAR PI50732):v Viewing program specifications, PSB source, and PSB XML documentv Listing logical DBDs and PSBs that refer to a specific DBDSC19-3979-01Integrity Checker utilityInstructions to maintain RDEs for HALDBs and DEDBs during an onlinedatabase change were added. For more information, see the followingtopics:v “Considerations for activating Integrity Checker” on page 52v “Altering the definition of a DMB verification-enabled online HALDB byusing the HALDB alter function” on page 74v “Altering the definition of a DMB verification-enabled online DEDB byusing the DEDB Alter utility (DBFUDA00)” on page 75Multiple Resource Checker utilityThe utility supports a new option that you can use when you comparemultiple sets of RECON data sets. When you use this option, you cancompare only the database definitions in RECON data sets or bothdatabase definitions and recovery environment definitions in RECON datasets (APAR PI12851). The following topics were added or updated tosupport this enhancement:v “Multiple Resource Checker utility overview” on page 160v “Checking the consistency of multiple sets of RECON data sets” on page166v “JCL requirements for the Multiple Resource Checker utility” on page175v “Control statements for the Multiple Resource Checker utility” on page178v “Fields compared in RECON data sets” on page 181v “FABWSUMM data set” on page 193v “FABWRRPT data set” on page 197DBD/PSB/ACB Compare utilityv The utility supports new parameters for the NOCOMP statement. Thenew parameters are the AREA, RMNAME, COMPRTN, PCBNAME, andKEYLEN parameters (APAR PI21707). The following topics wereupdated to support this enhancement:– “Restrictions and considerations for the DBD/PSB/ACB Compareutility” on page 2064IMS Library Integrity Utilities User's Guide
– “Control statements for the DBD/PSB/ACB Compare utility” on page211v The utility can generate source-level compare reports even when nodifference is found (APAR PI18270). The following topics were added orupdated to support this enhancement:– “DBD/PSB/ACB Compare utility overview” on page 204– “Restrictions and considerations for the DBD/PSB/ACB Compareutility” on page 206– “Control statements for the DBD/PSB/ACB Compare utility” on page211DBD/PSB/ACB Reversal utilityv The utility prints the following information with the converted IMSDBDGEN or IMS PSBGEN utility control statements in the SYSPUNCHdata set (APAR PI21708):– The date and time when the DBD, PSB, or ACB control block wasconverted to IMS DBDGEN or IMS PSBGEN utility control statements– The version of IMS that was used to create the control blockThe report examples were updated in “SYSPUNCH data set” on page309.v The utility supports a new keyword, POPTREF, for defining criteria toidentify and report on specific PSBs (APAR PI17798). The followingtopics were added or updated to support this enhancement:– “DBD/PSB/ACB Reversal utility overview” on page 284– “Control statements for the DBD/PSB/ACB Reversal utility” on page292– “PSB PROCOPT reference reports for PSB and ACB(PSB)” on page326Catalog Manager utilityThe new Catalog Manager utility can help you ensure that DBDs and PSBsin the IMS catalog match the DBD and PSB members in the ACB libraries(APAR PI21200). For more information, see Chapter 10, “Catalog Managerutility,” on page 355.ACBLIB Analyzer utilityThe utility supports a new operand, GENDATE, for the LISTLIB command.This operand specifies to print the date and time when the ACB memberswere generated in the Library Contents report (APAR PI09309). Thefollowing topics were added or updated to support this enhancement:v “JCL requirements for the ACBLIB Analyzer utility” on page 434v “ACBSYSIN control statements” on page 436v “Output from the ACBLIB Analyzer utility” on page 438v “Library Contents report” on page 440Also see “Functional enhancements in Version 2 Release 2” on page 17 for moreinformation about these enhancements.SC19-3979-00Integrity Checker utilityInstructions to activate Integrity Checker are revised. To activate IntegrityChecker, follow the instructions from “Planning for Integrity Checkerconfiguration” on page 41.Chapter 1. IMS Library Integrity Utilities overview5
Multiple Resource Checker utilityA new utility, Multiple Resource Checker, is added. You can use this utilityto check the consistency of DBD and PSB definitions in the RECON datasets, DBD, PSB, and ACB libraries and to report differences betweenRECON data sets. See Chapter 5, “Multiple Resource Checker utility,” onpage 159.DBD/PSB/ACB Compare utilityDBD/PSB/ACB Compare can generate a source-level compare report forACBLIB members that are generated by different IMS releases. For moreinformation, see Chapter 6, “DBD/PSB/ACB Compare utility,” on page203.OthersSupports the DBD Map Viewer, which is the IMS Library Integrity Utilitiesextension for Management Console and Tools Base AdministrationConsole, to view the graphical visualization of a database structure map,the DBD macro source, and the DBD XML document. For moreinformation, see “Functional enhancements in Version 2 Release 2” on page17.6IMS Library Integrity Utilities User's Guide
IMS Library Integrity Utilities terminologyIMS Library Integrity Utilities information includes several unique terms that youneed to understand before you begin to use IMS Library Integrity Utilities.To make this information easier to read, the version and release levels of IMS areabbreviated, as follows:v IMS Version 14 refers to IMS Version 14 Release 1 and IBM IMS Database ValueUnit Edition Version 14 Release 1.v IMS Version 15 refers to IMS Version 15 Release 1 and IBM IMS Database ValueUnit Edition Version 15 Release 1.The various versions of IMS are referred to simply as IMS, except wheredistinctions among them must be made.The following table summarizes the terminology used in this information.Table 1. IMS Library Integrity Utilities terminologyAcronymMeaningACBApplication control blockBPEBase Primitive EnvironmentDBDDatabase descriptionDBRCIMS Database Recovery Control facilityDIFDevice input formatDOFD
Deactivating Integrity Checker . . 88 Deactivating Integrity Checker when IMS Library Integrity Checker is installed as a stand-alone pr oduct . . 88 Deactivating Integrity Checker when IMS Library Integrity Utilities is installed as a component of an IMS tools solution pack . . 89 Output fr om Integrity Checker . . 91
