Data Express 4.0. Toolkit for z/os

Transcription

1 Data Express 4.0 Toolkit for z/os

2 Micro Focus (IP) Ltd. The Lawn Old Bath Road Newbury, Berkshire RG14 1QN UK Copyright Micro Focus (IP) Limited. All Rights Reserved. MICRO FOCUS, the Micro Focus logo and are trademarks or registered trademarks of Micro Focus (IP) Limited or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. All other marks are the property of their respective owners. ii

3 Contents About this Guide...4 Publications...5 Considerations...6 Load Sequential File with DB2 Catalog...7 Load IMPSRC for Life Cycle...8 DB2 Catalog Synchronization...9 Create CSV File from Referential Integrity...10 Load Sequential File with ADABAS FDT Report...11 Toolkit Tables...12 Contents 3

4 About this Guide This guide outlines the concepts and procedures used by the Data Express Toolkit, which is a collection of utilities that help provide input to Data Express processes in order to automate data inventory functionality. It shows how to start and work with the toolkit in a mainframe environment. This guide is for users who want to verify the integrity of data contained in databases (DB2 or DL/I) or data sets (VSAM, SEQUENTIAL, or GDG) of applications running on z/os systems that are either developed internally or purchased by external suppliers. The use of Data Express requires a minimum experience of z/os. 4 About this Guide

5 Publications The following documentation is available for Data Express: Data Masking Guide Data Model Guide Data Subset Extraction Guide Error Messages Front End Guide Getting Started with Distributed Data Stores Getting Started with z/os Data Stores Installation Guide Life Cycle Guide Process for z/os Guide Readme Toolkit (z/os) Guide This guide outlines the concepts and procedures used by the Data Masking module. Data Masking makes sensitive data anonymous in application test environments while maintaining the same characteristics as the original data. This guide provides descriptions of the table structures used in the Data Builder, Data Masking, and Data Subset Extraction modules. This guide outlines the concepts and procedures used by the Data Subset Extraction module. Data Subset Extraction uses selection criteria specified by the user to create a new test environment from an existing environment. This guide provides a detailed list of all warning, error, and informational messages that can be displayed in log files during batch processing or on the screen during elaboration processing. This guide outlines the concepts and procedures used by Data Express, a product that lets you analyze the database of a given application. This guide contains explanatory information and a series of tutorials that show you how to start using Data Express. The tutorials introduce the major features in a number of short sessions, typically minutes. This guide contains explanatory information and a series of tutorials that show you how to start using Data Express in order to analyze and manage data stores from System z servers running z/os. The tutorials introduce the major features in a number of short sessions, typically minutes. This guide outlines the concepts and procedures needed to install Data Express. This guide provides step-by-step instructions to help you handle modifications within the layout of the files already processed by Data Express. This guide outlines the concepts and procedures used by Data Express for z/os. It shows how to start and work with Data Express in the mainframe environment. Contains general information on the product including hardware and software requirements, backward compatibility, and known errors and restrictions. This guide outlines the concepts and procedures used by the Data Express Toolkit, which is a collection of utilities that help provide input to Data Express processes in order to automate data inventory functionality. It shows how to start and work with the Toolkit in a mainframe environment. Publications 5

6 Considerations Bear in mind the following points about Data Express: You do not need to analyze the sources of the programs in the application in order to use Data Express. This product does not perform any operation capable of altering the analyzed data. To use this product, you must have the correct licence. Refer to the Installation Guide for more details. The tables defined during the installation phase and updated by the toolkit are described in the Appendix A. Toolkit Tables. 6 Considerations

7 Load Sequential File with DB2 Catalog The process Load Sequential File reads the DB2 system catalog (starting from the list of tables that need to be loaded into the knowledge base), and then produces the sequential file containing the information needed for the load. After a new Load File From External Interface job is created and scheduled, the sequential file is used when the job executes to perform the load. For more information about the data inventory process, see the section Data Inventory in the chapter Project Implementation in the Process Guide for z/os. For information about the structure of the output sequential file, see the section Direct Access - API Load Sequential File in the chapter Sequential Files in the Data Model Guide. Note: The filename listed in the FILENAME field can be indicated by a partial name or the special value '*ALL'. The function will then populate all the DB2 tables with the name in accordance with the value specified. To load the sequential file with the DB2 catalog: 1. From the Main Menu panel, enter the following command: TSO CUINFIL. 2. Specify the company name and press Enter. 3. Insert parameter names into all fields as required: Data Set Name Inp Data Set Name Out Process Id Select Count Name of the sequential file which contains the list of the files that must be loaded into Data Express. Name of the sequential file which will be created from this function, with all the information about the files that must be loaded into Data Express. Identifier for the process. Type of select to get the total number of records: 1. select count on DB2 table (slowest). 2. select on SYSIBM.SYSTBALES (fastest). 3. select on SYSIBM.SYSTBALES and if there aren't statistics, a select count on the DB2 table is performed. Load Sequential File with DB2 Catalog 7

8 Load IMPSRC for Life Cycle The Life Cycle is a feature that enables automatic updates for file layout information. The Life Cycle process can use a guide file, which is a sequential file with a name that is similar to the project and group specification and followed by the IMPSRC file. It can be completed by the user (using an interface from Endevor, Changeman, or any other change management tool) or directly with the job Load Sequential for Life Cycle. The job Load Sequential for Life Cycle writes the IMPSRC file (starting from a PDS with the copy loaded in the knowledge base or from a DB2 owner (schema)) with all the copy or the new or changed DB2 tables. After a new job is created and scheduled, the IMPSRC file is used when the job executes to schedule the Life Cycle phases. Note: The Life Cycle process uses only one IMPSRC file. Therefore, we recommend that the process be executed for every DB2 owner (database schema) or for every partitioned data set. For more information about the Life Cycle, see the chapter Life Cycle in the Process Guide for z/os. To load the IMPSRC file for the Life Cycle: 1. From the Main Menu panel, enter the following command: TSO CUINLIC. 2. Insert parameter names into all fields as required: Data Set Type Data Set Name Select Count Mode with which you want to work. Note: Like the Analyze FDT report, the Life Cycle for ADABAS lets you analyze an FDT report, but with the difference that you can analyze multiple FDT Reports simultaneously. Name of the partitioned data set or DB2 Owner (schema name) with which you want to work. Note: If you are using Life Cycle for ADABAS, the data set name must be the name of the PDS file that contains the desired FDT Report as a member. Type of select to get the total number of records: 1. select count on DB2 table (slowest). 2. select on SYSIBM.SYSTBALES (fastest). 3. select on SYSIBM.SYSTBALES and if there are no statistics, a select count on the DB2 table is performed. 8 Load IMPSRC for Life Cycle

9 DB2 Catalog Synchronization Use the z/os process DB2 Catalog Synchronization to produce the sequential file containing the information needed for the load, unless the file can be produced in another manner. After a new DB2 Catalog Synchronization (client) job is created and scheduled, the sequential file is used when the job executes to load information for the cardinality for DB2 tables and the existence of a key or the existence of an image copy into the knowledge base. The DB2 Catalog Synchronization (client) job should be executed before beginning the data subset extraction process, so that all the information is synchronized and this process can be independent of the system tables. For more information about the job, see the section DB2 Catalog Synchronization Job in the chapter Work with Jobs in the Front End Guide. Note: For information about the structure of the output sequential files for HEADER, INTERNAL KEY, EXTERNAL KEY, and IMAGE COPY see the section DB2 Catalog Synchronization Information in the chapter Sequential Files in the Data Model Guide. To synchronize the DB2 catalog: 1. From the Main Menu panel, enter the following command: TSO CUINSYNC. 2. Indicate the scope of the process by specifying the DB2 tables you need in the DB2 Owner and Table Name fields, and the name of the sequential file in the Data Set Name field. Note: For the DB2 Owner and Table Name fields, you can specify *ALL if you want to process all owner names or all table names. DB2 Catalog Synchronization 9

10 Create CSV File from Referential Integrity The process Create CSV file from Referential Integrity analyzes a SQL DDL generated by the Erwin Data Modeler that describes the referential integrity relation using the IBM DB2 standard, and then creates a CSV file that contains all relations described in the DDL. After a new Import Method From Referential Integrity job is created and scheduled, the CSV file is used when the job executes to create the method needed to generate the test environment. For more information about method creation, see the chapter Data Subsetting in the Process Guide for z/os. To create the CSV file from referential integrity: 1. From the Main Menu panel, enter the following command: TSO CVTEARI. 2. Insert parameter names into fields as required: PDS or Data set name Source Name CSV data set name Name of the DDL source data set or PDS containing the referential integrity relation generated by the Erwin Data Modeler. Name of the member of PDS that contains the DDL generated by the Erwin Data Modeler. Name of the CSV data set that will contain the referential integrity relation. The CSV data set will be created if it does not exist. If it already exists, it will be written in append mode. 10 Create CSV File from Referential Integrity

11 Load Sequential File with ADABAS FDT Report The process Analyze ADABAS FDT report reads the FDT Report source sequential file (generated by the command ADAREP REPORT) and then produces the output sequential file containing the information needed for the load. After a new Load Data Store From External Interface job is created and scheduled, the output sequential file is used when the job executes to perform the load. For more information about the Data Inventory process, see the section Data Inventory in the chapter Project Implementation in the Process Guide for z/os. For information about the structure of the output sequential file, see the section ADABAS - API Load Sequential File in the chapter Sequential Files in the Data Model Guide. To load the sequential file with the ADABAS FDT report: 1. From the Main Menu panel, enter the following command: TSO CVURAAD. 2. Select the appropriate Machine ID and company name, and press Enter. The Analyze ADABAS FDT report (BURAAD) panel displays. 3. Insert parameter names into fields as required: PDS or data set name Name of the PDS or sequential file that contains the FDT report ADABAS files. Source Name Data Set Name Out Name of the member that contains the FDT report ADABAS files. Name of the sequential file to create which will contain all the information about the ADABAS files that must be loaded into Data Express. Load Sequential File with ADABAS FDT Report 11

12 Toolkit Tables During toolkit installation, the following tables are created: Table Name HSSYSCKS HSSYSCOL HSSYSDAU HSSYSDBA HSSYSDEP HSSYSFKE HSSYSIND HSSYSIPA HSSYSKEY HSSYSRAU HSSYSREL HSSYSSYN HSSYSTAB HSSYSTAU HSSYSTPA HSSYSTSP HSSYSVDE HSSYSVIE HSURDCOL HSURDSYC Description View of SYSIBM.SYSCHECKS View of SYSIBM.SYSCOLUMNS View of SYSIBM.SYSDBAUTH View of SYSIBM.SYSDATABASE View of SYSIBM.SYSCHECKDEP View of SYSIBM.SYSFOREIGNKEYS View of SYSIBM.SYSINDEXES View of SYSIBM.SYSINDEXPART View of SYSIBM.SYSKEYS View of SYSIBM.SYSRESAUTH View of SYSIBM.SYSRELS View of SYSIBM.SYSSYNONYMS View of SYSIBM.SYSTABLES View of SYSIBM.SYSTABAUTH View of SYSIBM.SYSTABLEPART View of SYSIBM.SYSTABLESPACE View of SYSIBM.SYSVIEWDEP View of SYSIBM.SYSVIEWS View of SYSIBM.SYSCOLUMNS View of SYSIBM.SYSCOPY 12 Toolkit Tables

13 Index A about this guide 4 C considerations 6 create CSV file from referential integrity 10 D DB2 catalog synchronization 9 L load IMPSRC for life cycle 8 load sequential file 7 load sequential file with ADABAS FDT report 11 T toolkit tables 12 Index 13