publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/itaafdfsm/sc27-2347-01/en_us/p… ·...

IBM Tivoli Advanced Audit for DFSMShsm

User's GuideVersion 2 Release 3

SC27-2347-01

��

Note:Before using this information and the product it supports, read the information in Chapter 14, “Notices,” on page 145.

This edition applies to Version 2 Release 3 Modification 0 of IBM Tivoli Advanced Audit for DFSMShsm (productnumber 5698-B12) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright Rocket Software Inc., 2007-2010

Contents

About this information . . . . . . . . . . . . . . . . . . . . . viiWho should read this book . . . . . . . . . . . . . . . . . . . . viiService updates and support information . . . . . . . . . . . . . . . viiHow to look up message explanations . . . . . . . . . . . . . . . . vii

Searching an information center. . . . . . . . . . . . . . . . . . viiUsing a Web search . . . . . . . . . . . . . . . . . . . . . . viiiUsing LookAt . . . . . . . . . . . . . . . . . . . . . . . . viii

How to send your comments . . . . . . . . . . . . . . . . . . . . viii

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Introduction to Advanced Audit for DFSMShsm . . . . . . . . 1What does Advanced Audit for DFSMShsm do? . . . . . . . . . . . . . 1Advanced Audit for DFSMShsm components . . . . . . . . . . . . . . 1Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . 2Accessibility features . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Advanced Audit for DFSMShsm Configuration . . . . . . . . 3Configuration Summary . . . . . . . . . . . . . . . . . . . . . . 3Step 1: Run AKDCRRUN . . . . . . . . . . . . . . . . . . . . . 3Step 2: Run AKDINIMG . . . . . . . . . . . . . . . . . . . . . . 4Step 3: Update AKDINI . . . . . . . . . . . . . . . . . . . . . . 4Step 4: Customize PARMLIB member AKDCMD00 . . . . . . . . . . . . 4Step 5: Run AKDJCLBD . . . . . . . . . . . . . . . . . . . . . . 5Step 6: Run AKDSYMBL. . . . . . . . . . . . . . . . . . . . . . 5Step 7: Run AKDPLANS . . . . . . . . . . . . . . . . . . . . . . 5Step 8: Run AKDGLOBA. . . . . . . . . . . . . . . . . . . . . . 5Step 9: Modify Product JCL Library Members . . . . . . . . . . . . . . 5Step 10: Modify Product SAKDCLST Library . . . . . . . . . . . . . . 6Step 11: Create User JOB Card Member . . . . . . . . . . . . . . . . 6Step 12: APF Authorize SAKDLOAD Library . . . . . . . . . . . . . . 7Step 13: Start the AKDJMAIN started task . . . . . . . . . . . . . . . 7Step 14: Add AKD07735 to the Authorized Programs List . . . . . . . . . . 7Step 15: Ensure RACF ALTER Authority for User ID . . . . . . . . . . . 7Step 16: Define OMVS segment for the started task . . . . . . . . . . . 7Step 17: Configure the Display of EBCDIC Characters . . . . . . . . . . . 8AKDCMD00 configuration values. . . . . . . . . . . . . . . . . . . 8AKDCMD00 keyword syntax and descriptions . . . . . . . . . . . . . . 9

About cross-system communications . . . . . . . . . . . . . . . . 13AKDCMD00 cross-system communication keyword syntax and descriptions 14

Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . 17About the Interface . . . . . . . . . . . . . . . . . . . . . . . 17

Starting the Advanced Audit for DFSMShsm Interface . . . . . . . . . 17The Advanced Audit for DFSMShsm Main Menu . . . . . . . . . . . 17Viewing Messages . . . . . . . . . . . . . . . . . . . . . . 18Exiting Advanced Audit for DFSMShsm . . . . . . . . . . . . . . . 18

Filtering Pattern Masks . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 4. Performing an Audit . . . . . . . . . . . . . . . . . . 21The Advanced Audit for DFSMShsm panel. . . . . . . . . . . . . . . 21

iii

||

||

||

||

||||

||

Running an Audit Procedure . . . . . . . . . . . . . . . . . . . . 21Including and Excluding Catalogs . . . . . . . . . . . . . . . . . 22

Audit Procedures for Control Data Sets . . . . . . . . . . . . . . . . 23AKDAUDAL Audit Procedure . . . . . . . . . . . . . . . . . . . 23AKDAUDBD Audit Procedure. . . . . . . . . . . . . . . . . . . 23AKDAUDCM Audit Procedure . . . . . . . . . . . . . . . . . . 23AKDAUDCT Audit Procedure. . . . . . . . . . . . . . . . . . . 24AKDAUDMD Audit Procedure . . . . . . . . . . . . . . . . . . 24AKDAUDOD Audit Procedure . . . . . . . . . . . . . . . . . . 24AKDAUDRM Audit Procedure . . . . . . . . . . . . . . . . . . 24AKDAUDTP Audit Procedure . . . . . . . . . . . . . . . . . . . 25AKDAUDZR Audit Procedure. . . . . . . . . . . . . . . . . . . 25

Audit Procedures for DFSMShsm-Owned Tapes. . . . . . . . . . . . . 25AKDAUDFD Audit Procedure. . . . . . . . . . . . . . . . . . . 25AKDAUDFL Audit Procedure . . . . . . . . . . . . . . . . . . . 25AKDAUDFT Audit Procedure . . . . . . . . . . . . . . . . . . . 26OPTION Keyword . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5. Gathering HSM Host Information . . . . . . . . . . . . . 29The DFSMShsm Host Reports panel . . . . . . . . . . . . . . . . . 29HSM Host Information report . . . . . . . . . . . . . . . . . . . . 30Control Data Sets report . . . . . . . . . . . . . . . . . . . . . 31HSM CDS Backups report. . . . . . . . . . . . . . . . . . . . . 31Active Allocations report . . . . . . . . . . . . . . . . . . . . . 32Issuing HSM commands . . . . . . . . . . . . . . . . . . . . . 32

Chapter 6. Performing Administrative Tasks . . . . . . . . . . . . . 33The Administrative Tasks panel . . . . . . . . . . . . . . . . . . . 33

The Customization Menu panel . . . . . . . . . . . . . . . . . . 33Testing user access to HSM commands. . . . . . . . . . . . . . . 36Listing PARMLIB data set members . . . . . . . . . . . . . . . . 36Listing PLAN data set members . . . . . . . . . . . . . . . . . 36Listing CNTL data set members. . . . . . . . . . . . . . . . . . 37

Chapter 7. Viewing product information . . . . . . . . . . . . . . . 39Viewing version and release level data . . . . . . . . . . . . . . . . 40Listing data sets used during processing . . . . . . . . . . . . . . . 40Listing data sets allocated to the address space. . . . . . . . . . . . . 41Listing enqueues held by the address space . . . . . . . . . . . . . . 42Displaying address space virtual storage information . . . . . . . . . . . 42Displaying product message documentation . . . . . . . . . . . . . . 43Displaying product work data set information . . . . . . . . . . . . . . 43Displaying a list of system connections . . . . . . . . . . . . . . . . 43

Chapter 8. Correcting Errors . . . . . . . . . . . . . . . . . . . 45Automatic Error Correction . . . . . . . . . . . . . . . . . . . . 45

Error Threshold Monitoring . . . . . . . . . . . . . . . . . . . 46Automatic Error Correction Quick Reference . . . . . . . . . . . . . 47

Analyzing and Correcting Errors Manually . . . . . . . . . . . . . . . 48Browsing Audit Results . . . . . . . . . . . . . . . . . . . . . . 48Modifying Audit Results . . . . . . . . . . . . . . . . . . . . . . 49Using SDSF to Monitor Automatic Fixes. . . . . . . . . . . . . . . . 49

Chapter 9. Messages and Codes for Advanced Audit for DFSMShsm . . . 51Product Error Messages . . . . . . . . . . . . . . . . . . . . . 51Audit Diagnostic Messages . . . . . . . . . . . . . . . . . . . . 73

iv User's Guide

||

||||||

Chapter 10. AKDINI Configuration Values . . . . . . . . . . . . . . 91PRODUCT_INFO . . . . . . . . . . . . . . . . . . . . . . . . 92CUSTOMER_ENVIRON . . . . . . . . . . . . . . . . . . . . . 92AKD_DATASETS . . . . . . . . . . . . . . . . . . . . . . . . 93PRODUCT_DATASETS. . . . . . . . . . . . . . . . . . . . . . 93DEFAULT_ALLOC_PARMS . . . . . . . . . . . . . . . . . . . . 96DEFAULT_JOB_PARMS . . . . . . . . . . . . . . . . . . . . . 96

Chapter 11. Snap Dump Utility . . . . . . . . . . . . . . . . . . 99

Chapter 12. Advanced Audit for DFSMShsm and HSM Equivalents . . . . 101Advanced Audit for DFSMShsm and HSM Audit Equivalents. . . . . . . . 101Advanced Audit for DFSMShsm and HSM Diagnostic Error Equivalents . . . 102

Chapter 13. The Query Language Feature . . . . . . . . . . . . . 131Query Language Guidelines . . . . . . . . . . . . . . . . . . . 131CREATE. . . . . . . . . . . . . . . . . . . . . . . . . . . 132FROM . . . . . . . . . . . . . . . . . . . . . . . . . . . 133FROMKEY . . . . . . . . . . . . . . . . . . . . . . . . . . 133JOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134ORDER BY. . . . . . . . . . . . . . . . . . . . . . . . . . 137SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . 138TOKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . 139USING . . . . . . . . . . . . . . . . . . . . . . . . . . . 140WHERE . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Boolean Operators . . . . . . . . . . . . . . . . . . . . . . 141Extended Boolean Operators . . . . . . . . . . . . . . . . . . 142Argument Literals . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 14. Notices . . . . . . . . . . . . . . . . . . . . . . 145Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 147

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Contents v

vi User's Guide

About this information

This user's guide provides instructions for using IBM® Tivoli® Advanced Audit forDFSMShsm. To use the procedures in this user's guide, you must have alreadyinstalled Advanced Audit using the SMP/E installation process that came with theproduct.

This document provides instructions for installing, configuring, and using IBM TivoliAdvanced Audit for DFSMShsm. This information is designed to help systemadministrators and system programmers perform the following tasks:

v Plan for and install Advanced Audit for DFSMShsm

v Configure Advanced Audit for DFSMShsm

v Use Advanced Audit for DFSMShsm

Who should read this bookThis book is intended for Storage Administrators, System Programmers, andTechnical Managers responsible for maintaining DFSMShsm Control Data Sets andthe associated records within them.

The authors of this book assume that most readers are data processingprofessionals.

Service updates and support informationTo find service updates and support information, including software fix packs, PTFs,Frequently Asked Question (FAQs), technical notes, troubleshooting information,and downloads, refer to the following Web page:

www.ibm.com/software/sysmgmt/products/support/

The IBM Tivoli Advanced Audit for DFSMShsm Library Web page provides currentproduct documentation that you can view, print, and download. To locatepublications with the most up-to-date information, refer to the following Web page:

www.ibm.com/software/tivoli/sw-library/

How to look up message explanationsYou can use any of the following methods to search for messages and codes:

Searching an information centerIn the search box that is located in the top left toolbar of any Eclipse help system,such as the IBM Information Management Software for z/OS® Solutions InformationCenter, enter the number of the message that you want to locate. For example, youcan enter DFS1065A in the search field.

Use the following tips to help you improve your message searches:

v You can search for information on codes by entering the code; for example, enter-327.

v Enter the complete or partial message number. You can use wild cards (* or ?) inthe message number to broaden your search; for example, DFS20??I.

vii

http://www.ibm.com/software/sysmgmt/products/support/

http://www.ibm.com/software/tivoli/sw-library

http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp

http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp

The information center contains the latest message information for all of theinformation management products that are included in the information center.

Using a Web searchYou can use any of the popular search engines that are available on the Web tosearch for message explanations. When you type the specific message number orcode into the search engine, you will be presented with links to the messageinformation in IBM information centers.

Using LookAtLookAt is an online facility that you can use to look up explanations for most of theIBM messages you encounter, as well as for some system abends and codes.Using LookAt to find information is faster than a conventional search because inmost cases LookAt goes directly to the message explanation.

You can use LookAt from the following locations to find IBM message explanationsfor z/OS elements and features, z/VM®, VSE/ESA, and Clusters for AIX® andLinux®:

v The Internet. You can access IBM message explanations directly from the LookAtWeb site at http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/.

v Your z/OS TSO/E host system. You can install code on your z/OS or z/OSesystems to access IBM message explanations, using LookAt from a TSO/Ecommand line (for example, TSO/E prompt, ISPF, or z/OS UNIX® SystemServices running OMVS).

v Your Microsoft® Windows® workstation. You can install code to access IBMmessage explanations on the z/OS Collection (SK3T-4269) using LookAt from aMicrosoft Windows command prompt (also known as the DOS command line).

v Your wireless handheld device. You can use the LookAt Mobile Edition with ahandheld device that has wireless access and an Internet browser (for example,Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera forLinux handheld devices). Link to the LookAt Mobile Edition from the LookAt Website.

You can obtain code to install LookAt on your host system or Microsoft Windowsworkstation from a disk on your z/OS Collection (SK3T-4269) or from the LookAtWeb site (click Download, and select the platform, release, collection, and locationthat suit your needs). More information is available in the LOOKAT.ME filesavailable during the download process.

How to send your commentsYour feedback is important in helping to provide the most accurate and high-qualityinformation. If you have any comments about this book or any other IBM Toolsdocumentation, use either of the following options:

v Use the online reader comment form, which is located at:

www.ibm.com/software/data/rcf/

v Send your comments by e-mail to [email protected]. Be sure to includethe name of the book, the part number of the book, the version of AdvancedAudit and, if applicable, the specific location of the text you are commenting on(for example, a page number or table number).

viii User's Guide

http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/

http://www.ibm.com/software/data/rcf/

Figures

1. Advanced Audit for DFSMShsm Main Menu . . . . . . . . . . . . . . . . . . . . . 182. AKD710—The audit panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 213. The Host Menu panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294. The Administrative Menu panel . . . . . . . . . . . . . . . . . . . . . . . . . 335. The Customization Menu panel . . . . . . . . . . . . . . . . . . . . . . . . . 346. The JCLPARMS panel, 1 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 347. The JCLPARMS panel, 2 of 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 358. The DSNPARMS panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359. The Product Menu panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

10. The Data Sets Being Used by this Product panel . . . . . . . . . . . . . . . . . . . 4011. The Filtering Values for Data Sets Allocated to Address Space panel. . . . . . . . . . . . 4112. The Data Sets Allocated to Address Space panel . . . . . . . . . . . . . . . . . . . 41

ix

||||

||||

x User's Guide

Tables

1. Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32. Filtering Pattern Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193. SAKDCNTL Members Referred to by the SELECTS or SELECTI DD Statement . . . . . . . 474. Additional Records Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . 995. Advanced Audit for DFSMShsm and HSM Audit Equivalent . . . . . . . . . . . . . . . 1016. Advanced Audit for DFSMShsm and HSM Audit Error Equivalents . . . . . . . . . . . . 1037. Boolean Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428. Extended Boolean Operators . . . . . . . . . . . . . . . . . . . . . . . . . . 1429. Argument Literals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

xi

||

xii User's Guide

Chapter 1. Introduction to Advanced Audit for DFSMShsm

These topics introduce you to the functionality that is provided with IBM TivoliAdvanced Audit for DFSMShsm, including its major components and some of thekey benefits of using it.

What does Advanced Audit for DFSMShsm do?IBM Tivoli Advanced Audit for DFSMShsm delivers a set of auditing commands thathelp support the health of the control data sets.

Without fast, accurate, and reliable audits, you risk losing access not only to yourz/OS data, but also all your HSM migrated data. To avoid serious outages, youneed a powerful data interrogation solution that keeps your z/OS environmenttrouble-free with high-speed, accurate, and flexible audits.

Advanced Audit for DFSMShsm helps you keep your z/OS environment trouble-freewith fast, accurate, and flexible audits. With Advanced Audit for DFSMShsm,storage administrators can maintain healthy metadata environments and preventtemporary or permanent loss of data access. Advanced Audit for DFSMShsmprovides extremely fast and accurate audits and diagnostics, as well as automaticcorrective actions to resolve error conditions

Advanced Audit for DFSMShsm provides:

v Non-disruptive audits for the metadata structures in your environment: catalogs,DASD VTOC records, DFSMShsm, and tape management systems.

v Easy-to-use online selection and submission of audits, diagnostic aids, andcorrective actions.

v Easy online viewing of audit results.

v Automatic historical tracking of all audit errors found in the environment.

v Flexibility to create, save, and reuse your own customized diagnostic aids andcorrective actions.

v Complete control over which meta data structures are audited.

v Complete control over which diagnostic aid or corrective action is implementedfor your unique environment.

v Flexibility to edit JCL and corrective action commands to apply fix controlstatements to only the records you want to fix.

v Automatic application of fixes to reported errors.

v Capability to turn ON or OFF individual error correction actions.

v Automatic halting of audits if a high threshold of errors is reported.

v Ability to apply automatic fixes to specific high-level qualifiers.

v Support for both DFSMShsm standard TTOC and extended TTOC.

Advanced Audit for DFSMShsm componentsAdvanced Audit for DFSMShsm consists of two audit components: the auditing ofHSM control data sets and DFSMShsm-owned tapes.

Advanced Audit for DFSMShsm evaluates the migration control data set (MCDS),backup control data set (BCDS), and the offline control data set (OCDS) to helpresolve structural and logical discrepancies that can prevent migrated data from

1

being recalled, or backup data from being restored. It correlates entries with the ICFcatalog environment to help maintain consistency.

Advanced Audit for DFSMShsm helps you audit and correct errors with yourDFSMShsm migration and backup tapes. It works outside of the DFSMShsmenvironment to correct errors that it finds and has customer-documented benchmarkspeeds faster than the traditional DFSMShsm AUDITMEDIACONTROLS command.

PrerequisitesAdvanced Audit for DFSMShsm requires the following software levels.

v z/OS release V1R9, through V1R11

v DFSMShsm running on z/OSMVS/ESA 4.1 or higher

Accessibility featuresAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use a software product successfully.

The major accessibility features in Advanced Audit for DFSMShsm enable users to:

v Use assistive technologies such as screen readers and screen magnifiersoftware. Consult the assistive technology documentation for specific informationwhen using it to access z/OS interfaces.

v Customize display attributes such as color, contrast, and font size.

v Operate specific or equivalent features by using only the keyboard. Refer to thefollowing publications for information about accessing ISPF interfaces:

– z/OS ISPF User's Guide, Volume 1

– z/OS TSO/E Primer

– z/OS TSO/E User's Guide

These guides describe how to use ISPF, including the use of keyboard shortcuts orfunction keys (PF keys), include the default settings for the PF keys, and explainhow to modify their functions.

2 User's Guide

Chapter 2. Advanced Audit for DFSMShsm Configuration

After you install Advanced Audit for DFSMShsm using the installation instructionsprovided in the IBM Tivoli Advanced Audit for DFSMShsm Program Directory, that isincluded with the product, you must configure Advanced Audit for DFSMShsm foryour environment.

Configuration SummaryThe following table summarizes the steps that are required to configure AdvancedAudit for DFSMShsm.

Some of these steps are optional or might not apply to your environment.

Table 1. Configuration Steps

Step Description

1 Run AKDCRRUN.

2 Run AKDINIMG.

3 Update AKDINI.

4 Update AKDCMD00.

5 Run AKDJCLBD.

6 Run AKDSYMBL.

7 Run AKDPLANS.

8 Run AKDGLOBA

9 Modify product SAKDJCL library members.

10 Modify product SAKDCLST library.

11 Create user JOB card member JOBCARD.

12 APF authorize product SAKDLOAD library.

13 Start the AKDJMAIN task.

14 Add AKD07735 to the authorized programs list.

15 Ensure RACF® ALTER authority for user ID.

16 Define an OMVS segment.

17 Configure the display of EBCDIC characters.

Step 1: Run AKDCRRUNAKDCRRUN creates a set of runtime libraries using the target libraries as thesource.

1. Copy the JCL AKDCRRUN from the SAKDJCL target library and place it in apersonal PDS.

2. Modify the parameter TGTHLQ to reflect the high level qualifier of the targetlibraries.

3. Modify the PPFX to reflect the high level qualifer of the runtime libraries that thisjob creates.

4. Submit the job using a valid jobcard.

You can continue with the configuration using these newly created runtime libraries.

3

Step 2: Run AKDINIMGRun the AKDINIMG member of the ppfx.SAKDJCL library to create a new AKDINISAKDPARM member.

AKDINIMG was created by submitting INSTJCL during the install process.

Note: Do not alter the contents of the AKDINI# member.

1. Provide a valid job card statement.

2. Change the STEPLIB data set name to the ppfx.SAKDLOAD library.

3. Change the INI DD statement to point to ppfx.SAKDPARM as the data set nameand specify AKDINI# as the member name. If this is the first time running thisjob, the INI DD statement must point to the AKDINI# as the member name.

4. Change the MSCINI DD statement to point to the ppfx.SAKDPARM data set,and ensure that the member name remains as AKDINI#.

5. Change the UPDATE DD statement to point to the ppfx.SAKDPARM data set,and ensure that the member name remains as AKDINI.

6. Submit the job, and ensure it executes and completes with a completion code 0before proceeding to the next configuration step.

If the job terminates with a non-zero completion code, first check to see if any errormessages indicate a situation that is easily correctable. You can run AKDINIMGmultiple times. If the situation does not appear to be easily correctable, pleasecontact Technical Support before proceeding to the next configuration step.

Step 3: Update AKDINIModify the values in the AKDINI member of the SAKDPARM library, which controlsmany product functions.

1. Use ISPF Edit to update the values. Be sure to review all of the tokens in theAKDINI member and set appropriate values for your installation. Pay particularattention to the RLS token of the CUSTOMER_ENVIRON section.

2. After you have made all your edits, save your updated AKDINI.

Step 4: Customize PARMLIB member AKDCMD00Modify the values in the AKDCMD00 member of the SAKDPARM library.

Important: If you do not plan on running the AKD started task then you can skipthis step. If not running the AKD started task, you can access the onlineISPF audit screens by executing CLIST AKDAUDIT instead ofAKDSTART.

To customize the SAKDPARM member AKDCMD00:

1. Change the data sets listed in the member to point to appropriate AdvancedAudit for DFSMShsm libraries.

2. Change the job card lines to something appropriate for your site.

Note: See ‘AKDCMD00 configuration values’ for a complete list of availableparameters.

4 User's Guide

|

|

||||

|

||

|

||

Step 5: Run AKDJCLBDRun the AKDJCLBD member of the SAKDJCL library to substitute variables codedin the AKDINI into the SAKDJCL members.

1. Modify the AKDJCLBD job as indicated by the comments at the beginning of themember.

2. Be sure that the AKDINI values are set as desired before running AKDJCLBD.You can run AKDJCLBD multiple times.

3. Submit the AKDJCLBD job.

Step 6: Run AKDSYMBLRun the member AKDSYMBL to update the SYMBOLIC member of theppfxx.SAKDCNTL library.

This step retrieves information you have established in AKDINI and inserts it withthe proper format into member SYMBOLIC. Add the proper JOBCARD informationand submit the job.

Step 7: Run AKDPLANSRun the member AKDPLANS of the SAKDJCL library to create a PLANS library.

The PLANS library contains PLANS and FIXES used by Advanced Audit forDFSMShsm.

Step 8: Run AKDGLOBARun the member AKDGLOBA of the SAKDJCL library to allocate a Global SummaryHistory file.

The Global Summary History file contains history records produced by all of thedifferent Audit jobs. The records are kept for a default setting of 999 days. Thisdefault setting can be changed by modifying the KEEP_HISTORY_DAYS = 999parameter in the AKDINI member in the SAKDPARM library.

Step 9: Modify Product JCL Library MembersModify the following ppfx.SAKDJCL library members for your installation.

These jobs are not intended to be submitted directly by you, but are used internallyby Advanced Audit for DFSMShsm processes. Please note that some fields will stillbe blank after you have completed this step. The rest of the JCL will be generatedby the Advanced Audit for DFSMShsm audit process at execution time.

1. Modify the SYSPROC and JCLLIB statements in member AKDBTTSO so thatppfx is the product prefix assigned to Advanced Audit for DFSMShsm by yourinstallation.

2. Change the ZARACAT and the ZARAVLT data set names in memberAKDBTZRA to match the ZARA data sets installed in your system. If yourinstallation does not use ZARA TMS, then ignore this step.

3. Change the SYSPROC statement in member AKDBDTTC of ppfx.SAKDJCL tothe SAKDCLST library as installed. The DSN= and SPACE= statements mustremain blank so when the fix create process is run, these two statements arefilled in with the appropriate parameters.

Chapter 2. Advanced Audit for DFSMShsm Configuration 5

|

|

||

||||

Note: Use of the SMS construct to release unused space after a data set isclosed can cause problems when running Advanced Audit forDFSMShsm fixes. HSM closes and opens the data set specified by ODSin the control statements frequently. This causes space to be releasedwhen it may still be required. It is recommended that you use aMGMTCLAS statement with a class that does not release unused space.

4. Modify member AKDBATCH in the ppfx.SAKDJCL library, to identify the MCDS,BCDS, and OCDS DSNames for your environment. The names of theproduction SAKDLOAD library and SAKDPARM need to be provided as well.This set of JCL is used to verify CDS records and display them in a dumpformat. The Snap Dump utility will also display HSM records and display them ina dump format. If you use multi-cluster CDSs, you must include the names of allthe CDS splits in the AKDBATCH member in the ppfx.SAKDJCL library.

5. Change the AUDIT statement in member AKDTMSBQ, to the CA1 AUDIT dataset name installed in your system. In a typical TMS installation, there is no needto specify the AUDIT DSName. If your installation does not use CA1 TMS, thenignore this step.

6. After running AKDJCLBD, make the following changes to the batch catalogedprocedures AKDAUDxx:

a. Change the JOB control statement to suit your environment.

b. Choose a JOB CLASS that allows about five minutes of processing time (ittakes a while to capture and analyze all of the information in an entireinstallation).

7. Add started task JCL AKDJMAIN to a system PROC Library This JCL can alsobe run as a batch job, but it is recommended that you run as a started task.

Important: If you are not running the AKD started task you can skip substep 7.

Step 10: Modify Product SAKDCLST LibraryModify the ppfx.SAKDCLST library for your installation.

Modify FSTPLB in the AKDMONTR member of the SAKDCLST library with theinstallation’s SAKDLOAD library. Replace the xxxxxxxx.LOAD with the name of theSAKDLOAD library installed for Advanced Audit for DFSMShsm

Important: If you are going to use the started task, then you do not need to makethese changes to AKDAUDIT member.

Modify AKDAUDIT member of the SAKDCLST library.

1. Change HLQ.AKD0203 to your product prefix, the same value you gave toPPFX in the AKDINI member in SAKDPARM library.

2. Change RUNTIME.R23 to your runtime prefix, the same value as you gave toPFX in the AKDINI member in SAKDPARM library.

If you decide not to run the AKD started task, you can access the online ISPF auditscreens by executing clist AKDAUDIT instead of AKDSTART.

Step 11: Create User JOB Card MemberEach person executing corrective actions or diagnostic aids must have a uniquemember in ppfx.SAKDCNTL containing their JOB card information.

6 User's Guide

||

|

|

|

|||

||

|

||

||

||

The unique job card member is referenced on the JOBCARD DD statement as&USERID.J of &ppfx.SAKDCNTL. The member name is based on the TSO userid ofthe user and is suffixed by the letter J (for JOB card). For example, you wouldcreate a job card member DDAVENJ for user ID DDAVEN.

In some environments, security groups are utilized to provide sufficient authority tothe user ID executing programs in batch; others accomplish this with the use of aGROUP parameter on your JOB card. For example, GROUP=ARCCATGP. Toimplement this, your security administrator must add your user ID to the GROUPspecified in the parameter. Using this parameter on the JOB card provides theproper security authority to READ ICF catalogs required for some of the auditprocedures. Although the audit procedure only reads ICF catalogs, ALTER accessmay be required. Security software and procedures vary so consult your securityadministrator for the proper procedures to follow in your environment.

Step 12: APF Authorize SAKDLOAD LibraryThe Advanced Audit for DFSMShsm product SAKDLOAD library requires explicitAPF authorization, even if it appears in the system link list with theLINKAUTH=LNKLST option.

If the contents of the product SAKDLOAD library are copied to another SAKDLOADlibrary, it must be APF authorized. Although SMS managed load libraries can beassigned APF authorization, most installations prefer to have all authorized librariesreside on specific non-SMS system volumes.

Step 13: Start the AKDJMAIN started taskStart task AKDJMAIN on every system on which users will access the onlineAdvanced Audit for DFSMShsm ISPF Panels.

Important: If you decide not to run the AKD started task then you can skip thisstep.

Step 14: Add AKD07735 to the Authorized Programs ListYou must add the program AKD07735 to the AUTHPGM NAMES list ofSYS1.PARMLIB member IKJTSO00.

The program AKD07735 is used by the automatic fix process to interrogate theHSM address space to determine how many commands may be safely submitted atany one time

Step 15: Ensure RACF ALTER Authority for User IDEnsure that your user ID has the appropriate RACF ALTER authority.

Many of the Advanced Audit for DFSMShsm procedures read system catalogs.Although they only read and do not update any catalogs, because of an IBMrequirement, the user submitting the job must have RACF ALTER authority.

Step 16: Define OMVS segment for the started taskTo take advantage of cross system communication between Advanced Audit forDFSMShsm instances that reside on different systems, you must define an OMVSsegment for the started task.


||

|

|||

The started task requires UNIX System Services access. The user ID under whichthe started task runs must have an OMVS segment in its RACF profile. To checkwhether the ID has an OMVS segment in its profile, use the following command:LU userid OMVS

To add an OMVS segment to an ID’s RACF profile, use the following command:ADDUSER ddfuid OMVS(UID(nnn))

Step 17: Configure the Display of EBCDIC CharactersIf the code tables used by your installation are different, then you must enter theEBCDIC character peculiar to your code tables that results in the binary value forthe EBCDIC character specified in the product manuals.

Advanced Audit for DFSMShsm uses the U.S.A. EBCDIC code set for specificationand display of EBCDIC characters and for the extended ACS masking charactersused for filtering.

v Data supplied as input to batch programs

For product code shipped in binary, when specifying input where the producttakes special action based on specific characters, you must enter the EBCDICcharacter peculiar to your code tables that results in the binary value for theEBCDIC character specified in the product manuals, according to the U.S.A.EBCDIC code set.

For example, if an exclamation mark ( ! ) is called for, and your code tables donot translate the ! character to a hexadecimal 5A, you must enter the characterthat your code table will translate to a 5A.

v Product output

Depictions of product output shown in the product manuals are based on theU.S.A. EBCDIC code set. Actual output may vary if your EBCDIC code tables aredifferent.

v Extended ACS masking characters

Your installation may need to specify different masking characters to achieve thedesired result if your code tables are different from the U.S.A. EBCDIC code set.

AKDCMD00 configuration valuesThis section describes the structure of the AKDCMD00 PARMLIB member, itssyntax rules, and its keyword syntax and descriptions.

Important: If you change any of the configuration values in this PARMLIB member,be aware that you must restart AKDJMAIN before the changes take effect.

Syntax rules

Member AKDCMD00 consists of token assignment statements that are organizedby sections. The general format for a token statement is:Keyword = Parameter

orKeyword = (Parameter1, Parameter2, ..., Parametern)

Leading blanks from the beginning of the logical card-image records are allowed forall statements. Syntax scan processing locates the first non-blank character in each

8 User's Guide

|||

|

|

|

|

logical record. The entire length of the 80-byte logical record is considered for validdata. Do not renumber the AKDCMD00 member; sequence numbers assigned incolumns 73 through 80 will cause errors.

Continuation rules

Continuation is assumed to occur whenever data crosses from one line to another,such as when you specify multiple values for the same parameter. An example ofthis situation follows:ParameterKeyword=(value1, value2, value3, value4, value5)

Comments

Both line mode and block mode commenting are supported:

v An asterisk (*) in column-1 marks the entire line as a comment. A line that isentirely blank can also be considered a comment.

v Entire lines, blocks of lines, or portions of a line can be commented by beginningthe comment with a '/*' and terminating the comment with a '*/'.

AKDCMD00 keyword syntax and descriptionsThese are the required and optional keywords for the AKDCMD00 member.

Required parameters

CLIST_DSN

Name(s) of the product library containing CLIST/REXX members.

Default value None

Syntax CLIST_DSN=clist.dsn.name

Acceptable values Specify any valid data set name.

Example CLIST_DSN=AKD.SAKDCLST

CNTL_DSN

Name(s) of the product library containing sample members.

Default value None

Syntax CNTL_DSN=sample.dsn.name


Example CNTL_DSN=AKD.SAKDCNTL

MSGS_DSN

Name(s) of the product library containing the message members.

Default value None

Syntax MSGS_DSN=messages.dsn.name


Example MSGS_DSN=AKD.SAKDMSGS


OPFX

Operational prefix for the audit dataset allocations. Ensure this is the same prefix asused in the PFX parameter in the AKDINI member.

Default value None

Syntax OPFX=hlq1.hlq2

Acceptable values Specify any valid high-level qualifier, 1-13 bytes.

Example OPFX=AKD.WORK

PLANS_DSN

Name(s) of the product library containing PLANS members. This is the datasetname which is created in job AKDPLANS in the SAKDJCL library.

Default value None

Syntax PLANS_DSN=plans.dsn.name


Example PLANS_DSN=AKD.PLANS

PLIB_DSN

Name(s) of the product library containing ISPF panels.

Default value None

Syntax PLIB_DSN=panels.dsn.name


Example PLIB_DSN=AKD.SAKDPENU

PPFX

Product library prefix. Name of the product library prefix.

Default value None

Syntax PPFX=hlq1.hlq2

Acceptable values Specify any valid high-level qualifier.

Example PPFX=AKD0203.AKD

Optional parameters

JOBCARD1

First line to be used when creating JCL.

Default value Not applicable

Syntax JOBCARD1='jobcard data'

Acceptable values 3 to 60 bytes of data delimited by single quote (') marks.

10 User's Guide

Example JOBCARD1='//AKDJOB JOB (Acct),''AKD job'','

JOBCARD2

Second line to be used when creating JCL.




Example JOBCARD2='// MSGCLASS=A,CLASS=B,'

JOBCARD3

Third line to be used when creating JCL.




Example JOBCARD3='// NOTIFY=&SYSUID'

JOBCARD4

Fourth line to be used when creating JCL.




Example JOBCARD4='//*'

JOBCARD5

Fifth line to be used when creating JCL.




Example JOBCARD5='//* '

WORKDC

SMS data class name to be used for file allocations.

Default value None

Syntax WORKDC=dataclas

Acceptable values Any valid SMS data class, 1 – 8 bytes.

Example WORKDC=DC001


WORKMC

SMS management class name to be used for file allocations.

Default value None

Syntax WORKDC=mgmtclas

Acceptable values Any valid SMS management class, 1 – 8 bytes.

Example WORKMC=MC008

WORKPRI

Primary allocation amount to be used for file allocations.

Default value 100

Syntax WORKPRI=number

Acceptable values Any integer in the range 1 – 99999.

Example WORKPRI=50

WORKSEC

Secondary allocation amount to be used for file allocations.

Default value 100

Syntax WORKSEC=number

Acceptable values Any integer in the range 1 – 99999.

Example WORKSEC=10

WORKSC

SMS storage class name to be used for file allocations.

Default value None

Syntax WORKSC=storclas

Acceptable values Any valid SMS storage class, 1 – 8 bytes.

Example WORKSC=SC002

WORKUNIT

UNIT name to be used for file allocations.

Default value SYSALLDA

Syntax WORKUNIT=unitname

Acceptable values Any valid unit name, 1 – 8 bytes.

Example WORKUNIT=AKDUNIT

12 User's Guide

About cross-system communicationsWith this release, Advanced Audit for DFSMShsm can use TCP/IP services tocommunicate with Advanced Audit for DFSMShsm address spaces on multiplesystems, which allows you to coordinate work on multiple systems by retrieving anddistributing information across a multi-system complex.

If you intend to take advantage of cross-system communications, you need tospecify appropriate values for the parameters described in this section. However, ifyou do not intend to use cross-system communications, there is no need to set upthese parameters. If you intend to use the cross-system communication feature, beaware that an OMVS segment must be defined for the Advanced Audit forDFSMShsm address space.

As it is used here, the generic term network is used to define whatever setup youfind convenient. You can include all systems in your network or you can segregatesome of your systems in any way that makes processing easier. In general, anetwork should be set up in such a way that it encompasses an entire DFSMShsmconfiguration. Usually, the control data sets are shared within a SYSPLEX only. Ifthere is more than one SYSPLEX at your site, you can establish a separatenetwork for each DFSMShsm complex.

When control data sets are shared between multiple systems (spanning multipleSYSPLEXes), the network must include all systems that are accessing that set ofcontrol data sets. When control data sets are shared within a SYSPLEX, it isrecommended that you set up a separate network for each SYSPLEX.

AKDCMD00 provides several options to help facilitate network definition. The usageof system symbols is supported within the AKDCMD00 member, in any value. Forexample, if SYSNAME were defined to the name of the local system and the DNStoken for all systems is the system name followed by MYSHOP.COM, only oneLOCALCONN definition is needed in all AKDCMD00 member setups:LOCALCONN=&SYSNAME..MYSHOP.COM.

Two conditional logic statements have been built into the AKDCMD00 member:

v Use the IF_SYSNAME statement to specify a condition based on the localsystem name.

v Use the IF_SYSPLEX statement to specify a condition based on the SYSPLEXname.

Note: You can use masking characters in your specifications for these conditionalstatements.

If a conditional statement is true, any parameters following the statement areaccepted; if a conditional statement is false, any parameters following the statementare ignored.

Consider an example in which the goal is to use one AKDCMD00 member for allsystems, but to specify different parameter values for each SYSPLEX:LOCALCONN=&SYSNAME..IP.ADDRESSIF_SYSPLEX=PRODPLEXCONNECTION=PROD1.IP.ADDRESSCONNECTION=PROD2.IP.ADDRESSIF_SYSPLEX=TESTPLEXCONNECTION=TEST1.IP.ADDRESSCONNECTION=TEST2.IP.ADDRESS

Alternatively, you could use a masking character to specify the SYSNAME:


|

||||

||||||

|||||||

||||

||||||

|

||

||

|||||

||

|||||||

|

IF_SYSNAME=P*CONNECTION=PROD1.IP.ADDRESSCONNECTION=PROD2.IP.ADDRESS

AKDCMD00 cross-system communication keyword syntax anddescriptions

These are the required and optional keywords to enable cross-systemcommunication.

Important: These three parameters, properly set up, are required to successfullysetup cross-system communications:

v PORTNUM

v CONNECTION

v LOCALCONN

CONNECTION

One CONNECTION statement is needed for each system that is to be part of thisnetwork. You also need one for the local system connection.

Default value None

Syntax CONNECTION = <ip address or dns name>

Acceptable values Specify any valid IP address or DNS name.

Example CONNECTION = <ip address or dns name>

LOCALCONN

Local connection IP address or DNS name. This entry should also have acorresponding CONNECTION statement. To use this member for more than onesystem, use the following example to see how to code values for different systems.

Default value None

Syntax LOCALCONN = <ip address or dns name>

Acceptable values Specify any valid IP address or DNS name.

Example IF_SYSNAME = SYSTEM1

LOCALCONN = SYSTEM1.DNS.NAME

IF_SYSNAME = SYSTEM2

LOCALCONN = SYSTEM2.IP.ADDRESS

PORTNUM

Port number to use for the connections. This should be the same number on everysystem.

Default value None

Syntax PORTNUM = 27020

Acceptable values Specify any valid port number.

Example PORTNUM = 27020

14 User's Guide

|||

|

|

||

||

|

|

|

|

||

|||

||

||

|||

|

|||

|||

||

||

||

|

|

||

|

||

|||

||

||

|||

SYSCHKINTVL

System check interval time in seconds.

Default value 15

Syntax SYSCHKINTVL = 15

Acceptable values Specify any valid integer.

Example SYSCHKINTVL = 15

TIMEOUT

Timeout value in minutes for inactive systems.

Default value 60

Syntax TIMEOUT = 60


Example TIMEOUT = 60

USEXSYS

For any cross system processing to be attempted, this parm must be set to YES.

Default value NO

Syntax USEXSYS = YES

Acceptable values Specify YES or NO.

Example USEXSYS = YES

USERWAIT

Wait time in seconds for user requests. If no response is received within this timeinterval, the request is ended early.

Default value 300

Syntax USERWAIT = 300


Example USERWAIT = 300


|

|

|||

||

||

|||

|

|

|||

||

||

|||

|

|

|||

||

||

|||

|

||

|||

||

||

||||

16 User's Guide

Chapter 3. Getting Started

This chapter helps you start using Advanced Audit for DFSMShsm and describesother general topics about its use.

About the InterfaceAdvanced Audit for DFSMShsm provides an ISPF-based interface that allows you toeasily do the following tasks:

v Analyze and correct errors.

v View Advanced Audit for DFSMShsm messages.

v If during installation and configuration you chose to use the AKD started taskthen you get the ability to use the following functions:

– View DFSMShsm tasks which are running.

– View DFSMShsm control dataset information.

– View DFSMShsm control dataset backup information.

– View Advanced Audit for DFSMShsm product information.

Starting the Advanced Audit for DFSMShsm InterfaceThere are two ways to start the Advanced Audit for DFSMShsm interface,depending on whether you chose to use the AKD started task or not.

v If during installation and configuration you chose to use the AKD started task,then you would access the online ISPF interface by doing the following:

Type EX 'ppfx.SAKDCLST(AKDSTART)'

ppfx is the product prefix assigned at installation time. If the AKDSTART CLISThas been copied to a system CLIST library, you can issue %AKDSTART.

v If during installation and configuration you chose not to use the AKD started task,then you would access the online ISPF interface by doing the following:

Type EX 'ppfx.SAKDCLST(AKDAUDIT)'

ppfx is the product prefix assigned at installation time. If the AKDAUDIT CLISThas been copied to a system CLIST library, you can issue %AKDAUDIT.

The Advanced Audit for DFSMShsm Main MenuThis topic describes the options that are available from the Advanced Audit forDFSMShsm Main Menu (MAINMENU) panel.

17

|

||

||

|

||

||

|

||

The valid options are:

1 Auditing–displays a list of the available classic auditing data.

2 HSM Host Information–displays information about the DFSMShsm Hoststhat are actively running on this system.

3 Administrative Tasks–displays a menu of administrative tasks that can beperformed.

4 Product Information–displays a menu of product level information.

These options are described in detail in the following chapters.

Viewing MessagesAdvanced Audit for DFSMShsm allows you to view the error messages and theirhelp.

1. Put the cursor on the HELP pull-down menu at the top of the panel and pressEnter.

2. Select 3. Product Messages.

3. When the message viewing filter panel displays you can:

v enter a specific message number and leave message member blank todisplay a specific message

v leave all filters blank and press Enter to display all messages

Another option to view messages is to browse the product message dataset named'ppfx.SAKDMSGS'.

Exiting Advanced Audit for DFSMShsmTo exit Advanced Audit for DFSMShsm, either type END on the command line orpress PF3 from the Main menu panel.

Filtering Pattern MasksMany commands allow you to specify powerful filtering masks using extended ACSmasking characters, as shown in the following table.

MAINMENU ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 12:07Command ===> Scroll ===> PAGE

Main Menu: Row 1 of 5

Report Name Description

1 Auditing Auditing Data2 HSM Host Information Information on DFSMShsm Hosts3 Administrative Tasks Administrative Functions4 Product Information Product Information

Figure 1. Advanced Audit for DFSMShsm Main Menu

18 User's Guide

Note: Your installation may need to specify different masking characters to achievethe desired result if your code tables are different from the U.S.A. EBCDICcode set.

Table 2. Filtering Pattern Masks

Mask Hex Description

* (Single) 5C Represents 0-n characters.You can specify this wildcardcharacter before an item,after an item, or both todesignate a wildcard position.You can not use an * in themiddle of a single item(except for data set names)Use the % character instead.For example, *PROD willselect an item if the last fourcharacters are PRODregardless of the startingcharacters. Using the *character before and after anitem (for example, *ZREM*)means that item is to beselected if any characterstring matches ZREM in itsname.

% 6C Denotes a single characterplaceholder value, which canbe alpha-numeric or anyspecial character. The %character can be used in anyposition order. For example,CRM%%ER6 will select anitem if it is 8-characters inlength, the first threecharacters are CRM, the lastthree characters are ER6.The two middle placeholdervalues can be anycharacters.

< 4C Denotes a placeholder valuefor only alpha characters.The < character can be usedin any position order. Forexample, CR<<ER* willselect an item if the first twocharacters are CR, the firstand third characters arealpha, the fifth and sixthcharacters are ER, and therest are any remainingcharacters.

Chapter 3. Getting Started 19

Table 2. Filtering Pattern Masks (continued)

Mask Hex Description

> 6E Denotes a placeholder valuefor only numeric characters.The > character can be usedin any position order. Forexample, CR>>ER* willselect an item if the first twocharacters are CR, the thirdand fourth characters arenumeric, the fifth and sixthcharacters are ER, and therest are any remainingcharacter.

** (Double) 5C5C Allows compatibility withstandard ACS andDFSMSdss filtering masks.This mask is used only forpartially qualified data setnames. The * or ** characterscan be used in any qualifierposition to denote a wildcardnode. For example,CRFM*.*VER.** will select adata set entry if it has atleast two qualifiers and thefirst qualifier starts withCRFM, the second qualifiermust end with VER, and anyremaining qualifiers.Note: As with common dataset name masking, anycombination of *, **, %, <and/or > characters can beused for the item mask value.

! 5A Denotes a placeholder valuefor only national characters(based on the U.S.A.EBCDIC code set. The !character can be used in anyposition order. Nationalcharacters, based on theU.S.A. EBCDIC code set,are: @ # $ .

20 User's Guide

Chapter 4. Performing an Audit

This chapter describes how to setup and run the audit procedures provided withAdvanced Audit for DFSMShsm.

The Advanced Audit for DFSMShsm panelWhen you enter option 1 on the MAINMENU panel and press Enter, the audit panelappears:

The options that are available from the Advanced Audit for DFSMShsm (AKD710)panel are:

1 MCDSType 1 to access the audit results from the audit procedures AKDAUDMD,AKDAUDCT, AKDAUDAL.

2 BCDSType 2 to access the audit results from the audit procedure AKDAUDBD.

3 OCDSType 3 to access the audit results from the audit procedure AKDAUDOD.

4 HSMTAPEType 4 to access the audit results from the audit procedures AKDAUDTP,AKDAUDZR, AKDAUDRM, AKDAUDCM.

5 MEDCTLType 5 to access the audit results from the audit procedures AKDAUDFD,AKDAUDFL, AKDAUDFT.

Running an Audit ProcedureThis topic describes the steps for running an audit procedure to obtain audit results.

This procedure assumes you already have a job card member defined for runningthe audit procedures. See “Step 11: Create User JOB Card Member” on page 6 formore information.

AKD710 ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 13:43Command ===> Scroll ===> PAGE

1 MCDS Created by procs AKDAUDMD, AKDAUDCT, AKDAUDAL2 BCDS Created by proc AKDAUDBD3 OCDS Created by proc AKDAUDOD4 HSMTAPE Created by procs AKDAUDTP, AKDAUDZR, AKDAUDRM, AKDAUDCM5 MEDCTL Created by procs AKDAUDFD, AKDAUDFL, AKDAUDFT

Figure 2. AKD710—The audit panel

21

1. Determine which audit procedure you want to run.

2. Display the audit procedure JCL in an edit session.

3. Optionally, update the audit procedure JCL to include or exclude specificcatalogs from the audit.

4. Type SUBMIT to run the audit procedure.

Make sure the audit procedure JCL finished successfully before viewing orcorrecting any auditing errors.

Note:

1. It is suggested that all data sets allocated by the audit procedures rununder SMS control. There are several programs in the audit procedureswhich create a data set, close it, and then another module is linkedwhich looks up the catalog for the data set just created. If the data set isnot cataloged, the system issues a NOT CAT message. Data sets underSMS control must be cataloged upon creation time thus circumventingthis issue.

2. It is best to run the audit procedures during those times of lowest HSMactivity to avoid any possible reporting of erroneous errors.

3. Multi-volume data set allocation is limited to a maximum of 5 volumes.The maximum 5 volume limit is enforced to ensure maximumperformance for the audits.

Including and Excluding CatalogsThe audit procedures AKDAUDAL and AKDAUDCT allow you to include or excludecatalogs from the audit.

The exclude member for each audit procedure is in the ppfx.SAKDCNTL library. Forthe audit procedure AKDAUDAL, the exclude member is AKDZXCAL and for theaudit procedure AKDAUDCT the exclude member is AKDZXCCT.

To include or exclude specific catalogs from these audits:

1. Modify the statement //EXCLUDE DD DSN=&ppfx.SAKDCNTL(AKDZXCxx)in the auditprocedure so it refers to the proper exclude member.

2. Modify member AKDZXCxx in ppfx.SAKDCNTL with one of the following:

v a list of catalogs to exclude after the EXCLUDES FOLLOW statement

v a list of catalogs to include after the INCLUDES FOLLOW statement

See “AKDAUDCT Audit Procedure” on page 24 or “AKDAUDAL AuditProcedure” on page 23 for additional information on what to include or excludefor each audit procedure.

The following shows an example list of included catalogs for an audit procedure:INCLUDES FOLLOWUSERCAT.UCAT1FACUCAT.FORTY.FOUR.BYTE.CATALOG.NAME.X000001FACUCAT.FORTY.FOUR.BYTE.CATALOG.NAME.X000002

The following shows an example list of excluded catalogs for an audit procedure:EXCLUDES FOLLOWICF.ZAPP02CRTUCAT.EH.REORG01

If you use multi-cluster CDSs, you must:

22 User's Guide

v Include the names of all CDS splits in the JCL for each catalog procedure.

v Include the names of all splits in the AKDBATCH member of the ppfx.SAKDJCLlibrary.

Audit Procedures for Control Data SetsAdvanced Audit for DFSMShsm provides the following audit functions for varioustypes of control data sets.

AKDAUDAL Audit ProcedureAKDAUDAL audits all the MCDS migration components and the catalog entries thatare cataloged to VOLSER MIGRAT.

This procedure creates two data sets that are used in error analysis and correction.

v pfx.AUDIT.MCDS.ERRSUM MCDS - Audit Errors Summary

v pfx.AUDIT.MCDS.ERRORS MCDS - Audit Errors Detail

You can include and exclude specific catalogs. It is recommended that you excludeall master catalogs on the complex. You should check what you are excludingbefore running any procedures involving catalog extraction. It is also recommendedthat you do not exclude user catalogs. When a data set is found that is cataloged toan excluded user catalog, it is reported as if the data set were cataloged to themaster catalog. Additionally, this will cause the product to run considerably longer.See “Including and Excluding Catalogs” on page 22 for more information.

Authorization

The user submitting this job must have RACF ALTER authority.

AKDAUDBD Audit ProcedureAKDAUDBD audits the BCDS backup components.


v pfx.AUDIT.BCDS.ERRSUM - BCDS Audit Errors Summary

v pfx.AUDIT.BCDS.ERRORS - BCDS Audit Errors Detail

Note: You must stop the EXPIREBV and the FREEVOL BACKUPVOL processesbefore running this audit procedure.

AKDAUDCM Audit ProcedureAKDAUDCM audits the DFSMShsm tape inventory OCDS against the BMCControl/M Tape (CNM).

If DFSMShsm manages the tapes directly, this procedure can still be run; however,the diagnostic messages relating to the CNM tape inventory will have little value.


v pfx.AUDIT.TAPE.ERRSUM - Tape Audit Errors Summary

v pfx.AUDIT.TAPE.ERRORS - Tape Audit Errors Detail

Chapter 4. Performing an Audit 23

AKDAUDCT Audit ProcedureAKDAUDCT audits all the MCDS true name entries (MCD and MCO) againstcatalog entries with VOLSER MIGRAT.

The MCDS error analysis will only contain errors related to the catalog extraction.For a full MCDS analysis, run AKDAUDAL or AKDAUDMD.


v pfx.AUDIT.MCDS.ERRSUM MCDS - Audit Errors Summary

v pfx.AUDIT.MCDS.ERRORS MCDS - Audit Errors Detail

If you include certain catalogs instead of excluding them, only those entries inDFSMShsm that qualify for that catalog will be audited. It is recommended that youexclude all master catalogs on the complex. You should check what you areexcluding before running any procedures involving catalog extraction. See“Including and Excluding Catalogs” on page 22 for information.

Authorization

The user ID submitting this job must have RACF ALTER authority.

AKDAUDMD Audit ProcedureAKDAUDMD audits all the MCDS components; excluding the catalog.


v pfx.AUDIT.MCDS.ERRSUM - MCDS Audit Errors Summary

v pfx.AUDIT.MCDS.ERRORS - MCDS Audit Errors Detail

AKDAUDOD Audit ProcedureAKDAUDOD audits the DFSMShsm OCDS volume pointer chains forward andbackward.

This audit is necessary to ensure that the tapes in the OCDS inventory can recycleproperly. This audit not only examines the correct pointers, but it also verifies eachdata set in the pointer conflict to determine the correct pointer and provides theappropriate fixes.


v pfx.AUDIT.OCDS.ERRSUM - TTOC Audit Errors Summary

v pfx.AUDIT.OCDS.ERRORS - TTOC Audit Errors Detail

AKDAUDRM Audit ProcedureAKDAUDRM audits the DFSMShsm tape inventory OCDS against the IBMRemovable Media Manager (RMM).

If DFSMShsm manages the tapes directly, this procedure can still be run; however,the diagnostic messages relating to the RMM tape inventory will have little value.




24 User's Guide

AKDAUDTP Audit ProcedureAKDAUDTP audits the DFSMShsm tape inventory OCDS against the CA1 TMSsystem.

This procedure is useful if your installation has installed the DFSMShsm exit toallow CA1 to manage the tapes. If DFSMShsm manages the tapes directly, thisprocedure can still be run; however, the diagnostic messages relating to the CA1tape inventory will have little value.




AKDAUDZR Audit ProcedureAKDAUDZR audits the DFSMShsm tape inventory OCDS against the ZARA tapemanagement system.

This procedure is useful if your installation has installed the DFSMShsm exit toallow ZARA to manage the tapes. If DFSMShsm manages the tapes directly, thisprocedure can still be run; however, the diagnostic messages relating to the ZARAtape inventory will have little value.




Audit Procedures for DFSMShsm-Owned TapesAdvanced Audit for DFSMShsm provides the following audit functions to executeoutside of the DFSMShsm started task environment.

AKDAUDFD Audit ProcedureAKDAUDFD is the equivalent of the IBM AUDIT DIRECTORYCONTROLSVOLUMES(volser) command and produces diagnostics that are useful indetermining the health and contents of a tape before it is mounted and read.

The TTOC information for the tape is extracted. If the tape is an DFSMShsm ML2volume, the MCDS is read and any MCD (migration control data set record)references to the volume are captured. If the tape is a DFSMShsm backup volume,all MCC (backup control data set backup version record) references found in theBCDS are captured. No automatic corrections or TTOC rebuild statements arecreated in this procedure.

After examining the results of this audit, execute audit procedure AKDAUDFL andmake sure to code the same TAPEVOL parameter.

AKDAUDFL Audit ProcedureAKDAUDFL depends on the successful completion of procedure AKDAUDFD for thesame tape volume because it uses the data sets created by AKDAUDFD and runsadditional diagnostics after reading the physical tape.

The second part of the audit requires the tape to be mounted and read. Afterreading the contents of the tape, further auditing is performed, and diagnostics


messages are produced. In addition, automatic error corrections for the MCD andMCC records are created and contained in the output data set&pfx.MEDIACTL.Vtttttt.FIXES. All TTOC rebuilds and corrections are created andcontained in the output data set &pfx.MEDIACTL.Vtttttt.FIXTTOC.

Repairing or recreating the entire TTOC for a volume may require thousands ofFIXCDS T statements. To avoid flooding the DFSMShsm QUEUE, a monitor isprovided. Even with the monitor, a QLIMIT parameter is provided. The default valueof QLIMIT is 3,000,000, which is typically enough to successfully rebuild the TTOC.The OUTDATASET space allocation also uses the QLIMIT value to allocate enoughspace to contain all the resultant fix processes. Although you may lower the QLIMITvalue, more than one job and set of control statements will be built, requiringseparate job submission and monitoring.

To control how to process the tape, AKDAUDFL supports the processing optionsFAST, THOROUGH, and INTENSE on the OPTION keyword.

AKDAUDFT Audit ProcedureAKDAUDFT is the equivalent of the IBM AUDIT MEDIACONTROLS VOLUMEScommand and combines the functions of the AKDAUDFD and AKDAUDFLprocedures in a single audit procedure.

AKDAUDFT is useful to reclaim volumes in failed create or failed recycle statuswhen the TTOC has been damaged or deleted. It is also useful to rebuild the entireTTOC for tapes that have been inadvertently scratched and are no longer underDFSMShsm control. This is possible as long as the tapes have not been writtenover.

To control how to process the tape, AKDAUDFT supports the processing optionsFAST, THOROUGH, and INTENSE on the OPTION keyword. If you specify FAST orTHOROUGH and the audit detects errors on the tape, the program willautomatically invoke the INTENSE processing option.

OPTION KeywordThe OPTION keyword of the AKDAUDFL and AKDAUDFT audit procedures controlhow to process the tape.

FAST Option

Use the FAST option when auditing tapes that are in 'failed create' status. Typically,a tape is in 'failed create' status if it was being written to when the system orDFSMShsm abnormally terminated or when DFSMShsm is cancelled or FORCECANCELLED. For performance reasons, DFSMShsm retains information in memoryand writes the information to the TTOC about every 20 minutes. If the systemabnormally terminates, or is brought down, before the information in memory can bewritten to the TTOC, the information is lost. The only resolution to recover therecords required to access all data on the tape is to execute the AUDITMEDIACONTROLS VOLUMES command provided in the AKDAUDFL auditprocedure.

When the FAST option is specified, the audit procedure requests the tape to bemounted and positions the tape to a location determined by the last known blockthat has a valid MCD/MCC entry and a matching TTOC entry. The remainder of thetape is read until the end of the tape is encountered. TTOC entries for additionaldata found on the tape are created by FIXCDS T statements. All entries on the tape

26 User's Guide

that physically exist prior to the starting point are presumed to be accurate and arenot audited.

THOROUGH Option

Use the THOROUGH option when the true data set names of one or more datasets are not found in the MCDS or BCDS. It is useful to use this option whenauditing tapes that are in a 'failed recycle' status. Occasionally, you might want toreestablish the pointers to an entry on the tape to initiate an DFSMShsm RECALLor RECOVER command. The TTOC contains alias names assigned by DFSMShsmwhen a data set is migrated or backed up. When a data set name is deleted fromthe MCDS or BCDS, the references to the true name are deleted. The TTOC aliasnames are retained and the data on the tape is still there until the tape is recycledand returned to the scratch pool; however, there is no way to determine the truename without physically reading the tape.

When the THOROUGH option is specified, the audit procedure positions the tape tothe beginning and uses the contents of the TTOC to 'skip' through the tape to theposition where the CDD (common data set descriptor) records are supposed to be.The skip and compare technique is a fast method of determining the entire contentsof the tape. Each CDD entry encountered is audited against the TTOC andMCDS/BCDS extractions. Fixes are automatically generated to correct mismatchesin the corresponding records. In addition, you may create new migration andbackup records to RECALL or RECOVER entries from the tapes.

INTENSE Option

Use the INTENSE option when the TTOC of a tape is damaged or no longer exists.For example, if an ML2 tape has been recycled and returned to the scratch pool,and this is not desired, the INTENSE option is useful to completely rebuild theTTOC of the tape so it can be utilized again for RECALL. The THOROUGH optionis not useful in this scenario because the TTOC for the scratched tape no longerexists. If you code the THOROUGH option and the procedure finds that the TTOCinformation is inaccurate or missing, the INTENSE option is automatically initiated.Informational messages are written to the console to notify you when this occurs.

The INTENSE option reads every record on the tape and counts blocks betweenthe CDD true name entries. The INTENSE option execution can take seven to tenhours to complete, depending on the tape media used, the number of data sets,and the tape subsystem resources available. This process recreates all the TTOCextents and every entry in the extent. The automatically generated FIX commandsfor the MCD and MCC records are placed in output data set&pfx.MEDIACTL.Vtttttt.FIXES. All TTOC rebuilds and corrections are created andcontained in the output data set &pfx.MEDIACTL.Vtttttt.FIXTTOC. These FIXcommands can be subsequently executed to correct the errors on the tape.


28 User's Guide

Chapter 5. Gathering HSM Host Information

This chapter describes how to gather information about the DFSMShsm Hosts thatare actively running on the system.

The DFSMShsm Host Reports panelWhen you enter option 2 on the MAINMENU panel and press Enter, theDFSMShsm Host Reports panel appears:

The options that are available from the Advanced Audit for DFSMShsmHOSTMENU panel are:

1 HSM Host InformationType 1 to display the DFSMShsm hosts that are actively running on thissystem.

2 Control Data SetsType 2 to display a list of the control data sets being used by DFSMShsm.

3 HSM CDS BackupsType 3 to display a list of the backup versions of the control data sets andthe journal.

4 Active AllocationsType 4 to display a list of data sets actively allocated to the DFSMShsmhost.

5 Issue HSM CommandsType 5 to issue a DFSMShsm command to a DFSMShsm host and displaythe messages resulting from the command.

HOSTMENU ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 08:33Command ===> Scroll ===> PAGE

DFSMShsm Host Reports: Row 1 of 6


1 HSM Host Information Lists Active HSM Hosts2 Control Data Sets HSM Control Data Set List3 HSM CDS Backups Shows CDS Backup Versions4 Active Allocations Data Sets Allocated to HSM Hosts5 Issue HSM Commands Issue Command to DFSMShsm Host

Figure 3. The Host Menu panel

29

SCOPE command

For all of the display options available from the DFSMShsm Host Reports panel,options 1–4, you can use the SCOPE command to either expand the scope to allsystems defined in the AKDCMD00 member or to just a single system. The syntaxisSCOPE systemname

Specify the name of the system or a mask. The report data is gathered from thesystem(s) specified and the data displayed together.

You can also issue SCOPE RESET to return to the default behavior.

HSM Host Information reportSelect the HSM Host Information option from DFSMShsm Host Reports menu tocreate an HSM Host Information report.

You can set up filters on DFSMShsm job name or DFSMShsm host ID (or both) sothat the report includes only those hosts whose attributes match your filters. Reportinformation includes one row for each DFSMShsm host whose attributes match thespecified filters. For each host, the report information includes the following:

v Job name and job number

v Host ID

v HSM release level and type

v Logging status

v MCTV address

v QCT and QCT element addresses

v Host AS ID

v Command suffix

v SMF number

v Migrate and Backup prefixes

v Maximum backup, migrate, dump, recall, interval migration, and recover tasks

v Maximum CSA usage

v Active and inactive request limits

v CSA used

v Percentage of allowed CSA currently being used

v Maximum number of work elements allowed to be in CSA

v Audit, autodump, autobackup, automigrate, backup, dump, list, migrate, recall,recover, recycle, and report status

v Tape DSN recall, tape DSN recover, tape DSN replace, and TSO tape DSNstatus information

v BCDS, MCDS, OCDS, and journal backup status information

v ID of the system or the sysplex from which the data was retrieved

Attention: Press the HELP function key to display full online help that describesthe report columns and the available line commands for this report. Use the functionkeys to scroll the display to show all report columns.

30 User's Guide

|

||||

|

||

|

Control Data Sets reportSelect the Control Data Sets option from DFSMShsm Host Reports menu to createa Control Data Sets report.

You can set up filters on:

v DFSMShsm job name

v DFSMShsm host ID

v Control data set name

v Type file

v RLS Managed

v Volume serial

or any combination of these so that the report includes only those control data setswhose attributes match your filters.

Report information includes one row for each control data set whose attributesmatch the specified filters. For each control data set, the report information includesthe following:

v Data set name

v File type

v Volser number

v RLS flag

v Job name

v Job number

v DFSMShsm host ID

v ID of the system or the sysplex from which the data was retrieved


HSM CDS Backups reportSelect the HSM CDS Backups option from DFSMShsm Host Reports menu tocreate a Control Data Set Backup Information report that shows information aboutthe backup copies of the control data sets and the journal.

For each backup copy, the report information includes the following:

v Type of process for which HSM used the original data set. This is the name ofthe DD to which the data set would be allocated.

v Name of the backup data set

v Date on which the backup version was created

v Time at which the backup version was created

v Number of days elapsed since the backup data set was created

v Name of the DFSMShsm data set that was backed up

v Volser of the volume where this data set resided before being backed up

Attention: Press the HELP function key to display full online help that describesthe report columns and the available line commands for this report. Scroll thedisplay by using the RIGHT and LEFT function keys to show all report columns.

Chapter 5. Gathering HSM Host Information 31

Active Allocations reportSelect the Active Allocations option from DFSMShsm Host Reports menu tocreate an Active Allocations report that lists and displays information about datasets allocated to HSM hosts.


v DFSMShsm job name

v Data set name

v DD name

v Volume serial

or any combination of these so that the report includes only those data sets whoseattributes match your filters.

Report information includes one row for each data set whose attributes match thespecified filters. For each data set, the report information includes the following:

v Data set name

v DD name

v Volser

v Member name

v Allocation disposition

v Normal and conditional dispositions of the allocation

v EXCP count

v Job name and number *Host ID


Issuing HSM commandsSelect the Issue HSM Commands option from the DFSMShsm Host Reports menuto send a command to an HSM host and view the messages that result from thatcommand. You can send any command that can be accepted by the HSENDcommand.

Important: You may send commands to any one HSM host. If you need to sendcommands to more than one host, you must return to the DFSMShsmHost Reports menu and select the Issue HSM Commands option andcomplete the fields on the DFSMShsm Command Response panelagain for each host.

To isse an HSM command and view the resulting messages, complete these steps:

1. From the DFSMShsm Host Reports menu, select the Issue HSM Commandsoption to display the DFSMShsm Command Response panel.

2. Specify an address space in the Job Name field on the DFSMShsm CommandResponse panel.

3. In the Host ID field, specify the identifier for the HSM host to which you wantthe command sent.

4. In the Command field, specify the command you want sent to the HSM host.

5. Press Enter.

32 User's Guide

Chapter 6. Performing Administrative Tasks

This chapter describes the administrative tasks that can be performed in IBM TivoliAdvanced Audit for DFSMShsm.

The Administrative Tasks panelWhen you enter option 3 on the MAINMENU panel and press Enter, theAdministrative Menu panel appears:

The options that are available from the Advanced Audit for DFSMShsmADMNMENU panel are:

1 CustomizationType 1 to display a menu allowing the completion or updating of processingparameters.

2 HSM Command AccessType 2 to test a user's access to specific HSM commands.

3 List Parmlib MembersType 3 to browse a list of members in the Parmlib data sets.

4 List PLAN MembersType 4 to browse a list of members in the PLANS data sets.

5 List CNTL MembersType 5 to browse a list of members in the CNTL data sets.

The Customization Menu panelWhen you enter option 1 on the ADMNMENU panel and press Enter, theCustomization Menu panel appears:

ADMNMENU ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 09:54Command ===> Scroll ===> CSR

Administrative Menu: Row 1 of 6


1 Customization Customization Functions2 HSM Command Access Test User Access to HSM Commands3 List Parmlib Members Interact With Parmlib Members4 List PLAN Members Interact with PLAN Members5 List CNTL Members Interact with CNTL Members

Figure 4. The Administrative Menu panel

33

The options that are available from the Advanced Audit for DFSMShsmCUSTMENU panel are:

1 JCL ParametersType 1 to modify parameters used in JCL processing.

2 Data Set Name ParametersType 2 to override the names of data sets used in processing.

Changing JCL parameter settingsSelect the JCL Parameters option on the Customization Menu to display the JCLParameters panel, where you can change the current value assigned to any of theJCL parameters used by the started task in IBM Tivoli Advanced Audit forDFSMShsm.

Attention: These parameters are not used for JCL changes in the batch auditjobs in the SAKDJCL library.

CUSTMENU ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 10:01Command ===> Scroll ===> CSR

Customization Menu: Row 1 of 3


1 JCL Parameters Change JCL Processing Parms2 Data Set Name Parameters Override Data Set Names

Figure 5. The Customization Menu panel

JCLPARMS ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 10:31Command ===> Scroll ===> CSR

Enter Values for the Following Command: Row 1 of 21Parameter Used in JCL Processing:

Job Card 1. . . . . . . . . //AKDJOB JOB (11111),'AKD JOB CARD',REGION=8M,Job Card 2. . . . . . . . . // MSGLEVEL=(1,1),MSGCLASS=A,CLASS=A,Job Card 3. . . . . . . . . // NOTIFY=&SYSUID,TYPRUN=SCANJob Card 4. . . . . . . . . //*Job Card 5. . . . . . . . . //*Unit Name . . . . . . . . . SYSALLDAVolume. . . . . . . . . . .Data Class. . . . . . . . .Management Class. . . . . .Storage Class . . . . . . .Space Type. . . . . . . . . CYLPrimary Allocation. . . . . 100Secondary Allocation. . . . 100Block Size. . . . . . . . . 0

Press END to cancel request, ENTER to use values

Figure 6. The JCLPARMS panel, 1 of 2

34 User's Guide

||||||||||||||||||||||||||

|||||

||||

Attention: These values were set initially when the product was installed andconfigured.

To change the parameter settings:

1. Type the new value over the old value in the appropriate field; press the HELPfunction key and use the online help to guide you as you specify the new valuesfor the parameters.

2. Press Enter to save your changes.

3. Press the END function key to exit the JCL Parameters panel and display theCustomization Menu.

Overriding Advanced Audit for DFSMShsm data set namesSelect the Data Set Name Parameters option on the Customization Menu todisplay the Data Set Name Overrides panel, where you can change the valueassigned to any of the data sets used by the started task in IBM Tivoli AdvancedAudit for DFSMShsm.

Attention: These overrides are not used for JCL changes in the batch audit jobsin the SAKDJCL library.

JCLPARMS ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 10:31Command ===> Scroll ===> CSR

Enter Values for the Following Command: Row 17 of 21Parameter Used in JCL Processing:

Product Prefix. . . . . . . AKDX.AKD0203Date Format . . . . . . . . YYYY/MM/DDDisplay Prev Filter Screen. YVSAM Index Buffers. . . . . 2VSAM Data Buffers . . . . . 30

.

.

.Press END to cancel request, ENTER to use values

Figure 7. The JCLPARMS panel, 2 of 2

DSNPARMS ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 10:55Command ===> Scroll ===> CSR

Enter Values for the Following Command: Row 1 of 11Data Set Name Overrides:

PLANS Data Set. . . . . . . PDUSER.AKD.PLANSCNTL Data Set . . . . . . . PDUSER.AKD.CNTLMigration CDS 1 . . . . . .Migration CDS 2 . . . . . .Migration CDS 3 . . . . . .Migration CDS 4 . . . . . .Backup CDS 1. . . . . . . .Backup CDS 2. . . . . . . .Backup CDS 3. . . . . . . .Backup CDS 4. . . . . . . .Offline CDS . . . . . . . .


Figure 8. The DSNPARMS panel

Chapter 6. Performing Administrative Tasks 35

||||||||||||||||||||||

|

|||

|

||

Attention: These values were set initially when the product was installed andconfigured.

To change the parameter settings:

1. Type the new value over the old value in the appropriate field; press the HELPfunction key and use the online help to guide you as you specify the new valuesfor the data sets.

2. Press Enter to save your changes.

3. Press the END function key to exit the Data Set Name Overrides panel anddisplay the Customization Menu.

Testing user access to HSM commandsThere might be occasions where it would be convenient to be able to see to whichHSM commands a given user ID has access.

To test user access to HSM commands:

1. Select the HSM Command Access option from the Administrative Menu todisplay the User DFSMShsm Access panel.

2. On the User DFSMShsm Access panel, enter the appropriate user ID in theUser ID field and press Enter. The HSM access information for that user ID isdisplayed.

Listing PARMLIB data set membersYou can use the Administrative Menu to generate a list of the members in thePARMLIB data sets.

To list the PARMLIB data set members:

1. Select the List Parmlib Members option from the Administrative Menu todisplay the Members in the Parmlib Data Sets panel.

2. In the Member Name field on the Members in the Parmlib Data Sets panel,specify a mask that will match the member names of interest.

3. In the Data Set Name field, specify a mask that matches the data set names ofinterest.

4. Press Enter to display the member list. Use the HELP function key to guide youas you make entries and use line commands on this panel.

5. Press the END key to return to the Administrative Menu.

Listing PLAN data set membersYou can use the Administrative Menu to generate a list of the members in the PLANdata sets.

To list the PLAN data set members:

1. Select the List PLAN Members option from the Administrative Menu to displaythe Members in the Plans Data Sets panel.

2. In the Member Name field on the Members in the Plans Data Sets panel,specify a mask that will match the member names of interest.




36 User's Guide

Listing CNTL data set membersYou can use the Administrative Menu to generate a list of the members in the CNTLdata sets.

To list the PLAN data set members:

1. Select the List CNTL Members option from the Administrative Menu to displaythe Members in the CNTL Data Sets panel.

2. In the Member Name field on the Members in the CNTL Data Sets panel,specify a mask that will match the member names of interest.




Chapter 6. Performing Administrative Tasks 37

38 User's Guide

Chapter 7. Viewing product information

When you enter option 4 on the MAINMENU panel and press Enter, the ProductMenu panel appears:

The options that are available from the Advanced Audit for DFSMShsm PRDMENUpanel are:

1 Version/Release DataType 1 to display information about the product's name and version.

2 Product Data SetsType 2 to display the product data sets that are being used for processing.

3 Address Space AllocationsType 3 to display a list of the data sets that are currently allocated to theproduct address space.

4 Address Space Enq DataType 4 to display a list of the enqueues being held by the product addressspace.

5 Address Space MemoryType 5 to display the virtual storage being used by the product addressspace.

6 Product MessagesType 6 to display the documentation available on product messages.

7 Product Work Data SetsType 7 to display the data sets used by the product to store data as well asgenerate reports.

8 System Connection ListType 8 to display all remote systems that have been defined to the product.

PRDMENU ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 22:36Command ===> Scroll ===> CSR

Product Menu: Row 1 of 8


1 Version/Release Data Product Name and Release Data2 Product Data Sets Data Sets Used by the Product3 Address Space Allocations A/S Active Allocation List4 Address Space Enq Data Enqs Held by the Address Space5 Address Space Memory A/S Current Memory Usage6 Product Messages Product Message Documentation7 Product Work Data Sets Data Sets Used for Processing8 System Connection List Product Cross System Connections

Figure 9. The Product Menu panel

39

||

Viewing version and release level dataSelect the Version/Release Data option from the Product Menu to display theProduct Version/Release Information panel.

This panel provides the version and release level for IBM Tivoli Advanced Audit forDFSMShsm and shows copyright and trademark information.

To exit the panel and redisplay the Product Menu, press the END function key.

Listing data sets used during processingSelect the Product Data Sets option from the Product Menu to display the DataSets Being Used by this Product panel.

The Data Sets Being Used by this Product panel shows you the data set names,data set type, job name, and job number.

By selecting an individual data set and using the appropriate line command, youcan do any of the following from this panel:

v Browse the data set

v View the data set

v Display backup information for the data set

v Display information about the backup versions available for the data set

v Back up the data set

v Display LISTCAT information for the data set

To exit the PRODDSNS panel and display the Product Menu panel, press the ENDfunction key.

PRODDSNS ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 22:54Command ===> Scroll ===> CSR

Data sets being used by this product: Row 1 of 8Line Commands are . . . : B V HB LC

Dsn Job JobCmd Data Set Name Type Name Number

AKD.JKS0203.LOADLIB STEPLIB AKD0203 S0011133AKDX.AKD0203.SAKDLOAD STEPLIB AKD0203 S0011133AKDX.AKD0203.SAKDCLST CLIST AKD0203 S0011133AKDX.AKD0203.SAKDCNTL CNTL AKD0203 S0011133AKDX.AKD0203.SAKDMSGS MESSAGES AKD0203 S0011133AKDX.AKD0203.PLANS PLANS AKD0203 S0011133AKDX.AKD0203.SAKDPENU PLIB AKD0203 S0011133AKDX.AKD0203.SAKDPARM PARMLIB AKD0203 S0011133

Figure 10. The Data Sets Being Used by this Product panel

40 User's Guide

Listing data sets allocated to the address spaceSelect the Address Space Allocation option from the Product Menu to display afilter panel for the Data Sets Allocated to Address Space panel.

The Data Sets Allocated to Address Space panel shows the following informationfor each data set:

v Data set name

v Name of the DD statement to which the data set is allocated

v Serial number of the volume on which the data resides

v Name of the member allocated in the data set

v Disposition of allocation

PRDALLOC ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 11:11Command ===> Scroll ===> CSR

Enter Filtering Values for the Following Report: Row 1 of 3Data Sets Allocated to the Product Address Space:

Data Set Name . . . . . . . EQDD Name . . . . . . . . . . EQVolume Serial . . . . . . . EQ


Type your filtering values and press Enter to proceed to the Data Sets Allocated to Address Space panel.Figure 11. The Filtering Values for Data Sets Allocated to Address Space panel

PRDALLOC ------- IBM Tivoli Advanced Audit for DFSMShsm V2R3 ----------- 11:13Command ===> Scroll ===> CSR

Data Sets Allocated to the Product Address Space: Row 1 of 7 More >Line Commands are . . . : LC VOL

DDCmd Data Set Name Name Volser Member Disp

AKD.JKS0203.LOADLIB STEPLIB SMS022 SHRAKDX.AKD0203.SAKDLOAD SMS023 SHRAKDX.AKD0203.SAKDPARM PARMLIB SMS023 SHRSTC.AKD0203.S0011133.D0000101.? CEEDUMP MODSTC.AKD0203.S0011133.D0000102.? SYSOUT MODSTC.AKD0203.S0011133.D0000103.? AKDLOG MODSTC.AKD0203.S0011133.D0000104.? AKDVERS MOD

Figure 12. The Data Sets Allocated to Address Space panel

Chapter 7. Viewing product information 41

||||||||||||||||||||||||

|||

|||||||||||||||||||||||||

||

||

|

|

|

|

|

v Normal and conditional dispositions of allocation

v Number of EXCPs to the data set

By selecting an individual data set and using the appropriate line command, youcan do any of the following from this panel:

v Display primary volume information

v Display LISTCAT information for the data set

To exit the Data Sets Allocated to Address Space panel and display the ProductMenu, press the END function key.

Listing enqueues held by the address spaceSelect the Address Space Enq Data option from the Product Menu to display theENQ Information for Address Space panel.

The ENQ Information for Address Space panel provides the following information foreach enqueue:

v Major name and the first portion of the minor name

v Request type for the enqueue

v Name of the job issuing the request

v Address space ID of the job issuing the request

v System name associated with the enqueue

v Request level and request scope

v Request status

v Total number of users waiting for the resource, number of users waiting forexclusive use of the resource, and number of users waiting for shared use of theresource

v Number of resource owners for the enqueue

v TCB address associated with the enqueue

v SVRB address that issued the enqueue

v ECB address of the task that issued the enqueue request

v Whether the step must complete for the enqueue

v Device number associated with the enqueue

v The major and minor names in hexadecimal format

To exit the ENQ Information for Address Space panel and display the ProductMenu, press the END function key.

Displaying address space virtual storage informationSelect the Address Space Memory option from the Product Menu to display theAddress Space Memory Information panel.

The panel displays:

v A description of the type of memory

v Data related to memory

To exit the Address Space Memory Information panel and display the ProductMenu, press the END function key.

42 User's Guide

|

|

||

|

|

||

Displaying product message documentationSelect the Product Messages option from the Product Menu to display theMembers in Messages Data Sets panel, which provides information about themessages generated during IBM Tivoli Advanced Audit for DFSMShsm processing.


v Message Identifier

v Member name

v Data set name

or any combination of these so the resulting report includes information for onlythose messages whose attributes match the filters.

Important: It is recommended that the filter for Member Name be left blank whensearching for messages.

Additionally, you can leave all filters blank and press Enter to view all productmessages.

The Members in the Messages Data Sets panel shows the following information foreach message:

v Message ID

v Name of the member containing the message

v Name of the data set to which the member containing the messagedocumentation belongs

v Data from the first line in the message member for the message

Attention: Use the HELP function key to display further information about thecolumns and commands available on the Members in the MessagesData Sets panel. Use the LEFT and RIGHT function keys to scroll thedisplay to show all the columns.

Displaying product work data set informationSelect the Product Work Data Sets option from the Product Menu to display theData Set List panel, which provides information about data sets IBM TivoliAdvanced Audit for DFSMShsm uses for storing report data and to generate thereports.

The Data Set List panel provides the following information about each data set:

v Data set name

v Entry type for the data set

v Volume serial number for the first (or only) volume on which the data set resides

Attention: Use the HELP function key to display further information about thecolumns and commands available on the Data Set List panel.

Displaying a list of system connectionsSelect the System Connection List option from the Product Information menu todisplay the Cross-System Connection list panel, which provides information aboutthe status of the cross-system connections that were set up within the productcommand member.

Chapter 7. Viewing product information 43

|

||||

This reports shows the status of the cross system connections that have been setup within the command member.

Parm USEXSYS must be set to YES for any cross system processing to beattempted. Use parameters PORTNUM, CONNECTION, and LOCALCONN in thecommand member to set up the cross-system connections.

For each system that is to use cross-system communication, you must provide anIP address or domain name through a CONNECTION parameter. Use theLOCALCONN parameter to specify the local system’s IP address or domain name.You need to specify both a CONNECTION and LOCALCONN parameter for thelocal system. The PORTNUM value will be used as the port number that allsystems will use to connect.

Attention: Press the HELP function key to display full descriptions of the columnsand commands available for this report. Use the function keys to scrollthe display to show all columns.

44 User's Guide

||

|||

||||||

||||

Chapter 8. Correcting Errors

This chapter provides information on how to setup your audit procedures to correcterrors automatically or to use Advanced Audit for DFSMShsm to analyze andcorrect errors manually.

Automatic Error CorrectionAdvanced Audit for DFSMShsm allows you select the fixes that most appropriatelysatisfy your environment, make it the default, and then apply them automatically.

All of the audit procedures have a member in the &ppfx.SAKDCNTL library. Theseare the generic plans and automatic fix routines for each diagnostic error that canbe repaired. The recommended fixes must be defined by the customer whereappropriate. You should review the automatic fixes member and select the fixes thatmost appropriately satisfy your environment so only those fixes are applied whenthe audit procedure is run.

A plan for each diagnostic error is distributed with the product and resides in the&ppfx.PLANS library. The naming convention of each plan member is the five-digitdiagnostic error preceded by a P. The naming convention of the preferred fix for thatplan is a five-digit diagnostic error preceded by an F. The contents of a sampleautomatic fixes member is shown below.

Note: This is an example of the AKDZAFxx member in the &ppfx.SAKDCNTLlibrary.

***************************** Top of Data ******************************* LIST OF AUTOMATIC FIXES FOR THE xxxx AUDIT (AKDAUDxx)----+----1----+----2----+----3----+----4----+----5----+----6----+----7--* COLUMN 1 IS PLAN MEMBER TO EXECUTE, COLUMN 10 IS PREFERRED FIXPxxxxx Fxxxxx

Column 1 contains the start of the plan member name and column 10 contains thestart of the fix to apply. If you do not want to apply a fix automatically, specifyNONE for both the plan member to execute (starting in column 1) and the preferredfix (starting in column 10).

If automatic fixes have been turned on, a dataset named &PFX.AUDIT.&TYPE.FIXES will contain the JCL and fix commands needed to fix the errorsidentified. &PFX is the runtime prefix set in the AKDINI member in SAKDPARMlibrary. The &TYPE is determined based upon the type of audit performed (MCDS,BCDS, etc.).

To apply the fixes automatically, you must make the following change to your auditprocedure:

v Near the end of each audit job, there is an IEBGENER step that is commentedout. When you uncomment this step, the automatic fixes created by the job aresubmitted to the internal reader.

Advanced Audit for DFSMShsm has the ability to perform IBM recommended fixesautomatically. This option is turned on by changing the IBM_AUTOFIX token in theAKDINI member in SAKDPARM. (See AKDINI Configuration Chapter 10) If thisparameter is set to yes, specific IBM recommended fixes are generated when errorsare found. These fixes are placed into a dataset and can be sent to the internalreader for submission. It is highly recommended to have a relatively clean CDS

45

|

||

||||||

|||||

||

|||||

||||

|||||

||

|||

||||||

environment before automatically submitting fixes to the internal reader. In thebeginning it is recommended to review the fixes before submitting them.

Error Threshold MonitoringYou can bypass automatic error correction if the number of errors exceeds apredefined threshold or based on filtering by high-level qualifier or group ofhigh-level qualifiers.

The following example shows the default plan for diagnostic xxxx, where xxxx wouldbe the diagnostic error.****** ***************************** Top of Data ******************************000001 PLAN PLAN01000002 *000003 *000004 SELECT *000005 FROM (datset)000006 USING dataset(member)000007 CREATE dataset .000008 WHERE DIAGNOSTIC = 'xxxx'000010 AND ERR-COUNT GT '0'000011 END PLAN01000012 PLAN PLAN02 COND EQ 0 PLAN01000013 * SAMPLE PLAN TO TEST A COPY OF ARGUMENTS000014 SELECT *000015 FROM (dataset)000016 USING dataset(member)000017 USE error dataset000018 FROMKEY ERRNUM = 'xxxx'000019 TOKEY ERRNUM = 'xxxx'000020 WHERE ERRNUM = 'xxxx'000021 * ANY COPY MEMBER STATEMENTS FOR ENHANCED PLANS WOULD GO HERE000022 * COPY TESTLIST000023 END PLAN02

PLAN01 determines if any diagnostics have been detected with the logic in lines 8and 10. If the answer is zero, the COND example in PLAN02 determines whetherthe second part of the plan should run. The syntax allows more than one conditionto be tested before a condition is true. All conditions must be satisfied before theresult is set to true.

In this case, if some diagnostics are detected, PLAN02 captures and spools theerror detail to the error dataset.

If you do not want to run fixes when the error count exceeds a predefinedthreshold, you can add a statement in the example after line 10 similar to thefollowing:WHERE DIAGNOSTIC = 'xxxx'

AND ERR-COUNT GT '0'AND ERR-COUNT LT '10000'

Lines 21 and 22 of the example plan show a comment about copying a member formore conditional setting. This is where you can enter data set name filter patternsto distinguish test from production data or any other criteria. You can add thestatements directly into the plan or place them in a separate member in the PLANSlibrary. An example of what you might specify for line 21 to test true on a specificDSN is shown below:AND TDSN AE 'DCD.**'OR TDSN AE 'EDP.**'OR TDSN AE 'DANR.**'

46 User's Guide

||

|

|||

||

|||||||||||||||||||||||

|||||

||

|||

|||

||||||

|||

The AE operation means ACS PATTERN EQUAL to the filter pattern presented inthe argument. You can use the corresponding operation of AN (ACS PATTERNNOT EQUAL) for an exclusion test. See Chapter 13, “The Query LanguageFeature,” on page 131 for more information.

If the same list of data sets are needed from plan to plan, you can create a memberin the PLANS data set with these arguments in it and use the COPY statement toemploy the member in each plan where needed. In the above example, COPYTESTLIST on line 22 is commented out. Create the member name and change theCOPY statement to refer to that member. All the statements in the memberTESTLIST will be placed after the WHERE statement and applied.

More than one selection plan can be processed against the same diagnostic. Forexample, if you have a list of data sets stored in member PRODLIST, an additionalplan would be identical to the one shown above except COPY PRODLIST would bespecified. Assume that the fix to apply for production data sets is different than thetest data sets. The SELECT DD statement of the audit procedure would contain areference to the automatic fix member containing multiple plans and their fixes.

Automatic Error Correction Quick ReferenceThe following table lists the members of SAKDCNTL that are referred to by theSELECTS DD statement and the SELECTI DD statement. The SELECTS DDstatement is used for customer defined automatic fixes and the SELECTI DDstatement is used by the IBM_AUTOFIX automatic fixes. The SELECTI DDstatement is used when the AKDINI parameter IBM_AUTOFIX is set to YES. SeeAKDINI configuration for a description on IBM_AUTOFIX parameter.

Table 3. SAKDCNTL Members Referred to by the SELECTS or SELECTI DD Statement

SAKDCNTL Member Audit Procedure Diagnostics MAPS

AKDZAFMC,AKDZIFMC

AKDAUDAL 11D1C - 1126I AKDZ0037

AKDZAFMC,AKDZIFMC

AKDAUDCT 11D1C - 1126I AKDZ0037

AKDZAFMC,AKDZIFMC

AKDAUDMD 11D1C - 1126I AKDZ0037

AKDZAFBC,AKDZIFBC

AKDAUDBD 2101W - 2117W AKDZ0029

AKDZAFTC,AKDZIFTC

AKDAUDCM 3101W - 3114I AKDZ0040

AKDZAFTR,AKDZIFTR

AKDAUDRM 3101W - 3116W AKDZ0040

AKDZAFTT,AKDZIFTT

AKDAUDTP 3101W - 3116W AKDZ0040

AKDZAFOC,AKDZIFOC

AKDAUDOD 4001W - 4013I AKDZ0039

AKDZAFAM,AKDZIFAM

AKDAUDFL 8000I - 8020I AKDZ0038

AKDZAFAM,AKDZIFAM

AKDAUDFT 8000I - 8020I AKDZ0038

Chapter 8. Correcting Errors 47

||||

||||||

||||||

|

||||||

||

||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|

Analyzing and Correcting Errors ManuallyAdvanced Audit for DFSMShsm provides a method of analyzing and correctingaudit errors after the audits have been executed and researched.

The audit error correction processes create TSO, DFSMShsm, TMSBINQ, andTMSUPDTE commands. Advanced Audit for DFSMShsm does not alter the controldata sets (CDSs) other than by using the IBM-supported FIXCDS command. Theselection and application of a particular fix strategy is your responsibility and shouldbe applicable to your environment.

Note: Multiple users may apply fixes after an audit has been run.

To view and correct errors:

1. From the MAINMENU panel, select Option 1 Auditing. After selecting Option 1you will see the (AKD710) panel. Type the option on the command line thatapplies to the audit procedure you have just run and press Enter. The Error(AKD720) panel for the selected audit procedure is displayed.

2. Type F (fix) next to the error number to fix the error and press Enter. The FixList (AKD715) panel is displayed. This panel lists the provided fixes ordiagnostic aids for this error.

Tip: To view additional details about a fix, type H next to the fix and press Enteron the Error (AKD720) or Fix List (AKD715) panels.

3. Type F (fix) next to the member name and press Enter. A sequential data set isautomatically created with the JCL FIX control statements.

Note: If you do not already have a job card member defined for running jobs tofix audit errors, you will be prompted to create a job card member foryour user ID.

4. Optionally, modify the JCL and control statement prior to executing them.

5. Type SUBMIT on the command line to run the JCL. The results of the executionare placed in a data set prefixed with your TSO user ID. For example, thefollowing data set was created:FA390.FIXAUDIT.F11D1CA

FA390 is the User ID and F11D1CA is the error number and the fix option forthis error.

6. Type the data set name in the DSNAME LEVEL field on the Data Set ListUtility panel (ISPF 3.4) to display the data set containing the results of the fixprocessing and press Enter. The results are displayed.

Browsing Audit ResultsAdvanced Audit for DFSMShsm provides a method of browsing audit results afterthe audits have been executed and researched.

To browse audit results:


48 User's Guide

|

Tip: To view additional details about a fix, type H next to the fix and pressEnter.

2. Type B (browse) next to an error number and press Enter. The data set isdisplayed in browse mode. You can scroll right to see any additional information

3. Press End (PF3) to return to the Error (AKD720) panel.

Modifying Audit ResultsAdvanced Audit for DFSMShsm provides a method of modifying audit results afterthe audits have been executed.

When you modify the audit results, you are not making permanent changes to theresults. The modified data is made within a temporary data set. Any data that isdeleted or corrected is still accessible by Advanced Audit for DFSMShsm and is notupdated until the audit is run again.

To modify audit results:


2. Type M (modify) next to an error number and press Enter. The data set isdisplayed in edit mode within a temporary data set. You can scroll right to seeany additional information

3. Make any deletions or modifications to the audit results and save your changes.

4. Press End (PF3) to advance to the Fixes (AKD715) panel.

Using SDSF to Monitor Automatic FixesYou can use SDSF to monitor the progress of automatic fixes of an active batchjob.

The Monitor examines the command input stream and estimates the number ofcommands it will process. Also, it determines what the OUTDATASET is that HSMwill use to record the activity. The default command limit is 1,000. Depending on theHSM COMMAND STORAGE AREA (CSA) the number of commands may bereduced. Whenever the Monitor wakes up to process another series of commands,it examines the number of extents of the ODS data set. The AKDMONTR013message is issued so you can watch the progress of extents taken. At completionof the input stream, the AKDMONTR014 message is issued to show the actualcommands processed and the expected estimated commands.

To monitor the SYSTSPRT data:

1. On the SDSF Held Output Display panel, type ? (question mark) to the left ofthe fix job and press Enter.

2. On the SDSF Job Data Set Display panel, type S to the left of SYSTSPRT andthe current contents of SYSTSPRT will be displayed.

3. Optionally, press Enter again to display any additional messages as they occur.

Chapter 8. Correcting Errors 49

50 User's Guide

Chapter 9. Messages and Codes for Advanced Audit forDFSMShsm

This appendix documents the messages and error codes issued by Advanced Auditfor DFSMShsm and are presented in ascending alphabetical and numerical order.

All messages generated by Advanced Audit for DFSMShsm have a severity codeprinted as the last character of the message ID. The severity codes are describedin the following table.

Severity Code Description

I Information only. No action required.

W Warning message. Results maybe not be asexpected.

E Error message. Some may beuser-correctable, read the User Response todetermine the course of action.

Product Error Messages

AKD10501E xxxxxxxx VSAM Point failed forDDNAME

Explanation: VSAM processing failed during a POINTcommand.

User response: Validate that your JCL is correct. Ifyou can't resolve this problem, call support.

AKD10502E xxxxxxxx VSAM Point failed forDDNAME

Explanation: VSAM processing failed during a POINTcommand.


AKD10701E VSAM open error, process ended

Explanation: VSAM open failed. Processing isterminated.


AKD10702E INPUT open error, process ended

Explanation: VSAM open for input failed. Processingis terminated.


AKD10703E OUTPUT open error, process ended

Explanation: VSAM open for output failed. Processingis terminated.


AKD10901E ERR1 key not found

Explanation: VSAM key read failed. Processing isterminated.


AKD10902E xxxxxxxx close failed for DDNAME

Explanation: Check dataset for DDNAME.

User response: If you can't resolve this problem, callsupport.

AKD11101E Key not found

Explanation: The Multi-CDS processor was unable toread a key in the split CDS.

User response: Check to see if the order of the splitdsnames in the catalog procedure is correct.


Explanation: The Multi-CDS processor was unable toclose DDNAME xxxxxxxx.

User response: Check to see if the order of the splitdsnames in the catalog procedure is correct.

51





Explanation: VSAM close failed for the DDNAME.

User response: Check dataset for DDNAME. If youcan't resolve this problem, call support.





Explanation: VSAM close failed for the DDNAME.

User response: Check dataset for DDNAME. If youcan't resolve this problem, call support.

AKD11701E Open failed for MCDS

Explanation: The request to open the MCDS hasfailed.

User response: Check the spelling of the MCDS andits splits for accuracy. If the names are proper, callsupport.

AKD11702E Open failed for MCDS1








User response: Check the spelling of the MCDS and

its splits for accuracy. If the names are proper, callsupport.

AKD11901E Open failed for OCDS

Explanation: The request to open the OCDS hasfailed.


AKD11902E Open failed for OCDS1









AKD12101E xxxxxxxx failed to open

Explanation: The request to open ddname xxxxxxxxhas failed.

User response: Validate that your JCL is correct.Check to see if the order of the split dsnames in thecataloged procedure is correct. If you can't resolve thisproblem, call support.

AKD12102E xxxxxxxx DDNAME split out of order

Explanation: The split CDS was found out of order.


AKD12103E No key for DDNAME was found.

Explanation: No key exists for this DDNAME.


AKD11301E • AKD12103E

52 User's Guide



















AKD12901E INI DD missing, cannot determinevalues

Explanation: The request to open the INI DD hasfailed.


AKD13101E No volume given at exec parm

Explanation: No volume parm was given on the execparameter.

User response: Supply a valid volume parm in theJCL.

AKD13102I xxxx Length of TTOC record from R0

Explanation: The length of the TTOC record isdisplayed.

User response: No action required.

AKD13301E No CDS request found

Explanation: An invalid CDS request name was given

User response: Supply a valid CDS request ofMCDS, BCDS, or OCDS.

AKD13901E xxxxx was invalid function

Explanation: An invalid function name was given

User response: Supply a valid function name ofOPEN, CLOSE or GET.




AKD14301E Failed to open MCV volume table

Explanation: The MCV extraction module failed toopen a file contaminating the extracted HSM volumeinventory (MCV) table. This message is followed byuser abend 1001.

User response: Verify that the MCDS and its splitsare spelled correctly and that it is truly the MCDS.

AKD14302E Bad return from AKD10149

Explanation: The MCDS extraction module passes alist of ML1 volumes to AKD10149. AKD10149 was notsuccessful in processing DCOLLECT statements to listtheir contents.

User response: Contact support.

AKD14901E No volume list passed

Explanation: Module AKD10149 formats DCOLLECTstatements to list the contents of the ML1 volumes. Inthis instance the module found no ML1 volumes to list.


AKD15301E Bad return from date routine

Explanation: An problem was encountered in dateroutine.

User response: Supply a valid date to the dateroutine.

AKD12301E • AKD15301E

Chapter 9. Messages and Codes for Advanced Audit for DFSMShsm 53

AKD15701I Locate failed for Master Catalog

Explanation: A problem was encountered using locatefor the Master Catalog. Processing continues.

User response: None.




AKD16301E MASTRCAT Open failed

Explanation: DDNAME MASTRCAT failed to open.Processing terminates.


AKD16302E UCATS Open failed

Explanation: DDNAME UCATS failed to open.Processing terminates.





AKD16701I Found data component

Explanation: Informational message.


AKD16702W No length passed on data component

Explanation: No length passed for data component.


AKD17701E POINT on open failed

Explanation: The catalog extraction module attemptedto open a catalog but the VSAM read module failed toopen it.

User response: Probably an empty catalog. Performan IDCAMS LISTC USERCAT UCAT command to verifythe integrity of the catalog.

AKD17702E xxxxxxxx VSAM open failed

Explanation: The catalog extraction module attemptedto open a catalog but the VSAM read module failed toopen it.

User response: Probably an empty catalog. Performan IDCAMS LISTC USERCAT UCAT command to verifythe integrity of the catalog.

AKD17901E dsname Allocation failed

Explanation: Audit attempts to extract information inthe Small Data Set Packing data set for audit purposesSometimes the SDSP is temporarily in use by HSM andthe allocation will fail. Audit attempts to allocate the dataset again after all others have been processed (usuallywith success). If the dsname is displayed twice in therun time messages, the audit of the SDSP may not beaccurate.

User response: If the dsname above is displayedtwice then Audit Error 1118C may be erroneouslydiagnosed. However audit extracts the SDSPinformation again for verification purposes to insure it'saccuracy. If you see an unusually large number of1118C errors in the MCDS audit, contact support.

AKD17902E SDSP open failed

Explanation: Audit attempts to extract information inthe Small Data Set Packing data set for audit purposes.In this case the allocation was successful but the openfailed. Audit will attempt to open later after all othershave been processed. If the dsname is displayed twicein the run time messages, the audit of the SDSP will notbe accurate. The SDSP is probably contaminated and isnot in service.

User response: Try to analyze why the SDSP is introuble.

AKD17903E dsname Unallocate failed

Explanation: Audit dynamically allocates andunallocates all SDSP datasets. In this instance theallocation was good but the unallocation failed. This isunlikely but is an indicator that the audit process iscontaminated.

User response: If you can't resolve this problem, callsupport.

AKD18101E Key not found.

Explanation: Module AKD10181 issued an open tothe SDSP VSAM cluster but the open failed with aPOINT key.


AKD15701I • AKD18101E

54 User's Guide

AKD18102E Open failed on SDSP cluster

Explanation: Module AKD10181 issued an open tothe SDSP VSAM cluster, but the open failed. Probably acontaminated SDSP VSAM cluster.

User response: Try to determine why the SDSP iscontaminated.

AKD19701E SDSP Verify failed to open

Explanation: Audit has reextracted the SDSPinformation into a sequential file. When attempting toverify the SDSP errors, the extracted file failed to open.


AKD19901E MCDS Open failed


User response: Check the spelling of the MCDS andits splits for accuracy. If the names are proper contactsupport.

AKD22101E xxxxxxxx key was TTVKEY

Explanation: The BCDS extraction module hasabended while attempting to update the table of backupvolumes where xxxxxxxx is the key of the table.


AKD23701E AKD10125 failed to load

Explanation: One of the VSAM read modules failed aload attempt.

User response: Check loadlib allocation orconcatenation.

AKD27701E TTCVOLS table failed to open

Explanation: An attempt to open a table failedcontaminating the volumes extracted from the TTOC.


AKD28501E TTCVOLS table failed to open

Explanation: An attempt to open a table failedcontaminating the volumes extracted from the TTOC.



Explanation: The date conversion routine hasencountered an invalid date.


AKD28702E Open failed for TMS extraction

Explanation: An attempt to open a table failedcontaminating the TMS extracted information.


AKD28703E Open failed for TTC extraction

Explanation: An attempt to open a table failedcontaminating the TTOC extracted information.





AKD28902E xxx OCDS failed to open

Explanation: An attempt to open the OCDS TTOCfailed. The TMS extracted information.

User response: Check the spelling of the OCDS dsnin the cataloged procedure.

AKD29501E Table replace failed

Explanation: While auditing the TTOC chain, anattempted update to the TTOC extraction file failed.


AKD29901E Open failed for MCDS

Explanation: An attempt was made to open theMCDS and it failed.

User response: Check the spelling of the MCDS andits splits.

AKD30901E Sort of error records failed

Explanation: An attempt to sort the error recordsfailed.


AKD31501E Allocation of catalog failed

Explanation: An attempt to allocate the catalog failed.

User response: Check catalog name. If in errorcontact support.

AKD31502E Unallocation of catalog failed

Explanation: An attempt to unallocate the catalogfailed.

AKD18102E • AKD31502E


User response: Check catalog name. If in errorcontact support.

AKD31701E PARM is incorrect

Explanation: An invalid parm was passed to theprogram.

User response: Valid parms are NOTEMPS orINCTEMP.

AKD34901E No volume given at Exec parm

Explanation: To perform an audit of a tape volume, avolume serial number must be supplied.

User response: Make sure the cataloged procedurehas not been altered and the execution parameter forprogram AKD10349 contains a valid volume serialnumber.




AKD34903E Extended TTOC found in OCDS butsystem is not at 1.7 or OCDS hasmaxlrecl LT 6140

Explanation: Audit found an extended TTOC in theOCDS, but because the system is not at level 1.7 ORthe OCDS has a maxlrecl LT 6140 the audit can notcontinue.

User response: Check the extended TTOC setting forthe HSM system.

AKD35301E Internal Error 2

Explanation: An attempt to access the HSM addressspace information for the migration or backup prefix hasfailed.

User response: This might mean that HSM is notrunning on the same system as the audit job. Makesure HSM is active on the same system the audit isrunning on.




AKD35501I HSM is active, EXTENDEDTTOC(Y) isset

Explanation: Informational message showing theEXTENDEDTTOC setting.


AKD35502I HSM is inactive, OCDS is eligible forXTTC

Explanation: Informational message showing HSM ininactive and the OCDS is eligible for XTTC processing.


AKD35503I HSM is active, EXTENDEDTTOC(N) isset

Explanation: Informational message showing theEXTENDEDTTOC setting.








AKD35701E xxxxxxxx open failed

Explanation: An attempt to open xxxxxxxx failed.

User response: Check cataloged procedure for properspelling of dsn for xxxxxxxx.

AKD36501I oooooooo was the option

Explanation: This message is issued at the beginningof the tape audit. There are three options for the tapeaudit - FAST, THOROUGH or INTENSE. This messageis useful when analyzing the results of the audit job.

User response: Information only. Processingcontinues.

AKD31701E • AKD36501I

56 User's Guide

AKD36502E Bad read on first block

Explanation: The first block read on the tape failed.Further auditing is not possible.

User response: Audit is terminating.

AKD36503W Audit changed to INTENSE process

Explanation: When navigating through the tape anexpected data set name represented by the CDD eyecatcher was not found. This means the informationabout the data on the tape can not be used. The tape isbackspaced to the last good position and every block ofdata is read for the remainder of the audit.

User response: Auditing continues.


Explanation: The first block read on the tape failed.Further auditing is not possible.

User response: Audit is terminating.

AKD36505I xxxxxxxx xxxxxxxx RQST FBID andNOTE results

Explanation: Informational message displayinglocation of the tape read module.


AKD36506W Option FAST mismatch FBID and NOTE

Explanation: Option FAST was unable to continue.The audit will change the option to THOROUGH andstart over.


AKD36507W POINT failed to find *CDD**

Explanation: Option FAST was requested for a tapeaudit but the File Block Identifier given for the last goodblock to skip to did not contain the CDD eye catcher.

User response: The audit is restarted at the beginningof the tape with the option THOROUGH.

AKD36508W Option FAST mismatch DSN,THOROUGH started

Explanation: Option FAST was requested for a tapeaudit and the File Block Identifier CDD eye catcher wasfound, but the DSN did not match.


AKD36509W Positioning failed

Explanation: Option FAST was requested for a tapeaudit but the POINT command physically failed for thetape.


AKD36510I Audit method changed to THOROUGH

Explanation: When option FAST is being changed toTHOROUGH, the tape is closed with rewind andre-opened.

User response: None. Information only.

AKD36511I Audit method changed to INTENSE

Explanation: When navigating through the tape anexpected data set name represented by the CDD eyecatcher was not found. This means the informationabout the data on the tape can not be used. The tape isback-spaced to the last good position and every blockof data is read for the remainder of the audit.


AKD36512E Audit tape OPEN failed

Explanation: An audited tape failed to open. The auditcan not be run.

User response: Make sure the correct tape volserwas coded on the cataloged procedure.

AKD36513W No HSM prefix, default to HSM.

Explanation: An examination of the tape data setname has failed to find a prefix to use to assign HSMalias names.

User response: The prefix of HSM. will be used as adefault.

AKD36514W EODAD reached, Audit status not open

Explanation: The tape encountered EOD on an OPENor POSITIONING.

User response: Audit continues.

AKD36515W CC LL ECB read warning, ECB list

Explanation: A read error was detected on the tape.The CC represents the completion code and LLrepresents one of ten possible read commands the badread occurred in. Usually the CC is 48, whichrepresents a bad length block. When this is the case,end of data is assumed and normal terminationprocesses are invoked.

User response: Audit terminates normally.

AKD36502E • AKD36515W


AKD36516I nnnnnnnn Blocks audited

Explanation: After every 200,000 blocks read, thismessage is issued. It is for progression purposes. Sincetapes can contain over ten million blocks and the jobcan take several hours to complete, this messageprovides a convenient method of following the progressof the audit.


AKD36517E xxxx A bad length block has beenfound

Explanation: Each block on the tape should be 16k inlength. If the tape read process encounters a length thatis not this size, it indicates the integrity of the data ontape has been compromised.

User response: Auditing is terminated.

AKD36518W *CDD** Missing after skip ahead

Explanation: Audit options FAST and THOROUGHskip over blocks for a number of blocks dictated by theblock count in the TTOC. An expected data set name issearched. In this case the eye catcher CDD is not foundso the data set can not be examined.

User response: Auditing is changed to INTENSE andauditing continues.

AKD36519W Audit changed to INTENSE process

Explanation: When navigating through the tape anexpected data set name represented by the CDD eyecatcher was not found. This means the informationabout the data on the tape can not be used. The tape isback-spaced to the last good position and every blockof data is read for the remainder of the audit.


AKD36520I SYNAD exit entered

Explanation: A SYNAD exit has been entered onbehalf of the tape IO process.

User response: The processed is returned toterminate normally.

AKD36521E CCC RR DCB Abend exit entered

Explanation: An abend has occurred where CCC isthe abend code and RR is the reason code. This abendis trapped but the DCB abend exit related to the HSMtape that is being processed.

User response: The status of the audit is examinedand reported. Depending on the status of the abend,normal termination is attempted otherwise the abendcontinues.

AKD36522I Audit completed OPEN

Explanation: The tape file has been successfullyopened.

User response: Information only.

AKD36523I Tape EOD detected

Explanation: The tape file has been read and the endof data condition has been detected. This means thetape has been read as far as possible. Any diagnosticsfor the audit will be valid.


AKD36524I Audit files closed

Explanation: All files except the tape file have beenclosed successfully.


AKD36525I Audit errors sorted

Explanation: All data sets found on the tape havebeen sorted successfully.


AKD36526I Tape file close issued

Explanation: A close to the tape file has been issued.


AKD36527I Tape file close succeeded

Explanation: A close to the tape file has beensuccessful.


AKD36528W Abend is being ignored

Explanation: After examining the abend condition ithas been determined that processing may continue.

User response: Return to normal processing is taken.

AKD36529E Abend cannot be ignored, abendcontinues

Explanation: After examining the abend condition ithas been determined that further processing isimpossible.

User response: Return to continue the abendprocess.

AKD36516I • AKD36529E

58 User's Guide

AKD37501E Unable to decode execution parm

Explanation: The parm was examined but theprogram could not decode it.

User response: Check cataloged procedure forruntime parm.

AKD37502E Invalid QLIMIT value. Limit parmexceeds seven digits

Explanation: The QLIMIT parm is invalid. Parmexceeds seven digits.

User response: Check the QLIMIT parm.

AKD37503E No prefix given at Exec parm

Explanation: To properly create the FIXTTOC dataset, a user prefix is needed for the target ODS data setname. This prefix is passed through the executionparameter of AKD10375. This message is issued whenthe parm is missing.

User response: Correct the runtime parameter.

AKD37901E Function passed is invalid, xxxxxxxxshould be OPEN, CLOSE or FIXCDS

Explanation: The parm was examined but theprogram could not decode it.

User response: Check cataloged procedure forruntime parm.

AKD38501E VSAM open error, process ended

Explanation: VSAM open encountered a problemduring open processing.


AKD38502E INPUT open error, process ended

Explanation: INPUT open encountered a problemduring open processing.


AKD38503E OUTPUT open error, process ended

Explanation: OUTPUT open encountered a problemduring open processing.


AKD38701E Failed to find proper format

Explanation: The PLAN formatter moduleencountered a format problem.

User response: Check the PLAN for properformatting.

AKD38702W Call to AKD07863 PUTX failed

Explanation: The formatter module encountered anerror during a PUTX function.

User response: Check sysout messages for theadditional messages issued by the formatter module.

AKD38703E Failed to write reformatted record

Explanation: The formatter module encountered anerror during a PUT function.

User response: Check sysout messages for theadditional messages issued by the formatter module.

AKD39701E Unable to obtain information aboutdsname

Explanation: A dsname was passed to this modulebut the module was unable to obtain any informationabout it.

User response: Audit terminates.


Explanation: The first block read failed. Furtherauditing is not possible.

User response: Auditing is terminated.

AKD39703W xxxx Point was no good

Explanation: A POINT command to block xxxx failed.


AKD39704W BBBB Read failed at this block

Explanation: A read was attempted at block BBBB.The wait ECB code was A.


AKD39705W Passed block contain zeros

Explanation: The block which was read containszeros.


AKD39901E xxxxxxxx Open failed for ddname

Explanation: The ddname xxxxxxxx failed to open.

User response: Check JCL for spelling of CDS orcorrect splits.

AKD37501E • AKD39901E


AKD70301E Allocation was unsuccessful

Explanation: The generalized allocation routineencountered an error while attempting to allocate adataset.

User response: Contact Support.

AKD70302E Unallocation failed

Explanation: The generalized allocation routineencountered an error while attempting to unallocate adataset.


AKD70303I Unallocation was good

Explanation: The generalized allocation routinesuccessfully unallocated the dataset.


AKD70501E Audit type missing

Explanation: Authorization processing has detectedthat the audit type parameter statement for this jobstepis missing.

User response: Check that the appropriate audit typeparameter is coded on the execution statement for thisjobstep.

AKD70502E xxxxxxxx Support Module Missing.

Explanation: Identified module is not in the loadlibrary.


AKD70503E xxxx is an invalid auth Parm

Explanation: Authorization processing has detectedthat the audit type parameter statement for this jobstepis invalid.


AKD70504E Unable to initialize INI

Explanation: During program start, one or moreproblems occurred during decoding of the //INI member.As the //INI provides vital information for this product,the program cannot continue execution.

User response: Contact Support. Have available thelisting that contains this message and the PARMLIBmember that controls execution of this product.

AKD70505E No CONTROL DD statement

Explanation: The program tried to determine whatkind of tape is being audited but was unable to openthe control dataset.


AKD70506E The LOADLIB is not authorized. Theaudit will terminate.

Explanation: The LOADLIB library is not added toAPF list.

User response: Use the SETPROG APF command toadd library to APF list or contact your systemadministrator.

AKD70701I HSM audits are enabled



AKD70901I DASD audits are enabled



AKD71101I Tape audits are enabled



AKD71301I Catalog audits are enabled



AKD71501I Audit MEDIACONTROLS audits areenabled



AKD71701E Read JFCB failed on member list

Explanation: An attempt to open the member list forthe messages PDS failed.


AKD71702E Open of MESSAGE member failed

Explanation: An attempt to open a message memberin the messages PDS failed.


AKD70301E • AKD71702E

60 User's Guide

AKD71703E Open for MSGDIR failed

Explanation: An attempt to open the DDNAMEMSGDIR failed.


AKD72302E xxxxxxxx close failed

Explanation: Program processing was unable to closethe DFHSM Control Dataset.


AKD72702E Read of extension failed

Explanation: An attempt was made to read the nextextension of a data set.


AKD72703E Bad primary computation

Explanation: The program encountered a problemwhen try to compute the total number of primaryallocation trks of the ds.


AKD72901E xxxxxxx had bad function call

Explanation: The function code passed to programprocessing was inaccurate.



Explanation: The universal formatter routine did notsuccessfully write out the record passed to it.


AKD73103E xxxx was the return code from formatroutine.



AKD73104E failed to process the JCL data set

Explanation: The rdjfcb on the jcl file failed.


AKD73105E xxxxxxxx with this plan member

Explanation: xxxxxxxx is the plan member whichaccess failed.


AKD73106E failed to find proper format

Explanation: The function passed to the universalformatter was not found.


AKD73107E XXXXXXXX failed to find prescribed fix

Explanation: PLANS dataset open processing failed;xxxxxxxx is the name of the fix member.


AKD73108E XXXXXXXX close failed processing fix

Explanation: PLANS dataset close processing failed;xxxxxxxx is the name of the fix member.


AKD73109E failed to process PLANS JFCB

Explanation: PLANS dataset rdjfcb processing failed.


AKD73110E Bad untranslated record

Explanation: The universal formatter failed to put jclrecord.


AKD73301E Selection of fixes failed

Explanation: Selection of fix from INI member failed.





AKD73303E xxxx was the return code from formatroutine.



AKD73304E failed to process the JCL data set

Explanation: The rdjfcb on the jcl file failed.


AKD71703E • AKD73304E


AKD73305E xxxxxxxx with this plan member

Explanation: xxxxxxxx is the plan member whichaccess failed.


AKD73306E failed to find proper format

Explanation: The function passed to the universalformatter was not found.


AKD73307E XXXXXXXX failed to find prescribed fix

Explanation: PLANS dataset open processing failed;xxxxxxxx is the name of the fix member.


AKD73308E XXXXXXXX close failed processing fix

Explanation: PLANS dataset close processing failed;xxxxxxxx is the name of the fix member.


AKD73309E failed to process PLANS JFCB

Explanation: PLANS dataset rdjfcb processing failed.


AKD73310E Bad untranslated record

Explanation: The universal formatter failed to put jclrecord.








AKD74302E xxxxxxxx close failed

Explanation: A VSAM close was attempted but failed.The DDNAME is xxxxxxxx.


AKD74501I pppppppp ffffffff trace SELECTs

Explanation: Informational message. pppppppp is theplan and ffffffff is the fix.


AKD74502E pppppppp dddddddd member inDDNAME failed

Explanation: The plan pppppppp in DDNAMEdddddddd has failed.

User response: Examine the plan and ensure correctformatting.

AKD74902E xxxxxx Volume not found in system

Explanation: UCBSCAN unable to locate the volumexxxxxx.

User response: Check that the volume is online andavailable.

AKD74903E had a bad UCBSCAN

Explanation: UCBSCAN encountered an error.

User response: Check the UCBSCAN messages.Correct and resubmit.

AKD75101E Format 3 DSCB READ FAILED

Explanation: An attempt to read the Format 3 DSCBfailed.


AKD75301E xx Excessive TIME parameter passed

Explanation: A TIME parameter was passed to thisprogram and its value is greater than 59.

User response: Check the parameter and insure it isbetween 10 and 59 inclusive.

AKD75302I Setting 59 seconds as default



AKD73305E • AKD75302I

62 User's Guide

AKD75303E Excessive TIME parameter passed

Explanation: A TIME parameter was passed to thisprogram and its value or format is not proper. Makesure the parameter is a value between 10 and 59inclusive.

User response: Check the parameter and insure it isbetween 10 and 59 inclusive.

AKD75304E Setting 10 seconds as default



AKD75701E Unknown function requested

Explanation: An unknown function was passed to theprogram. The function must be END, FIND, BUILD orIDCAMS.

User response: Check the parameter being passed.Insure it is one of the values in the list.

AKD75702E Active SI27 table failed to close

Explanation: A function of EOD was passed to theprogram signaling the program to close the table. Theclose failed.


AKD75901E AMSOPEN failed

Explanation: An open to Access Method ServicesFailed.


AKD75902E nnn message number sent fromAKD07759

Explanation: An AMS message number nnn is issued.


AKD76701I xxxxxxxxxx processing option

Explanation: xxxxxxxxxx is the processing option.

User response: Informational only.

AKD76703W Non-VSAM found for catalog

Explanation: A non-VSAM data set was found for acatalog.

User response: Processing continues.

AKD76704E xxx CAT number allocation failed

Explanation: Audit retrieves a list of catalogs to readfrom the Master Catalog. Each catalog name isassigned a number. In this instance the catalog couldnot be allocated. This may be a defunct catalog orotherwise legitimately not processable.

User response: Browse data set PFX.AUDIT.CATLISTto determine the name of the catalog by the specifiednumber. If this catalog is no longer in use this messagemay be ignored.

AKD76705E xxx CAT number obtain failed

Explanation: The catalog extraction module attemptsto verify that a catalog is on the volume it is catalogedto. In this instance the user catalog was not on thevolume it was cataloged to.


AKD76706E xxx bad return, catalog abandoned

Explanation: Catalog extraction has found a catalogname in the Master Catalog but was unable to list itscontents.


AKD76711I xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAllocate good

Explanation: The allocate for catalog xxxx wassuccessful.

User response: Informational message.







AKD75303E • AKD76903E








AKD77101E LOCATE failed for master catalog

Explanation: The catalog extraction module attemptedto retrieve information from the master catalog but couldnot find it.

User response: Browse data set PFX.AUDIT.CATLISTto determine the name of the Master Catalog indicatedby a flag of M.

AKD77701E xxxxx function failed

Explanation: The function passed to this programxxxxx, is unknown. It should be OPEN, CLOSE, or GET.


AKD78101W bad repl

Explanation: An attempt was made to replace the key,but failed.


AKD78102W Node count update had blank key



AKD78103W Node count update had a 000 key



AKD78104W Node count update had B FFF key



AKD78105E xxxxxxxxxx was bad repl key

Explanation: A replace was attempted with keyxxxxxxxxxx but it failed.


AKD78301E xxxxxxxxxx was bad repl key

Explanation: A replace was attempted with keyxxxxxxxxxx but it failed.


AKD80301E INCLUDE/EXCLUDE option ambiguous

Explanation: The include/exclude processor found anoption it could not interpret.

User response: The first line in the Include/Excludefile must be either INCLUDES FOLLOW or EXCLUDESfollow.

AKD80302E xxxxxxxx



AKD80303E xxxxxxxx was incorrect

Explanation: The ACS filter pattern was found to beincorrect.

User response: Check the ACS filter pattern.

AKD80501E INCLUDE/EXCLUDE option ambiguous



AKD80502E xxxxxxxx



AKD80503E xxxxxxxx was incorrect

Explanation: The ACS filter pattern was found to beincorrect.

User response: Check the ACS filter pattern.

AKD76904E • AKD80503E

64 User's Guide

AKD80902I xxxxxxxx

Explanation: The first issue of the message is thecatalog name that failed to open. Audit attempts toverify any diagnostic related to the catalog by verifyingthat the error condition still exists. It does so byallocating and individual catalog and reading each entryby key. If a catalog can not be allocated and opened,then verification will be performed by SVC 26. This cancause a very long run time.

User response: It could be that a reorg or backupEXPORT was being performed. It may be better torerun the audit than to wait for the verifications tocomplete. Make sure that maintenance activities arecomplete on the catalogs and resubmit the audit.

AKD80902I Failed to allocate, verify by SVC 26

Explanation: The first issue of the message is thecatalog name that failed to open. Audit attempts toverify any diagnostic related to the catalog by verifyingthat the error condition still exists. It does so byallocating and individual catalog and reading each entryby key. If a catalog can not be allocated and opened,then verification will be performed by SVC 26. This cancause a very long run time.

User response: It could be that a reorg or backupEXPORT was being performed. It may be better torerun the audit than to wait for the verifications tocomplete. Make sure that maintenance activities arecomplete on the catalogs and resubmit the audit.

AKD81101W VOL GT 125

Explanation: The number of volumes has exceeded125.

User response: Informational message. Processingcontinues.













AKD84501E TMSVOL replace failed, critical error

Explanation: An attempt to replace a record with thecatalog indicator switch failed.


AKD85901E R15 is lost, has zeroes

Explanation: Unable to determine appropriate label.

User response: Next label is processed. Processingcontinues.

AKD85902E xxxxxxxx label not found

Explanation: Label xxxxxxxx was not found.


AKD86101E Values in line will exceed 255characters

Explanation: The limit of 255 character per line hasbeen reached. The line will be truncated.


AKD86102E label search ended prematurely

Explanation: A search for a label ended prematurely.


AKD86103E xxxxxxxx not found

Explanation: The label with key xxxxxxxx was notfound.


AKD80902I • AKD86103E


AKD86104E premature end reached at INCR2

Explanation: Progression message.


AKD86105E xxx recomputed line length



AKD86301E Found improper parameters

Explanation: The processing program is unable tocontinue. The program was unable to find a properparameter.


AKD86302E xxxxxxxx DDNAME not found

Explanation: The DDNAME xxxxxxxx was not found.Insure JCL has this DDNAME coded.


AKD86303E failed to find dictionary member

Explanation: The dictionary member was not found inthe PDS.


AKD86304E Dictionary failed to open

Explanation: Unable to open the dictionary member.Review the dictionary name for proper spelling.

User response: If dictionary name is correct andpresent in the PDS, then contact support.

AKD86306E bad return from format

Explanation: A call to the format routine received anon-zero return code. A message stating the number ofrecords processed follows.


AKD86307E xxxxxx was number of recordsprocessed

Explanation: A call to the format routine received anon-zero return code. This message states the numberof records that were processed.


AKD86501E xxxxx was invalid function

Explanation: An invalid function name was given.

User response: Supply a valid function name ofOPEN, CLOSE or GET.




AKD90501I xxxxx is number of indices to print



AKD90503I xxx xxxxxxxx is counted blocks/track



AKD90504I xxx xxxxxxxx was calculatedblocks/track



AKD90505I xxxxx LL x blocks/track



AKD90506I xxxxx last block on track



AKD90507I xxxxx xxxxxxxxxx Max blocks in table



AKD90508I xxxxx xxxxxxxxxx is kenlen+4



AKD90509I xxxxx xxxxxxxxxx max index



AKD86104E • AKD90509I

66 User's Guide

AKD90510I xxxxx xxxxxxxxxx is increment



AKD90511I xxxxxxxx assigned xxx buffers



AKD90512I xxx was binary index table



AKD90512E XXXXXXXX empty file

Explanation: DDNAME of xxxxxxxx is an empty file.

User response: Abend 1111 occurs. Contact support.

AKD90512I xxxxxxxx FKEY last block



AKD90513I xxxxxxxx xxxxxxxx Length of last block



AKD90514I xxxxxxxx LKEY EOD



AKD90515I xxxxx xxxxxxxx was the index count



AKD90516I xxxxxxxx was index key



AKD90701I XXXX end at relative block



AKD90702I XXXX end at max blocks



AKD90703I XXXXXXXXXXXXXXX XXXXX MAXBLKSkey of ARG



AKD90704I xxxxx xxxxxxxxxxxxxxx THISBLK LASTKIN BUF



AKD90705I is last block length



AKD90901E Buffer inventory has been overlaid

Explanation: There has been a problem in buffermanagement. Abend 130 follows.


AKD90902E 140 FOUND AT GOLOW

Explanation: A condition has been found at locationGOLOW.


AKD91001I was number of index read

Explanation: Displays the number of index recordsread.

User response: Informational message.

AKD91002E lost in back

Explanation: This message is issued when theprogram encounters a situation it can not recover from.An abend follows.


AKD91002E lost searching by 1



AKD90510I • AKD91002E


AKD91002E lost in next



AKD91701I Loading SUB MODULES


User response: None. Processing continues.

AKD91702E Dynamic table is exhausted

Explanation: The end of the table has been reached.A return code of 12 has been issued.


AKD91703E Allocation of CATIN001 was bad

Explanation: Allocation failed.


AKD91704E Deallocation of CATIN001 was bad

Explanation: Deallocation failed.


AKD91901E xxxx failed allocation

Explanation: Multivol allocation routine failed toallocate.


AKD91902E xxxxxx volume failed allocation

Explanation: Multivol allocation failed. Volume isdisplayed.


AKD91903E xxxxxx DDNAME failed ALLOC

Explanation: Multivol allocation failed. DDNAME isdisplayed.


AKD91904E xxxx DSN failed

Explanation: Multivol allocation failed. DSN isdisplayed.


AKD91905E no parms found

Explanation: No parameters were passed to theprogram.


AKD91907E Allocation was unsuccessful

Explanation: Dynamic allocation was unsuccessful.


AKD91908E Unallocation failed

Explanation: Unallocation of data set wasunsuccessful.


AKD91910I Unallocation was good



AKD92301I xxxxxxxx DSN



AKD92302I xxxxxxxx List of VOLS



AKD92303E DSN has exceeded five volumes

Explanation: While attempting to open one of theextracted files for auditing, it was determined that thefile exceeded the five volume limit. This message isfollowed by the DSN in question.

User response: The calling program will abend with auser abend. Insure the extracts do not exceed fivevolumes.

AKD92303E xxxxx

Explanation: While attempting to open one of theextracted files for auditing, it was determined that thefile exceeded the five volume limit. This message isfollowed by the DSN in question.

User response: The calling program will abend with auser abend. Insure the extracts do not exceed fivevolumes.

AKD91002E • AKD92303E

68 User's Guide

AKD92305E xxxxxxxx not cataloged

Explanation: The dataset xxxxxxxx is not cataloged.


AKD92306E DSNAME shows no volumes

Explanation: The DSNAME shows no volsers.

User response: The dataset is not cataloged. Checkthe dataset.

AKD93101E xxxxxxxx Support module missing

Explanation: Unable to load the support modulexxxxxxxx.

User response: Check the spelling or theconcatenation of the loadlib.


Explanation: An attempt was made to read the INIfile. The program was unable to initialize the INI file.

User response: Check the INI file allocated to the INIDDNAME.

AKD93301I Value of RLS parm: x

Explanation: This message displays the value of theRLS setting in the INI file.


AKD93302W RLS parm not found, default toNON-RLS

Explanation: The INI file was searched for the RLSparm setting but it was not found. The program willcontinue with the default of NON-RLS.



Explanation: The INI DD could not be opened.

User response: Check the cataloged procedure andvalidate the INI DD statement.

AKD93401I IBM AUTO FIXES are in effect

Explanation: This message declares that the IBMAUTO FIXES are in effect.

User response: None. Informational only.

AKD93402W AUTOFIX_IBM parm not found, defaultto NON_IBM

Explanation: The INI file was searched for theAUTOFIX_IBM parameter setting but it was not found.The program will continue with the default of NON-IBM.

User response: None. Auditing continues.




AKD93801I KEEP_HISTORY_DAYS = xxxx

Explanation: This message shows the value used forKEEP_HISTORY_DAYS.

User response: Informational only.

AKD93802W KEEP_HISTORY_DAYS - invalid value,used value 999

Explanation: The INI file was searched for theKEEP_HISTORY_DAYS parameter setting but it wasnot found or it is invalid. The program will continue withthe default value of KEEP_HISTORY_DAYS.


AKD93803W INI DD missing, cannot determinevalues



AKD94201W MAX_VOLUMES - not found in the INIfile

Explanation: The INI file was searched for theMAX_VOLUMES parameter setting but it was not foundor it is invalid. The program continues with the defaultvalue of MAX_VOLUMES.


AKD94202W MAX_VOLUMES - xxxx invalid value,used value 5

Explanation: The INI file was searched for theMAX_VOLUMESparameter setting but it was not foundor it is invalid. The program continues with the defaultvalue of MAX_VOLUMES.


AKD92305E • AKD94202W


AKD94203W INI DD missing, cannot determinevalues



AKDI0101W AKD already active in this session.AKD can only be entered once within asession.

Explanation: An attempt was made to enter AKDmore than once (by invoking the CLIST AKDSTART) atthe same time.

User response: Use the active session of AKD.Contact Technical Support for further assistance.

AKDI0102E The AKD address space is either notactive or has not completed initializing.

Explanation: The AKD address space (programAKDAM001), must be active on the system to makerequests to AKD.

User response: Start the AKD address space. SampleJCL can be found in member AKDJMAIN. ContactTechnical Support for further assistance.

AKDI0104E Error retrieving Name/Token pair, Rc=rcName='name'

Explanation: An attempt to retrieve the Name/Tokenpair of name failed with a return code of rc.

User response: Exit AKD completely and attempt tore-enter the product to retry the request. ContactTechnical Support for further assistance.

AKDI0105W Access to AKD data restricted

Explanation: Access to AKD has been restricted.

User response: Contact Technical Support for furtherassistance.

AKDM0001W Non-Zero Return Code from program.Rc=rc, Rs=rs, SubRs=srs

Explanation: A Non-Zero return code was receivedfrom program. The return rc and reason codes rs, srsare listed.

User response: Review other messages received withthis message for a further explanation of the error.Contact Technical Support for further assistance.

AKDM0002W Non-Zero Return Code from functionfunc. Rc=rc, Rs=rs, SubRs=srs

Explanation: A Non-Zero return code was receivedfrom function func. The return rc and reason codes rs,srs are listed.

User response: Review other messages received withthis message for a further explanation of the error.Contact Technical Support for further assistance.

AKDM0003W Task is not running APF authorized

Explanation: The current started task or batch job isnot running with APF authorized libraries.

User response: Verify that all libraries listed inSTEPLIB are APF authorized and rerun process.Contact Technical Support for further assistance.

AKDM0004S multiple possible messages listed below

Explanation: Unable to obtain storage, Rc=rc,Length=len, Key=key, Subpool=sp

or

Unable to obtain storage, 64-bit memory objects notavailable.

or

Unable to obtain memory objects, Rc=rc, Rs=rs,Length=len, Key=key

AKD was unable to obtain storage during one or moreof its processes.

User response: Review the message, increase theRegion size or MEMLIMIT, if appropriate, and rerunprocess. Contact Technical Support for furtherassistance.

AKDM0005W multiple possible messages listed below

Explanation: Error releasing storage, Rc=rc,Address=adr, Length=len, Subpool=sp, Key=key

or

Unable to release storage, Rc=rc, Address=adr,Length=len, Subpool=sp, Key= key

or

Unable to release memory objects, Rc=rc, Rs=rs,Token=tok

or

Unable to release memory object, Rc=rc, Rs=rs,Address=adr

AKD was unable to release storage during one or moreof its processes.

User response: Contact Technical Support if thispersists.

AKD94203W • AKDM0005W

70 User's Guide

AKDM0006I A product release started task is alreadyactive in this system.

Explanation: An AKD started task is already runningon this system. Only one copy of the AKD started taskcan be active on a system at a time.


AKDM0007W Unable to setup recoveryenvironment...Rc=rc

Explanation: Abend recovery was not established.

User response: Review messages for moreinformation Contact Technical Support for furtherassistance.

AKDM0008W Unable to remove recoveryenvironment...Rc=rc

Explanation: The abend recovery environment couldnot be removed.

User response: Review messages for moreinformation. Contact Technical Support for furtherassistance.

AKDM0010I product release initialized on sysname

Explanation: This message indicates the productname productand release level releaseof the currentprocess that has successfully initialized on systemsysname.

User response: None required.

AKDM0011W Error loading module 'mod' , Rc=rc,Rs=rs, SubRs=srs

Explanation: Module mod was unable to be loaded.The return rc and reason codes rs srs providediagnostic information about the failures.

User response: Attempt to rerun the process thatfailed. Contact Technical Support for further assistance.

AKDM0012S Error matching pattern, Rc=rcMsg=msg | Pattern='pattern' |String='string'

Explanation: An error occurred while trying to match apattern pattern with a string string.

User response: Refer to msg, pattern, and string todetermine the error. Attempt to correct the error andrerun the process. Contact Technical Support for furtherassistance.

AKDM0013I product release stopped on sysname

Explanation: This message indicates the productname product and release level release of the currentprocess that has stopped on system sysname.


AKDM0014I product release starting on sysname

Explanation: This message indicates the productname product and release level release of the currentprocess that is attempting to start on system sysname.


AKDM0015I product release terminating on sysname

Explanation: This message indicates the productname product and release level release of the currentprocess that is terminating on system sysname.


AKDM0016W Unable to deallocate DD 'dd', R15=rc,S99ERROR=err, S99INFO=info

Explanation: An error occurred while trying todeallocate dd from the current task.

User response: Look in MVS Programming:Authorized Assembler Services Guide under RequestingDynamic Allocation Functions. Use rc, err, and info toanalyze the error that occurred. Contact TechnicalSupport for further assistance.

AKDM0017I text

Explanation: This message will appear with othermessages.

User response: Refer to other messages that appearwith this message for more information. ContactTechnical Support for further assistance.

AKDM0018W Unable to allocate DD 'dd' | DSN 'dsn',R15=rc, S99ERROR=err, S99INFO=info

Explanation: An error occurred while trying to allocatedd or dsn to the current task.

User response: Look in MVS Programming:Authorized Assembler Services Guide under RequestingDynamic Allocation Functions. Use rc, err, and info toanalyze the error that occurred. Contact TechnicalSupport for further assistance.

AKDM0020E Unable to locate DSAB for ddname,Rc=rc, Rs=rs

Explanation: An attempt to locate the DSAB pointerfor ddname failed with return code rc and reason coders.

AKDM0006I • AKDM0020E



AKDM0021I text

Explanation: An error occurred while trying to accessAKD data.

User response: Consult other AKD messages thatwere issued with this message for more information.Contact Technical Support for further assistance.

AKDM0022E The AKD address space is no longeravailable.

Explanation: Something has caused the AKD addressspace to no longer be available for services.

User response: Consult other AKD messages thatwere issued with this message for more information andcheck the status of the AKD address space. ContactTechnical Support for further assistance.

AKDM0023E Unable to gain control of major/minor,Rc=rc, Rs=rs

Explanation: A request to obtain control of a resource,major/minor, failed with return code rc and reason coders.


AKDM0024W Unable to release control ofmajor/minor, Rc=rc, Rs=rs

Explanation: A request to release control of aresource, major/minor, failed with return code rc andreason code rs.


AKDM0030E Unable to perform ALESERV/ADD for'name', Rc=rc

Explanation: An attempt to gain access to thespecified resource name using ALESERV failed with thereturn code rc.


AKDM0031E Unable to perform ALESERV/DELETEfor 'name', Rc=rc

Explanation: An attempt to remove the connectionbetween the current address space and the resourcefailed with return code rc.


AKDM0032E Unable to create data space, Rc=rc,Rs=rs

Explanation: An attempt to create a new data spacefailed with return code rc and reason code rs.


AKDM0033E Unable to delete data space name,Rc=rc, Rs=rs, Stoken=stoken

Explanation: An attempt to delete an old data spacefailed with return code rc and reason code rs.


AKDM0034E VGET failed, Rc=rc, Name=name

Explanation: A request to retrieve the value of anISPF variable failed with return code rc.

User response: The name of the variable can befound in name. Consult other AKD messages that wereissued with this message for more information. ContactTechnical Support for further assistance.

AKDM0035E VPUT failed, Rc=rc, Name=name

Explanation: A request to update an ISPF variablefailed with return code rc.

User response: The name of the variable can befound in name. Consult other AKD messages that wereissued with this message for more information. ContactTechnical Support for further assistance.

AKDM0036E TBADD failed for table, Rc=rc

Explanation: A request to add a row to ISPF tabletable> failed with return code rc.


AKDTRACE01I Program Entered: pgm, asm dateasm time

Explanation: This is a diagnostic message forTechnical Support use only.


AKDM0021I • AKDTRACE01I

72 User's Guide

AKDTRACE02I Program Exitted: pgm, Rc=rc, Rs=rs,SubRs=srs



AKDTRACE03I Routine Entered: routine



AKDTRACE04I Routine Exitted: routine, Rc=rc,Rs=rs, SubRs=srs



AKDX0101E cmd can only be run while in ISPF

Explanation: cmd was invoked in an environment thatdid not have ISPF services available.

User response: Enter ISPF and re-invoke cmd.Contact Technical Support for further assistance.

AKDX0102E Failure invoking command cmd ...Rc=rc

Explanation: A severe error occurred in command

cmd with a return code of rc.

User response: Review any messages that may haveappeared for more information. Contact TechnicalSupport for further assistance.

AKDX0103W AKD is not active

Explanation: The AKD primary started task (programAKDAM001) is not active.

User response: Start the AKD primary started task(program AKDAM001) and rerun process. ContactTechnical Support for further assistance.

AKDX0104E Unable to allocate file(s) to dd...Rc=rc

Explanation: Files could not be allocated to dd. rc isthe return code from TSO's ALLOCATE command.

User response: Review information on the TSOALLOCATE command and rerun process. ContactTechnical Support for further assistance.

AKDX0105E Unable to setup libraryconcatenation...Rc=rc

Explanation: Access to AKD product files could not beestablished. rc is the return code from either ALTLIB orLIBDEF.

User response: Review information onALTLIB/LIBDEF and rerun process. Contact TechnicalSupport if this persists.

Audit Diagnostic Messages

11D1C MCD ENTRY IS NOT CATALOGED

Explanation: Audit Suite has compared the MCDSMCD extraction against the Catalog extraction and hasfound an MCD entry with no catalog entry. When thiscondition occurs, Audit Suite verifies the catalog statusby doing a direct catalog lookup.

User response:

The recommended default fix is F11D1CA TSOCATALOG A MIGRATED DATASET TO VOLSERMIGRAT

Field # Description EXAMPLEField 1 Error number 11D1CField 2 dsname BMOHN.ISPF.ISPPROFBField 3 HSM Generated name HSM.HMIG.T350200.dsnField 4 HSM VOLSER HM0069Field 5 VSAM/NVSAM NField 6 HSM Level 2

11D2C MCD ENTRY IS CATALOGED ONDIFFERENT VOLUME

Explanation: Audit Suite has compared the MCDSMCD extraction against the Catalog extraction and hasfound an MCD entry but the catalog indicates that the

data set is on a volume other than MIGRAT..

User response:

The recommended default fix is F11D2CC HSMFIXCDS DELETE OF A AND D RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 11D2CFIELD 2 DSNAME IPO1.PPROCLIBFIELD 3 HSM GENERATED NAME HSM.HMIG.T080300.dsnFIELD 4 HSM VOLSER HM0124FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 2FIELD 7 CATALOGED VOLSER MVSCTAFIELD 8 CATALOG NAME UCAT.TECH

11V1C MCO VSAM COMPONENT IS NOTCATALOGED

Explanation: Audit Suite has compared the MCDSMCO extraction against the Catalog extraction and hasfound an MCO VSAM component with no catalog entry.When this condition occurs, Audit Suite verifies thecatalog status by doing a direct catalog lookup. WhenDFSMShsm migrates a VSAM cluster it creates anMCO record and an MCA record for the cluster'scomponents. Each component 'looks like' a single

AKDTRACE02I • 11V1C


migrated data set but it really isn't. Reference to theMCO entry is required any one of the components isreferenced.

User response:

The recommended default fix is F11V1CA TSOCATALOG A MIGRATED DATASET TO VOLSERMIGRAT

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 11V1CFIELD 2 CLUSTER NAME USERID.VSAM.CLUSTERFIELD 3 COMPONENT NAME USERID1.VSAM.DATAFIELD 4 HSM GENERATED ALIAS HSM.HMIG.T352004.dsn

11V2C MCO VSAM COMPONENT ONDIFFERENT VOLUME

Explanation: Audit Suite has compared the MCDSMCO extraction against the Catalog extraction and hasfound an MCO entry but the catalog indicates that theVSAM component is on a volume other than MIGRAT.

User response:

The recommended default fix is F11V2CF HSMGENERATE FIXCDS DELETE FOR CONFLICT MCOAND MCD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 11V2CFIELD 2 CLUSTER NAME USERID.VSAM.CLUSTERFIELD 3 COMPONENT NAME USERID1.VSAM.DATAFIELD 4 VOLSER FROM CATALOG TSO002FIELD 5 HSM GENERATED NAME HSM.HMIG.T472104.dsnFIELD 6 CATALOG NAME UCAT.TECH

1103W MCD ENTRY IS MISSING THE MCAENTRY

Explanation: Audit Suite has compared the MCDSMCD extraction against the MCDS MCA extraction andhas found an MCD entry but the MCA entry is missing.Although information in the MCA is not used duringrecall, it may be an indicator of the health of the MCDSinventory. A missing MCA can cause recycle to run veryslowly because recycle must verify missing MCAentries.

User response:

The recommended default fix is F1103WC HSMFIXCDS CREATE NEW MCA RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1103WFIELD 2 DSNAME DRS.ICS91102.CLISTFIELD 3 HSM GENERATED NAME HSM.HMIG.T472104.dsnFIELD 4 HSM VOLSER HM0017FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 2

1104C MCD LEVEL 1 ENTRY HAS NO VTOCENTRY ON L1 VOLUME

Explanation: Audit Suite has compared the MCDSMCD ML1 extraction towards the DFSMShsm ML1volume DCOLLECT extraction and has found an MCDentry but no VTOC entry. Audit Suite verifies this bydoing an OBTAIN against the volume in question.

User response:

The recommended default fix is F1104CC HSM FIXCDSCOMMAND TO DELETE DSN MISSING ML1 VOL

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1104CFIELD 2 DSNAME XXX.XXXXXXXX.DSNFIELD 3 HSM GENERATED NAME HSM.HMIG.T433206.dsnFIELD 4 HSM VOLSER HSM001FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 1

1105W MCD VSAM BASE IS MISSING IN MCO

Explanation: Audit Suite has compared the MCDSMCD extraction towards the DFSMShsm MCOextraction and was unable to find an MCO entry thatcontains the Base Cluster Name associated with theVSAM data set. The data set can probably be recalledbut this might be a health indicator of the VSAMinventory. Typically, VSAM components are not recalledindependent of the cluster name; however, if they are,the recall might fail. Also note that this is a normalcondition for multiple AIX VSAM files.

User response:

There is no recommended default fix.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1105WFIELD 2 DSNAME DSN.VSAM.CLUSTERFIELD 3 HSM GENERATED NAME HSM.HMIG.T233206.dsnFIELD 4 HSM VOLSER MIGR01FIELD 5 VSAM/NVSAM VFIELD 6 MIGRATION LEVEL 1

1106C MCD IS ON VOLUME WHICH HAS NOMCV ENTRY

Explanation: Audit Suite has compared the MCDSMCD extraction towards the DFSMShsm MCVextraction and has found an entry for a migrationvolume that is no longer managed by DFSMShsm. Thisis a critical error; the data set can't be recalled. See1106V for a summary of the volumes with this condition.

User response:

See Default fix for related 1106V diagnostic.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1106CFIELD 2 DSNAME DSN.NOMCV.DSNFIELD 3 HSM GENERATED NAME HSM.HMIG.T433206.dsn

11V2C • 1106C

74 User's Guide

FIELD 4 HSM VOLSER MIGR01FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 1

1106V SUMMARY OF VOLUMES HAVING NOMCV ENTRY

Explanation: This error is a summary by volumes oferror 1106C. Research of this problem is easier to do ata volume level. Supporting fixes and interrogations at avolume level is supplied for this error.

User response:

The recommended default fix is F1106VA HSM FIXCDSCOMMAND TO VERIFY MISSING MCV RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1106VFIELD 2 VOLSER HM0061FIELD 3 TAPE TYPE L2FIELD 4 DSN NUMBER 000009

1107V SUMMARY OF VOLUMES MISSING INTTOC

Explanation: This error is a summary by volumes oferror 1107W. Research of this problem is easier to do ata volume level. Supporting fixes and interrogations at avolume level is supplied for this error.

User response:



1107W MCD LEVEL 2 IS ON VOLUME WHICHHAS NO TTOC ENTRY

Explanation: Audit Suite has compared the MCDSMCD extraction (Level 2) against the HSM OCDS(TTOC) extraction and has found an entry for a volumethat is not in the TTOC inventory. In other words, theroot entry for the volume is not in the OCDS. The TTOCinformation is not used for Recall, however, these errorsmay reflect the general health of the HSM environment.For example: This error would indicate possible lostdata if the tape volume had been returned to scratchstatus. See error message 1107V for a summary ofvolumes with this condition.

User response:

See Default fix for related 1107V diagnostic.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1107WFIELD 2 DSNAME XAS.IXPV3R2.LOADFIELD 3 HSM GENERATED NAME HSM.HMIG.T040202.dsnFIELD 4 HSM VOLSER HM0348FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 2

1108W MCA ENTRY IS MISSING MCO VSAMCOMPONENT ENTRY

Explanation: When auditing the MCA extractionagainst the MCD extraction, a VSAM component namewas found but the cluster name was missing. This is nota critical error for Recall but if there are many of these,it indicates that the MCDS inventory may be corrupted.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1108WFIELD 2 VSAM CUSTER NAME DRS.ICS91102.CLUSTERFIELD 3 VSAM COMPONENT NAME DRS.ICS91102.DATAFIELD 4 HSM VOLSER UNKFIELD 5 VSAM/NVSAM VFIELD 6 HSM LEVEL U

1109V SUMMARY OF VOLUMES WHEREALIAS IS NOT IN TTOC


User response:

Run the AUDIT MEDIACONTROLS for completeanalysis.


1109W MCD ALIAS IS NOT ON TTOC

Explanation: Audit Suite has compared the MCDSMCD extraction (Level 2) against the HSM OCDS TTOCextraction and has been unable to find a matching HSMgenerated alias name in the TTOC. HSM does not usethe TTOC information during Recall but these errorsmay indicate a general health problem in the HSMenvironment. This can also be the result of anincomplete TTOC update resulting from an HSMABEND or system crash or an IPL over a working HSM.This problem will impact the tape recycle process.

Note: Audit Suite does not verify these errors in realtime. If recycle was running while the audit wasextracting information, these errors may beerroneous. For best results, make sure recycle isnot running at the same time as Audit Suite.

User response:

Run the AUDIT MEDIACONTROLS for completeanalysis.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1109WFIELD 2 DSNAME DRS.ICS91102.CLIST

1106V • 1109W


FIELD 3 HSM GENERATED NAME HSM.HMIG.T472104.dsnFIELD 4 HSM VOLSER HM0017FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 2

1110W MCD HAS DUPLICATE MCA ENTRY

Explanation: Audit Suite has scanned the MCDSMCD alias names for duplicate names. This conditioncan happen on CPUs when the alias name isgenerated. It is possible that the data set can not berecalled.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1110WFIELD 2 DSNAME DRS.ICS91102.CLISTFIELD 3 HSM GENERATED NAME HSM.HMIG.T472104.dsnFIELD 4 HSM VOLSER HM0017FIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL 2

1111W MCA ENTRY IS MISSING MCD ENTRY

Explanation: Audit Suite has compared the MCDSMCA extraction against the MCDS MCD extraction andhas been unable to find a matching MCD true name.These errors will cause recycle of tapes to fail. In thefield explanations below, the MCA has no VOLSERinformation and no HSM level information. Therefore,field 4 and field 6 values are unknown.

User response:

The recommended default fix is F1111WC HSM FIXCDSDELETE ORPHANED MCA RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1111WFIELD 2 DSNAME TEST.MA.MA0525EDFIELD 3 HSM GENERATED NAME HSM.HMIG.T582104.dsnFIELD 4 HSM VOLSER UNKFIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL U

1112W MCO VSAM BASE NAME IS MISSINGIN MCD

Explanation: Audit Suite has compared the MCDSMCO extraction against the MCDS MCD extraction andhas been unable to find a matching VSAM Base name.This means that the MCO entry is orphaned and shouldbe deleted.

User response:

The recommended default fix is F1112WA HSM FIXCDSO DELETE FOR ORPHANED MCO RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1112WFIELD 2 VSAM BASE NAME MCO.BASE.CLUSTERFIELD 3 VSAM COMPONENT MCO.BASE.DATAFIELD 4 MCO ALIAS NAME HSM.HMIG.T473100.dsn

1113W MCO VSAM COMPONENT NAME ISMISSING IN MCA

Explanation: Audit Suite has compared the MCDSMCO extraction against the MCDS MCA extraction andhas been unable to find a matching VSAM component.This means that the MCO entry is orphaned and shouldbe deleted.

User response:

The recommended default fix is F1113WB HSMFIXCDS DELETE OF MCO RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1113WFIELD 2 VSAM BASE NAME MCO.BASE.CLUSTERFIELD 3 VSAM COMPONENT MCO.BASE.DATAFIELD 4 MCO ALIAS NAME HSM.HMIG.T473100.dsn

1114W ALIAS NAME EXISTS IN VTOC, MCA ISMISSING

Explanation: Audit Suite has compared the VTOCextraction against the alias name found in the MCDSrecord (as opposed to the native MCA record). WhenAudit Suite verifies the problem, an MCA record reallymight be found. When this occurs, the true name field isreplaced (usually it is unknown). However, this is still anorphaned record because the MCD (true name in HSMMCDS) doesn't match. This means that the entry in theVTOC is orphaned and should be deleted.

User response:

The recommended default fix is F1114WR1 IDCCATALOG AND DELETE ORPHANED L1 HSM ALIASW/O RECAT

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1114WFIELD 2 DSNAME UNKNOWNFIELD 3 HSM ALIAS HSM.HMIG.T070109.dsnFIELD 4 HSM VOLSER HSM003FIELD 5 HSM LEVEL 1FIELD 6 VTOC ERR NUMBER 0

1115W VTOC ALIAS NAME HAS VTOC ERROR

Explanation: Audit Suite has compared the VTOCextraction against the MCDS MCA extraction and hasdetected a Format 1 DSCB error on an ML1 volume.This means that even though the data set exists, thedata set probably can not be recalled.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1115WFIELD 2 DSNAME SOURCE.PLSTCOB2.PROGRAMSFIELD 3 HSM ALIAS HSM.HMIG.T473104.dsnFIELD 4 HSM VOLSER HSM003FIELD 5 HSM LEVEL 1FIELD 6 VTOC ERR NUMBER 1

1110W • 1115W

76 User's Guide

1116C CATALOG ENTRY HAS NO MCD/MCOENTRY

Explanation: Audit Suite has compared the catalogextraction against the MCDS MCD extraction and hasdetermined that even though the data set is cataloged,the MCD does not exist and the data set can not berecalled. These entries should be deleted from thecatalog. The data set could be recovered if a backupcopy exists.

User response:

The recommended default fix is F1116CA TSO DELETENOSCRATCH FOR MIGRAT DSNS MISSING MCD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1116CFIELD 2 DSNAME AMS.ASAMMLIBFIELD 3 HSM VOLSER MIGRATFIELD 4 CATALOG NAME UCAT.TECHFIELD 5 CREATION DATE 1999245

1117C CATALOG ENTRY IS NOT CONNECTEDTO MASTER CAT

Explanation: Audit Suite has compared the catalogextraction against the MCDS MCD extraction and hasdetermined that even though the data set is cataloged,and the MCD exists, the high level node(s) of the dataset is not connected to the master catalog and thereforecan not be recalled. This error will also be generated forany data set that is cataloged in the master catalog thatdoes not have a high level node of SYS1. Althoughthese data sets can be recalled, IBM recommends thatthe master catalog should contain only entries for usercatalogs, their aliases and system, or 'SYS1' data sets.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1117CFIELD 2 DSNAME XAS.VSAMMLIBFIELD 3 HSM VOLSER MIGRATFIELD 4 CATALOG NAME UCAT.TECHFIELD 5 CREATION DATE 2000198

1118C MIGRATED DATA SET IS MISSING INSDSP CLUSTER

Explanation: Audit Suite has compared the MCDSextraction against the Small Data Set Packing (SDSP)extraction and has determined that the data set ismissing in the SDSP VSAM cluster on the MigrationLevel 1 volume. The data set can not be recalled.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1118CFIELD 2 DSNAME PO0.CHG.QMFCERT.INUSEFIELD 3 ML1 VOLSER ML1001FIELD 4 MIG LEVEL 1

1119W ENTRY IN SDSP DATA SET IS MISSINGIN MCDS

Explanation: Audit Suite has compared the SmallData Set Packing (SDSP) extraction against the MCDSextraction and has determined that a data set is in theSDSP but has no MCD entry in the MCDS. The dataset can not be recalled.

User response:

The recommended default fix is F1119WD HSM AUDITAKD725 FOR SDSP MISSING MCD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1119WFIELD 2 DSNAME PO0.CSB.QMFCERT.INUSEFIELD 3 SDSP DSNAME HSM.SMALLDS.VML1003FIELD 4 ML1 VOLSER ML1001FIELD 5 MIG LEVEL 1

1120I TTOC VOLUME IS EMPTY

Explanation: Audit Suite has found a tape in theTTOC inventory that has no entries. This is probably notan error but if there are a large number of these it ispossible that the HSM ARCTVEXT exit for the TMS isnot working properly. This tape information is useful tointerrogate TMS to determine the DSN assigned to it. IfTMS indicates that the data set is other thanhlq.HMIGTAPE..., then there may be a conflict if HSMchooses one of these tapes to use in migration.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1120IFIELD 2 TAPE VOLUME 010018FIELD 3 TAPE TYPE L2

1121W MIGRATION LEVEL 2 VOLUME HAS NOTTOC ENTRY

Explanation: This error is similar to 1107V except thatthese volumes contain no migrated data. A tape is in theMCV inventory but no root record exists in the TTOC.The information in this error can be used to interrogateCA1 TMS and HSM TTOC information.

User response:

For further analysis of the tape, run the AUDITMEDIACONTROLS

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1121WFIELD 2 TAPE VOLUME 010018FIELD 3 TAPE TYPE L2

1122W MCD ALIAS IS OWNED BY DIFFERENTMCD

Explanation: Audit Suite has found an MCD recordwhose alias name (the MCA) record is owned by adifferent MCD.

1116C • 1122W


User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1122WFIELD 2 DSNAME SOURCE.PLSTCOB2.dsnFIELD 3 HSM ALIAS HSM.HMIG.T473104.dsnFIELD 4 HSM VOLSER HSM003FIELD 5 HSM LEVEL 1FIELD 6 VTOC ERR NUMBER 1FIELD 7 OWNING TRUENAME SOURCE.PLSTCOB2.MACROS

1123W MCA TRUENAME RECORD ISMISMATCHED

Explanation: Audit Suite has found an MCA recordwhose true name (the MCD)exists. The alias name inthe MCD record contains a different alias name. Thatalias name in turn exists and points to the MCD. Inother words, these MCA records are orphaned andshould be deleted.

User response:

F1123WB HSM FIXCDS DELETE CONFLICTING A RECORD

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1123WFIELD 2 DSNAME (FROM MCA) SOURCE.PLSTCOB2.PROGRAMSFIELD 3 HSM ALIAS (FROM MCA) HSM.HMIG.T473104.dsnFIELD 4 HSM VOLSER UNKFIELD 5 VSAM/NVSAM NFIELD 6 HSM LEVEL UFIELD 7 CORRECT ALIAS NAME HSM.HMIG.T500119.dsn

1124W VALID BLOCK COUNT IN TTOC DOESNOT AGREE

Explanation: When the customer has requestedTTOC contents verification in AKDAUDAL, AKDAUDMDor AKDAUDBD (TOPT=YES), Audit Suite counts all thevalid records in the TTOC extraction and compares it tothe original block count from the TTOC record. It reportson tapes that are ten days old or older. It then verifiesthat the record count is still off and reports this error.

User response:

F1124WB HSM FIXCDS PATCH T FOR VOL WITH MISSMATCH BLOCK COUNT

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1124WFIELD 2 TAPE VOLUME 010018FIELD 3 TAPE TYPE L2FIELD 4 COUNTED VALID BLOCKS 0000005FIELD 5 BLOCK COUNT (TTOC) 0000004-FIELD 6 COUNTED BLKS (IN HEX) 00000005FIELD 7 BLK CNT (TTOC IN HEX) FFFFFFF3FIELD 8 DATE OF TTOC UPDATE 1997266FIELD 9 DATE OF TTOC CREATE 1997252

1125W TTOC ENTRY MARKED INVALID,MCD/MCC EXISTS

Explanation: Audit Suite has compared the MCDSMCD extraction or BCDS MCC extraction against theextracted TTOC and has found DSNAMES in the TTOCthat are marked invalid but the MCD/MCC exists. Thiscan cause HSM to drop valid data if the tape isrecycled. Special fields are captured in this error toallow you to patch the TTOC to be valid. Field 5 is thehex representation of the DSNAME flags as they existin the TTOC. Field 6 is the hex representation of theDSNAME flags as they would be if patched valid. Field7 is the offset in the TTOC extension record to theDSNAME in question and Field 8 is the offset in theTTOC to the Flags byte for the DSNAME.

User response:

F1125WD HSM FIXCDS PATCH T MARK DSN VALID

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1125WFIELD 2 MIGRATION VOLUME HM02225FIELD 3 TAPE TYPE (L2, SP OR CY) L2FIELD 4 TTOC EXTENSION NUMBER 0001FIELD 5 DSNAME FLAGS (IN HEX) 00FIELD 6 DSNAME PATCH VALID (HEX) 04FIELD 7 OFFSET TO DSNAME IN TTOC 0724FIELD 8 OFFSET TO FLAG BYTE 0758FIELD 9 ALIAS NAME IN TTOC HSM.HMIG.dsnFIELD 10 TRUE NAME FROM MCD/MCC DDAVENP.ZIP.EXEC

1126I SUMMARY OF TTOC VOLUMES WITHINVALID DSNS

Explanation: Audit Suite has examined the TTOCextraction and has found volumes containingDSNAMES marked invalid. This is an unexpectedcondition since HSM no longer maintains the valid bit inthe TTOC (since HSM 2.4). This is an informationmessage and will allow you to research this condition.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 1126IFIELD 2 VOLSER HM0002FIELD 3 VOL TYPE (L2, SP OR CY) L2

2101W MCB IS CONTAMINATED

Explanation: When Audit Suite was extracting theMCB records from the BCDS it found an entry that hadthe current number of backup copies field with anegative number. The alias of the first backup entry ispresented but the remaining entries, if any, are notaudited.

User response:


1123W • 2101W

78 User's Guide

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2101WFIELD 2 DSNAME BMOHN.ISPF.ISPPROFBFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 DATE OF BACKUP 1994273FIELD 5 VSAM/NONVSAM NFIELD 6 BACKUP VERSION 001 textFIELD 7 FROMVOL V39999 text

2102W MCB HAS DUPLICATE MCC ENTRY

Explanation: Audit Suite for the BCDS has found anHSM generated alias in the MCB that is a duplicate fora different MCB. Recover for one of these data setsmight not be possible. This error is presented in twolines. Line 1 shows the true name record and thegenerated alias name. Line 2 shows the true name andthe duplicate generated alias name.

User response:


FIELD 1 ERROR NUMBER 2102WFIELD 2 DSNAME BMOHN.ISPF.CNTL.FILEFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 DATE OF BACKUP 1994273FIELD 5 VSAM/NONVSAM N

2103C MCB ENTRY IS MISSING THE MCCENTRY

Explanation: Audit Suite failed to find thecorresponding MCC (HSM generated alias name) in theBCDS. Information to recover the data set is containedin the MCC. The DSN can not be recovered.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2103CFIELD 2 DSNAME APPL1.CRITICAL.FILEFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 DATE OF BACKUP 1994273FIELD 5 VSAM/NONVSAM NFIELD 6 BACKUP VERSION 001FIELD 7 BACKUP GENERATION 02FIELD 8 PRIMARY VOLUME DVLP09

2104C MCC BACKUP TO LEVEL 1 HAS NOVTOC ENTRY

Explanation: A data set that has been backed up toan HSM Migration Level 1 volume has no VTOC entryfor the HSM generated alias name. This data set cannot be recovered.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2104CFIELD 2 DSNAME APPL1.CRITICAL.FILEFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 VOLUME SERIAL MIGR01

FIELD 5 DATE OF BACKUP 1994273FIELD 6 VSAM/NONVSAM NFIELD 7 TAPE OR DASD DFIELD 8 BACKUP VERSION 001FIELD 9 BACKUP GENERATION 03FIELD 10 TYPE OF BKUP TAPE SPFIELD 11 TTOC EXTENSION NUM 0002FIELD 12 PRIMARY VOLUME STR002

2105W DUPLICATE BACK-UP VOLUMESFOUND

Explanation: Audit has found two back-up volumeswith the same volser. This condition is rarelyencountered. It is recommended that the duplicateTTOC records be examined.

User response:

F2105WA HSM FIXCDS COMMAND TO EXAMINEDUPLICATE TTOC RECORDS

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2105WFIELD 2 VOLSER OF DUPLICATE 023455FIELD 3 TTOC TYPE SPFIELD 4 FOUND FLAG FFIELD 5 CONFLICTING VOLSER 028733FIELD 6 TTOC TYPE SPFIELD 7 FOUND FLAG N

2106C MCC IS ON VOLUME WHICH HAS NOMCT ENTRY

Explanation: A data set that has been backed up toan HSM backup volume that has no BCDS MCT record.The volume must exist in the MCT before the volumecan be mounted for recover.

User response:

See recommended fixes for 2106V

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2106CFIELD 2 DSNAME APPL1.dsnFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 VOLUME SERIAL 025346FIELD 5 DATE OF BACKUP 1994273FIELD 6 VSAM/NONVSAM NFIELD 7 TAPE OR DASD TFIELD 8 BACKUP VERSION 001FIELD 9 BACKUP GENERATION 03FIELD 10 TYPE OF BKUP TAPE SPFIELD 11 TTOC EXTENSION NUM 0002FIELD 12 PRIMARY VOLUME STR002

2106V SUMMARY OF VOLUMES MISSINGMCT ENTRY

Explanation: This error is a summary by volumes oferror 2106C. Research of this problem is easier to do ata volume level. Supporting fixes and interrogations at avolume level is supplied for this error.

2102W • 2106V


User response:

F2106VE HSM ADDVOL FOR BACKUP CYCLE TAPEF2106VG HSM ADDVOL FOR SPILL TAPE

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2106VFIELD 2 VOLSER HB0021FIELD 3 TAPE TYPE SP (text)FIELD 4 DSN NUMBER 000009 (text)

2107V SUMMARY OF VOLUMES MISSINGTTOC ENTRY


User response:

Run the AUDIT MEDIACONTROL job for these volumes


2107W MCC TAPE VOLUME HAS NO TTOCENTRY

Explanation: A data set has been backed up to anHSM tape backup volume that is not currently in theOCDS TTOC volume inventory. The data set on thisvolume might be able to be recovered, however, it ispossible that this volume has been returned to thesystem scratch pool and has been written over.

User response:

See the fixes in diagnostic 2107V

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2107WFIELD 2 DSNAME APPL1.CRITICAL.FILEFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 VOLUME SERIAL 048751FIELD 5 DATE OF BACKUP 1994273FIELD 6 VSAM/NONVSAM NFIELD 7 TAPE OR DASD TFIELD 8 BACKUP VERSION 001FIELD 9 BACKUP GENERATION 03FIELD 10 TYPE OF BKUP TAPE SPFIELD 11 TTOC EXTENSION NUM 0002FIELD 12 PRIMARY VOLUME STR002

2109V SUMMARY OF VOLUMES MCC ALIASMISSING TTOC ENTRY


User response:



2109W MCC ALIAS IS NOT ON TTOC

Explanation: A data set has been backed up to anHSM tape backup volume. The HSM generated aliasname is not in the alias name inventory in the TTOC forthat volume. This can happen if HSM has abnormallyterminated or the system has been IPLed before theTTOC information has been updated. The data set canprobably be recovered but when the tape is recycled anerror may occur. Also, if tape recycle was running, thiscondition might not be true. For best results, stoprecycle while running the audit. Note: Audit Suite doesnot verify these errors in real time. If recycle wasrunning while the audit was extracting information theseerrors may be erroneous. For best results make surerecycle is not running at the same time as Audit.

User response:



2111W MCC ENTRY IS MISSING MCB ENTRY

Explanation: Audit Suite has found an orphaned MCCentry. Either the MCB is missing altogether or thereferenced MCC is not contained in the array of MCCswithin the MCB record. The MCC is a record in theBCDS whose key is the HSM generated alias name ofthe backup. The MCC is required for a successfulRECOVER of a data set. It contains all the informationabout what tape it is on, its size, etc. In the MCC is areference back to the true data set name or the MCB.The MCB is a record in the BCDS whose key is the truename of the data set that was backed up. It contains anarray of HSM generated alias names which are the keysof the MCC record. The recycle of the tape volumecontaining this data set might fail. If it is successful, itwill recycle data that is not RECOVERABLE. Since thetrue name does not exist, a RECOVER for this backupversion will fail because HSM can not find the truename.

2107V • 2111W

80 User's Guide

User response:

F2111WB HSM FIXCDS DELETE C FOR MCC MISSING MCB


2113I BACKUP TTOC VOLUME IS EMPTY

Explanation: Audit Suite has found a volume entry inthe TTOC that has no backup data sets. This is forinformation only. If there are a large number of these,they may need to be released for scratch.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2113IFIELD 2 VOLSER HB0003FIELD 3 TAPE TYPE SP

2114W BACKUP NAME EXISTS ON VTOC,MCC IS MISSING

Explanation: Audit Suite has found an HSMgenerated alias name on an ML1 volume VTOC for abackup version that has no corresponding entry in theBCDS MCC inventory. The alias name needs to bedeleted from the VTOC.

User response:

F2114WA TSO CATALOG AND DELETE ORPHANED L1 MCC ALIAS

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2114WFIELD 2 DSNAME UNKNOWN (text)FIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 VOLUME SERIAL MIGRL1FIELD 5 DATE OF BACKUP 1994273FIELD 6 VSAM/NONVSAM NFIELD 7 TAPE OR DASD DFIELD 8 VTOC ERR 0 (0 INDICATES NO ERROR)

2115W VTOC BACKUP NAME HAS VTOCERROR

Explanation: Audit Suite has found an HSMgenerated alias name for a backup version. There is anerror in the VTOC. The alias name needs to be deletedfrom the VTOC.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2115WFIELD 2 DSNAME APPL1.CRITICAL.FILEFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 VOLUME SERIAL MIGRL1FIELD 5 DATE OF BACKUP 1994273FIELD 6 VSAM/NONVSAM NFIELD 7 TAPE OR DASD DFIELD 8 VTOC ERR 5 (text)

2116W MCB TRUENAME IS MISMATCHEDWITH MCC ENTRY

Explanation: Audit Suite has found a backup truename (MCB) whose generated alias name ismismatched. The MCC record indicates that a differentMCB true name owns it.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2116WFIELD 2 DSNAME PO0.ISI.dsnFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 DATE OF BACKUP 1998108FIELD 5 TAPE OR DASD DFIELD 6 VSAM/NONVSAM NFIELD 7 BACKUP VERSION NUM 001FIELD 8 REAL OWNER OF MCC PO0.ISI.dsn

2117W MCC ENTRY IS OWNED BYDIFFERENT MCB

Explanation: Audit Suite has found a backupgenerated alias name (an MCC) whose true namerecord exists, but the MCC is owned by a different MCBthan that indicated in the MCC.

User response:

F2117WC HSM FIXCDS PATCH C WITH CORRECT DSN

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 2117WFIELD 2 DSNAME CXTT.CLK.dsnFIELD 3 HSM GENERATED NAME HSM.BACK.dsnFIELD 4 VOLSER 035228FIELD 5 DATE OF BACKUP 1994273FIELD 6 VSAM/NONVSAM NFIELD 7 TAPE OR DASD TFIELD 8 BACKUP VERSION NUM 001FIELD 9 BACKUP GEN NUM UNFIELD 10 REAL OWNER OF MCC CXTT.CLK.dsn

3101W TAPE IS IN MCV/MCT, NOT IN TTOC

Explanation: When Audit Suite extracts the tapeinformation it examines the elements in HSM thatcontrol the tapes. The MCV is for Level 2 tapes, and theMCT is for cycle and spill tapes (backup). Recall orrecover may be successful even though a TTOC recordfor the tape is missing. If a TTOC record is missingHSM can not recycle the tapes. If the tapes are underTMS control then there may be many tapes that are

2113I • 3101W


empty and should be scratched. The information in thiserror record may be used to interrogate TMS.

User response:

F3101WE HSM DELETE MCV RECORD FROM MCDS

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3101WFIELD 2 VOLSER 010018FIELD 3 TAPE TYPE L2 (text)FIELD 4 DSN COUNT 000034

3102C TAPE IS IN TTOC, NOT IN MCV/MCT

Explanation: When Audit Suite extracts the tapeinformation it examines the elements in HSM thatcontrol the tapes. It has found a TTOC entry that is notbeing managed by HSM. The entries on these tapescan not be recalled. In addition they may have beenscratched and written over. Use this information tointerrogate TMS. If the tapes still have HSM names thedata might be reconstructed.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3102CFIELD 2 VOLSER 010020FIELD 3 TAPE TYPE L2 (text)FIELD 4 DSN COUNT 000004

3103C TAPE IS NOT IN TTOC OR MCV/MCTBUT HAS ENTRIES

Explanation: Audit Suite has discovered tapes thathave Level 2 dump volumes or backup data sets, butthe tape is not under HSM control. The tapes might stillbe managed by TMS. If this data is critical, use TMS tointerrogate the status of these tapes. If no record ofthem is in TMS, the data sets referencing these tapesmay be deleted from HSM.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3103CFIELD 2 VOLSER 010020FIELD 3 TAPE TYPE L2 (text)FIELD 4 DSN COUNT 000004

3104W TAPE IS IN TTOC & MCV/MCT, NOT INTMS (RMM, CNM)

Explanation: Audit Suite has compared the HSM tapeextraction against the Tape Inventory extraction and hasfound HSM managed tapes that are not under TapeInventory control. It is possible the tape has beenwritten over. Use the Tape Inventory interrogationsystem to find the current name of the tape. If the tapeshows 'invalid' then it is not managed and the data isprobably safe. If Tape Inventory shows a DSName otherthan the appropriate HSM data set then the tape has

probably been written on and the HSM data has beenlost.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3104WFIELD 2 VOLSER 010021FIELD 3 TAPE TYPE L2 (text)FIELD 4 DSN COUNT 000004

3110W TAPE IS PERMANENT IN TMS (RMM,CNM), NOT IN TTOC

Explanation: Audit Suite has compared the HSM tapeextraction against the Tape Inventory extraction and hasfound Tape Inventory managed tapes marked as'permanent'. HSM has no record of the tapes. It ispossible that these tapes have been orphaned and maybe scratched.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3110WFIELD 2 VOLSER 010021FIELD 3 TAPE TYPE L2 (text)FIELD 4 DSN COUNT 000004FIELD 5 EXPIRATION DATE PERMANENT (1999/365)FIELD 6 TAPE DSNAME HSM.HMIGTAPE.DATASETFIELD 7 CREATING JOB HSM

3111W TAPE IS IN TMS (RMM, CNM), VALID INHSM, HAS NO ENTRIES

Explanation: Audit Suite has compared the HSM tapeextraction against the Tape Inventory extraction and hasfound Tape Inventory managed tapes marked as'permanent'. HSM has all the appropriate records but nodata is written on the tape. This probably is not an error.However, if there are a very large number of thesetapes, the analyst should investigate why. Audit Suitehas extracted all data sets on ML2, all backup versionson tape, and all volume dump tapes. When any tapevolume is referenced it is marked as occupied. Thiswarning message displays the tape volumes that havenot been referenced, however, all the appropriatestructures for tapes in the HSM environment are correctand Tape Inventory indicates that HSM has control.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3111WFIELD 2 VOLSER 010022FIELD 3 TAPE TYPE L2 (text)FIELD 4 DSN COUNT 000004FIELD 5 EXPIRATION DATE PERMANENT (1999/365)FIELD 6 TAPE DSNAME HSM.HMIGTAPE.DATASETFIELD 7 CREATING JOB HSM

3102C • 3111W

82 User's Guide

3112W TAPE IS VALID IN HSM BUT EXPIREDIN TMS (RMM, CNM)

Explanation: Audit Suite has compared the HSM tapeextraction against the Tape Inventory extraction and hasfound Tape Inventory managed tapes that are due toexpire. These tapes could be written over and validHSM data lost. It is possible that these tapes werereleased to Tape Inventory if recycle was running duringthe audit. If in doubt, rerun the audit when recycle is notexecuting. Examine the expiration date for the currentJulian date to verify the scratch status. Other auditoptions may be necessary to determine the status ofthese tapes.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3112WFIELD 2 VOLSER 010024FIELD 3 TAPE TYPE SP (text)FIELD 4 DSN COUNT 000004FIELD 5 EXPIRATION DATE 15JUN1996FIELD 6 TAPE DSNAME HSM.HMIGTAPE.DATASETFIELD 7 CREATING JOB HSM

3114I TAPE IS SCHEDULED FOR SCRATCH

Explanation: Audit Suite has compared the HSM tapeextraction against the tape extraction and has foundTMS managed tapes that have expired. There are noHSM references to these tapes and everything isworking as it should. This message is for informationonly to review the pool of scratch tapes released byHSM but not yet selected for use by other applications.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3114IFIELD 2 VOLSER 010024FIELD 3 DSN COUNT 000000FIELD 4 EXPIRATION DATE 15JUN1996FIELD 5 TAPE DSNAME HSM.HMIGTAPE.DATASETFIELD 6 CREATING JOB HSM

3115I TAPE IS IN TMS DELETE STATUS

Explanation: Audit Suite has compared the HSM tapeextraction against the TMS extraction and has foundTMS managed tapes that have been deleted. There areno HSM references to these tapes and everything isworking as it should. This message is for informationonly to allow the Storage Manager to know the TMSdelete status of HSM tapes.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3115IFIELD 2 VOLSER 010025

FIELD 3 DSN COUNT 000000FIELD 4 EXPIRATION DATE 12JUN1995FIELD 5 TAPE DSNAME HSM.HMIGTAPE.DATASETFIELD 6 CREATING JOB HSM

3116I TAPE DOES NOT INDICATE EXTERNALDATA MANAGEMENT

Explanation: This error is for CA1 TMS only. The bitindicating external management has not been turned onby TMS. If the tape has truly been created on behalf ofHSM and HSM is attempting to give the tape back, TMSmay indicate it. This will result in tapes not beingreturned to the scratch pool.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 3116WFIELD 2 VOLSER 010025FIELD 3 DSN COUNT 000000FIELD 4 EXPIRATION DATE 16JUN1997FIELD 5 TAPE DSNAME HSM.HMIGTAPE.DATASETFIELD 6 CREATING JOB HSM

4001W PREVIOUS VOLUME NOT FOUND INOCDS

Explanation: In the OCDS each tape has a rootrecord called extension 0000. In this extension is aprevious volume pointer, indicating that the first data seton the tape is continued from a previous volume. AuditSuite has looked up the detail of that first data set andhas determined that it is valid and is continued from aprevious volume. In this case the previous volume isdifferent than the PVOL field in the OCDS. This errormay be corrected by patching the previous volume field.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4001WFIELD 2 VOLSER 014673FIELD 3 TAPE TYPE L2 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 PVOL IN OCDS 014926FIELD 6 CORRECT PVOL (IN HEX) F0F1F4F5F4F5FIELD 7 FIRST DSN ON TAPE HSM.HMIG.dsn

4002W SUCCESSOR VOLUME NOT FOUND INOCDS

Explanation: In the OCDS each tape has a rootrecord called extension 0000. In this extension is asuccessor volume pointer, indicating that the last dataset on the tape is continued to a successor volume.Audit Suite has looked up the detail of that last data setand has determined that it is valid and is continued to asuccessor volume. In this case the successor volume isdifferent than the SVOL field in the OCDS. This errormay be corrected by patching the successor volumefield.

3112W • 4002W


User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4002WFIELD 2 VOLSER 014869FIELD 3 TAPE TYPE L2 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 SVOL IN OCDS 026898FIELD 6 CORRECT SVOL(IN HEX) F0F1F7F3F4F5FIELD 7 LAST DSN ON TAPE HSM.HMIG.dsn

4003W PREVIOUS VOLUME POINTER ISINCORRECT

Explanation: This error messages differs from 4001Wbecause the previous volume pointer was found but wasincorrect. In error 4001W, the previous volume was notn the OCDS inventory. Audit Suite has compared thefirst DSN on the extension 0000 record with the lastDSN on the previous volume and has found a conflict.Audit Suite has looked up the detail about the data setand has determined that the PVOL field in the OCDS isincorrect. This error may be corrected by patching theprevious volume field.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4003WFIELD 2 VOLSER 011487FIELD 3 TAPE TYPE L2 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 PVOL IN OCDS 012247FIELD 6 CORRECT PVOL(IN HEX) F0F2F5F8F5F0

4004W SUCCESSOR VOLUME POINTER ISINCORRECT

Explanation: This error messages differs from 4002Wbecause the successor volume pointer was found butwas incorrect. In error 4002W, the successor volumewas not in the OCDS inventory. Audit Suite hascompared the last DSN on the extension 0000 recordwith the first DSN on the successor volume and hasfound a conflict. Audit Suite has looked up the detailabout the data set and has determined that the SVOLfield in the OCDS is incorrect. This error may becorrected by patching the successor volume field.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4004WFIELD 2 VOLSER 011487FIELD 3 TAPE TYPE L2 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 PVOL IN OCDS 012247FIELD 6 CORRECT PVOL(IN HEX) F0F2F5F8F5F0

4005C TAPE HAS FAILED CREATE STATUS

Explanation: The TTOC extraction process has founda tape marked as 'active in storage' and the last activitywas more than 24 hours prior to the current time. TTOCactivity is updated every 20 minutes or less. This is thecriteria that LIST TTOC SELECT(FAILEDCREATE) usesto determine failed create status. Tapes in this statuscan only be reclaimed by performing an AUDITMEDCTL. This diagnostic can be verified by submittinga LIST TTOC SELECT(FAILEDCREATE). The preferredfix is F4005CA AUDIT MEDCTL.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4005CFIELD 2 VOLSER 011529FIELD 3 TAPE TYPE SP (text)FIELD 4 TAPE CREATION DATE 1997214

4007C TTOC RECORD HAS BROKENSEQUENCE SET

Explanation: Each tape in the OCDS inventory canhave many extension records starting from extension0000 to 9999. While Audit Suite processes theextensions for a volume, it counts the extensions and aseach extension is read, its extension number iscompared to the running count. If the count is differentthan the number in the extension record then recyclewill fail for this volume. This error may be corrected byrunning AUDIT MEDIACONTROLS for the volume inerror.

User response:

See the recommended fix for 4007V

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4007CFIELD 2 VOLSER 011487FIELD 3 TAPE TYPE 01 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 EXPECTED SEQUENCE 00013FIELD 6 ENCOUNTERED SEQUENCE 00015

4007V VOLUME CONTAINS BROKENSEQUENCE SET/SETS

Explanation: For each tape identified in error 4007C(where the extension number of a tape extension recorddoes not agree with the counted number of extensionsfor that tape (see error 4007C, above)), a singleinstance of error 4007V is generated. There is one4007V error for each tape VOLSER identified in 4007C.This error may be corrected by running AUDITMEDIACONTROLS for the volume in error.

User response:

Run Audit MEDIACONTROLS for the tape.

4003W • 4007V

84 User's Guide

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4007VFIELD 2 VOLSER 011487FIELD 3 TAPE TYPE 01 (text)FIELD 4 TAPE CREATION DATE 1997214

4008C TTOC EXTENSION RECORDS ARELESS THAN EXPECTED

Explanation: Each tape in the OCDS inventory has anexpected extension number in extension 0000. WhileAudit Suite was reading the extension records itencountered the end of extensions before the expectedcount was finished. This volume will probably failrecycle. This error may be corrected by running AUDITMEDIACONTROLS for the volume in error.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4008CFIELD 2 VOLSER 067487FIELD 3 TAPE TYPE 02 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 EXPECTED EXTENSIONS 00013FIELD 6 LAST EXTENSION READ 00009

4009C TTOC EXTENSION RECORDS AREMORE THAN EXPECTED

Explanation: Each tape in the OCDS inventory has anexpected extension number in extension 0000. WhileAudit Suite was reading the extension records it foundmore extensions than was expected. This volume willprobably fail recycle. This error may be corrected byrunning AUDIT MEDIACONTROLS for the volume inerror.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4009CFIELD 2 VOLSER 067487FIELD 3 TAPE TYPE 02 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 EXPECTED EXTENSIONS 00013FIELD 6 LAST EXTENSION READ 00016

4010W 16K BLOCK COUNT DOES NOTMATCH COMPUTED BLKCNT

Explanation: Extension 0000 for each volume in theOCDS contains a field indicating how many 16K blocksof data is written on that tape. Audit Suite has read thedetail about the number of 16K blocks for each data setand has accumulated the totals. At the end of theextensions, these fields are compared and are found tohave a mismatch. This tape will either not recycle orsome of the data may not be recalled/recovered. RunAUDIT MEDIACONTROLS to examine and correct thistape volume.

User response:

Run MCDS or BCDS audit. Diagnostic 1124W willcorrect the problem.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4010WFIELD 2 VOLSER 069260FIELD 3 TAPE TYPE 30 (text)FIELD 4 TAPE CREATION DATE 1997214FIELD 5 EXPECTED BLK COUNT 019013FIELD 6 ACCUMULATED BLK COUNT 018393

4011W TAPE HAS FAILED RECYCLE

Explanation: When Audit reads the OCDS inventory,in each TTOC record 0000 for each tape, it examinesthe field that indicates whether the tape has failedrecycle. This is an indicator that something is in error onthe tape and some corrective action is required beforethe tape can be successfully recycled. Run AUDITMEDIACONTROLS to examine and correct this tapevolume.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4011WFIELD 2 VOLSER 069260FIELD 3 TAPE TYPE SP (text)FIELD 4 TAPE CREATION DATE 1997214

4012C TAPE IS NOT FULL AND WILL NOT BESELECTED FOR RECYCLE

Explanation: When Audit Suite reads the OCDSinventory, it looks for tapes that are eleven days old orolder that have not been marked full. Usually thisindicates that for some reason, such as an IPL beforeHSM could be shut down, the volume had been in usebut the TTOC information in memory had not beenrewritten to the OCDS. When HSM is restarted, thesevolumes are not selected for the various backup,migration, or recycle tasks. When the recycle processlooks for tapes to mark as eligible for recycle, it looksonly for full tapes. The volumes with these errors willnever be marked eligible for recycle because they arenot full. To recycle these tapes, issue the recyclecommand.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4012CFIELD 2 VOLSER 045092FIELD 3 TAPE TYPE SP (text)FIELD 4 TAPE CREATION DATE 1997214

4008C • 4012C


4013I TAPE IS ELIGIBLE FOR RECYCLE

Explanation: When Audit Suite reads the OCDSinventory, it looks for tapes that are marked eligible forrecycle. This is an information only message and isintended to be used to indicate the health of the recycleprocess. If there are a large number of tapes eligible forrecycle, then perhaps more recycle tasks need to beassigned. A recycle command may be issued for thesetapes.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 4013IFIELD 2 VOLSER 069260FIELD 3 TAPE TYPE SP (text)FIELD 4 TAPE CREATION DATE 1997214

8000I LIST OF DATA SETS RECORDED INMCDS/BCDS

Explanation: Audit Suite has read the MCDS orBCDS and has found these data set references to therequested tape number. This diagnostic is informationaland does not necessarily indicate an error. The usermay run cataloged procedure AKDAUDFD to list thesedata sets and discover corresponding information thatHSM has recorded about the tape. This information isdisplayed independent of the absence of other recordsabout the tape such as TTOC, MCT or MCV.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8000IFIELD 2 TAPE VOLSER CART05FIELD 3 TAPE TYPE (text)FIELD 4 TRUE DSNAME DEMO1.ML2.dsnFIELD 5 TTOC EXTENSION 0000FIELD 6 BACK-UP VER (IF MCC) 001FIELD 7 MIGRATED/RECALLED FLAG MIGRATED OR RECALLEDFIELD 8 HSM GENERATED ALIAS HSM.HMIG.dsnFIELD 9 DATA COMPONENT IF VSAM DEMO1.ML2.dsn

8001C NO HSM REFERENCE FOUND FORREQUESTED TAPE

Explanation: Audit-MediaControls has read theDFSMShsm CDSs and has found no references to therequested tape number. The tape volume may bemounted and read (if it's a DFSMShsm formatted tape)and the TTOC contents may be rebuilt from the CDDrecords on the tape. This error condition can beresolved by executing AKDAUDFL or AKDAUDFT withthe INTENSE option. The default is Level 2. EDIT&PFX.MEDIACTL.Vvvvvvv.CONTROL to change backuptype to SP or cycle number (01-07)

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8001CFIELD 2 TAPE VOLSER FAKE05

8003C NO TTOC EXTENSION 0000 WASFOUND FOR VOLSER

Explanation: Audit-MediaControls has interrogated theOCDS and has found no TTOC (T) record for therequested VOLSER. Extension '0000' contains all thecontrol information such as number of TTOCextensions, number of valid blocks, etc. Without thisrecord, the TTOC information can't be verified. Thiserror condition can be corrected by executingAKDAUDFL or AKDAUDFT with the INTENSE option.After the complete audit the TTOC is automaticallyrebuilt.

User response:

The TTOC will be rebuilt to correct this condition.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8003CFIELD 2 TAPE VOLSER FAKE05FIELD 3 TYPE OF TAPE L2 SP CY UN

8004W VOLUME IS IN FAILED CREATESTATUS

Explanation: Audit-MediaControls has interrogated theOCDS and has found a volume in failed create status.This means DFSMShsm might have been shut down orthe system abnormally terminated before the informationabout the tape, stored in active memory, could bewritten to the tape's TTOC. This error condition isdetermined by reading the extension '0000' of the TTOCand examining the TTCFAIST bit in the second flag ofthe TTCFFLGS bytes. If the bit is on, and the recordhas not been updated in more than 24 hours, thevolume is considered to be in failed create status. Toresolve this error condition, execute AKDAUDFL withoption FAST. After the tape has been physically readand audited, the corrections to the TTOC may be rebuiltby submitting the '&pfx.MEDIACTL.Vtttttt.FIXTTOC' dataset which contains the automatically generated fixes.

User response:

The TTOC will be rebuilt and the TTCFAIST bit set tozero.

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8004WFIELD 2 TAPE VOLSER FAKE05FIELD 3 TYPE OF TAPE L2 SP CY UNFIELD 4 EXTENS IN XTN 0000 0000FIELD 5 EXTENSIONS COUNTED 0000FIELD 6 BLOCKS WRITTEN IN HEX) 00000005FIELD 7 BLOCKS COUNTED (IN HEX)00000005

4013I • 8004W

86 User's Guide

8005W VOLUME IS IN FAILED RECYCLESTATUS

Explanation: Audit-MediaControls interrogated theOCDS and has found a volume in failed recycle status.Input tapes are marked in error when one of thefollowing occurs: * an I/O error on the input tape. * anOPEN failure for the input tape. * an allocation error forthe input tape. * a deallocation error for the input tape.These errors prevent a successful recycle of the tape.The error condition is determined by reading theextension '0000' of the TTOC and examining theTTCFFAIL bit in the TTCFFLGS byte. To resolve thiscondition, execute AKDAUDFL with option THOROUGHor INTENSE. After the tape has been physically readand audited, the corrections to the TTOC may beimplemented by submitting the&pfx.MEDIACTL.Vtttttt.FIXTTOC data set that containsthe automatically generated fixes.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8005WFIELD 2 TAPE VOLSER FAKE05FIELD 3 TYPE OF TAPE L2 SP CY UNFIELD 4 EXTNTS IN 0000 0000FIELD 5 EXTENSIONS COUNTED 0000FIELD 6 RECORDED BLKS WRITTEN 00000005FIELD 7 BLKS COUNTED (IN HEX) 00000005

8006C TTOC EXTENSION RECORDS ARE OUTOF SEQUENCE

Explanation: Audit-MediaControls has interrogated theOCDS for the volume specified and has found TTOCextension records that are out of sequence. TTOCrecords are numbered sequentially from '0000' to '9999'and are incremented by one. If the TTOC extensionrecords do not follow the sequence, then this diagnosticis declared. To resolve this condition, executeAKDAUDFL with option THOROUGH.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8006CFIELD 2 TAPE VOLSER CART05FIELD 3 TYPE OF TAPE L2 SP CY L2FIELD 4 EXTNTS IN 0000 0005FIELD 5 EXTENSIONS COUNTED 0007FIELD 6 BLKS WRITTEN IN HEX 000000F2FIELD 7 BLKS COUNTED (IN HEX) 000000F2

8007C TTOC EXTENSION RECORD ISCONTAMINATED

Explanation: Audit-MediaControls has interrogated theOCDS for the volume specified and has found at leastone TTOC extension record that contains erroneousinformation. This audit corrects the TTOC structure. To

resolve this condition, execute AKDAUDFL with optionTHOROUGH.

User response:


FIELD 1 ERROR NUMBER 8007CFIELD 2 TAPE VOLSER CART05FIELD 3 TYPE OF TAPE L2 SP CY L2FIELD 4 EXTNTS IN 0000 0005FIELD 5 EXTENSIONS COUNTED 0005FIELD 6 BLKS WRITTEN IN HEX 00000005FIELD 7 BLKS COUNTED (IN HEX) 000000F5

8008C TTOC EXTENSION RECORDS DO NOTMATCH EXPECTED COUNT

Explanation: Audit-MediaControls has interrogated theOCDS for the volume specified and has determined thatthe number of extension records recorded in extension'0000' does not match the number of extension recordsread. This audit corrects the TTOC structure. To resolvethis condition, execute AKDAUDFL with optionTHOROUGH.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8008CFIELD 2 TAPE VOLSER CART05FIELD 3 TYPE OF TAPE L2 SP CY L2FIELD 4 EXTNTS IN 0000 0005FIELD 5 EXTENSIONS COUNTED 0007FIELD 6 BLKS WRITTEN IN HEX 00000005FIELD 7 BLKS COUNTED IN HEX 00000005

8009W 16K BLOCK COUNT DOES NOTMATCH COUNTED BLOCKS

Explanation: Audit-MediaControls has interrogated theOCDS for the volume specified and has determined thatthe number of blocks written on the tape does notmatch the total number of blocks counted for each dataset name record. To resolve this condition, executeAKDAUDFL with option THOROUGH. After executingthis audit, the block counts will match what is actuallyon the tape.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8008CFIELD 2 TAPE VOLSER CART05FIELD 3 TYPE OF TAPE L2 SP CY L2FIELD 4 EXTNTS IN 0000 0005FIELD 5 EXTENSIONS COUNTED 0007FIELD 6 BLKS WRITTEN IN HEX 00000005FIELD 7 BLKS COUNTED IN HEX 00000007

8005W • 8009W


8020I LIST OF DATA SETS ON TAPE

Explanation: This diagnostic is for information only. Ifyou have executed the AKDAUDFL audit procedure withthe THOROUGH or INTENSE option, every CDD recordencountered on the tape is listed here. If you executeAKDAUDFL with the FAST option, only those CDDrecords encountered after the starting point are listed.This diagnostic can be used to rebuild an MCC or anMCD record for the purposes of RECALL or RECOVER.

User response:


FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8020IFIELD 2 TAPE VOLSER CART05FIELD 3 TRUE DSNAME IN CDD MCD.DATA.SETFIELD 4 TTOC EXTENSION 0001FIELD 5 BLOCKS WRITTEN 00000005FIELD 6 FBID FROM TAPE) 00000007FIELD 7 ML0 VOL DATASET WAS ON TSO003FIELD 8 TRACKS ON ML0 VOL(HEX) 0000005FFIELD 9 DSORG (HEX) 0200FIELD 10 HSM ALIAS NAME HSM.HMIG.dsnFIELD 11 CLUSTER NAME IF VSAM

8C02C NO MCT ENTRY WAS FOUND FORREQUESTED TAPE

Explanation: Audit-MediaControls has interrogated theBCDS and has found no MCT (X) record for therequested VOLSER. This error condition can beresolved by executing corrective action F8C02CB orF8C02CC. You must determine whether it is a backupSPILL or CYCLE tape before submitting a fix.

User response:

F8C02CB or F8C02CC

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8C02CFIELD 2 TAPE VOLSER FAKE05FIELD 3 TAPE TYPE SP

8C10C MCC EXISTS, NOT ON TAPE

Explanation: Audit-MediaControls has found a validMCC record in the BCDS with no matching true namerecord on the tape. This means that the MCC record isorphaned and should be deleted. Corrective actionF8C10CA can be executed to delete the backupversion.

User response:

F8C10CA

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8C10CFIELD 2 TAPE VOLSER BACK05FIELD 3 TYPE OF TAPE L2 SP CY SPFIELD 4 TRUE DSNAME IN CDD MCC.LIVE.DATASETFIELD 5 TTOC OFFSET IN MCC 0005

FIELD 6 BKUP VER NUMBER (HEX) 0002FIELD 7 16K BLOCKS IN MCC(HEX) 00000005FIELD 8 FBID IN MCC(HEX) 00000007

8C12C MCC MISMATCH FILE BLOCKIDENTIFIER

Explanation: Audit-MediaControls, after reading thetape and issuing a NOTE macro to determine theposition on tape, has found a mismatch of the File BlockIdentifier (FBID) as recorded in the corresponding MCCrecord. The FBID is used to position a tape to the blockwhere the data set begins. Corrective action F8C11CAcan be executed to patch the correct FBID in the MCC.

User response:

F8C12CA

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8C12CFIELD 2 TAPE VOLSER BACK05FIELD 3 TYPE OF TAPE L2 SP CY SPFIELD 4 TRUE DSNAME IN CDD MCC.DATA.SETFIELD 5 FBID (FROM TAPE) 00000007FIELD 6 HSM ALIAS NAME HSM.BACK.dsnFIELD 7 CLUSTER NAME IF VSAM

8D02C NO MCV ENTRY WAS FOUND FORREQUESTED TAPE

Explanation: Audit-MediaControls has interrogated theMCDS and has found no MCV (V) record for therequested VOLSER. This error condition can beresolved by executing corrective action F8D02CA.

User response:

F8D02CA

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8D02CFIELD 2 TAPE VOLSER FAKE05FIELD 3 TYPE OF TAPE L2

8D10C MCD EXISTS, NOT ON TAPE

Explanation: Audit-MediaControls has found a validMCD record in the MCDS with no matching true namerecord on the tape. This means that the valid MCDrecord, which indicates the data set is migrated to thisvolume, is incorrect and should be deleted. Correctiveaction F8D10CA can be executed to delete this dataset.

User response:

F8D10CA

FIELD # DESCRIPTION EXAMPLEFIELD 1 ERROR NUMBER 8D10CFIELD 2 TAPE VOLSER CART05FIELD 3 TYPE OF TAPE L2 SP CY L2FIELD 4 TRUE DSNAME IN CDD MCD.LIVE.DATAFIELD 5 TTOC OFFSET IN MCD 0005FIELD 6 16K BLOCKS IN MCD(HEX) 00000005FIELD 7 FBID IN MCD(HEX) 00000007FIELD 8 CLUSTER NAME IF VSAM MCD.LIVE.CLUSTER

8020I • 8D10C

88 User's Guide

8D12C MCD MISMATCH FILE BLOCKIDENTIFIER

Explanation: Audit-MediaControls, after reading thetape and issuing a NOTE macro to determine theposition on tape, has found a mismatch of the File BlockIdentifier (FBID) as recorded in the corresponding MCDrecord. The FBID is used to position a tape to the blockwhere the data set begins when a recall is issued.Corrective action F8D12CA can be executed to correctthe FBID in the MCD.

User response:

F8D12CA

FIELD 1 ERROR NUMBER 8D12CFIELD 2 TAPE VOLSER 300038FIELD 3 TYPE OF TAPE L2 SP CY L2FIELD 4 TRUE DSNAME IN CDD MCD.DATA.SETFIELD 5 FBID (FROM TAPE) 00000007FIELD 6 HSM ALIAS NAME HSM.HMIG.dsnFIELD 7 CLUSTER NANE IF VSAM

8D12C


90 User's Guide

Chapter 10. AKDINI Configuration Values

The AKDINI member (the product initialization member) of the SAKDPARM library isused to define global information regarding Advanced Audit for DFSMShsm usageand options within your installation.

The AKDINI member is organized in sections. A section name is indicated by thecolon character (:), immediately followed by the section name. Section names are tobe changed or added only under the direction of Technical Support.

Each section contains a set of individual parameter specifications known as tokenstatements. The general format for a token statement is:Token = Value

Tokens are set with a value, specified by you or Technical Support, that is a set ofstrings to the right of the token's equal (=) sign. Token values may be keywords,user values, or a keyword with a user value, shown as VALUE(uservalue).

You can enclose values in either single or double quotes. The quotes are strippedaway before the product uses the value. Quotes may be supplied as data by:

v Using the opposite quote symbol as delimiters (for example, " ' " will yield asingle quote as data).

v Specifying two to get one (for example, ' ' ' will yield a single quote as data).

Leading blanks from the beginning of the logical card-image records are allowed forall token statements. Syntax scan processing locates the first non-blank character ineach logical record. The entire length of the 80-byte logical record is considered forvalid data. Do not renumber the AKDINI member sequence numbers assigned incolumns 73 through 80 because this will cause errors to occur.

Continuing a token statement

Token statements can be continued, using either a minus (-) or plus (+) characteranywhere within the text. All data to the right of the continuation character on thatlogical record are interpreted as a comment and ignored.

Reading the token statements

The token statements shown in this document follow these rules:

v Default values are underlined.

v Multiple values are separated with a vertical bar ( | ). You must choose one.

v User-supplied values are in lowercase italic. For example, text.

Commenting Rules

Both line mode and block mode methods of commenting are supported:

v An asterisk (*) in column 1 marks the entire line as a comment. This style ofcomment is not allowed inside a continued /* */ type comment, but is allowed in acontinued token/value statement.

v Entire lines, blocks of lines, or portions of a line may be commented bybeginning the comment with a '/*' and terminating the comment with a '*/'. Nestedcomments are honored.

91

You can add a Notes token to document changes to any section including the initialor unnamed section. The AKDINIMG program will retain these notes along with anycomments that continue from the Notes token. For example:Notes = /* Updated by Dan

on 2006/12/01 */

You can also use a portion of the section-statement line after the first space fordocumenting changes to that section. For a multi-image INI, the section name canbe qualified by sysplex, system name, or both as shown below, except for thePRODUCT_INFO section:

v Sysplex-name and system-name qualification::section-name.sysplex-name.system-name

v Sysplex-name only qualification::section-name.sysplex-name

v System-name only qualification::section-name..system-name

The sysplex and system names must be explicitly specified with no wildcardcharacters allowed.

AKDINIMG will retain your qualified sections and merge new tokens for thosesections.

Those programs using the AKDINI will use only the first matching section. All othervariations of that section will be ignored. You can specify qualified sections for thoseimages with unique requirements, followed by an unqualified section that applies toall of the other images.

PRODUCT_INFOThis section of AKDINI sets product version and release information.

Important: Do not modify any tokens in the :PRODUCT_INFO section. Thesetokens are documented for your reference only.

AKD_REL = VvvRrr

The version and release of Advanced Audit for DFSMShsm software currentlyrunning.

AKD_REL_DATE = dd mmm yyyy

The date that the base level software currently installed was packaged.

AKD_MAINT_DATE = dd mmm yyyy

The date that the maintenance level software currently applied was packaged.

AKD_TITLE1 = '...' and AKD_TITLE2 = '...' and AKD_TITLE3 = '...'

The copyright and release values that are used in ISPF and report displays.

CUSTOMER_ENVIRONThis section of AKDINI sets values that define the running environment.

92 User's Guide

AUTOFIX_IBM = N | Y

This token defines whether you want to use IBM autofixes rather then customerspecified fixes. (See Chapter 8: Correcting errors for more detail on IBM Autofixes.It is recommended that the default of N be used until you understand the fixeswhich will be automatically submitted.)

KEEP_HISTORY_DAYS = 999

This token defines the number of days to keep history records in the GlobalSummary History File. Value can be 1 - 9999. Default is 999.

MAX_VOLUMES = 5

This token defines the allowed number of volumes the CDS extract files are allowedto span. Value can be 1 - 256. The default value of 5 is recommended forperformance reasons.

RLS = N | Y

This token defines whether your HSM CDSs use Record Level Sharing (RLS).

AKD_DATASETSThis section of AKDINI sets values for the high level qualifiers for data sets createdby the Advanced Audit for DFSMShsm. It also defines the high level qualifiers forthe installed product libraries.

LOAD = dsn

The name of your authorized runtime load library.

PFX = hlq

The high level qualifier of the files created by Advanced Audit for DFSMShsm batchjobs.

PPFX = hlq

The high level qualifier of the installed Advanced Audit for DFSMShsm libraries.

PRODUCT_DATASETSThis section of AKDINI sets values for the installed dataset names for variousproducts that are used in the auditing procedures. Various products includeDFSMShsm, CA1, RMM, and CNM.

BCDS = dsn

The name of your installation's HSM backup control data set.

BCDS1 = dsn | NULLFILE

The first split name of your installation's HSM backup control data set, if you havesplit your BCDS.

Chapter 10. AKDINI Configuration Values 93

|

||||

|

||

|

|||


The second split name of your installation's HSM backup control data set, if youhave split your BCDS.


The third split name of your installation's HSM backup control data set, if you havesplit your BCDS.

MCDS = dsn

The name of your installation's HSM migration control data set.

MCDS1 = dsn | NULLFILE

The first split name of your installation's HSM migration control data set, if you havesplit your MCDS.


The second split name of your installation's HSM migration control data set, if youhave split your MCDS.


The third split name of your installation's HSM migration control data set, if youhave split your MCDS.

OCDS = dsn

The name of your installation's HSM offline control data set.

OCDS1 = NULLFILE

Do not change.

OCDS2 = NULLFILE

Do not change.

OCDS3 = NULLFILE

Do not change.

RMMCDS = dsn | NULLFILE

The name of your RMM control data set, if you are using RMM as your tapemanagement system.

RMMMSG = dsn | NULLFILE

The name of your RMM message data set, if you are using RMM as your tapemanagement system.

94 User's Guide

RMMRPT = dsn | NULLFILE

The name of your RMM report data set, if you are using RMM as your tapemanagement system.

CA1TMC = dsn | NULLFILE

The name of your CA1 Tape Management Catalog, if you are using CA1 as yourtape management system.

ZARATMC = dsn | NULLFILE

The name of your ZARA Tape Management Catalog, if you are using ZARA as yourtape management system.

VAULT = dsn | NULLFILE

The name of your ZARA Vault Data Set, if you are using ZARA as your tapemanagement system.

ZARALOAD = dsn | NULLFILE

The name of your ZARA Load Library, if you are using ZARA as your tapemanagement system.

OASISLD = dsn | NULLFILE

The name of your OASIS Load Library, if you are using OASISLD as your tapemanagement system.

CTLMMDB = dsn | NULLFILE

The dataset name of your Control/M Tape Database DATA portion.

CTLMMDI = dsn | NULLFILE

The dataset name of your Control/M Tape Database INDEX portion.

CTLMSDB = dsn | NULLFILE

The dataset name of your Control/M Tape Stacking database DATA portion.

CTLMSDI = dsn | NULLFILE

The dataset name of your Control/M Tape Stacking database INDEX portion.

CTLMTRC = dsn | NULLFILE

The dataset name of your Control/M Tape TRC (trace) dataset.

CTLMCAL = dsn | NULLFILE

The dataset name of your Control/M Tape CAL (calendar) dataset.


CTLMPRM = dsn | NULLFILE

The dataset name of your Control/M Tape PARM dataset.

CTLMENV = dsn | NULLFILE

The dataset name of your Control/M Tape IOAENV (environment) dataset.

CTLMLOD = dsn | NULLFILE

The dataset name of your Control/M Tape LOAD library dataset.

DEFAULT_ALLOC_PARMSThis section of AKDINI sets values for the parameters that are used during an audit.They specify locations and sizes of runtime data sets.

WRKUNIT = SYSALLDA

The work data set unit.

SOUT = *

The SYSOUT setting.

ATP = CYL

The space allocation. You can either specify TRK or CYL.

PRI = 100

The Primary space amount.

SEC = 200

The Secondary space amount.

PUNIT = SYSALLDA

Permanent data set unit allocation..

TUNIT = 3590-1

The Tape unit.

TAPEVOL = xxxxxx

The tape volume number. Specify the appropriate value.

DEFAULT_JOB_PARMSThis section of AKDINI sets values for the default runtime parameters usedthroughout the audit procedures.

96 User's Guide

TOPT = YES

This token specifies whether to audit the TTOC alias blocks.

USERID = &&SYSUID

The prefix for automatic fixes.

OPTION = FAST | THOROUGH | INTENSE

This token specifies how to process the audit when you run AKDAUDFL andAKDAUDFT.

QLIMIT = 3000000

This token specifies the maximum number of FIXCDS that can be submitted whenyou run AKDAUDFL and AKDAUDFT. You can specify a value between 1 and9999999.


98 User's Guide

Chapter 11. Snap Dump Utility

You can use the snap dump utility to display HSM records in a snap dump format.

The AKDBATCH JCL in the SAKDJCL library is a template you can use to run thesnap dump utility. Do not modify the AKDBATCH member directly because it is usedin the automatic error correction process. Make a copy of the AKDBATCH templateas a member in your personal PDS and edit it by adding these two DD statementsat the end of your copy://SYSPRINT DD SYSOUT=*//SYSIN DD *

(dump commands here)

The sample input shown below will produce a dump format of the A record which isthe Alias Name Record (MCA) that resides in the HSM MCDS. A single characterrepresenting the type of record in the CDS and the key of the record are the twoinput requirements.//SYSIN DD *DUMP A HSM.HMIG.T034211.TEST1.DUASMI.J3211DUMP A HSM.HMIG.T392109.EDP.LAB.J3202

An example of the snap dump produced from the sample input is shown below.

0RECORD FOUND DUMP A HSM.HMIG.T034211 .TEST1.DUASMI.J3211DUMP FOLLOWS00000000 C8E2D44B C8D4C9C7 4BE3F0F3 F4F2F1F1 4BE3C5E2 E3F14BC4 E4C1E2D4 C94BD1F3 *HSM.HMIG.T034211.TEST1.DUASMI.J3*00000020 F2F1F140 40404040 40404040 00701100 B9CC096E 8F55D100 B9CC096E 8F55D100 *211 .......>..J....>..J.*00000040 00000000 E3C5E2E3 F14BC4E4 C1E2D4C9 4BC7C4C7 4BC7F0F0 F0F1E5F0 F0404040 *....TEST1.DUASMI.GDG.G0001V00 *00000060 40404040 40404040 40404040 40404040 00000000 * .... *

0RECORD FOUND DUMP A HSM.HMIG.T392109.EDP.LAB.J3202DUMP FOLLOWS00000000 C8E2D44B C8D4C9C7 4BE3F3F9 F2F1F0F9 4BC5C4D7 4BD3C1C2 4BD1F3F2 F0F24040 *HSM.HMIG.T392109.EDP.LAB.J3202 *00000020 40404040 40404040 40404040 00701100 B9C09943 BE0EC180 B9C09943 637AFC40 * .....{r...A..{r..:. *00000040 00000000 C5C4D74B D3C1C24B D9C5D5C1 D4C54BD8 F0F0F0F2 4BC7F0F0 F0C14BD8 *....EDP.LAB.RENAME.Q0002.G000A.Q*00000060 F0F0F0C2 4BD8F0F0 F0C34040 40404040 00000000 *000B.Q000C .... *

This table shows the additional records that may display and in which control dataset they are found.

Table 4. Additional Records Displayed

Character Record Type Control Data Set Name

B MCB BCDS

C MCC BCDS

X MCT BCDS

Y DVL BCDS

A MCA MCDS

D MCD MCDS

O MCO MCDS

V MCV MCDS

N TCN OCDS

Snap Dump Example

99

Table 4. Additional Records Displayed (continued)

Character Record Type Control Data Set Name

T TTOC OCDS

100 User's Guide

Chapter 12. Advanced Audit for DFSMShsm and HSMEquivalents

This appendix provides the Advanced Audit for DFSMShsm and HSM diagnosticerror equivalents and the Advanced Audit for DFSMShsm and HSM Auditequivalents.

Advanced Audit for DFSMShsm and HSM Audit EquivalentsThe following table shows Advanced Audit for DFSMShsm audit procedure and theHSM audit type equivalent.

Table 5. Advanced Audit for DFSMShsm and HSM Audit Equivalent

Advanced Audit for DFSMShsm Audit Procedure HSM Audit Type

AKDAUDAL AUDIT MCDS

AUDIT DIRECTORYCONTROLSVOLUMES(allml1,allml2)

AUDIT VOLUMECONTROLS(MIGRATION)

AUDIT DATASETCONTROLS(MIGRATION)

AUDIT OCDS(ML2)

AUDIT MEDIACONTROLS(SDSP)

AUDIT MEDIACONTROLS VOLUMES(allml1)

AUDIT MEDIACONTROLS VOLUMES(allml2) someanalysis

AUDIT MASTERCATALOG

AUDIT USERCATALOG (all user catalogs)

AKDAUDBD AUDIT BCDS

AUDIT DIRECTORYCONTROLSVOLUMES(allspill,allcycle)

AUDIT VOLUMECONTROLS(BACKUP)

AUDIT DATASETCONTROLS(BACKUP)

AUDIT OCDS(spill,cycle)

AUDIT MEDIACONTROLS VOLUMES(spill,cycle)

AUDIT MEDIACONTROLS VOLUMES(ml1bkup)

AKDAUDCT AUDIT MCDS

AUDIT MASTERCATALOG

AUDIT USERCATALOG(all-catalogs)

AKDAUDFD AUDIT DIRECTORYCONTROLS

AKDAUDFL AUDIT MEDIACONTROLS

AKDAUDFT AUDIT DIRECTORYCONTROLS and MEDIACONTROLS

101

Table 5. Advanced Audit for DFSMShsm and HSM Audit Equivalent (continued)

Advanced Audit for DFSMShsm Audit Procedure HSM Audit Type

AKDAUDMD AUDIT DIRECTORYCONTROLSVOLUMES(allml1,allml2)

AUDIT VOLUMECONTROLS(MIGRATION)

AUDIT DATASETCONTROLS(MIGRATION)

AUDIT OCDS(ML2)

AUDIT MEDIACONTROLS(SDSP)

AUDIT MEDIACONTROLS VOLUMES(allml1)

AUDIT MEDIACONTROLS VOLUMES(allml2) someanalysis

MEDCTL(SDSP), VOLCTL(MIG) MEDCTLVOLUMES(ML2)

AKDAUDOD AUDIT OCDS(DAILY)

AUDIT OCDS(SPILL)

AUDIT OCDS(ML2)

AUDIT OCDS(ALL)

AKDAUDTP AUDIT VOLUMECONTROLS(MIGRATION)

AUDIT VOLUMECONTROLS(BACKUP)

AUDIT VOLUMECONTROLS(RECOVERABLE)

Advanced Audit for DFSMShsm and HSM Diagnostic Error EquivalentsThe following table lists the Advanced Audit for DFSMShsm audit diagnostics andthe closest related HSM AUDIT error.

The IBM-provided automatic fixes are listed in the HSM Auto-Fix column. TheAdvanced Audit for DFSMShsm recommended default fix, listed in the AdvancedAudit for DFSMShsm Available Fixes column, is shown in bold.

102 User's Guide

Table 6. Advanced Audit for DFSMShsm and HSM Audit Error Equivalents

Advanced Audit forDFSMShsm AuditDiagnostic

HSM AuditDiagnostic HSM Audit Type HSM Auto-Fix

Advanced Audit forDFSMShsm AvailableFixes (RecommendedDefault Fix in Bold)

11D1C - MCDENTRY IS NOTCATALOGED

ERR003 MCDS, BCDS, OCDS Yes F11D1CA TSOCATALOG AMIGRATED DATA SETTO VOLSER MIGRAT

F11D1CB TSO HSENDDELETE MIGRATEDDSN MISSINGCATALOG

F11D1CC TSO LISTCFOR DATA SET NOTCATALOGED

F11D1CD HSA DISPLAYDUMP OFMCDRECORD

F11D1CR1 HSMDELETE MCD RECORDWHEN UNABLE TOCATALOG MIGRA

F11D1CR3 HSMFIXCDS PATCHASSIGNED ANDNEEDS SCRATCH

Chapter 12. Advanced Audit for DFSMShsm and HSM Equivalents 103

Table 6. Advanced Audit for DFSMShsm and HSM Audit Error Equivalents (continued)




11V1C - MCO VSAMCOMPONENT ISNOT CATALOGED

ERR003 MCDS, BCDS, OCDS Yes F11V1CA TSOCATALOG AMIGRATED DATASETTO VOLSER MIGRAT

F11V1CB TSO HSENDDELETE MIGRATEDDSN MISSINGCATALOG

F11V1CC TSO LISTCFOR DATA SET NOTCATALOGED

F11V1CD HSA DISPLAYDUMP OF MCORECORD

F11V1CE HSM FIXCDSDELETE OFUNCATALOGEDCOMPONENT

F11V1CF HSA DISPLAYDUMP OF ALIASRECORD

F11V1CG HSM FIXCDSDELETE OF MCORECORD

F11V1CH TSO RECALLJUST THE CLUSTERNAME

F11V1CR1 HSMFIXCDS DELETE OFMCD FOR UNCATCOMP

F11V1CR2 HSMDELETE ORPHANEDMCO RECORDS

F11V1CR3 HSMDELETE ORPHANEDMCA RECORDS

104 User's Guide





11D2C - MCDENTRY ISCATALOGED ONDIFFERENTVOLUME

ERR007

ERR009

ERR018

VOLCTL

MCDS, BCDS

MCDS, BCDS,OCDS, DSCTL

No F11D2CA TSO DELETEAND CATALOG DSN TOVOLSER MIGRAT

F11D2CB TSO DELETEAN UNCATALOGEDMIGRATED DATASET

F11D2CC HSM FIXCDSDELETE OF A AND DRECORD

F11D2CR1 HSMDELETE MCD RECORDWHEN DATA SET ISCATALOGED ONLINE

F11D2CR3 HSMFIXCDS PATCHASSIGNED ANDNEEDS SCRATCH

11V2C - MCO VSAMCOMPONENT ONDIFFERENTVOLUME

None F11V2CA TSO DELETEAND CATALOG DSN TOVOLSER MIGRAT

F11V2CB TSO DELETEAN UNCATALOGEDMIGRATED DATA SET

F11V2CE HSA DISPLAYDUMP OF MCORECORD

F11V2CF HSMGENERATE FIXCDSDELETE FORCONFLICT MCO ANDMCD






1103W - MCDENTRY IS MISSINGTHE MCA ENTRY

ERR022 DSCTL (MIG) F1103WA HSMGENERATE FIXCDSDISPLAY FOR MISSINGMCA RECORD

F1103WB HSA VERIFYMCD AND MCARECORDS

F1103WC HSM FIXCDSCREATE NEW MCARECORD

F1103WR1 HSMGENERATE RECALLFOR DATA SETS

F1103WR2 HSMGENERATE HMIG FORDATA SETS

F1103WR3 HSMGENERATE HSENDDELETES FOR DATASETS

1104C - MCD LEVEL1 ENTRY HAS NOVTOC ENTRY ON L1VOLUME

ERR148

ERR149

DIRCT, MEDCTL

DIRCTL, MEDCTL(SDSP), MEDCTL

F1104CA TSO DELETEAND RECOVER ML1DSN

F1104CB HSA DISPLAYDUMP OF MCDRECORD MISSING ML1

F1104CC HSM FIXCDSCOMMAND TO DELETEDSN MISSING ML1VOL

F1104CR1 HSMRR-DELETE MCDRECORD WHEN ML1MCV MISSING

1105W - MCD VSAMBASE IS MISSING INMCO

ERR023

ERR169

DSCTL (MIG)

MEDCTL

F1105WA TSO DELETEAND RECOVERMISSING VSAM MCO

F1105WB HSA DISPLAYMCO RECORDMISSING BASE NAME

F1105WC TSOGENERATE RECALLFOR DATASETS

106 User's Guide





1106C - MCD IS ONVOLUME WHICHHAS NO MCVENTRY

ERR020

ERR042

DSCTL(MIG)

MEDCTL

See 1106V forfixes.

F1106CA HSM FIXCDSCOMMAND TO VERIFYMISSING MCVRECORD

F1106CB TSOUNCATALOG ANDRECOVER FOR DSNMISSING MCV

F1106CC HSM FIXCDSDELETE OF MCDMISSING MCV

F1106CD HSA DUMPDISPLAY D RECORD,VERIFY MCV RECORD

F1106CE TSO HSENDDELETE (AFTERF1106VC) RAN

F1106CF HSM FIXCDSCOMMAND TO DELETEDSN MISSING ML2 VOL

F1106CR1 HSM FIXCDSDELETE OF MCAMISSING MCV

1106V SUMMARY OFVOLUMES HAVINGNO MCV ENTRY

ERR110 DIRCTL, MEDCTL F1106VA HSM FIXCDSCOMMAND TO VERIFYMISSING MCVRECORD

F1106VB TMSINTERROGATE TMSFOR HSM TAPESMISSING MCV

F1106VC HSM FIXCDSTO ADD NEW MCVLEVEL 2 RECORD

F1106VD HSM FIXCDSTO DELETE MCVLEVEL 2 RECORD

1107W - MCD LEVEL2 IS ON VOLUMEWHICH HAS NOTTOC ENTRY

ERR029

ERR051

ERR115

DSCTL(MIG)

MEDCTL, VOLCTL

DIRCTL

Yes (see 1107V) F1107WA HSMGENERATE FIXCDSDISPLAY FOR MISSINGMCA RECORD






1107V - SUMMARYOF VOLUMESMISSING IN TTOC

None F1107VA HSM FIXCDSCOMMAND TO VERIFYMISSING TTOCRECORD

F1107VB HSM LISTTTOC FOR MISSINGVOLUME

F1107VC RMMINTERROGATE RMMFOR HSM TAPES

F1107VD HSM FIXCDSDISPLAY TTOCRECORD EXTENTS 3 -5

F1107VE HSM FIXCDSDISPLAY TTOCRECORD EXTENTS 6 -8

F1107VF HSM FIXCDSDISPLAY TTOCRECORD EXTENTS 9 -11

F1107VG HSM FIXCDSDISPLAY TTOCRECORD EXTENTS 12- 14

F1107VH HSM FIXCDSDISPLAY TTOCRECORD EXTENTS 15-17

F1107VI TMSINTERROGATE TMSFOR HSM TAPESMISSING IN OCDS

F1107VJ HSM AUDITMEDIACONTROLS FORMISSING TTOC

F1107VK TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT

108 User's Guide





1108W - MCA ENTRYIS MISSING MCOVSAM COMPONENTENTRY

ERR024 DSCTL (MIG) Yes (not critical) nodefault suggested

F1108WA HSM FIXCDSDISPLAY MCA RECORDMISSING MCOCOMPONENT

F1108WB HSM FIXCDSDELETE MCA MISSINGMCO COMPONENT

1109W - - MCDALIAS IS NOT ONTTOC

ERR016

ERR114

ERR147

ERR149

MCDS, BCDS

DIRCTL

DIRCTL, MEDCTL(SDSP)

DIRCTL, MEDCTL(DSP), MEDCTL

No

Yes

Yes

Yes (See defaultfor 1109V)

F1109WA HSM LISTTTOC FOR DSNINFORMATION

F1109WB HSM LISTDSN INFO FOR MCAMISSING IN TTOC

F1109WC HSM FIXCDSDISPLAY D FORENTRY MISSING INTTOC

F1109WD HSM LISTVOLUMES FORFAILEDCREATE

F1109WE HSM RECALLFOR MISSING TTOC

1109V - SUMMARYOF VOLUMESWHERE ALIAS ISNOT IN TTOC

None F1109VA HSM LISTTTOC FOR VOLUMEHAVING MISSING MCAENTRY

F1109VB HSM FIXCDSDISPLAY T FOR VOLMISSING MCA ENTRY

F1109VC HSM LISTTTOC VOLUMES FORFAILEDCREATE

F1109VD HSM AUDITMEDIA CONTROL FORMCA MISSING IN TTOCNote: It isrecommended that youuse Advanced Audit forDFSMShsm to rebuildthe TTOC.

F1109VE TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT






1110W - MCD HASDUPLICATE MCAENTRY

None F1110WA TSO LISTCFIXCDS D AND FIXCDSA TO ANALYZE MCADUPLICATES

F1110WB HSM RECALLFOR CONFLICTINGALIAS NAMES

F1110WC HSM RECALLFOR CONFLICTINGALIAS NAMES

1111W - MCA ENTRYIS MISSING MCDENTRY

ERR028

ERR113

DSCTL(MIG)

DIRCTL

Yes F1111WA HSM FIXCDSA, D AND O TOEXAMINE MISSMCD/MCO

F1111WB HSM LISTTRUE NAME IN MCDS

F1111WC HSM FIXCDSDELETE ORPHANEDMCA RECORD

F1111WR1 HSMFIXCDS D TO EXAMINEMISSING MCD/MCO

F1111WR2 HSM FIXA/D/O DISP MISSINGMCD/MCO ** ADDLOGONLY

F1111WR3 HSM FIX A/ODELETE AFTERVERIFY D MISSING

1112W - MCO VSAMBASE NAME ISMISSING IN MCD

ERR027 DIRCTL Yes F1112WA HSM FIXCDSO DELETE FORORPHANED MCORECORD


F1112WC HSA DISPLAYDUMP OF MCORECORD

1113W – MCO VSAMCOMPONENT NAMEIS MISSING IN MCA

ERR025 DSCTL (MIG) Yes F1113WA TSO DELETEAND RECOVER VSAMCLUSTER MISSINGMCA

F1113WB HSM FIXCDSDELETE OF MCORECORD

110 User's Guide





1114W - ALIASNAME EXISTS INVTOC, MCA ISMISSING

ERR115

ERR140

DIRCTL

DIRCTL, MEDCTL

Yes F1114WA HSM VERIFYMISSING MCARECORD

F1114WB TSOCATALOG AND DELETEORPHANED L1 HSMALIAS

F1114WR1 IDCCATALOG ANDDELETE ORPHANEDL1 HSM ALIAS W/ORECAT

1115W - VTOC ALIASNAME HAS VTOCERROR

None F1115WA TSO DEL NVRFOR FORMAT1 DSCBERROR

F1115WB VTCSCRATCH ENTRYFROM VTOC

1116C - CATALOGENTRY HAS NOMCD/MCO ENTRY

ERR010

ERR011

ERR147

DSCTL, BCDS,OCDS

MCDS, BCDS, OCDS

DIRCTL, MEDCTL(SDSP)

Yes F1116CA TSO DELETENOSCRATCH FORMIGRAT DSNSMISSING MCD

F1116CB TSO LISTC TOVERIFY CATALOGSTATUS OF DATA SET

F1116CC HSM LISTCOMMANDS TOVERIFY MISSING MCD

1117C - CATALOGENTRY IS NOTCONNECTED TOMASTER CAT

None F1117CA TSO DELWITH CAT STATEMENT

F1117CB TSO LISTCFOR DSN MISSINGCONNECTOR

F1117CE IDC DELNOSCRATCH WITHCAT STATEMENT

1118C - MIGRATEDDATA SET ISMISSING IN SDSPCLUSTER

ERR148 DIRCTL, MEDCTL No F1118CA TSO DELETEAND RECOVER FORSDSP MISSING

F1118CB TSOUNCATALOG DSN FORSDSP MISSING

F1118CC HSM FIXCDSD DELETE FOR SDSPMISSING






1119W - ENTRY INSDSP DATA SET ISMISSING IN MCDS

ERR160

ERR161

ERR162

ERR163

MEDCTL

MEDCTL (SDSP)

MEDCTL (SDSP)

MEDCTL (SDSP)

Yes F1119WA HSM FIXCDSD FOR TO VERIFYMISSING MCD ISREALLY SDSP


F1119WC TSO LISTCFOR SDSP DATA SET

F1119WD HSM AUDITMEDCTL FOR SDSPMISSING MCD

F1119WE HSA VERIFYMCD RECORDMISSING FOR SDSPCLUSTER

F1119WF HSA DUMPMCD RECORDMISSING FOR SDSPCLUSTER

1120I TTOC VOLUMEIS EMPTY

None F1120IA HSM LISTTTOC FOR EMPTYVOLUME

F1120IB TMS LISTEMPTY VOLSER INTMS

F1120IC RMMINTERROGATE RMMFOR HSM TAPESF1120ID

HSM RECYCLE EMPTYVOLUMES

112 User's Guide





1121W - MIGRATIONLEVEL 2 VOLUMEHAS NO TTOCENTRY

ERR051 MEDCTL, VOLCTL Yes F1121WA TMSINTERROGATE LEVEL2TAPE MISSING TTOC

F1121WB HSM FIXCDSCOMMAND TO VERIFYMISSING TTOCRECORD

F1121WC HSM DELVOLPURGE FOR ML2VOLUMESNote: It isrecommended that youuse Advanced Audit forDFSMShsm to rebuildthe TTOC.

1122W - MCD ALIASIS OWNED BYDIFFERENT MCD

None F1122WA HSM AUDITMEDIA CONTROLSTATEMENT FOR HSM

F1122WB HSMGENERATE RECALLFOR DATA SETS

1123W MCATRUENAMERECORD ISMISMATCHED

ERR028 MEDCTL Yes F1123WA HSA DUMPMCD AND MCARECORDS

F1123WB HSM FIXCDSDELETE CONFLICTINGA RECORD

1124W - VALIDBLOCK COUNT INTTOC DOES NOTAGREE

ERR137 MEDCTL Yes F1124WA HSA DISPLAYDUMP OF TTOC WITHMISMATCH VALIDBLOCKS

F1124WB HSM FIXCDSPATCH T FOR VOLWITH MISMATCHBLOCK COUNT

F1124WC HSM AUDITDIRCTL FORMISMATCH BLOCKCOUNT

F1124WD TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT






1125W TTOC ENTRYMARKED INVALID,MCD/MCC EXISTS

ERR136 MEDCTL Yes F1125WA HSM FIXCDSDISPLAY TTOCRECORD EXTENSIONOF TAPE

F1125WB HSM FIXCDSDISPLAY MCDRECORD

F1125WC HSM FIXCDSDISPLAY MCA RECORD

F1125WD HSM FIXCDSPATCH T MARK DSNVALID F1125WR1

HSM HSEND LISTDATASET

F1125WE TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT

1126I - SUMMARYOF TTOC VOLUMESWITH INVALID DSNS

ERR136 MEDCTL Information only

2101W - MCB ISCONTAMINATED

None F2101WA HSM FIXCDSDISPLAY FORCONTAMINATED MCBRECORD

2102W - MCB HASDUPLICATE MCCENTRY

None F2102WA HSM FIXCDSDISPLAY FORDUPLICATE MCCENTRIES

114 User's Guide





2103C - MCB ENTRYIS MISSING THEMCC ENTRY

ERR039 DSCTL (BACKUP) No F2103CA HSM FIXCDSDISPLAY FOR MCBMISSING MCC ENTRY

F2103CB TSOBDELETE BACKUP

F2103CC HSM LISTCOMMANDS TOVERIFY MISSING MCC

F2103CR1 HSMHBDELETES FOR MCBMISSING MCC ENTRYW/VER #

F2103CR2 HSMFIXCDS DISPLAY FORMCB MISSING MCCENTRY

F2103CR3 TSO LISTCAT FOR MCBMISSING MCC ENTRY

F2103CR4 HSMRECALL FOR MCBMISSING MCC ENTRY

F2103CR5 HSMBACKUP FOR MCBMISSING MCC ENTRY

2104C - MCC BKUPTO LEVEL 1 HAS NOVTOC ENTRY

ERR047 DSCTL (BACKUP) No F2104CA TSOHBDELETE BACKUPVERSION MISSINGVTOC

2105W - DUPLICATEBACK-UP VOLUMESFOUND

F2105WA HSM FIXCDSCOMMAND TOEXAMINE DUPLICATETTOC RECORDS

F2105WB HSM FIXCDSCOMMAND TO DELETEFIRST DUPLICATE VOL

F2105WC HSM FIXCDSCOMMAND TO DELETESECOND DUPLICATEVOL

F2105WD HSM FIXCDSCOMMAND TODISPLAY MCT RECORD






2106C - MCC IS ONVOLUME WHICHHAS NO MCTENTRY

ERR041

ERR071

DSCTL (BACKUP)

MEDCTL, VOLCTL

Yes (defaults in2106V)

F2106CA TSOBDELETE BACK-UPVERSION MISSINGMCT

F2106CB HSM FIXCDSDISPLAY X FORMISSING MCT

F2106CC HSA VERIFYMCT RECORDMISSING

F2106CD TSOBDELETE BACKUPVER USING VER ANDFROMVOL

F2106CR1 HSMRECALL MIGRATEDDATA SET

F2106CR2 HSMBACKUP DATA SET

2106V - SUMMARYOF VOLUMESMISSING MCTENTRY

None Yes F2106VA TMSINTERROGATE TMSFOR HSM TAPESMISSING MCT

F2106VB HSM FIXCDSDISPLAY X FORMISSING MCT

F2106VC HSM FIXCDSTO ADD NEW MCTSPILL RECORD

F2106VD RMMINTERROGATE RMMFOR BACK-UPMISSING MCT

F2106VE HSM ADDVOLFOR BACKUP CYCLETAPE

F2106VG HSM ADDVOLFOR BACKUP SPILLTAPE

F2106VH TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT

116 User's Guide





2107W - MCC TAPEVOLUME HAS NOTTOC ENTRY

ERR014

ERR045

ERR071

DSCTL (BACKUP)

MEDCTL, VOLCTL

MEDCTL, VOLCTL

Yes (seerecommendation in2107V)

F2107WA HSM LISTTTOC FOR BACK-UPDSN MISSING TTOC

F2107WB TMSDISPLAY TMS STATUSFOR MISSING TTOCVOL

F2107WC TSOBDELETE BACK-UPVERSION MISSINGTTOC

F2107WR1 HSMRECALL MIGRATEDDATA SET

F2107WR2 HSMBACKUP DATA SET

2107V - SUMMARYOF VOLUMESMISSING TTOCENTRY

None F2107VA HSM LISTTTOC FOR BACK-UPDSN MISSING TTOC

F2107VB TMS DISPLAYTMS STATUS FORMISSING TTOC VOL

F2107VC RMMINTERROGATE RMMFOR HSM TAPESNote: It isrecommended that youuse Advanced Audit forDFSMShsm to rebuildthe TTOC.

F2107VD TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT






2109W - MCC ALIASIS NOT ON TTOC

ERR045 DSCTL (BACKUP) No F2109WA HSM LISTTTOC CONTENTS FORMISSING MCC

F2109WB TSOHBDELETE BACKUPVERSION MISSINGTTOC

F2109WC TSOHBDELETE BACKUPVERSION FROMVOL

F2109WR1 HSMRECALL MIGRATEDDATA SET

F2109WR2 HSMBACKUP DATA SET

2109V - SUMMARYOF VOLUMES MCCALIAS MISSINGTTOC ENTRY

ERR116 DIRCTL F2109VA HSM LISTTTOC VOLUME FORMCC MISSING TTOCENTRY

F2109VB HSM LISTTTOC FAILEDCREATE

F2109VC HSM AUDITMEDIA CONTROL FORMCC MISSING IN TTOC

F2109VD TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT

2111W - MCC ENTRYIS MISSING MCBENTRY

ERR040

ERR113

DSCTL (BACKUP)

DIRCTL

Yes F2111WA HSM FIXCDSDISPLAY B FOR MCCMISSING MCB

F2111WB HSM FIXCDSDELETE C FOR MCCMISSING MCB

2113I - BACK-UPTTOC VOLUME ISEMPTY

None F2113IA HSM LISTTTOC CONTENTS FOREMPTY VOLUME

2114W - BACKUPNAME EXISTS ONVTOC, MCC ISMISSING

ERR142 DIRCTL, MEDCTL Yes F2114WA TSOCATALOG ANDDELETE ORPHANEDL1 MCC ALIAS

118 User's Guide





2115W - VTOCBACKUP NAME HASVTOC ERROR

None F2115WA TSO DELETEBACK-UP DSN ON ML1WITH VTOC ERROR

F2115WB TSO DELETEBACK-UP VER ANDFROM VOL

2116W - MCBTRUENAME ISMISMATCHED WITHMCC ENTRY

ERR039 DSCTL No F2116WA HSM FIXCDSDISPLAY B FORMISMATCH MCC

F2116WB HSM FIXCDSDISPLAY C FOR MCBMISMATCH

2117W - MCCENTRY IS OWNEDBY DIFFERENT MCB

ERR040 DSCTL Yes F2117WA HSM FIXCDSDISPLAY B FOR MCCCONFLICT

F2117WB HSM FIXCDSDISPLAY C FOR MCBMISMATCH

F2117WC HSM FIXCDSPATCH C WITHCORRECT DSN

3101W - TAPE IS INMCV/MCT, NOT INTTOC

ERR051 MEDCTL, VOLCTL Yes F3101WA TMSINTERROGATE TMSFOR HSM TAPES SANSTTOC

F3101WB HSM VERIFYTTOC VOLUMEMISSING FROM OCDS

F3101WC ZRAINTERROGATE ZARAFOR HSM TAPES SANSTTO

F3101WD RMMINTERROGATE RMMFOR HSM TAPES

F3101WE HSM DELETEMCV RECORD FROMMCDS

F3101WF HSM FIXCDSDISPLAY THE TTOCRECORD FROM OCD

F3101WH HSMDELETE MCT RECORDFROM BCDS






3102C - TAPE IS INTTOC, NOT IN MCV/MCT

ERR071 MEDCTL, VOLCTL No F3102CA HSM FIXCDSDISPLAY V RECORDFOR MISSING MCV

F3102CB RMMINTERROGATE RMMFOR HSM TAPES

F3102CC HSM FIXCDSTO ADD NEW MCVLEVEL 2 RECORD

F3102CD HSM FIXCDSTO ADD NEW MCTSPILL TAPE

F3102CE HSM FIXCDSDISPLAY X RECORDFOR MISSING MCT

F3102CF HSM FIXCDSPATCH TTOC FORCOPY VOLUME

F3102CG HSM FIXCDSTO ADD NEW MCTCYCLE TAPE

F3102CH HSM FIXCDSDELETE X RECORD

F3102CI TMSINTERROGATE TMSFOR TAPE WITHENTRIES

3103C - TAPE ISNOT IN TTOC ORMCV/MCT BUT HASENTRIES

None F3103CA TMSINTERROGATE TMSFOR TAPE WITHENTRIES

F3103CB ZRAINTERROGATE ZARAFOR HSM TAPES WITHENTRIES

F3103CC RMMINTERROGATE RMMFOR HSM TAPES

F3103CR1 HSM BUILDLIST TTOC FOR TAPESW/ENTRIES

120 User's Guide





3104W - TAPE IS INTTOC & MCV/MCT,NOT IN TMS

None F3104WA TMSINTERROGATEEXPIRED TAPE IN CA1TMS

F3104WB ZRAINTERROGATEEXPIRED TAPE INZARA

F3104WC HSM LISTCONTENTS OF TAPEMISSING IN ZARA


F3104WE HSM FIXCDSDISPLAY OF TTOCRECORD

F3104WF HSM FIXCDSDISPLAY OF DVLRECORD

F3104WG HSM FIXCDST PATCH COPYVOLUME GONE

F3104WR1 HSM LISTACTIVE DATA FROMTAPE

F3104WR2 HSMDELVOL PURGE FORBACKUP VOLUMES

F3104WR3 HSMDELVOL PURGE FORML2 VOLUMES

F3104WR4 HSMDELVOL PURGE FORDUMP VOLUMES

F3104WS CNMINTERROGATECONTROL M FOR HSMTAPES






3110W - TAPE ISPERMANENT INTMS, NOT IN TTOC

None F3110WA HSM FIXCDSDISPLAY MCV FORTMS MISSING TTOC

F3110WB TMSINTERROGATE TAPEIN TMS, NOT IN TTOC

F3110WC RMMINTERROGATE RMMFOR HSM TAPES

F3110WD HSM FIXCDSDISPLAY OF DVLRECORD

F3110WE RMM EXPIREA TAPE VOLUMEASSIGNED TO HSM

F3110WR1 HSMADDVOL/DELVOL FORBACKUP TMS MISSINGTTOC

F3110WR2 HSMADDVOL/DELVOL FORLEVEL2 TMS MISSINGTTOC


F3110WT CTMCONTROL M SCRATCHTAPE VOLUMES

F3110WU TMC EXPIRETMS TAPES

F3110WV ZRA EXPIREZARA TAPES

122 User's Guide





3111W - TAPE IS INTMS, VALID IN HSM,HAS NO ENTRIES

None F3111WA TMSINTERROGATE TMSFOR EMPTY HSMTAPES

F3111WB HSM LISTCONTENTS OF TAPEWITH NO ENTRIES

F3111WC ZRAINTERROGATE ACTIVETAPE IN ZARA


F3111WE HSM FIXCDSTO ADD NEW MCVLEVEL 2 RECORD

F3111WF HSM FIXCDSDISPLAY OF MCVRECORD

F3111WR1 HSMDELVOL PURGE FORML2 VOLUMES

F3111WR2 HSMRECYCLE VOLUMESTHAT HAD VALID DATA

F3111WR3 HSMDELVOL PURGE FORBACKUP VOLUMES

F3111WR4 HSMDELVOL PURGE FORDUMP VOLUMES

F3111WR5 HSM AUDITMEDIACONTROLS FORRECYCLE







3112W - TAPE ISVALID IN HSM BUTEXPIRED IN TMS

None F3112WA TMSINTERROGATEEXPIRED TAPE IN CA1TMS

F3112WB HSM LISTCONTENTS OF TAPEEXPIRED IN TMS

F3112WC ZRAINTERROGATEEXPIRED TAPE INZARA


F3112WE HSMGENERATE FIXCDSDELETE FOR DUMPTAPE


3114I - TAPE IS INTMS SCRATCHSTATUS

None F3114IA RMMINTERROGATE RMMFOR HSM TAPES

F3114IS CNMINTERROGATECONTROL M FOR HSMTAPES

3115I - TAPE IS INTMS DELETESTATUS

None Information only

3116W - TAPE DOESNOT INDICATEEXTERNAL DATAMANAGEMENT

None F3116WA TMC RESETTHE EDM AND ETMFLAG IN THE TMC

F3116WB HSA VERIFYEXISTENCE OF TTOCRECORD

F3116WR1 HSM LISTTTOC FOR NON EDMTAPES

4001W - PREVIOUSVOLUME NOTFOUND IN OCDS

ERR119 DIRCTL, MEDCTL No F4001WA HSM FIXCDSCOMMAND TOCORRECT PREVIOUSVOL MISSING

124 User's Guide





4002W -SUCCESSORVOLUME NOTFOUND IN OCDS

ERR120 DIRCTL No F4002WA HSM FIXCDSCOMMAND TOCORRECTSUCCESSOR VOLMISSING

4003W - PREVIOUSVOLUME POINTERIS INCORRECT

ERR121

ERR123

DIRCTL

DIRCTL

No

No

F4003WA HSM FIXCDSCOMMAND TOCORRECT PREVIOUSVOL INCORRECT

4004W -SUCCESSORVOLUME POINTERIS INCORRECT

ERR122

ERR124

DIRCTL

DIRCTL

No

No

F4004WA HSM FIXCDSCOMMAND TOCORRECTSUCCESSOR VOLINCORRECT

4005C - TAPE HASFAILED CREATESTATUS

None F4005CA HSM AUDITMEDIA CONTROL FORSELECT FAILEDCREATE

4007C - TTOCRECORD HASBROKENSEQUENCE SET

ERR111 DIRCTL, MEDCTL Yes (seerecommendation in4007V)

F4007CB HSM FIXCDSDELETE OF TTOCEXTENSION RECORD

4007V - VOLUMECONTAINS BROKENSEQUENCESET/SETS

ERR111 DIRCTL, MEDCTL F4007VA HSM AUDITMEDIA CONTROL FORBROKEN SEQ SET

F4007VB HSM AUDITDIRECTORY CONTROLFOR BROKEN SEQSET

F4007VC TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT

F4007VR1 HSM LISTTTOC FOR VOLUME

F4007VR3 TMSINTERROGATE TMSFOR HSM TAPES WITHBROKEN SEQUENCE

F4007VR4 RMMINTERROGATE RMMFOR HSM TAPESNote: It isrecommended that yourun audit procedureAKDAUDFT.






4008C - TTOCEXTENSIONRECORDS ARELESS THANEXPECTED

ERR112 DIRCTL Yes F4008C TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT.

F4008CA HSM AUDITMEDIA CONTROL FOREXTENSION ERRORNote: It isrecommended that yourun audit procedureAKDAUDFT.

4009C - TTOCEXTENSIONRECORDS AREMORE THANEXPECTED

ERR112 DIRCTL Yes F4009CA HSM AUDITMEDIA CONTROL FOREXTENSION ERRORNote: It isrecommended that yourun audit procedureAKDAUDFT.

F4009CB TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT.

4010W - 16K BLOCKCOUNT DOES NOTMATCH COMPUTEDBLKCNT

ERR135 MEDCTL Yes F4010WA HSM AUDITDIRECTORY CONTROLFOR MISMATCHBLKCNTNote: It isrecommended that yourun audit procedureAKDAUDFT.

F4010WB TSO SUBMITAUDITMEDIACONTROLS JOBAKDAUDFT.

4011W - TAPE HASFAILED RECYCLE

None F4011WA HSM AUDITMEDIA CONTROL FORRECYCLE FAILED

F4011WR1 HSMRECYCLE VOLUMEBEFORE AUDIT

126 User's Guide





4012C - TAPE ISNOT FULL AND WILLNOT BE SELECTEDFOR RECYCLE

None F4012CA TSORECYCLE TAPE NOTFULL

F4012CB HSM LISTCONTENTS OF TAPE

F4012CR1 TSOMARKFULL ANDRECYCLE ML2 TAPES

F4012CR2 TSOMARKFULL ANDRECYCLE BACKUPTAPES

4013I - TAPE ISELIGIBLE FORRECYCLE

None F4013IA TSO RECYCLEELIGIBLE TAPE

8000I - LIST OFDATA SETSRECORDED INMCDS/BCDS

None F8000ID TSO HSENDRECOVER DATA SETFROM TAPE

8001C - NO HSMREFERENCEFOUND FORREQUESTED TAPE

ERR017

ERR050

ERR110

MCDS

BCDS

OCDS

No fixes

8C02C - NO MCTENTRY WAS FOUNDFOR REQUESTEDTAPE

ERR110 DIRCTL, MEDCTL No F8C02CA HSM FIXCDSTO ADD NEW MCTBACKUP RECORD

F8C02CB HSMADDVOL FOR BACKUPCYCLE TAPE

F8C02CC HSMADDVOL FOR BACKUPSPILL TAPE

8D02C - NO MCVENTRY WAS FOUNDFOR REQUESTEDTAPE

ERR110 DIRCTL, MEDCTL No F8D02CA HSM FIXCDSTO ADD NEW MCVLEVEL 2 RECORD






8003C - NO TTOCEXTENSION 0000WAS FOUND FORVOLSER

ERR071

ERR111

MEDCTL, VOLCTL,DIRCTL

Yes

Yes

F8003CA HSM VERIFYTTOC VOLUMEMISSING FROM OCDS

F8003CB HSM FIXCDSDISPLAY OF TTOCRECORDNote: The TTOCrecords will be rebuilt asa result of runningAKDAUDFT orAKDAUDFL.

8004W - VOLUME ISIN FAILED CREATESTATUS

ERR164 MEDCTL Yes F8004WA HSM FIXCDSDISPLAY OF TTOCRECORDNote: The TTOCrecords will be rebuilt asa result of runningAKDAUDFT orAKDAUDFL and theTTCFAIST patched off.

8005W - VOLUME ISIN FAILED RECYCLESTATUS

None F8005WA HSM FIXCDSDISPLAY OF TTOCRECORD

8006C - TTOCEXTENSIONRECORDS ARE OUTOF SEQUENCE

ERR112 DIRCTL Yes F8006CA HSM LISTTTOC CONTENTSNote: The TTOCrecords will be rebuilt asa result of runningAKDAUDFT orAKDAUDFL.

8007C - TTOCEXTENSIONRECORD ISCONTAMINATED

None F8007CA HSM LISTTTOC CONTENTSNote: The TTOCrecords will be rebuilt asa result of runningAKDAUDFT orAKDAUDFL.

8008C - TTOCEXTENSIONRECORDS DO NOTMATCH EXPECTEDCOUNT

ERR111

ERR112

DIRCTL, MEDCTL Yes

Yes

F8008CA HSM LISTTTOC CONTENTSNote: The TTOCrecords will be rebuilt asa result of runningAKDAUDFT orAKDAUDFL.

128 User's Guide





8009W - 16K BLOCKCOUNT DOES NOTMATCH COUNTEDBLOCKS

None F8009WA HSM FIXCDSPATCH BLKCOUNT INTTOC 0000EXTENSIONNote: The TTOCrecords will be rebuilt asa result of runningAKDAUDFT orAKDAUDFL and theBLKCNT will be patchedproperly.

8C10C - MCCEXISTS, NOT ONTAPE

ERR116

ERR150

DIRCTL, MEDCTL No

No

F8C10CA TSO HSENDBDEL BACKUPVERSION FROM BCDS

8D10C - MCDEXISTS, NOT ONTAPE

ERR150 MEDCTL No F8D10CA TSO HSENDDEL DATA SET FROMMCDS

F8D10CB TSO HSENDRECOVER DATA SETFROM BACKUP

F8D10CC TSO DISPLAYDATA SET FORBACKUP ANDMIGRATION INFO

8C12C - MCCMISMATCH FILEBLOCK IDENTIFIER

None F8C12CA HSM FIXCDSPATCH CORRECT FBIDIN THE MCC RECORD

8D12C - MCDMISMATCH FILEBLOCK IDENTIFIER

None F8D12CA HSM FIXCDSPATCH CORRECT FBIDIN THE MCD RECORD

8020I - LIST OFDATA SETS ONTAPE

ERR113

ERR140

ERR151

ERR152

DIRCTL, MEDCTL Available forrebuilding selectentries. Automationnot appropriate.

F8020IA HSM FIXCDSCREATE NEW MCDRECORD

F8020IB HSM FIXCDSCREATE ADD MCDDSORG PRIMARYVOLUME

F8020IC HSM FIXCDSCREATE ADD ALIASNAME AND FBID

F8020ID HSM FIXCDSCREATE ADD TTOCEXTENSION AND 16KBLKS


130 User's Guide

Chapter 13. The Query Language Feature

The Query Language feature, based on the ANSI standard Structured QueryLanguage (SQL), is used to create prototype logic, audit existing files, prepareconversion files, capture test data, obtain hexadecimal dump files of specificrecords, and extract records in their native format.

The Query Language feature addresses the broadest range of data processingneeds. It is not limited to a specific discipline, such as HSM or ICF catalogs. It isdesigned to run efficiently and requires no data conversion.

For example, you can process your input files by:

v comparing the contents of two files and merging the result when specific criteriais met

v sorting the selected data

v applying boolean logic

Query Language GuidelinesYou must following these guidelines when using the Query Language to define aquery and plans for multiple queries.

Query Guidelines

The Query Language is similar to the Structured Query Language (SQL). When youcreate a query, you include a group of Query Language statements that will processyour input file and select only the data you want.

You must place your statements in the following order:

1. Begin the query with one of the following:

v A SELECT statement to define the name of the fields you want to process inthe file.

v A JOIN statement to join the data from two input files.

2. Use the FROM statement to define one or more input data sets containing thefiles you want to process.

3. Use the CREATE statement to define the extract data set.

4. Use the USING statement to specify the file containing the Cobol map of theinput file.

5. Use the FROMKEY and TOKEY statements to define where to start theprocessing in a KSDS.

6. Use the WHERE statement to define how to filter the data.

7. Use the ORDER BY statement to sort the data.

Each query must follow these guidelines:

v Use a maximum of 12 lines, starting with the SELECT statement.

v Use only one SELECT or JOIN statement.

v Use the ORDER BY statement to end a query that begins with the SELECTstatement.

v Use the WHERE statement to end a query that begins with the JOIN statement.

131

Plan Guidelines

The Query Language feature allows you to group multiple queries together thatperform more complex processing of your data. To group multiple queries together,you must place each query in a plan. A plan contains a logical set of QueryLanguage statements that perform a single query. If you are performing a singlequery only, do not place it in a plan.

You must follow these rules when defining a plan:

v Specify the start of the plan as PLAN plan-name.

v Start the PLAN statement in column 1.

v Specify the end of the plan as END plan-name

v Start the END statement in column 1.

v Separate the PLAN and END statement from the plan-name with one blankspace.

v Place only one query in each plan.

Single Query Example

The following example shows a single query and does not require the PLAN andEND statements.* STORAGE GROUPS HIGH OCCUPANCE CAPTURESELECT SGROUP-HIGH,SPERCENT-OCC-HIFROM (HLQ.MONTHLY.SUM

HLQ.WEEKLY.SUM)USING HLQ.CNTL(STGPSUM)CREATE HLQ.STGP.WORK04.RAWHIORDER DISTINCT BY SGROUP-HIGH A, SPERCENT-OCC-HI D

Multiple Plans Example

The following example shows multiple plans called PLAN02 and PLAN04.PLAN PLAN02* STORAGE GROUPS LOW OCCUPANCY CAPTURESELECT SGROUP-LOW,SPERCENT-OCC-LOFROM (HLQ.MONTHLY.SUM

HLQ.WEEKLY.SUM)USING HLQ.CNTL(STGPSUM))CREATE HLQ.STGP.WORK04.RAWLOORDER DISTINCT BY SGROUP-LOW A, SPERCENT-OCC-LO AEND PLAN02PLAN PLAN04* ELIMINATE DUPLICATE STORAGE GROUPSSELECT SGROUP-LOW,SPERCENT-OCC-LOFROM HLQ.STGP.WORK04.RAWLOUSING DEFERREDCREATE HLQ.STGP.WORK04.LOW.CSVORDER DISTINCT BY SGROUP-LOW AEND PLAN04

CREATEUse the CREATE statement to build the extract data set to populate with theselected data from your query.

If the data set already exists, it is deleted and reallocated. If the data set does notexist, it is created as new. All data sets are allocated as RECFM=VB, LRECL=8192,and BLKSIZE=23476. The type of allocation units (CYLINDERS or TRACKS) and

132 User's Guide

the number of units are controlled by a member called AKDZ0035 in theSAKDCNTL library. You can change these allocation units as needed.

CREATE Data Set Example

You can specify the extract data set name is as a fully qualified data set name withno apostrophes.CREATE HLQ.DVLP.STGP.TR01MODL.CSV

FROMUse the FROM statement to identify the input data set name for the query.

Generation data sets (GDGs) are supported by their entire spelled out name or therelative number in parentheses. You can also concatenate multiple data set nameswithin parentheses.

Fully Qualified Data Set Name Example

Specify the fully-qualified data set name with no apostrophes.FROM DCD.DEMO.SUM

Concatenated Data Sets Example

Concatenate data sets in parenthetical statements.FROM (DCD.WEEKLY.SUM

DCD.MONTHLY.SUM)

Concatenated GDGs Example

Place the GDG's relative number in parentheses.FROM (HLQ.GDG.TEST(0)

HLQ.GDG.TEST(-1)HLQ.GDG.TEST(-2))

FROMKEYUse the FROMKEY statement to indicate where the processing should start in theinput data sets specified in the FROM statement.

In the case of a KSDS, such as the HSM CDS, the specified key value is used topoint to the location in the file to start reading.

You can use FROMKEY and TOKEY independently.

FROMKEY Example

In this example, the processing begins at the first MCD record in the HSM MCDSthat starts with DCD. It finishes after passing the last record containing DCD. Thisallows the process to skip uninteresting records and save a large amount ofprocessing overhead.* SAMPLE FROMKEY IN HEXSELECT MCDDSN,MCDVSN,MCDTLR,MCDDMIG

FROM (RLS1.HSM.SPLIT.MCDS1RLS1.HSM.SPLIT.MCDS2)

CREATE DCD.HSM.MCDPLAN1.FORMAT

Chapter 13. The Query Language Feature 133

USING DCD.MFL.MAPS(MCD)FROMKEY MCDDSN = 'DCD.'TOKEY MCDDSN = 'DCD.'WHERE MCHTYPE = X'00'AND MCDFLGS ON B'10000000'ORDER BY MCDDSN A

JOINUse the JOIN statement to conditionally join the contents of one extract with thecontents of a second extract.

The JOIN statements allows you to easily relate data from diverse sources withouthaving to create a formal database. For example, you can extract and join legacydata, such as the contents of an HSM CDS, with a catalog extraction.

A query that contains the JOIN statement references two extract data sets that havealready been created by a previous query so it does not contain the SELECTstatement.

When you use the JOIN statement, you must also specify the following:

v The WITH parameter for the name of the second file.

v The CREATE statement for the name of the third file containing the combinedextracts.

v The WHERE statement for the condition that determines how to join the datatogether.

The JOIN statement provides parameters you can specify on the OPTIONstatement that define how to treat mismatches in the file. The default is to showeverything.

v NONULLS—suppress mismatches

v NULLSONLY—show mismatches only

Step-by-Step JOIN Example

This example shows the step-by-step process of running two separate queries andthen joining their two data sets into a third data set.

Step 1—This step selects data from two data sets and creates the data setDCD.HSM.MCBPLAN.FORMAT.* SAMPLE FROMKEY IN HEXSELECT BDSN,MCBBDSN,MCBVSN,MCBDBUFROM (SIS.HSM.SPLIT.BCDS1

SIS.HSM.SPLIT.BCDS2)CREATE DCD.HSM.MCBPLAN.FORMATUSING DCD.MFL.MAPS(MCB)FROMKEY BDSN = X'C4'TOKEY BDSN = X'C4'WHERE BDSN EQ 'D'

AND MCBFLGS ON B'10000000'ORDER BY BDSN A

Step 2—This step selects data from two additional data sets and creates the dataset DCD.HSM.MCCPLAN.FORMAT.* SAMPLE MCC PLAN GENERATED BY TTOCSELECT MCCADSN,MCK,MCCVSN,MCCFBID(HEX)FROM (RLS1.HSM.SPLIT.BCDS1

134 User's Guide

RLS1.HSM.SPLIT.BCDS2)USING DCD.MFL.MAPS(MCC)CREATE DCD.HSM.MCCPLAN.FORMATWHERE MCHTYPE = X'24'AND MCK LK '.DS01.'ORDER BY MCCADSN A

Step 3—This step joins the two data sets DCD.HSM.MCBPLAN.FORMAT andDCD.HSM.MCCPLAN.FORMAT from the previous two queries.* SAMPLE JOIN PLANJOIN DCD.HSM.MCBPLAN.FORMATWITH DCD.HSM.MCCPLAN.FORMATCREATE DCD.HSM.JOIN.FORMATWHERE BDSN EQ MCCADSNOPTION NONULLS

You can run the queries described above as a multiple plan query.PLAN PLAN01* SAMPLE FROMKEY IN HEXSELECT BDSN,MCBBDSN,MCBVSN,MCBDBUFROM (SIS.HSM.SPLIT.BCDS1

SIS.HSM.SPLIT.BCDS2)CREATE DCD.HSM.MCBPLAN.FORMATUSING DCD.MFL.MAPS(MCB)FROMKEY BDSN = X'C4'TOKEY BDSN = X'C4'WHERE BDSN EQ 'D'

AND MCBFLGS ON B'10000000'ORDER BY BDSN AEND PLAN01PLAN PLAN02* SAMPLE MCC PLAN GENERATED BY TTOCSELECT MCCADSN,MCK,MCCVSN,MCCFBID(HEX)FROM (RLS1.HSM.SPLIT.BCDS1RLS1.HSM.SPLIT.BCDS2)USING DCD.MFL.MAPS(MCC)CREATE DCD.HSM.MCCPLAN.FORMATWHERE MCHTYPE = X'24'AND MCK LK '.DS01.'ORDER BY MCCADSN AEND PLAN02PLAN PLAN03* SAMPLE JOIN PLANJOIN DCD.HSM.MCBPLAN.FORMATWITH DCD.HSM.MCCPLAN.FORMATCREATE DCD.HSM.JOIN.FORMATWHERE BDSN EQ MCCADSNOPTION NONULLS

JOIN Example

This example shows how the lowest and highest occupancy level of all the storagegroups in the system are logically joined into a third file.JOIN HLQ.STGP.WORK04.LOW.CSV

WITH HLQ.STGP.WORK04.HIGH.CSVCREATE HLQ.STGP.WORK04.HILOWHERE SGROUP-LOW EQ SGROUP-HIGH

The following shows the low occupancy extraction for storage groups.AA=SGROUP-LOWA0=SPERCENT-OCC-LOAAAAAAAA AAAAAAAAAAA 000


ARCHIVE 060CONCPY 001CRPSG9 003CRSU1 041DB2SG 017DTS1 001DUANEG 001HSMBACK 001HSMMIGL1 041HSMMIGL2 009NOGROUP 025PROD 066SGBRMI 001

The following shows the high occupancy extraction for storage groups.AA=SGROUP-HIGHA0=SPERCENT-OCC-HIAAAAAAAA AAAAAAAAAAA 000ARCHIVE 063CONCPY 001CRPSG9 003CRSU1 041DB2SG 017DTS1 001DUANEG 001HSMBACK 001HSMMIGL1 050HSMMIGL2 009NOGROUP 028PROD 076SGBRMI 001

This following shows the JOIN results.AA=SGROUP-LOWA0=SPERCENT-OCC-LOAB=SGROUP-HIGHA1=SPERCENT-OCC-HIAAAAAAAA AAA AAAAAAAA AAAAAAAAAAA 000 BBBBBBBB 111ARCHIVE 060 ARCHIVE 063CONCPY 001 CONCPY 001CRPSG9 003 CRPSG9 003CRSU1 041 CRSU1 041DB2SG 017 DB2SG 017DTS1 001 DTS1 001DUANEG 001 DUANEG 001HSMBACK 001 HSMBACK 001HSMMIGL1 041 HSMMIGL1 050HSMMIGL2 009 HSMMIGL2 009NOGROUP 025 NOGROUP 028PROD 066 PROD 076SGBRMI 001 SGBRMI 001

Missing Values Example

Using the JOIN example above, this example shows how to use OPTIONNULLSONLY to list only values without a match.JOIN HLQ.STGP.WORK04.LOW.CSV

WITH HLQ.STGP.WORK04.HIGH.CSVCREATE HLQ.STGP.WORK04.HILOWHERE SGROUP-LOW EQ SGROUP-HIGHOPTION NULLSONLY

136 User's Guide

The results are shown below.AA=SGROUP-LOWA0=SPERCENT-OCC-LOAB=SGROUP-HIGHA1=SPERCENT-OCC-HIAAAAAAAA AAA AAAAAAAA AAAAAAAAAAA 000 BBBBBBBB 111CONCPY 001 ............CRSU1 041 ............DTS1 001 ............HSMBACK 001 ............HSMMIGL2 009 ............

No Matches Example

Using the JOIN example above, this example shows how to use OPTIONNONULLS to eliminate records that have no match.JOIN HLQ.STGP.WORK04.LOW.CSV

WITH HLQ.STGP.WORK04.HIGH.CSVCREATE HLQ.STGP.WORK04.HILOWHERE SGROUP-LOW EQ SGROUP-HIGHOPTION NONULLS

The results are shown below.AA=SGROUP-LOWA0=SPERCENT-OCC-LOAB=SGROUP-HIGHA1=SPERCENT-OCC-HIAAAAAAAA AAA AAAAAAAA AAAAAAAAAAA 000 BBBBBBBB 111ARCHIVE 060 ARCHIVE 063CRPSG9 003 CRPSG9 003DB2SG 017 DB2SG 017DUANEG 001 DUANEG 001HSMMIGL1 041 HSMMIGL1 050NOGROUP 025 NOGROUP 028PROD 066 PROD 076SGBRMI 001 SGBRMI 001

ORDER BYUse the ORDER BY statement to sort the selected data into ascending ordescending order and end the query.

To order the selected data in ascending order, specify A one space after the fieldname. To order the selected data in descending order, specify D one space afterthe field name. The default is to sort the data in ascending order.

You can specify the DISTINCT parameter to eliminate duplicate rows. You mustspecify the DISTINCT parameter before the BY keyword of the ORDER BYstatement.

All field names after the ORDER BY statement must also be specified in theSELECT statement. The ORDER BY statement ends the query.

Ascending Order Example

This example shows how to sort the data in ascending order by date and time.


* STORAGE GROUP NOGROUP AT 09 AM MONTHLYSELECT SDATE,STIME,SSYSID,SGROUP,SCAPACITY-CYLS,SALLOC-CYLS,

SPERCENT-OCC,SHIGH-THRSHFROM (HLQ.MONTHLY.SUM)USING HLQ.CNTL(STGPSUM))CREATE HLQ.STGP.TR01MODL.CSVWHERE SGROUP = 'NOGROUP'AND STIME = '07'ORDER BY SDATE A, STIME A

Remove Duplicate Rows Example

In this example, the data in the field SGROUP-HIGH is sorted in ascending orderand the data in the field SPERCENT-OCC-HI is sorted in descending order. TheDISTINCT parameter will then remove any duplicate rows.* STORAGE GROUPS HIGH OCCUPANCE CAPTURESELECT SGROUP-HIGH,SPERCENT-OCC-HIFROM (HLQ.MONTHLY.SUM

HLQ.WEEKLY.SUM)USING HLQ.CNTL(STGPSUM)CREATE HLQ.STGP.WORK04.RAWHIORDER DISTINCT BY SGROUP-HIGH A, SPERCENT-OCC-HI D

SELECTUse the SELECT statement to identify the names of the fields you want to extractfrom the input file.

The following lists the guidelines for the SELECT statement:

v Use to start the query.

v Separate each field with a comma.

v List additional fields on the next line and specify a comma after the last field onthe previous line.

v Select each field in the record from the position that it corresponds to in theCobol map.

v Specify SELECT * to extract the entire file.

v Specify SELECT *DUMP to print the selected records in a SNAP DUMP format.

v Do not use SELECT * or SELECT *DUMP with the ORDER BY statement.

SELECT Example

The following example shows the SELECT statement and some fields that areshown on mapping.SELECT SDATE,STIME,SSYSID,SGROUP,SCAPACITY-CYLS,SALLOC-CYLS,

SPERCENT-OCC,SHIGH-THRSH

In this example, the selected fields are matched with the Cobol map of the file.Additionally, all numeric fields are converted to display numeric. If a selected fieldoccurs more than once in a record, multiple selected lines are created.

01 STORAGE-GROUP-SUMMARY.* IBM JULIAN DATE FIELD SDATE

05 SDATE PIC 9(7).05 STIME PIC X(8).05 SSYSID PIC X(4).05 SGROUP-GROUP.10 SGROUP PIC X(8).05 SGROUP-H REDEFINES SGROUP-GROUP.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

138 User's Guide

05 SCAPACITY-CYLS PIC 9(13).05 SALLOC-CYLS PIC 9(13).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -05 OCCUPANCY.10 SPERCENT-OCC PIC 9(3).05 SHIGH-THRSH PIC 9(3).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -05 FILLER PIC X(13).

* FIELD DESCRIPTIONS FOLLOW.* SDATE DATE STORAGE GROUP SUMMARY WAS CREATED* STIME TIME STORAGE GROUP SUMMARY WAS CREATED* SSYSID SYSTEM IDENTIFIER* SGROUP NAME OF STORAGE GROUP* SVOLS NUMBER OF VOLUMES WITH GROUP* SCAPACITY-CYLS GROUP CAPACITY IN CYLINDERS* SFREE-CYLS NUMBER OF FREE CYLINDERS IN GROUP* SPERCENT-OCC STORAGE GROUP PERCENT ALLOCATED

The following example shows what the file would look like when you run theSELECT statement. Each selected field is assigned a pair of legend characters. TheDA=SDATE signifies the SDATE field. The same matching pair of legend characters arealigned vertically over the position in the record that represents that field as shownin the DA fields in the example below. This continues with each selected field. Theselection of the legends has significance in their names. For example, all legendswith D as the first character represent date fields. All legends with an alphacharacter in the second character represent alpha fields. All legend characters witha numeric as the second character represent numeric fields.

000001 DA=SDATE000002 AA=STIME000003 AB=SSYSID000004 AC=SGROUP000005 A0=SCAPACITY-CYLS000006 A1=SALLOC-CYLS000007 A2=SPERCENT-OCC000008 A3=SHIGH-THRSH

----+----1----+----2----+----3----+----4----+----5----+----6----+----7--000009 DDDDDDD AAAAAAAA AAAA AAAAAAAA AAAAAAAAAAAAA AAAAAAAAAAAAA AAA AAA?000010 AAAAAAA AAAAAAAA BBBB CCCCCCCC 0000000000000 1111111111111 222 333?000011 2005113 07:17:03 DVLP NOGROUP 0000001148598 0000000309789 027 085000012 2005114 07:14:11 DVLP NOGROUP 0000001151938 0000000310545 027 085000013 2005115 07:14:35 DVLP NOGROUP 0000001151938 0000000311342 028 085000014 2005116 07:19:04 DVLP NOGROUP 0000001148598 0000000307399 027 085000015 2005117 07:11:06 DVLP NOGROUP 0000001145258 0000000297359 026 085000016 2005118 07:13:47 DVLP NOGROUP 0000001145258 0000000295147 026 085000017 2005119 07:17:49 DVLP NOGROUP 0000001145258 0000000295439 026 085000018 2005120 07:20:23 DVLP NOGROUP 0000001145258 0000000295380 026 085000019 2005121 07:12:58 DVLP NOGROUP 0000001141918 0000000295374 026 085000020 2005122 07:13:31 DVLP NOGROUP 0000001141918 0000000295374 026 085000021 2005123 07:12:32 DVLP NOGROUP 0000001141918 0000000295414 026 085000022 2005124 07:15:05 DVLP NOGROUP 0000001141918 0000000295855 026 085000023 2005126 07:10:24 DVLP NOGROUP 0000001151938 0000000296569 026 085000024 2005127 07:11:19 DVLP NOGROUP 0000001148598 0000000295153 026 085000025 2005128 07:12:21 DVLP NOGROUP 0000001148598 0000000295138 026 085000026 2005129 07:13:10 DVLP NOGROUP 0000001148598 0000000295162 026 085

TOKEYUse the TOKEY statement to specify where the processing should end in theFROM data set.

After the key value specified in the argument is passed, processing stops.


USINGUse the USING statement to define the file that contains the Cobol map of the inputfile.

The data set name containing the Cobol map is specified as a fully-qualified dataset name with no apostrophes. The Cobol map can be a member of a PDS or asequential file.

If the input file has already been processed by the Query Language feature, youmust use the DEFERRED parameter.

Fully Qualified Data Set Name Example

This example shows a fully qualified data set name with no apostrophes.USING HLQ.CNTL(STGPSUM)

DEFERRED Parameter Example

This example shows the DEFERRED parameter in the query of PLAN03 becausethe query in PLAN01 has already processed the three input files using a Cobol mapin HLQ.CNTL(STGPSUM).PLAN PLAN01* STORAGE GROUPS HIGH OCCUPANCE CAPTURESELECT SGROUP-HIGH,SPERCENT-OCC-HIFROM (HLQ.MONTHLY.SUM

HLQ.WEEKLY.SUM)USING HLQ.CNTL(STGPSUM))CREATE HLQ.STGP.WORK04.RAWHIORDER DISTINCT BY SGROUP-HIGH A, SPERCENT-OCC-HI DEND PLAN01PLAN PLAN03* ELIMINATE DUPLICATE STORAGE GROUPSSELECT SGROUP-HIGH,SPERCENT-OCC-HIFROM HLQ.STGP.WORK04.RAWHIUSING DEFERREDCREATE HLQ.STGP.WORK04.HIGH.CSVORDER DISTINCT BY SGROUP-HIGH AEND PLAN03

WHEREUse the WHERE statement to specify the filtering for selecting specific data.

If the WHERE statement is not specified, all fields specified in the SELECTstatement are selected without any filtering (not recommended).

Follow these rules when using the WHERE statement:

v You can specify boolean operators.

v You can specify an AND or OR connector to each argument.

v You can use parenthetical statements. All conditions coded in parentheses areevaluated to be either true or false.

v You can specify NOT to reverse a true or false condition.

v The fields in the WHERE statement must exist in the Cobol map specified in theUSING statement.

v You cannot specify the literal before the field.

140 User's Guide

If you specify a boolean operator, such as LT (less than), the field specified in theWHERE statement is compared to the argument specified by the literal. If thecontent of the field is less than the specified literal, then the condition is true andthe record is included. The same logic applies for the GT (greater than) operator. Ifthe content of the field is greater than the literal, then the condition is true and therecord is included.

Literal Equals Example

This example shows a simple equate to a literal value.WHERE SGROUP EQ 'HSMML1'

Greater Than Example

This example shows a field called MIGDATE is compared to a field called BACKDATE inthe same record. If the contents of MIGDATE is greater than the contents of the datadescribed by BACKDATE, the condition is true.WHERE MIGDATE GT BACKDATE

AND Connector Example

This example shows two arguments connected with AND. In this case, botharguments must be satisfied before the record is selected.WHERE MIGDATE GT BACKDATE

AND VOLSER EQ '123456'

OR Connector Example

This example shows two arguments connected with OR. In this example, eithercondition may be true to cause record selection.WHERE MIGDATE GT BACKDATE

OR MIGDATE GT '*-5'

Parenthetical Arguments Example

This example shows parenthetical arguments.WHERE (MIGDATE GT BACK DATE

AND VOLSER EQ '123456')AND (MIGDSN EQ 'USERID.DATA.SET'

OR MIGDSN EQ 'ANOTHER.USER.DATA.SET')

Reversed Parenthetical Arguments Example

This example shows parenthetical arguments that are reversed by NOT.WHERE (MIGDATE GT BACK DATE

AND VOLSER EQ '123456')AND NOT(MIGDSN EQ 'USERID.DATA.SET'

OR MIGDSN EQ 'ANOTHER.USER.DATA.SET')

Boolean OperatorsThis topic describes the supported boolean operators you can specify on theWHERE statement.


Table 7. Boolean Operators

Operator Explanation

EQ or = The condition is TRUE if the contents of the data described by the first argumentis EQUAL TO the second argument.

NE or ^= The condition is TRUE if the contents of the data described by the first argumentis NOT EQUAL TO the second argument.

LT or < The condition is TRUE if the contents of the data described by the first argumentis LESS THAN the second argument.

GT or > The condition is TRUE if the contents of the data described by the first argumentis GREATER THAN the second argument.

LE or <= The condition is TRUE if the contents of the data described by the first argumentis LESS THAN OR EQUAL TO the second argument.

GE or >= The condition is TRUE if the contents of the data described by the first argumentis GREATER THAN OR EQUAL TO the second argument.

NH or ^> The condition is TRUE if the contents of the data described by the first argumentis NOT HIGHER THAN the second argument.

NL or ^< The condition is TRUE if the contents of the data described by the first argumentis NOT LOWER THAN the second argument.

Extended Boolean OperatorsThis topic describes the extended boolean operators you can specify on theWHERE statement.

Table 8. Extended Boolean Operators


LIKE or LK ~(tilde)

The condition is TRUE if the string of data described by the secondargument occurs anywhere in the first argument. This is useful toidentify data in the data field that is unpredictable or free form.

NK The condition is TRUE if the string of data described by the secondargument does NOT occur anywhere in the first argument. This isuseful to identify data in the data field that is unpredictable or free form.

AE The string of data described by the second argument must be an ACSfilter pattern. The condition is TRUE if the filter pattern matches the firstargument. This is useful when working with OS/390® data set namingconventions. For example, WHERE DSN1 AE 'USERID.**.CNTL'.

AN The string of data described by the second argument must be an ACSfilter pattern. The condition is TRUE if the filter pattern does NOT matchthe first argument. This is useful when working with OS/390 data setnaming conventions. For example, WHERE DSN2 AN'USERID.*.CLIST'.

IS NUMERIC The condition is TRUE if the contents of the data described by the firstargument contains valid numeric data. Numeric data is described aspacked decimal, fixed point binary or display numeric. The condition isFALSE if a field described as numeric is compared to a numeric literalthat is not numeric. This evaluation ensures the data is numeric beforethe comparison is made.

IS NOTNUMERIC

The condition is TRUE if the content of the data described by the firstargument contains non-numeric data. Numeric data is described aspacked decimal, fixed point binary, or display numeric. This is useful foridentifying data in a file that should be numeric, but it is not.

142 User's Guide

Table 8. Extended Boolean Operators (continued)


IS NULL The condition is TRUE if the content of the data described by the firstargument contains all null data (hex zeroes).

IS NOT NULL The condition is TRUE if the content of the data described by the firstargument does NOT contain all null data (hex zeroes).

ON OS/390 files such as the HSM Control Data Sets contain many bitsettings that have meaning. ANSI SQL statements do not provide theseoperators. The condition is TRUE if the bit pattern described by thesecond argument all match. For example, WHERE MCDFLGS ONB'10000000'.

OFF The condition is TRUE if the bit pattern described by the secondargument has no matching bits. For example, WHERE MCDFLGS OFFB'10000000'.

MIX The condition is TRUE if the bit pattern described by the secondargument has some matching bits. For example, WHERE MCDFLGSOFF B'10001000'.

Argument LiteralsThis topic describes how to deal with literals in an argument specified on theWHERE statement.

You must enclose literals in the argument within apostrophes. The length of thevalue specified in the literal is used for the length of the compare. For example, if avalue like DCD.THIS.IS.A.LOGN.NAME is compared to DCD. as an equal value, thecondition would be true. DCD. matches the first four characters of the field in theargument.

Table 9. Argument Literals


Relative dateargument

If the field being examined is described in the map as a date, a relativedate argument may be coded in the argument field. Each time the queryis processed, this date is computed from today’s date plus or minus thenumeric value after the asterisk. For example, '*-5'.

BINARY For bit manipulation, an argument may be presented in a bit patternformat. For example B'10000000' is interpreted as value X'80' in thequery.

HEX Typically, the values coded are in EBCDIC format, but sometimesvalues exist in the files that cannot be represented by anything otherthan hexadecimal equivalents. Therefore, the HEX argument literal isprovided. For example, X'4040' represents two blanks. The argumentbuilt in the query would be translated to two blanks.

NUMBERS Numerical values are converted to the packed for binary arithmeticvalues before comparing. If the field specified in argument one isdisplay, the compare follows the length rules of the literal as opposed toevaluating the entire number.


144 User's Guide

Chapter 14. Notices

This information was developed for products and services offered in the U.S.A. IBMmay not offer the products, services, or features discussed in this document in othercountries. Consult your local IBM representative for information on the products andservices 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, orservice may be used. Any functionally equivalent product, program, or service thatdoes 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-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not apply toyou.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvements and/orchanges in the product(s) and/or the program(s) described in this publication at anytime without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseWeb sites. The materials at those Web sites are not part of the materials for thisIBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believesappropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programs

145

and other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:

IBM CorporationJ46A/G4555 Bailey AvenueSan Jose, CA 95141-1003U.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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of thoseproducts, their published announcements or other publicly available sources. IBMhas not tested those products and cannot confirm the accuracy of performance,compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of thoseproducts.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate 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 programsconforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughlytested under all conditions. IBM, therefore, cannot guarantee or imply reliability,serviceability, or function of these programs. You may copy, modify, and distribute

146 User's Guide

these sample programs in any form without payment to IBM for the purposes ofdeveloping, using, marketing, or distributing application programs conforming toIBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information softcopy, the photographs and color illustrationsmay not appear.

TrademarksThe following terms are trademarks of International Business Machines Corporationin the United States, other countries, or both.

IBM z/OS

IBM logo OS/390

ibm.com RACF

AIX MVS

BookManager OMEGAMON

DFSMS DFSMShsm

DFSMSdfp DFSORT

DFSMSdss REXX

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the Unites States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the UnitedStates, other countries, or both.

Other company, product, and service names may be trademarks or service marksof others.

Chapter 14. Notices 147

148 User's Guide

Glossary

AAlias. The name HSM assigns to a migrated orbackup of a data set. For example:HSM.HMIG.T120906.FA390.AUDIT.I6034. This aliasname might represent the migrated version ofFA390.CNTL.

BBCDS. Backup Control Data Set. This is a KSDSVSAM Cluster that contains information about thebackup versions of data sets.

CCDD. Common Data Set Descriptor record.Non-compressed dsname on a tape volume proceededby ’*CDD**’.

Cycle. For this document, cycle means a cycle daynumber assigned to a backup tape that contains backupcopies. A similar backup tape inventory is Spill.

LL2. L2 or ML2 is a term meaning Level 2 tape. Whena migrated data set is in L2 it means that it is on tape.

MMCA. Migration Control Data Set Alias Entry Record.Typically this is an alias name assigned to a true namefor a migrated data set. However, VSAM componentnames (data, index path, and so on) are alsoconsidered MCA records but are true names for theVSAM components. An MCA record has no significantinformation required to recall a data set. Mostly it isused to manage the tape recycle process.

MCB. Backup Control Data Set Record. This record isan entry in the BCDS. It is the actual true name forbackup versions. A single MCB contains informationabout all backup versions of the data set.

MCC. Backup Control Data Set Backup VersionRecord. This record is an entry in the BCDS. It is theHSM generated alias name and contains criticalinformation to recover a data set.

MCD. Migration Control Data Set Record. This recordis an entry in the MCDS. It is the true name for amigrated data set. This record must exist for a data setto be recalled.

MCDS. Migration Control Data Set. This is the VSAMcluster that contains information about migrated data.

MCO. Migration Control Data Set VSAM AssociationsRecord. This is a record in the MCDS that containsinformation about the VSAM components of a migrateddata set, such as Index name, Data name, Path name,AIX name, and so on.

MCT. Backup Control Data Set Backup VolumeRecord. This is a record in the BCDS. It containsinformation about the backup volumes and must existbefore a data set can be recovered.

MCV. Migration Control Data Set Volume Record. Thisis a record in the MCDS. It contains information aboutthe migration volumes and must exist before a data setcan be recalled.

OOCDS. Offline Control Data Set. This is the VSAMcluster that contains information about the tape volumesused for Migration Level 2 and Backup tapes. Itsprimary purpose is to maintain tape usage statistics forrecycle functions.

RRecycle. Recycle is a term used by IBM formaintaining the HSM tape inventory. As data stored ontapes expires, is recalled, or otherwise is no longervalid, the information on the tapes needs to be deletedin order to free up the space. To do this, HSM copiesvalid data from an old tape to a new tape and drops offunneeded data. This frees up the old tape for reuse.

RLS. Record Level Sharing is an OS/390 servicesupported by the SYSPLEX Coupling Facility. RLSpermits multiple OS/390 systems to concurrently shareVSAM files on shared DASD while in update mode,without compromising either file update integrity orperformance.

RMM. Removable Media Manager.

SSDSP. Small Data Set Packing. This is a function usedby HSM to pack data that occupies less than one trackinto a VSAM cluster. One track is the smallest allocationa data set can have. If an installation has many datasets smaller than one track, they can direct migration tothe SDSP cluster and save significant space.

Spill. Spill is a term used for recycled backup tapes.Original backup is directed to a cycle tape. The recycle

149

of the cycle tapes goes to spill volumes. Cycle tapesare assigned to a number (1 through 31) for the backupthat runs on those days of the month.

TTape Inventory. An external (to HSM) system tomanage an installation’s tape inventory.

TMS. Tape Management System. This term refers tothe Computer Associates CA1 Tape ManagementSystem. It is a system that contains information abouttape (cartridges) used in an MVS environment.

TTOC. Tape Table Of Contents. This is a record in theOCDS. It contains information about migrated/backedup data to tape. It is used to control recycle processes.

VVTOC. Volume Table Of Contents. For those data setsmigrated or backed up to Level 1 (except SDSP) anentry in the direct access volume is placed in its VTOC.

150 User's Guide

Index

Aaccess to HSM commands 36Active Allocations report 32address space 41, 42Administrative Menu 33Administrative Tasks 33

Cchanging JCL for started task 34changing started task data set names 35CNTL members 37communication

cross-system, about 13OMVS segment definition requirement 13

CONNECTION keyword 13Control Data Set Backup Information 31Control Data Sets report 31cross-system communications 13Customization Menu 34

Ddata sets allocated 41data sets used 40DFSMShsm Host Reports 29

Eenqueues 42error messages 18

HHSM CDS Backups report 31HSM command access 36HSM Host Information 30HSM information 29HSM Reports 29

Iissue commands 32Issuing HSM commands 32

Llist CNTL members 37list PARMLIB members 36list PLAN members 36listing data sets 40listing data sets allocated 41listing enqueues 42LOCALCONN keyword 13

Mmessage retrieval tool, LookAt viimessages 18, 43

methods for acessing viimulti-system communications 13

Nnot using the started task 17

OOMVS segment definition

requirement for using cross-systemcommunications 13

override started task data set names 35

PPARMLIB data set members 36PLAN members 36PORTNUM keyword 13Product Menu 39product messages 43

Rrelease 40

Sstarted task JCL parameters 34starting the interface 17SYSCHKINTVL keyword 13system connection 44

TTCP/IP

OMVS segment definition requirement 13using for cross-system communications 13

TIMEOUT keyword 13

UUSEEXSYS 13USERWAIT 13using the started task 17

Vversion 40viewing version and release level data 40virtual storage 42

151

Wwork data set 43

152 User's Guide

��

Program Number: 5698–B12

Printed in USA

SC27-2347-01

publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/itaafdfsm/sc27-2347-01/en_us/p… ·...

Documents