IBM Tivoli Advanced Audit for DFSMShsm. User's Guide. Version 2 Release 3 SC

Transcription

1 IBM Tivoli Advanced Audit for DFSMShsm User's Guide Version 2 Release 3 SC

2

3 IBM Tivoli Advanced Audit for DFSMShsm User's Guide Version 2 Release 3 SC

4 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 (product number 5698-B12) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright Rocket Software Inc.,

5 Contents About this information vii Who should read this book vii Service updates and support information vii How to look up message explanations vii Searching an information center vii Using a Web search viii Using LookAt viii How to send your comments viii Figures ix Tables xi Chapter 1. Introduction to Advanced Audit for DFSMShsm What does Advanced Audit for DFSMShsm do? Advanced Audit for DFSMShsm components Prerequisites Accessibility features Chapter 2. Advanced Audit for DFSMShsm Configuration Configuration Summary Step 1: Run AKDCRRUN Step 2: Run AKDINIMG Step 3: Update AKDINI Step 4: Customize PARMLIB member AKDCMD Step 5: Run AKDJCLBD Step 6: Run AKDSYMBL Step 7: Run AKDPLANS Step 8: Run AKDGLOBA Step 9: Modify Product JCL Library Members Step 10: Modify Product SAKDCLST Library Step 11: Create User JOB Card Member Step 12: APF Authorize SAKDLOAD Library Step 13: Start the AKDJMAIN started task Step 14: Add AKD07735 to the Authorized Programs List Step 15: Ensure RACF ALTER Authority for User ID Step 16: Define OMVS segment for the started task Step 17: Configure the Display of EBCDIC Characters AKDCMD00 configuration values AKDCMD00 keyword syntax and descriptions About cross-system communications AKDCMD00 cross-system communication keyword syntax and descriptions 14 Chapter 3. Getting Started About the Interface Starting the Advanced Audit for DFSMShsm Interface The Advanced Audit for DFSMShsm Main Menu Viewing Messages Exiting Advanced Audit for DFSMShsm Filtering Pattern Masks Chapter 4. Performing an Audit The Advanced Audit for DFSMShsm panel iii

6 Running an Audit Procedure Including and Excluding Catalogs Audit Procedures for Control Data Sets AKDAUDAL Audit Procedure AKDAUDBD Audit Procedure AKDAUDCM Audit Procedure AKDAUDCT Audit Procedure AKDAUDMD Audit Procedure AKDAUDOD Audit Procedure AKDAUDRM Audit Procedure AKDAUDTP Audit Procedure AKDAUDZR Audit Procedure Audit Procedures for DFSMShsm-Owned Tapes AKDAUDFD Audit Procedure AKDAUDFL Audit Procedure AKDAUDFT Audit Procedure OPTION Keyword Chapter 5. Gathering HSM Host Information The DFSMShsm Host Reports panel HSM Host Information report Control Data Sets report HSM CDS Backups report Active Allocations report Issuing HSM commands Chapter 6. Performing Administrative Tasks The Administrative Tasks panel The Customization Menu panel Testing user access to HSM commands Listing PARMLIB data set members Listing PLAN data set members Listing CNTL data set members Chapter 7. Viewing product information Viewing version and release level data Listing data sets used during processing Listing data sets allocated to the address space Listing enqueues held by the address space Displaying address space virtual storage information Displaying product message documentation Displaying product work data set information Displaying a list of system connections Chapter 8. Correcting Errors Automatic Error Correction Error Threshold Monitoring Automatic Error Correction Quick Reference Analyzing and Correcting Errors Manually Browsing Audit Results Modifying Audit Results Using SDSF to Monitor Automatic Fixes Chapter 9. Messages and Codes for Advanced Audit for DFSMShsm Product Error Messages Audit Diagnostic Messages iv User's Guide

7 Chapter 10. AKDINI Configuration Values PRODUCT_INFO CUSTOMER_ENVIRON AKD_DATASETS PRODUCT_DATASETS DEFAULT_ALLOC_PARMS DEFAULT_JOB_PARMS Chapter 11. Snap Dump Utility Chapter 12. Advanced Audit for DFSMShsm and HSM Equivalents Advanced Audit for DFSMShsm and HSM Audit Equivalents Advanced Audit for DFSMShsm and HSM Diagnostic Error Equivalents Chapter 13. The Query Language Feature Query Language Guidelines CREATE FROM FROMKEY JOIN ORDER BY SELECT TOKEY USING WHERE Boolean Operators Extended Boolean Operators Argument Literals Chapter 14. Notices Trademarks Glossary Index Contents v

8 vi User's Guide

9 About this information Who should read this book This user's guide provides instructions for using IBM Tivoli Advanced Audit for DFSMShsm. To use the procedures in this user's guide, you must have already installed Advanced Audit using the SMP/E installation process that came with the product. This document provides instructions for installing, configuring, and using IBM Tivoli Advanced Audit for DFSMShsm. This information is designed to help system administrators 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 This book is intended for Storage Administrators, System Programmers, and Technical Managers responsible for maintaining DFSMShsm Control Data Sets and the associated records within them. The authors of this book assume that most readers are data processing professionals. Service updates and support information To 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: The IBM Tivoli Advanced Audit for DFSMShsm Library Web page provides current product documentation that you can view, print, and download. To locate publications with the most up-to-date information, refer to the following Web page: How to look up message explanations You can use any of the following methods to search for messages and codes: Searching an information center In 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 Information Center, enter the number of the message that you want to locate. For example, you can 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 v Enter the complete or partial message number. You can use wild cards (* or?) in the message number to broaden your search; for example, DFS20??I. vii

10 The information center contains the latest message information for all of the information management products that are included in the information center. Using a Web search You can use any of the popular search engines that are available on the Web to search for message explanations. When you type the specific message number or code into the search engine, you will be presented with links to the message information in IBM information centers. Using LookAt LookAt is an online facility that you can use to look up explanations for most of the IBM messages you encounter, as well as for some system abends and codes. Using LookAt to find information is faster than a conventional search because in most cases LookAt goes directly to the message explanation. How to send your comments You can use LookAt from the following locations to find IBM message explanations for z/os elements and features, z/vm, VSE/ESA, and Clusters for AIX and Linux : v v v v The Internet. You can access IBM message explanations directly from the LookAt Web site at Your z/os TSO/E host system. You can install code on your z/os or z/ose systems to access IBM message explanations, using LookAt from a TSO/E command line (for example, TSO/E prompt, ISPF, or z/os UNIX System Services running OMVS). Your Microsoft Windows workstation. You can install code to access IBM message explanations on the z/os Collection (SK3T-4269) using LookAt from a Microsoft Windows command prompt (also known as the DOS command line). Your wireless handheld device. You can use the LookAt Mobile Edition with a handheld device that has wireless access and an Internet browser (for example, Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera for Linux handheld devices). Link to the LookAt Mobile Edition from the LookAt Web site. You can obtain code to install LookAt on your host system or Microsoft Windows workstation from a disk on your z/os Collection (SK3T-4269) or from the LookAt Web site (click Download, and select the platform, release, collection, and location that suit your needs). More information is available in the LOOKAT.ME files available during the download process. Your feedback is important in helping to provide the most accurate and high-quality information. If you have any comments about this book or any other IBM Tools documentation, use either of the following options: v Use the online reader comment form, which is located at: v Send your comments by to comments@us.ibm.com. Be sure to include the name of the book, the part number of the book, the version of Advanced Audit 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

11 Figures 1. Advanced Audit for DFSMShsm Main Menu AKD710 The audit panel The Host Menu panel The Administrative Menu panel The Customization Menu panel The JCLPARMS panel, 1 of The JCLPARMS panel, 2 of The DSNPARMS panel The Product Menu panel The Data Sets Being Used by this Product panel The Filtering Values for Data Sets Allocated to Address Space panel The Data Sets Allocated to Address Space panel ix

12 x User's Guide

13 Tables 1. Configuration Steps Filtering Pattern Masks SAKDCNTL Members Referred to by the SELECTS or SELECTI DD Statement Additional Records Displayed Advanced Audit for DFSMShsm and HSM Audit Equivalent Advanced Audit for DFSMShsm and HSM Audit Error Equivalents Boolean Operators Extended Boolean Operators Argument Literals xi

14 xii User's Guide

15 Chapter 1. Introduction to Advanced Audit for DFSMShsm These topics introduce you to the functionality that is provided with IBM Tivoli Advanced Audit for DFSMShsm, including its major components and some of the key benefits of using it. What does Advanced Audit for DFSMShsm do? IBM Tivoli Advanced Audit for DFSMShsm delivers a set of auditing commands that help support the health of the control data sets. Without fast, accurate, and reliable audits, you risk losing access not only to your z/os data, but also all your HSM migrated data. To avoid serious outages, you need a powerful data interrogation solution that keeps your z/os environment trouble-free with high-speed, accurate, and flexible audits. Advanced Audit for DFSMShsm helps you keep your z/os environment trouble-free with fast, accurate, and flexible audits. With Advanced Audit for DFSMShsm, storage administrators can maintain healthy metadata environments and prevent temporary or permanent loss of data access. Advanced Audit for DFSMShsm provides extremely fast and accurate audits and diagnostics, as well as automatic corrective 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, and corrective 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 and corrective actions. v Complete control over which meta data structures are audited. v Complete control over which diagnostic aid or corrective action is implemented for your unique environment. v Flexibility to edit JCL and corrective action commands to apply fix control statements 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 components Advanced Audit for DFSMShsm consists of two audit components: the auditing of HSM 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 help resolve structural and logical discrepancies that can prevent migrated data from 1

16 being recalled, or backup data from being restored. It correlates entries with the ICF catalog environment to help maintain consistency. Advanced Audit for DFSMShsm helps you audit and correct errors with your DFSMShsm migration and backup tapes. It works outside of the DFSMShsm environment to correct errors that it finds and has customer-documented benchmark speeds faster than the traditional DFSMShsm AUDITMEDIACONTROLS command. Prerequisites Accessibility features Advanced 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 features help a user who has a physical disability, such as restricted mobility 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 magnifier software. Consult the assistive technology documentation for specific information when 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 the following 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 or function keys (PF keys), include the default settings for the PF keys, and explain how to modify their functions. 2 User's Guide

17 Chapter 2. Advanced Audit for DFSMShsm Configuration Configuration Summary After you install Advanced Audit for DFSMShsm using the installation instructions provided in the IBM Tivoli Advanced Audit for DFSMShsm Program Directory, that is included with the product, you must configure Advanced Audit for DFSMShsm for your environment. The following table summarizes the steps that are required to configure Advanced Audit 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 AKDCRRUN AKDCRRUN creates a set of runtime libraries using the target libraries as the source. 1. Copy the JCL AKDCRRUN from the SAKDJCL target library and place it in a personal PDS. 2. Modify the parameter TGTHLQ to reflect the high level qualifier of the target libraries. 3. Modify the PPFX to reflect the high level qualifer of the runtime libraries that this job creates. 4. Submit the job using a valid jobcard. You can continue with the configuration using these newly created runtime libraries. 3

18 Step 2: Run AKDINIMG Step 3: Update AKDINI Run the AKDINIMG member of the ppfx.sakdjcl library to create a new AKDINI SAKDPARM 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 name and specify AKDINI# as the member name. If this is the first time running this job, 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 0 before proceeding to the next configuration step. If the job terminates with a non-zero completion code, first check to see if any error messages indicate a situation that is easily correctable. You can run AKDINIMG multiple times. If the situation does not appear to be easily correctable, please contact Technical Support before proceeding to the next configuration step. Modify the values in the AKDINI member of the SAKDPARM library, which controls many product functions. 1. Use ISPF Edit to update the values. Be sure to review all of the tokens in the AKDINI member and set appropriate values for your installation. Pay particular attention 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 AKDCMD00 Modify 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 skip this step. If not running the AKD started task, you can access the online ISPF audit screens by executing CLIST AKDAUDIT instead of AKDSTART. To customize the SAKDPARM member AKDCMD00: 1. Change the data sets listed in the member to point to appropriate Advanced Audit 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 available parameters. 4 User's Guide

19 Step 5: Run AKDJCLBD Step 6: Run AKDSYMBL Step 7: Run AKDPLANS Run the AKDJCLBD member of the SAKDJCL library to substitute variables coded in the AKDINI into the SAKDJCL members. 1. Modify the AKDJCLBD job as indicated by the comments at the beginning of the member. 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. Run the member AKDSYMBL to update the SYMBOLIC member of the ppfxx.sakdcntl library. This step retrieves information you have established in AKDINI and inserts it with the proper format into member SYMBOLIC. Add the proper JOBCARD information and submit the job. Run the member AKDPLANS of the SAKDJCL library to create a PLANS library. The PLANS library contains PLANS and FIXES used by Advanced Audit for DFSMShsm. Step 8: Run AKDGLOBA Run the member AKDGLOBA of the SAKDJCL library to allocate a Global Summary History file. The Global Summary History file contains history records produced by all of the different Audit jobs. The records are kept for a default setting of 999 days. This default setting can be changed by modifying the KEEP_HISTORY_DAYS = 999 parameter in the AKDINI member in the SAKDPARM library. Step 9: Modify Product JCL Library Members Modify the following ppfx.sakdjcl library members for your installation. These jobs are not intended to be submitted directly by you, but are used internally by Advanced Audit for DFSMShsm processes. Please note that some fields will still be blank after you have completed this step. The rest of the JCL will be generated by the Advanced Audit for DFSMShsm audit process at execution time. 1. Modify the SYSPROC and JCLLIB statements in member AKDBTTSO so that ppfx is the product prefix assigned to Advanced Audit for DFSMShsm by your installation. 2. Change the ZARACAT and the ZARAVLT data set names in member AKDBTZRA to match the ZARA data sets installed in your system. If your installation does not use ZARA TMS, then ignore this step. 3. Change the SYSPROC statement in member AKDBDTTC of ppfx.sakdjcl to the SAKDCLST library as installed. The DSN= and SPACE= statements must remain blank so when the fix create process is run, these two statements are filled in with the appropriate parameters. Chapter 2. Advanced Audit for DFSMShsm Configuration 5

20 Note: Use of the SMS construct to release unused space after a data set is closed can cause problems when running Advanced Audit for DFSMShsm fixes. HSM closes and opens the data set specified by ODS in the control statements frequently. This causes space to be released when it may still be required. It is recommended that you use a MGMTCLAS 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 the production 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 dump format. The Snap Dump utility will also display HSM records and display them in a dump format. If you use multi-cluster CDSs, you must include the names of all the CDS splits in the AKDBATCH member in the ppfx.sakdjcl library. 5. Change the AUDIT statement in member AKDTMSBQ, to the CA1 AUDIT data set name installed in your system. In a typical TMS installation, there is no need to specify the AUDIT DSName. If your installation does not use CA1 TMS, then ignore this step. 6. After running AKDJCLBD, make the following changes to the batch cataloged procedures AKDAUDxx: a. Change the JOB control statement to suit your environment. b. Choose a JOB CLASS that allows about five minutes of processing time (it takes a while to capture and analyze all of the information in an entire installation). 7. Add started task JCL AKDJMAIN to a system PROC Library This JCL can also be 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 Library Modify the ppfx.sakdclst library for your installation. Modify FSTPLB in the AKDMONTR member of the SAKDCLST library with the installation s SAKDLOAD library. Replace the xxxxxxxx.load with the name of the SAKDLOAD library installed for Advanced Audit for DFSMShsm Important: If you are going to use the started task, then you do not need to make these changes to AKDAUDIT member. Modify AKDAUDIT member of the SAKDCLST library. 1. Change HLQ.AKD0203 to your product prefix, the same value you gave to PPFX in the AKDINI member in SAKDPARM library. 2. Change RUNTIME.R23 to your runtime prefix, the same value as you gave to PFX in the AKDINI member in SAKDPARM library. If you decide not to run the AKD started task, you can access the online ISPF audit screens by executing clist AKDAUDIT instead of AKDSTART. Step 11: Create User JOB Card Member Each person executing corrective actions or diagnostic aids must have a unique member in ppfx.sakdcntl containing their JOB card information. 6 User's Guide

21 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 of the user and is suffixed by the letter J (for JOB card). For example, you would create a job card member DDAVENJ for user ID DDAVEN. In some environments, security groups are utilized to provide sufficient authority to the user ID executing programs in batch; others accomplish this with the use of a GROUP parameter on your JOB card. For example, GROUP=ARCCATGP. To implement this, your security administrator must add your user ID to the GROUP specified in the parameter. Using this parameter on the JOB card provides the proper security authority to READ ICF catalogs required for some of the audit procedures. Although the audit procedure only reads ICF catalogs, ALTER access may be required. Security software and procedures vary so consult your security administrator for the proper procedures to follow in your environment. Step 12: APF Authorize SAKDLOAD Library The Advanced Audit for DFSMShsm product SAKDLOAD library requires explicit APF authorization, even if it appears in the system link list with the LINKAUTH=LNKLST option. If the contents of the product SAKDLOAD library are copied to another SAKDLOAD library, it must be APF authorized. Although SMS managed load libraries can be assigned APF authorization, most installations prefer to have all authorized libraries reside on specific non-sms system volumes. Step 13: Start the AKDJMAIN started task Start task AKDJMAIN on every system on which users will access the online Advanced Audit for DFSMShsm ISPF Panels. Important: If you decide not to run the AKD started task then you can skip this step. Step 14: Add AKD07735 to the Authorized Programs List You must add the program AKD07735 to the AUTHPGM NAMES list of SYS1.PARMLIB member IKJTSO00. The program AKD07735 is used by the automatic fix process to interrogate the HSM address space to determine how many commands may be safely submitted at any one time Step 15: Ensure RACF ALTER Authority for User ID Ensure 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 IBM requirement, the user submitting the job must have RACF ALTER authority. Step 16: Define OMVS segment for the started task To take advantage of cross system communication between Advanced Audit for DFSMShsm instances that reside on different systems, you must define an OMVS segment for the started task. Chapter 2. Advanced Audit for DFSMShsm Configuration 7

22 The started task requires UNIX System Services access. The user ID under which the started task runs must have an OMVS segment in its RACF profile. To check whether 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 Characters If the code tables used by your installation are different, then you must enter the EBCDIC character peculiar to your code tables that results in the binary value for the EBCDIC character specified in the product manuals. Advanced Audit for DFSMShsm uses the U.S.A. EBCDIC code set for specification and display of EBCDIC characters and for the extended ACS masking characters used for filtering. v Data supplied as input to batch programs For product code shipped in binary, when specifying input where the product takes special action based on specific characters, you must enter the EBCDIC character peculiar to your code tables that results in the binary value for the EBCDIC character specified in the product manuals, according to the U.S.A. EBCDIC code set. For example, if an exclamation mark (!) iscalled for, and your code tables do not translate the! character to a hexadecimal 5A, you must enter the character that your code table will translate to a 5A. v Product output Depictions of product output shown in the product manuals are based on the U.S.A. EBCDIC code set. Actual output may vary if your EBCDIC code tables are different. v Extended ACS masking characters Your installation may need to specify different masking characters to achieve the desired result if your code tables are different from the U.S.A. EBCDIC code set. AKDCMD00 configuration values This section describes the structure of the AKDCMD00 PARMLIB member, its syntax 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 organized by sections. The general format for a token statement is: Keyword = Parameter or Keyword = (Parameter1, Parameter2,..., Parametern) Leading blanks from the beginning of the logical card-image records are allowed for all statements. Syntax scan processing locates the first non-blank character in each 8 User's Guide

23 logical record. The entire length of the 80-byte logical record is considered for valid data. Do not renumber the AKDCMD00 member; sequence numbers assigned in columns 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 of this 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 is entirely blank can also be considered a comment. v Entire lines, blocks of lines, or portions of a line can be commented by beginning the comment with a '/*' and terminating the comment with a '*/'. AKDCMD00 keyword syntax and descriptions These 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 Syntax Acceptable values Example None CLIST_DSN=clist.dsn.name Specify any valid data set name. CLIST_DSN=AKD.SAKDCLST CNTL_DSN Name(s) of the product library containing sample members. Default value Syntax Acceptable values Example None CNTL_DSN=sample.dsn.name Specify any valid data set name. CNTL_DSN=AKD.SAKDCNTL MSGS_DSN Name(s) of the product library containing the message members. Default value Syntax Acceptable values Example None MSGS_DSN=messages.dsn.name Specify any valid data set name. MSGS_DSN=AKD.SAKDMSGS Chapter 2. Advanced Audit for DFSMShsm Configuration 9

24 OPFX Operational prefix for the audit dataset allocations. Ensure this is the same prefix as used in the PFX parameter in the AKDINI member. Default value Syntax Acceptable values Example None OPFX=hlq1.hlq2 Specify any valid high-level qualifier, 1-13 bytes. OPFX=AKD.WORK PLANS_DSN Name(s) of the product library containing PLANS members. This is the dataset name which is created in job AKDPLANS in the SAKDJCL library. Default value Syntax Acceptable values Example None PLANS_DSN=plans.dsn.name Specify any valid data set name. PLANS_DSN=AKD.PLANS PLIB_DSN Name(s) of the product library containing ISPF panels. Default value Syntax Acceptable values Example None PLIB_DSN=panels.dsn.name Specify any valid data set name. PLIB_DSN=AKD.SAKDPENU PPFX Product library prefix. Name of the product library prefix. Default value Syntax Acceptable values Example None PPFX=hlq1.hlq2 Specify any valid high-level qualifier. PPFX=AKD0203.AKD Optional parameters JOBCARD1 First line to be used when creating JCL. Default value Syntax Acceptable values Not applicable JOBCARD1='jobcard data' 3 to 60 bytes of data delimited by single quote (') marks. 10 User's Guide

25 Example JOBCARD1='//AKDJOB JOB (Acct),''AKD job'',' JOBCARD2 Second line to be used when creating JCL. Default value Syntax Acceptable values Example Not applicable JOBCARD2='jobcard data' 3 to 60 bytes of data delimited by single quote (') marks. JOBCARD2='// MSGCLASS=A,CLASS=B,' JOBCARD3 Third line to be used when creating JCL. Default value Syntax Acceptable values Example Not applicable JOBCARD3='jobcard data' 3 to 60 bytes of data delimited by single quote (') marks. JOBCARD3='// NOTIFY=&SYSUID' JOBCARD4 Fourth line to be used when creating JCL. Default value Syntax Acceptable values Example Not applicable JOBCARD4='jobcard data' 3 to 60 bytes of data delimited by single quote (') marks. JOBCARD4='//*' JOBCARD5 Fifth line to be used when creating JCL. Default value Syntax Acceptable values Example Not applicable JOBCARD5='jobcard data' 3 to 60 bytes of data delimited by single quote (') marks. JOBCARD5='//* ' WORKDC SMS data class name to be used for file allocations. Default value Syntax Acceptable values Example None WORKDC=dataclas Any valid SMS data class, 1 8bytes. WORKDC=DC001 Chapter 2. Advanced Audit for DFSMShsm Configuration 11

26 WORKMC SMS management class name to be used for file allocations. Default value Syntax Acceptable values Example None WORKDC=mgmtclas Any valid SMS management class, 1 8bytes. 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 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 Example WORKSEC=10 WORKSC SMS storage class name to be used for file allocations. Default value Syntax Acceptable values Example None WORKSC=storclas Any valid SMS storage class, 1 8bytes. WORKSC=SC002 WORKUNIT UNIT name to be used for file allocations. Default value Syntax Acceptable values Example SYSALLDA WORKUNIT=unitname Any valid unit name, 1 8bytes. WORKUNIT=AKDUNIT 12 User's Guide

27 About cross-system communications With this release, Advanced Audit for DFSMShsm can use TCP/IP services to communicate with Advanced Audit for DFSMShsm address spaces on multiple systems, which allows you to coordinate work on multiple systems by retrieving and distributing information across a multi-system complex. If you intend to take advantage of cross-system communications, you need to specify appropriate values for the parameters described in this section. However, if you do not intend to use cross-system communications, there is no need to set up these parameters. If you intend to use the cross-system communication feature, be aware that an OMVS segment must be defined for the Advanced Audit for DFSMShsm address space. As it is used here, the generic term network is used to define whatever setup you find convenient. You can include all systems in your network or you can segregate some of your systems in any way that makes processing easier. In general, a network should be set up in such a way that it encompasses an entire DFSMShsm configuration. Usually, the control data sets are shared within a SYSPLEX only. If there is more than one SYSPLEX at your site, you can establish a separate network for each DFSMShsm complex. When control data sets are shared between multiple systems (spanning multiple SYSPLEXes), the network must include all systems that are accessing that set of control data sets. When control data sets are shared within a SYSPLEX, it is recommended that you set up a separate network for each SYSPLEX. AKDCMD00 provides several options to help facilitate network definition. The usage of system symbols is supported within the AKDCMD00 member, in any value. For example, if SYSNAME were defined to the name of the local system and the DNS token for all systems is the system name followed by MYSHOP.COM, only one LOCALCONN 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 local system name. v Use the IF_SYSPLEX statement to specify a condition based on the SYSPLEX name. Note: You can use masking characters in your specifications for these conditional statements. If a conditional statement is true, any parameters following the statement are accepted; if a conditional statement is false, any parameters following the statement are ignored. Consider an example in which the goal is to use one AKDCMD00 member for all systems, but to specify different parameter values for each SYSPLEX: LOCALCONN=&SYSNAME..IP.ADDRESS IF_SYSPLEX=PRODPLEX CONNECTION=PROD1.IP.ADDRESS CONNECTION=PROD2.IP.ADDRESS IF_SYSPLEX=TESTPLEX CONNECTION=TEST1.IP.ADDRESS CONNECTION=TEST2.IP.ADDRESS Alternatively, you could use a masking character to specify the SYSNAME: Chapter 2. Advanced Audit for DFSMShsm Configuration 13

28 IF_SYSNAME=P* CONNECTION=PROD1.IP.ADDRESS CONNECTION=PROD2.IP.ADDRESS AKDCMD00 cross-system communication keyword syntax and descriptions These are the required and optional keywords to enable cross-system communication. Important: These three parameters, properly set up, are required to successfully setup cross-system communications: v PORTNUM v CONNECTION v LOCALCONN CONNECTION One CONNECTION statement is needed for each system that is to be part of this network. You also need one for the local system connection. Default value Syntax Acceptable values Example LOCALCONN None CONNECTION = <ip address or dns name> Specify any valid IP address or DNS name. CONNECTION = <ip address or dns name> Local connection IP address or DNS name. This entry should also have a corresponding CONNECTION statement. To use this member for more than one system, use the following example to see how to code values for different systems. Default value Syntax Acceptable values Example PORTNUM None LOCALCONN = <ip address or dns name> Specify any valid IP address or DNS name. IF_SYSNAME = SYSTEM1 LOCALCONN = SYSTEM1.DNS.NAME IF_SYSNAME = SYSTEM2 LOCALCONN = SYSTEM2.IP.ADDRESS Port number to use for the connections. This should be the same number on every system. Default value None Syntax PORTNUM = Acceptable values Specify any valid port number. Example PORTNUM = User's Guide

29 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 Acceptable values Specify any valid integer. Example TIMEOUT = 60 USEXSYS For any cross system processing to be attempted, this parm must be set to YES. Default value Syntax Acceptable values Example USERWAIT NO USEXSYS = YES Specify YES or NO. USEXSYS = YES Wait time in seconds for user requests. If no response is received within this time interval, the request is ended early. Default value 300 Syntax USERWAIT = 300 Acceptable values Specify any valid integer. Example USERWAIT = 300 Chapter 2. Advanced Audit for DFSMShsm Configuration 15

30 16 User's Guide

31 Chapter 3. Getting Started About the Interface This chapter helps you start using Advanced Audit for DFSMShsm and describes other general topics about its use. Advanced Audit for DFSMShsm provides an ISPF-based interface that allows you to easily 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 task then 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 Interface There 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 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 CLIST has been copied to a system CLIST library, you can issue %AKDSTART. 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 CLIST has been copied to a system CLIST library, you can issue %AKDAUDIT. The Advanced Audit for DFSMShsm Main Menu This topic describes the options that are available from the Advanced Audit for DFSMShsm Main Menu (MAINMENU) panel. 17

32 MAINMENU IBM Tivoli Advanced Audit for DFSMShsm V2R :07 Command ===> Scroll ===> PAGE Main Menu: Row 1 of 5 Report Name Description 1 Auditing Auditing Data 2 HSM Host Information Information on DFSMShsm Hosts 3 Administrative Tasks Administrative Functions 4 Product Information Product Information Figure 1. Advanced Audit for DFSMShsm Main Menu The valid options are: 1 Auditing displays a list of the available classic auditing data. 2 HSM Host Information displays information about the DFSMShsm Hosts that are actively running on this system. 3 Administrative Tasks displays a menu of administrative tasks that can be performed. 4 Product Information displays a menu of product level information. These options are described in detail in the following chapters. Viewing Messages Advanced Audit for DFSMShsm allows you to view the error messages and their help. 1. Put the cursor on the HELP pull-down menu at the top of the panel and press Enter. 2. Select 3. Product Messages. 3. When the message viewing filter panel displays you can: v v enter a specific message number and leave message member blank to display a specific message 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 DFSMShsm To exit Advanced Audit for DFSMShsm, either type END on the command line or press PF3 from the Main menu panel. Filtering Pattern Masks Many commands allow you to specify powerful filtering masks using extended ACS masking characters, as shown in the following table. 18 User's Guide

33 Note: Your installation may need to specify different masking characters to achieve the desired result if your code tables are different from the U.S.A. EBCDIC code set. Table 2. Filtering Pattern Masks Mask Hex Description * (Single) 5C Represents 0-n characters. You can specify this wildcard character before an item, after an item, or both to designate a wildcard position. You can not use an * in the middle of a single item (except for data set names) Use the % character instead. For example, *PROD will select an item if the last four characters are PROD regardless of the starting characters. Using the * character before and after an item (for example, *ZREM*) means that item is to be selected if any character string matches ZREM in its name. % 6C Denotes a single character placeholder value, which can be alpha-numeric or any special character. The % character can be used in any position order. For example, CRM%%ER6 will select an item if it is 8-characters in length, the first three characters are CRM, the last three characters are ER6. The two middle placeholder values can be any characters. < 4C Denotes a placeholder value for only alpha characters. The < character can be used in any position order. For example, CR<<ER* will select an item if the first two characters are CR, the first and third characters are alpha, the fifth and sixth characters are ER, and the rest are any remaining characters. Chapter 3. Getting Started 19

34 Table 2. Filtering Pattern Masks (continued) Mask Hex Description > 6E Denotes a placeholder value for only numeric characters. The > character can be used in any position order. For example, CR>>ER* will select an item if the first two characters are CR, the third and fourth characters are numeric, the fifth and sixth characters are ER, and the rest are any remaining character. ** (Double) 5C5C Allows compatibility with standard ACS and DFSMSdss filtering masks. This mask is used only for partially qualified data set names. The * or ** characters can be used in any qualifier position to denote a wildcard node. For example, CRFM*.*VER.** will select a data set entry if it has at least two qualifiers and the first qualifier starts with CRFM, the second qualifier must end with VER, and any remaining qualifiers. Note: As with common data set name masking, any combination of *, **, %, < and/or > characters can be used for the item mask value.! 5A Denotes a placeholder value for only national characters (based on the U.S.A. EBCDIC code set. The! character can be used in any position order. National characters, based on the U.S.A. EBCDIC code set, are:@#$. 20 User's Guide

35 Chapter 4. Performing an Audit This chapter describes how to setup and run the audit procedures provided with Advanced Audit for DFSMShsm. The Advanced Audit for DFSMShsm panel When you enter option 1 on the MAINMENU panel and press Enter, the audit panel appears: AKD IBM Tivoli Advanced Audit for DFSMShsm V2R :43 Command ===> Scroll ===> PAGE 1 MCDS Created by procs AKDAUDMD, AKDAUDCT, AKDAUDAL 2 BCDS Created by proc AKDAUDBD 3 OCDS Created by proc AKDAUDOD 4 HSMTAPE Created by procs AKDAUDTP, AKDAUDZR, AKDAUDRM, AKDAUDCM 5 MEDCTL Created by procs AKDAUDFD, AKDAUDFL, AKDAUDFT Figure 2. AKD710 The audit panel Running an Audit Procedure The options that are available from the Advanced Audit for DFSMShsm (AKD710) panel are: 1 MCDS Type 1 to access the audit results from the audit procedures AKDAUDMD, AKDAUDCT, AKDAUDAL. 2 BCDS Type 2 to access the audit results from the audit procedure AKDAUDBD. 3 OCDS Type 3 to access the audit results from the audit procedure AKDAUDOD. 4 HSMTAPE Type 4 to access the audit results from the audit procedures AKDAUDTP, AKDAUDZR, AKDAUDRM, AKDAUDCM. 5 MEDCTL Type 5 to access the audit results from the audit procedures AKDAUDFD, AKDAUDFL, AKDAUDFT. This 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 running the audit procedures. See Step 11: Create User JOB Card Member on page 6 for more information. 21

36 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 specific catalogs from the audit. 4. Type SUBMIT to run the audit procedure. Make sure the audit procedure JCL finished successfully before viewing or correcting any auditing errors. Note: 1. It is suggested that all data sets allocated by the audit procedures run under SMS control. There are several programs in the audit procedures which create a data set, close it, and then another module is linked which looks up the catalog for the data set just created. If the data set is not cataloged, the system issues a NOT CAT message. Data sets under SMS control must be cataloged upon creation time thus circumventing this issue. 2. It is best to run the audit procedures during those times of lowest HSM activity 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 maximum performance for the audits. Including and Excluding Catalogs The audit procedures AKDAUDAL and AKDAUDCT allow you to include or exclude catalogs from the audit. The exclude member for each audit procedure is in the ppfx.sakdcntl library. For the audit procedure AKDAUDAL, the exclude member is AKDZXCAL and for the audit 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 audit procedure 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 Audit Procedure on page 23 for additional information on what to include or exclude for each audit procedure. The following shows an example list of included catalogs for an audit procedure: INCLUDES FOLLOW USERCAT.UCAT1 FACUCAT.FORTY.FOUR.BYTE.CATALOG.NAME.X FACUCAT.FORTY.FOUR.BYTE.CATALOG.NAME.X The following shows an example list of excluded catalogs for an audit procedure: EXCLUDES FOLLOW ICF.ZAPP02 CRTUCAT.EH.REORG01 If you use multi-cluster CDSs, you must: 22 User's Guide