Micro Focus. Data Express. Requirements and Installation Procedures

Transcription

1 Micro Focus Data Express Requirements and Installation Procedures

2 Copyright Micro Focus (IP) Ltd. All rights reserved. Micro Focus (IP) Ltd. has made every effort to ensure that this book is correct and accurate, but reserves the right to make changes without notice at its sole discretion at any time. The software described in this document is supplied under a license and may be used or copied only in accordance with the terms of such license, and in particular any warranty of fitness of Micro Focus software products for any particular purpose is expressly excluded and in no event will Micro Focus be liable for any consequential loss. Animator, COBOL Workbench, EnterpriseLink, Mainframe Express, Micro Focus, Net Express, REQL, and Revolve are registered trademarks, and AAI, Analyzer, Application Server, Application to Application Interface, AddPack, AppTrack, AssetMiner, CCI, DataConnect, Dialog System, Enterprise Server, Enterprise Server with MTO, EuroSmart, FixPack, LEVEL II COBOL, License Server, Mainframe Access, Mainframe Manager, Micro Focus COBOL, Micro Focus Studio, Micro Focus Server, Object COBOL, OpenESQL, Personal COBOL, Professional COBOL, Server Express, SmartFind, SmartFind Plus, SmartFix, SourceConnect, SupportLine, Toolbox, VS COBOL, WebSync, and Xilerator are trademarks of Micro Focus (IP) Ltd. IBM and CICS are registered trademarks, and IMS, DB2, DB2/390, DB2 Connect Enterprise Edition, DB2 Connect Personal Edition, COBOL for OS/390, Enterprise Systems Architecture/390, ESA/390, MVS, MVS/ESA, OS/390, S/390, System/390, VSE/ESA, and MFS are trademarks, of International Business Machines Corporation. Netscape Enterprise Server is a trademark of Netscape Communications Corporation. Internet Information Server, SQL Server, Visual Studio, Windows 95, Windows 98, Windows NT 4.0, Windows ME, Windows 2000, Windows Server, Windows XP, and Windows Vista are registered trademarks of Microsoft Corporation in the United States and other countries. Pentium is a registered trademark of INTEL Corporation. Borland Database Engine and MIDAS are trademarks of Borland Software Corporation. Oracle is a trademark of Oracle Corporation Inc. UNIX is a registered trademark of The Open Group. Solaris, Ultra Sparc, and Java are trademarks of Sun Microsystems, Inc. Linux, GCC compiler, GNU CTAGS, GNU DIFF, Samba, and KDE/GNOME refer to Open Source tools. This product includes modified versions of software developed by the Apache Software Foundation (as described on the Apache web site). The YGrep Search Engine is Copyright (c) Yves Roumazeilles. All other trademarks are the property of their respective owners. No part of this publication, with the exception of the software product user documentation contained on a CD-ROM, may be copied, photocopied, reproduced, transmitted, transcribed, or reduced to any electronic medium or machine-readable form without prior written consent of Micro Focus (IP) Ltd. Contact your Micro Focus representative if you require access to the modified Apache Software Foundation source files.

3 Licensees may duplicate the software product user documentation contained on a CD-ROM, but only to the extent necessary to support the users authorized access to the software under the license agreement. Any reproduction of the documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification. U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software and the Documentation were developed at private expense, that no part is in the public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFAR et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at FAR , as applicable. Contractor is Micro Focus (IP) Ltd, 9420 Key West Avenue, Rockville, Maryland Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software.

4 4

5 5 Table of Contents Table of Contents Requirements Host (Mainframe) Hardware Software DB2 Database Data Sets User Authorizations Site-specific Requirements Client (PC) Hardware Software User Authorizations Server Hardware Software Host Installation Procedures Installation Media Installation Phases Create Product PDS and Sequential Files Restore Product PDS and Sequential Files Create DB2 Database Environment and Generate Related Binds Software Installation Setup Parameter Selection Data Set Libraries Installation User Profile Update Database Creation Database Population Host - Upgrade Installation Upgrade Software Host - PTF Installation Host - New Modification Level Installation Host - Toolkit Installation Client Module Installation... 45

6 6

7 7 1. Requirements Micro Focus Data Express is an ISPF application that consists of three modules: Data, Data Masking, and Data Subset Extraction Host (Mainframe) This section describes requirements for the host Hardware Any mainframe system that supports the minimum software requirements listed in the Software section can be used. Data Express requires the following amount of disk space: 180 MB disk space available for product installation 3 MB of disk space per analyzed archive (50 fields) Software The following software items are required for Data Express: MVS, OS/ or later, or z/os 1.1 or later Language Environment 6.1 or later DB2 Database Data Express uses a DB2 database that contains about 150 tables and views. The database must be at leaset DB2 V7R1 with proper DDF configuration. The tablespace definition for one table and the DDL statements used to create the database and are shown below. CREATE TABLESPACE ANURDCLA IN &URDBASE USING STOGROUP &URSGROUP PRIQTY $PQTY SECQTY $SQTY FREEPAGE $FPAGE PCTFREE $PFREE BUFFERPOOL &URBPTS SEGSIZE 64 COMPRESS $COMPRESS; CREATE TABLE &UROWNER..ANURDCLA (MCRECID SMALLINT NOT NULL WITH DEFAULT, FILRECID INTEGER NOT NULL WITH DEFAULT, FLDRECID INTEGER NOT NULL WITH DEFAULT, CLATYPE SMALLINT NOT NULL WITH DEFAULT, PRG SMALLINT NOT NULL WITH DEFAULT, CDRULECLA INTEGER NOT NULL WITH DEFAULT, CONFID INTEGER NOT NULL WITH DEFAULT, FLAGDEL CHAR (001) NOT NULL WITH DEFAULT, BESTCLA CHAR (001) NOT NULL WITH DEFAULT) IN &URDBASE..ANURDCLA;

8 Data Sets Data Express uses 45 partitioned data sets (PDS) and 4 sequential data sets (SEQ). PDS and SEQ data sets are identified by the combination of a prefix and a suffix; however, the user can only choose the prefix. The current prefixes are MFDATA.VxRx for the VR release library, MFDATA.VxRxPTF for the PTF library, and MFDATA.VxRxPER for the Personalized library. These prefixes can be modified. Suffixes (for example, BIND, CLIST, and DDL) cannot be modified. Data Express uses the following 45 partitioned data sets: MFDATA.V3R5.BIND MFDATA.V3R5.CBL MFDATA.V3R5.CLIST MFDATA.V3R5.COPY MFDATA.V3R5.DBRMLIB MFDATA.V3R5.DDL MFDATA.V3R5.DDLALTER MFDATA.V3R5.FTOUTPUT MFDATA.V3R5.JCL MFDATA.V3R5.LOAD MFDATA.V3R5.OBJ MFDATA.V3R5.PACKAGE MFDATA.V3R5.PANEL MFDATA.V3R5.SKEL MFDATA.V3R5.SYSPUNCH MFDATA.V3R5PTF.BIND MFDATA.V3R5PTF.CBL MFDATA.V3R5PTF.CLIST MFDATA.V3R5PTF.COPY MFDATA.V3R5PTF.DBRMLIB MFDATA.V3R5PTF.DDL MFDATA.V3R5PTF.DDLALTER MFDATA.V3R5PTF.FTOUTPUT MFDATA.V3R5PTF.JCL MFDATA.V3R5PTF.LOAD MFDATA.V3R5PTF.OBJ MFDATA.V3R5PTF.PACKAGE MFDATA.V3R5PTF.PANEL MFDATA.V3R5PTF.SKEL MFDATA.V3R5PTF.SYSPUNCH MFDATA.V3R5PER.BIND MFDATA.V3R5PER.CBL MFDATA.V3R5PER.CLIST MFDATA.V3R5PER.COPY MFDATA.V3R5PER.DBRMLIB MFDATA.V3R5PER.DDL MFDATA.V3R5PER.DDLALTER MFDATA.V3R5PER.FTOUTPUT MFDATA.V3R5PER.JCL MFDATA.V3R5PER.LOAD

9 9 MFDATA.V3R5PER.OBJ MFDATA.V3R5PER.PACKAGE MFDATA.V3R5PER.PANEL MFDATA.V3R5PER.SKEL MFDATA.V3R5PER.SYSPUNCH Data Express uses the following four sequential data sets: MFDATA.V3R5.IMPSRC MFDATA.KBPARAM MFDATA.V3R5.ALLDDL MFDATA.V3R5.ALLBNDPK The installer can modify the names of the first and second qualifier of a data set (for example: MFDATA.V3R5, MFDATA.V3R5PTF, and MFDATA.V3R5PER) according to your requirements. Note: The total space occupied by all data sets does not exceed 50 MB User Authorizations Data Express users must be suitably configured both at the TSO and DB2 level. For a proper configuration, the following authorizations are required: RACF authorizations (create, update, and delete) to the product PDS and sequential files (for example, JCL, CLIST, and SKEL) Authorizations to the creation of the product DB2 database (storage group and database) Authorizations to the creation of the DB2 tablespaces, views, and indexes Authorizations to the execution of package and plan binds Site-specific Requirements Most activities in Data Express consist of batch jobs executed through JCLs, which are normally created by specific submission functions by updating predefined skeletons (parameters, environment, and database specifications). Note: If necessary, you can create permanent copies of the updated JCLs and adjust them to your organizational requirements. The following actions may be performed in order to customize the product to meet organizational standards: Modify job names (function supported during product installation) Customize the skeletons Start work with proprietary or third-party products for scheduling or controlling jobs Make adjustments as required to provide interfaces with scheduling products

10 10 Modify names such as the DB2 storage group group (STOGROUP), database, and owner (function supported during product installation) CREATE STOGROUP &URSGROUP VOLUMES (xxxxxxxx) VCAT xxx; CREATE DATABASE &URDBASE STOGROUP &URSGROUP; Modify names of tablespaces, tables, views, and indexes (function not supported during product installation) Define ALIAS or SYNONYM During the installation phase at your site, the installer will need to know your standards for: Jobs names, accounting, etc. Names of each DB2 subsystem, name of the DB2 load library, name and plan of DSNTIAD, name and plan of DSNTIAUL. Name of the volume on which to allocate your partitioned data sets Client (PC) This section describes requirements for the client Hardware The following hardware configurations are required for Data Express: PC Pentium III; 512 MB RAM; 40 MB disk space available (user data entered excluded); 200 MB disk space available to install all the modules of the Data Express suite. Display SVGA 800x600 with 256 colors (1024x768 with colors recommended). Disk space (Host site) 183 MB disk space available for the installation of Data Express Software The following software items are required for Data Express: Microsoft Windows 95, Windows 98, Windows NT 4.0 (Service Pack 6 or later versions), Windows 2000, Windows XP, or Windows ME. IBM DB2 Client Application Enabler for Windows version 6.1 or later; or IBM DB2 Connect Personal Edition version 6.1 or later (needed to access Gateway DB2 Connect Enterprise Edition).

11 11 To use Data Express with a Client/Server connection, you additionally need: In the Windows 95 environment, you must install Internet Explorer 4 and Winsock 2 (the latter only for socket connections). For earlier versions of Windows 95 and only for DCOM connections, you might need to install DCOM 95. Borland Midas 3. Local TCP/IP network to access Micro Focus kbde-server in LAN or an Internet connection to access Micro Focus kbde-server remotely User Authorizations When a project is opened for the first time, the user ID and password for the connection to the database server where the work environment resides must be provided. The user ID provided must have read privileges on the following: SYSIBM.SYSTABLES all tables created by Data Express during product installation 1.3. Server This section describes requirements for the server Hardware The following hardware configurations are required for Data Express: PC Pentium III (Pentium IV with 2GHZ bi-processor or higher recommended); 512 MB RAM (1 GB RAM for OS and 6 MB for each simultaneously connected module recommended); 300 MB disk space available (500 MB recommended). Display SVGA 800x600 with 256 colors (1024x768 with colors recommended). Disk space (Host site) 183 MB disk space available for the installation of Data Express. Note: For optimal performance, configurations with multiple servers is advisable Software The following software items are required for Data Express: Microsoft NT 4.0 (Service Pack 6 or later versions), Windows 2000, or Windows XP (Windows NT Server or Windows 2000 Server recommended). IBM DB2 Client Application Enabler for Windows version 6.1 or later; or IBM DB2 Connect Personal Edition version 6.1 or later (needed to access Gateway DB2 Connect Enterprise Edition). Borland Midas 3

12 12 Local TCP/IP network to access Micro Focus kbde-server in LAN or an Internet connection to access Micro Focus kbde-server remotely. To use Data Express with a web connection, you additionally need: Microsoft IIS version 4 or higher; or Netscape Enterprise version 3.6 or higher

13 13 2. Host Installation Procedures This chapter describes the installation media and procedures needed to successfully install Data Express Installation Media Data Express is typically installed from a CD-ROM that contains: IEUBPDTE A JCL in ASCII format used to restore INSTLIB from a sequential data set. All the partitioned data set members, unloaded in a sequential (IEBUPDTE) format. Note: If you downloaded Data Express from the Micro Focus web site or received it as an attachment, it is stored in a compressed ZIP file that contains the CD-ROM image. For the installation, assume the folder where the ZIP file has been uncompressed is the CD-ROM drive Installation Phases The installation of the host module includes 3 main phases Create Product PDS and Sequential Files The alias of the PDSs and sequential files (for example, CLIST, JCL, or DDL) where the product modules will reside is required. RACF authorizations at the TSO level (create, update, delete) need to be provided to the product PDSs and sequential files Restore Product PDS and Sequential Files The TCP/IP address of the host machine must be specified where required. The specified user must be authorized to transfer data from the PC to the host Create DB2 Database Environment and Generate Related Binds The following information is required: DSN on which the database must be created Name of the storage group (already existing or to be created) Name of the DB2 database to be created Name of the owner for the DB2 tables that will be created Name of the plan and collection to be created

14 14 Names of the buffer pools for data and indexes Plan of the DB2 system DSNTIAD Plan of the DB2 system DSNTIAUL Names of the DB2 system libraries (RUNLIB and SDSNLOAD) The specified user must be authorized to create the product DB2 database (storage group and database), to create tablespaces, views, indexes, and to execute package and plan binds Software Installation Setup To install Data Express, extract the files contained in the zip file of the installation media into an empty directory. This directory is referred to as your installation directory. To begin your Data Express installation: 1. Allocate an installation sequential data set (for example, MFDATA.INST.LIB.SEQ) to load the installation JCLs in IEBUPDTE format from the folder Installation Procedure on the CD- ROM. Note: The default Space units parameter is CYLS (cylinders). The menu Allocate New Data Set that shows the current allocation parameters is displayed, as shown in Figure 2-1: Figure 2-1: Example of Sequential Data Set Allocation Parameters

15 15 2. Copy the source of Iebupdte.jcl from the Installation Procedure folder, in ASCII mode, into a member of a partitioned data set, or use Personal Communications or FTP to transfer the source into an existing PDS. You can use a batch command (ftpinst.bat) that executes an FTP script (ftpinst.txt) or a PC3270 transfer file list (inst.srl). Note: Before transferring files, you must customize the FTP script or PC3270 transfer file list to include the correct values. (See the Readme_Floppy.txt in the Installation Procedure folder for specific customization instructions.) Customize the file ftpinst.txt located in the folder \**\HostSide\Installation Procedure on the CD-ROM. A sample of the file ftpinst.txt is shown below: open YOURUSERID YOURPASSWORD cd.. bin put iebupdte.jcl 'HLQ.SLQ.USERLIB(IEBUPDTE)' disconnect quit From a Windows CMD prompt, change to the \**\HostSide\Installation Procedure directory and execute the following command: ftp s:ftpinst.txt 3. Transfer the file Instlib.bin from the CD-ROM to the sequential data set that you have allocated. Note: You can use file ftpputinstlib.txt located in the folder \**\HostSide\Installation Procedure for the file Instilib.bin to transfer the files. Customize the file ftpputinstlib.txt located in the folder \**\HostSide\Installation Procedure on the CD-ROM. A sample of the file ftpputinstlib.txt is shown below: open YOURUSERID YOURPASSWORD cd.. bin put instlib.bin 'HLQ.SLQ.MFDATA.INSTJB.LIB.SEQ' disconnect quit From a Windows CMD prompt, change to the \**\HostSide\Installation Procedure directory and execute the following command: ftp s:ftpputinstlib.txt 4. Use the ISPF editor to modify the IEBUPDTE member to define the installation PDS where the sequential data set is loaded. 5. Change the JOB card using the standard customer parameters: $PDSINST the installation PDS name, for example: MFDATA.INST.LIB. $SEQINST the sequential data set name, for example: MFDATA.INST.LIB.SEQ.

16 16 $UNIT the DASD unit name, for example: SYSDA. $VOLSER the VOLUME name (for SMS managed DASD you must delete VOL=SER=$VOLSER from the JCL). An example of an IEBUPDTE source member is shown below: //IEBUPDTE JOB (00001),MU,MSGCLASS=A,CLASS=A,NOTIFY=&SYSUID //********************************************************************** //* THIS JOB CREATES THE PDS FOR THE INSTALLATION PROCEDURE AND //* LOADS IT FROM THE SEQUENTIAL FILE. //* //* YOU HAVE TO SPECIFY SOME INFORMATION. //* TO DO SO, YOU HAVE TO CHANGE THE FOLLOWING WORDS IN THIS JOB: //* //* 1) CHANGE '$PDSINST' TO THE NAME OF THE INSTALLATION PDS //* 2) CHANGE '$SEQINST' TO THE NAME OF THE INSTALLATION SEQ. FILE //* 3) CHANGE '$UNIT' TO THE NAME OF THE UNIT //* 4) CHANGE '$VOLSER' TO THE NAME OF THE VOLUME //********************************************************************** //STEP100 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //PO DD DSNAME=$PDSINST, // UNIT=$UNIT,DISP=(NEW,CATLG), // VOL=SER=$VOLSER,SPACE=(TRK,(15,15,30)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920,DSORG=PO) //* //STEP200 EXEC PGM=IEBUPDTE,PARM=MOD //SYSPRINT DD SYSOUT=* //SYSUT1 DD DISP=OLD,DSN=$PDSINST //SYSUT2 DD DISP=OLD,DSN=$PDSINST //SYSIN DD DISP=OLD,DSN=$SEQINST 6. Submit IEBUPDTE to allocate and load the installation PDS. 7. Browse the INST.LIB PDS. 8. Select the member INST.LIB using the Edit option. Change the first parameter in the CLIST INST.LIB (&INSTLIB) to use the name of the installation PDS INST.LIB, and then execute the CLIST command file. For example, execute the TSO command: TSO EX **.INST.4B(INSTLIB)

17 17 The Product Installation Menu panel is displayed, as shown in Figure 2-2: Figure 2-2: Product Installation Menu Panel 9. Select option Edit Product Installation Parameters to display the Product Installation Parameters panel, where you can choose the name of the installation PDS and the parameter data set (that contains all of this information). This panel is shown in Figure 2-3. Warning: The name of the library containing all the jobs to be submitted will be created by putting together the Submitted Job Library Prefix (if it exists, this is an optional field), the UID and the Submitted Job Library Suffix, all separated by a period.. Warning: The Parameter Data Set is a sequential file containing the environment parameters. The prefix of the name of this file must be different from the product library prefix.

18 18 Figure 2-3: Product Installation Parameters Panel Note: At the end of the edit session, the Product Installation Menu panel will be displayed again. Press F3 to exit the menu without submitting the jobs. 10. Continue to the section Parameter Selection. F F F F F F F F F F F F F F F F F F F F F

19 Parameter Selection To select installation parameters: 1. On the Product Installation Menu panel, select option Edit CD Installation Parameters to display the CD Installation Parameter panel so that you can choose the sequential files (SEQ) prefix for file transfer. An example of the CD Installation Parameter panel is shown below: Figure 2-4: CD Installation Parameter Panel You must customize the Unit and Volume name, although the latter can be left blank for SMS managed DASD. The parameter Override PDS Prefix existence (N) prevents data set allocation if a data set exists with the same prefix. If you need to use an existing prefix, specify Y. Note: Press Enter to display the Product Installation Menu panel again (Figure 2-2).

20 20 2. On the Product Installation Menu panel, select option Edit Knowledge Base Parameters to display the Knowledge Base Parameters panel so that you can insert name parameters such as DB2 and Language Environment PDS, DB2 storage group, database plan and collection, owner, and buffer pool. An example of this panel is shown below: Figure 2-5: Knowledge Base Parameters Panel 3. Insert parameter names into all fields as all parameters are mandatory: Name of DB2 Subsystem (Dsn) Name of the DB2 subsystem where the product tables will be created. Name of Current SQLID Name of the DB2 user who will perform the product tables creation. Name of Micro Focus Data Plan Name of the plan for the product. Name of Micro Focus Data Collection Name of the collection containing the product package. Name of Micro Focus Data Storage Group Name of the DB2 storage group where the product tables will be created. Name of Micro Focus Data Database Name of the DB2 database where the product tables will be created. Name of Micro Focus Data Database Owner Name of the DB2 creator that will be used in order to create all the product tables.

21 21 Name of Bufferpool for data and index Names of the two buffer pools containing the data and the indexes of the product tables. They can contain the same value. Name of DSNTIAD Program Name of DSNTIAD program or equivalent. Name of DSNTIAD Plan Plan associated with DSNTIAD program or equivalent. Name of DSNTIAUL Program Name of DSNTIAUL program or equivalent. Name of DSNTIAUL Plan Plan associated with DSNTIAUL program or equivalent. Dsname of DB2 Sdsnload DB2 SDSNLOAD library. Dsname of DB2 Runlib DB2 RUNLIB library. Note: Press Enter to display the Product Installation Menu panel again (Figure 2-2). 4. On the Product Installation Menu panel, select option Edit Knowledge Base Size Parameters to display the Knowledge Base Size Parameters panel so that you can customize size parameters such as the number of files, the number of fields for a single file, and the number of copies. An example of this panel is shown below: Figure 2-6: Knowledge Base Size Parameters Panel Note: Press Enter to display the Product Installation Menu panel again (Figure 2-2).

22 22 5. Customize the following size parameters: Files Number Total estimated number of files that will be cataloged in the environment to be created. By files, we mean single DB2 or Oracle or SQL Server tables, single record formats of a flat file, single formats of a DL/I segment, or single Adabas files. Fields Numbers (For File) Average number of fields for each file. Copy Number Total estimated number of different copybooks I/O areas that will be cataloged in the environment to be created. Fields Numbers (For Copy) Average number of fields for copybook I/O areas. Data Changer Files Number Total estimated number of files that will be reduced or masked. Data Changer Fields Numbers (For File) Average number of fields for each file that will be reduced or masked. 6. On the Product Installation Menu panel, select option Edit Job Card for Installation Jobs so that you can change the JOB cards of Data Express jobs as shown in Figure 2-7: Figure 2-7: Information for Data Express JOB Card Note: If you have line limits set in JES, then you should add /*JOBPARM LINES = Continue to the section Data Set Libraries Installation.

23 Data Set Libraries Installation To install data set libraries: Note: Press Enter to display the Product Installation Menu panel again (Figure 2-2). 1. On the Product Installation Menu panel, select option Load Product from CD to display the Load Product from CD panel, as shown in Figure 2-8: Figure 2-8: Load Product from CD Panel The Load Product from CD panel contains 3 options: PDS and SEQ product allocation Submits jobs to allocate the PDS and SEQ files that make up Data Express. Allocation of sequential file for FTP Submits a job to allocate a sequential file for file transfer. Use FTP or Personal Communication to load SEQ data sets. The Installation Procedure folder contains a PC3270 transfer file list (Kbd.srl) and a batch command (ftpput.bat) that executes an FTP script (ftpput.txt). See Readme_Cd.txt in the Installation Procedure folder for specific customization instructions. If the files are located on the hard drive, modify batch script files to recognize this.

24 24 The folder \**\HostSide\Installation Procedure contains the file ftpput.txt, which needs to be customized. A sample of the file ftpput.txt is shown below: open YOURUSERID YOURPASSWORD cd.. bin put bind.bin put cbl.bin put clist.bin put copy.bin put dbrmlib.bin put ddl.bin put ddlalter.bin put jcl.bin put load.bin put obj.bin put package.bin put panel.bin put skel.bin put syspunch.bin put hsurdmf.bin put hsurdmfd.bin put usdchadd.bin put usdchnam.bin put usdchsur.bin put usdchcom.bin disconnect quit 'MFI01.DE.V3R5M0.SEQ.bind' 'MFI01.DE.V3R5M0.SEQ.cbl' 'MFI01.DE.V3R5M0.SEQ.clist' 'MFI01.DE.V3R5M0.SEQ.copy' 'MFI01.DE.V3R5M0.SEQ.dbrmlib' 'MFI01.DE.V3R5M0.SEQ.ddl' 'MFI01.DE.V3R5M0.SEQ.ddlalter' 'MFI01.DE.V3R5M0.SEQ.jcl' 'MFI01.DE.V3R5M0.SEQ.load' 'MFI01.DE.V3R5M0.SEQ.obj' 'MFI01.DE.V3R5M0.SEQ.package' 'MFI01.DE.V3R5M0.SEQ.panel' 'MFI01.DE.V3R5M0.SEQ.skel' 'MFI01.DE.V3R5M0.SEQ.syspunch' 'MFI01.DE.V3R5M0.hsurdmf' 'MFI01.DE.V3R5M0.hsurdmfd' 'MFI01.DE.V3R5M0.usdchadd' 'MFI01.DE.V3R5M0.usdchnam' 'MFI01.DE.V3R5M0.usdchsur' 'MFI01.DE.V3R5M0.usdchcom' After customizing the files, copy the ftpput.txt file into the directory \HostSide\Bin within your installation directory. From a Windows CMD prompt, change to the \**\HostSide\Bin directory and execute the following command: ftp s:ftpput.txt Load Product from sequential files Submits a job to load Data Express from sequential files. 2. Press F3 to return to the Product Installation Menu panel (Figure 2-2). 3. Select option Actualize Parameter on the Product Installation Menu panel. 4. Continue the section User Profile Update User Profile Update To update user profiles: 1. Allocate the Data Express PDSs to ISPF. For example: if your data set library prefix is PPP.GGG and the keylists of Data Express panels are contained in member URDPROF of PPP.GGG.JCL, you need to copy member URDPROF to ISP.SISPTENU or to user_prefix.ispf.ispprof.

25 25 Execute the TSO command: TSO EXEC PPP.GGG.CLIST(MFDATA) The Micro Focus Data - Main Menu panel is shown below: Figure 2-9: Micro Focus Data - Main Menu Panel 2. Invoke the PFSHOW TAILOR command and ensure the parameters are set to 2, 2, 1, and 1 respectively as shown in Figure 2-10: Figure 2-10: ISPF Settings

26 26 3. Save your changes, and then continue to the section Database Creation. H 2.7. Database Creation To create the database: 1. On the Micro Focus Data - Main Menu panel, select option Environment Creation to display the Environment Creation panel as shown in Figure 2-11: Figure 2-11: Environment Creation Panel The Environment Creation panel contains 9 options: Option Linkedit All Modules Insert Environment Information Calculate Tables Information Description Submits jobs to linkedit all Data Express object modules. Warning: In a standard installation where you have installed the loaded PDS from a sequential load data set, do not execute this option. Inserts information about the environment, and submits a job that results in the source member: PPP.GGG.DDL(DB2NREC). Submits a job to calculate the values of parameters PRIQTY, SECQTY, FREEPAGE, PCTFREE, and COMPRESS for all tables used by Data Express. Note: Execute this option only if you are

27 27 installing Data Express for the first time. Actualize All Tables Create All Tables Create all Bind Packages and Plan JCL Submit all Bind Packages and Plan JCL Submits a job to actualize the DB2 table sources used by Data Express. Note: Execute this option only if you are installing Data Express for the first time. Creates the DB2 tables used by Data Express. Note: Execute this option only if you are installing Data Express for the first time. Creates Data Express DB2 and JCL to create packages and plan. Submits the JCL. The binding of all packages and plans is performed. Load Message and Business Protection std tables Load Process Ids and Classes Tables Submits a job to load messages and Business Protection standard tables. Submits a job to load the process IDs and classes tables. 2. Only if instructed to do so by Mirco Focus, select option Linkedit All Modules to linkedit all Data Express object modules. Warning: If you have installed the loaded PDS from a sequential load data set, do not execute this option. 3. Exit your TSO session and start a new session. 4. Verify that the DB2 administrator has created a storage group and database, and has granted all the necessary authorizations to the database owner. A set of DDL samples creating those entities is provided with the product. The DDL to do this is IURDDSG and IURDDDB in the PDS PPP.GGG.DDL. Note: If you use SPUFI and receive a CODE PAGE incompatability error, you can ignore the message. 5. On the Environment Creation panel, select the option Insert Environment Information to insert information about the environment and to submit a job that displays the source member: PPP.GGG.DDL(DB2NREC). Note: The source member contains the estimated number of records for each table and index. 6. Note the estimated number of records for each table and index, and evaluate the size of the environment values. Warning: You must make your evaluation of the environment values as accurate as possible. DB2NREC is used in the following steps as a starting point in order to calculate the size of the tables. If the value in DB2NREC is too large, a space problem can result when creating tables later.

28 28 If the estimated number of records for a table or index is greater than 999,999, the batch job ends with return code 4, and a message containing the object name is issued in the job SYSOUT. If necessary, edit PPP.GGG.DDL(DB2NREC) to change the number of records before proceeding. Note: When you sample tables, the rules used to calculate the number of records assume that the sampling phase will be executed for all files. This is true if the environment is small, but if the environment contains thousands of files, the sampling could be executed only for some of the files, and the calculation criteria can change, so the actual number of records could be lower than the calculated one. This argument holds true for the following tables: ANURDLOG, ANURDSPE, and ANURDSPN (with their indices ANURDLOGX1, ANURDLOGX2, ANURDLOGX3, ANURDLOGX4, ANURDSPEX1, ANURDSPEX2, ANURDSPEX3, ANURDSPNX1, and ANURDSPNX2). A rule could be that all these files have the same number of records as ANURDFLF. Note: Execute this option only if you are installing Data Express for the first time. If you are installing it to upgrade a previous release, see the chapter Data Express Upgrade Installation. 7. On the Environment Creation panel, select the option Create all Bind Packages and Plan JCL. Note: This job may return error messages at the end of the output JCL. If an error message is displayed at the end of the output JCL, note the Return Code. 8. On the Environment Creation panel, select the option Submit all Bind Packages and Plan JCL to submit a job to execute the binding for all packages and JCL plans. Note: This job may return error messages at the end of the output JCL. If you receive a Return Code of 0 after executing this JCL and the JCL in the previous step, the job was successful and the error messages can be ignored. 9. Continue to the section Database Population Database Population Perform this procedure only if you are installing Data Express for the first time. If you are installing it to upgrade a previous release, see the chapter Data Express Upgrade Installation. To populate the database: 1. On the Environment Creation panel, select option Load Message and Business Protection std tables. 2. On the Environment Creation panel, select option Load Process Ids and Class Tables. The installation is now complete. Before using Data Express, you must enable it, as described in the Data Express User Guide (Host).

29 29 3. Host Upgrade Installation Perform the following procedure only if you are installing Data Express to upgrade a previous release Upgrade Software A DB2 administrator must perform this procedure. To upgrade Data Express: 1. From the chapter Installation Procedures, perform the procedures described in sections Installation Material through Data Set Libraries Installation. 2. Execute an Unload of the following tables: ANLICLOG, ANURDFLF, ANURDFXF, ANURDLOG, and ANURDSPE. 3. On the Micro Focus Data - Main Menu panel, select option Environment Update to display the Environment Update panel as shown in Figure 3-1: Figure 3-1: Environment Update Panel The Environment Update panel contains 5 options: Update All Tables Submits a job for each changed or new table to create the DB2 tables used by the new release of Data Express, and to migrate the previous database instance. The release numbers for the tables you are updating are required. See the Data Express - Data Model User Guide for table information. Load Message Tables Submits a job to load the Data Express message tables. Load Data Changer Tables Submits a job to load the Data Changer Conversion tables.

30 30 Note: Only execute the Load Data Changer Tables option if you are migrating a version older than V3R0. Bind All Packages and Plan Submits a job to execute the binding for all packages and JCL plans. Update Level Id Submits a job to update the Level ID for all sources. Warning: Update the Level ID only if you are using a toolkit that is already installed and you have verified that the HSLICLID table is empty. 4. Execute a Load of the following tables: ANLICLOG, ANURDFLF, ANURDFXF, ANURDLOG, and ANURDSPE. 5. On the Environment Creation panel, select option Create all Bind Packages and Plan JCL to create a job for a new DB2 package and JCL plan, and then select option Submit all Bind Packages and Plan JCL to submit the job. 6. If you are migrating from a version earlier than V3R4, recompile all user-developed exit routines. 7. If you are migrating from a version earlier than V3R5, use the Data Subset Extraction module to verify the numeric values for the filter types FILTER BY RANGE and FILTER BY LIST VALUE. These filters are now padded with 31 digits instead of 18 digits as in previous production versions. To correct the padding, open and reapply the filter. Note: For more information, see the section Filter Types in the Work with Method - Selection class / Filter properties chapter in the Micro Focus Data Express Data Subset Extraction User Guide.

31 31 4. Host - PTF Installation To install a PTF, use the installation instruction document for that PTF. To begin your PTF installation: 1. Restore the PTF objects in the PTF libraries. 2. On the Micro Focus Data - Main Menu panel, select option Apply PTF to display the Apply PTF panel as shown in Figure 4-1: The Apply PTF panel contains 7 options. Figure 4-1: Apply PTF Panel Note: Based on the instructions listed in your PFT installation document, the following options may or may not apply. Linkedit Module Submits a job to linkedit the specified module. After specifying the module name, press Enter to submit the job. Note: Use the Linkedit Module option for each object specified in the PTF installation instruction. Duplicate Program Submits a job to create a duplicate of objects for the specified module. After specifying the module name and number of objects to create, press Enter to submit the job. (For the number of objects to create, see the PTF Installation Guide.) Note: Use the Duplicate Program option for each object specified in the PTF installation instruction.

32 32 Create Table Submits a job to create a DB2 table for an object specified in the PTF installation instruction. After specifying the table name, press Enter to submit the job. Note: Use the Create Table option for each object specified in the PTF installation instruction. Update Table Submits a job to update the new DB2 table specified in the PTF installation instruction. After specifying the table name, press Enter to submit the job. Note: Use the Update Table option for each object specified in the PTF installation instruction. Load Message Tables Submits a job to load message tables if specified in the PTF installation instruction. After specifying the table name, press Enter to submit the job. Load Data Changer Tables Submits a job to load data changer tables if specified in the PTF installation instruction. After specifying the table name, press Enter to submit the job. Bind Package Submits a job to bind a package for an object specified in the PTF installation instruction. After specifying the table name, press Enter to submit the job. Note: Use the Bind Package option for each object specified in the PTF installation instruction. 3. Perform the procedure as specified in the PTF installation instructions document.

33 33 5. Host - New Modification Level Installation To intall the new modification level: 1. On the Micro Focus Data - Main Menu panel, select option Installation New Modification Level to display the Installation New Modification Level - Main Menu panel, as shown in Figure 5-1: Figure 5-1: Installation New Modification Level - Main Menu Panel The Installation New Modification Level - Main Menu panel contains 9 options. 2. Select option Allocate Tempory PDS to submit a job to create a tempory PDS to contain PTF objects. You must specify the first and second qualifier for the PDS, and you must customize the Unit name and Volume name. However, the Volume name can be left blank for SMS managed DASD.

34 34 An example of the Allocate Temporary PDS (SEQALC) panel is shown below: Figure 5-2: Allocate Temporary PDS (SEQALC) Panel Press Enter to return to the Installation New Modification Level - Main Menu panel. 3. Select option Allocate Sequential File for PTF to submit a job to create the working sequential files. You must specify the prefix to be used for the sequential files, and you must customize the Unit name and Volume name. However, the Volume name can be left blank for SMS managed DASDs. An example of the Allocate Sequential files for FTP (FTPALC) panel is shown below: Figure 5-3: Allocate Sequential files for FTP (FTPALC) Panel Press Enter to return to the Installation New Modification Level - Main Menu panel.

35 35 4. Transfer the CD-ROM content into the previously created sequential files. 5. Select option Load Temporary PDS from Sequential Files to submit a job to load the temporary PDS with PTF objects from the working sequential files. You must specify the first and second qualifier used to allocate the tempory PDS and the prefix used to allocate the sequential files created previously. An example of the Load Temporary PDS from Sequential Files (LOAPTF) panel is shown below: Figure 5-4: Load Temporary PDS from Sequential Files (LOAPTF) Menu Panel Press Enter to return to the Installation New Modification Level Main Menu panel. 6. Select option Save old PDS of PTF to submit a job to save the PDS containing the latest PTF into the previously created temporary PDS. You must specify the same parameters as you did when executing the Allocate Temporary PDS option.

36 36 An example of the Save old PDS of PTF (SAVPTF) panel is shown below: Figure 5-5: Save old PDS of PTF (SAVPTF) Panel Press Enter to return to the Installation New Modification Level - Main Menu panel. 7. Select option Rename PDS to submit a job to create a JCL with a new PDS containing the last PTF, and to rename the previously created temporary PDS. You must specifiy the name of the temporary PDS used previously as the first parameter, and the name of the PDS that will contain the latest PTF as the second paramter. An example of this panel is shown below: Figure 5-6: Rename PDS (RENPDS) Panel

37 37 Press Enter to return to the Installation New Modification Level - Main Menu panel. 8. Exit from Data Express. 9. Exit the TSO session to release holds on data sets, and start a new session. 10. Execute the JCL you created using the option Create all Bind Packages and Plan JCL described in the section Database Creation from the chapter Installation Procedures. 11. Restart Data Express. On the Micro Focus Data - Main Menu panel, select option Installation New Modification Level. 12. On the Installation New Modification Level - Main Menu panel, select option Bind Package (PTF) to submit bind jobs. 13. Select option Linkedit Module to submit linkedit jobs. 14. Select option Bind Package (PER) to submit bind jobs for personalized objects. 15. Select option Update Modification Level to submit a job to update the modification level. 16. Only if you are migrating from to 3.5.1, execute the command (without exiting the product): tso iurupdtb ptf R35HSLOG

38 38

39 39 6. Host - Toolkit Installation To install the toolkit: 1. Select option Toolkit Installation from Main Menu panel. The Toolkit Installation - Main Menu panel is displayed, as shown in Figure 6-1: Figure 6-1: Toolkit Installation - Main Menu Panel The Toolkit Installation - Main Menu panel contains 8 options. 2. Select option Allocate Temporary PDS to submit a job to create a temporary PDS to contain toolkit objects. You must specify the first and second qualifier for the PDS, and you must customize the Unit name and Volume name. However, the Volume name can be left blank for SMS managed DASD.

40 40 An example of the Allocate Temporary PDS (SEQALC) panel is shown below: Figure 6-2: Allocate Temporary PDS (SEQALC) Panel Press Enter to return to the Toolkit Installation - Main Menu panel. A job will be submitted. 3. Select option Allocate Sequential File for FTP to submit a job to create the working sequential files. You must specify the prefix to be used for the sequential files, and you must customize the Unit name and Volume name. However, the Volume name can be left blank for SMS managed DASDs. An example of the Allocate Sequential files for FTP (FTPALC) panel is shown below: Figure 6-3: Allocate Sequential files for FTP (FTPALC) Panel Press Enter to return to the Toolkit Installation - Main Menu panel. A job will be submitted.

41 41 4. Transfer the CD-ROM content into the previously created sequential files (see ftpput.txt). 5. Select option Load Temporary PDS from Sequential Files to submit a job to load the temporary PDS with toolkit objects from the working sequential files. You must specify the first and second qualifier used to allocate the tempory PDS and the prefix used to allocate the sequential files created previously. An example of the Load Temporary PDS from Sequential Files (LOAPTF) panel is shown below: Figure 6-4: Load Temporary PDS from Sequential Files (LOAPTF) Panel Press Enter to return to the Toolkit Installation - Main Menu panel. A job will be submitted. 6. Select option Save old PDS of PTF to submit a job to save the PDS containing the latest PTF into the previously created temporary PDS. You must specify the same parameters as you did when executing the Allocate Temporary PDS option.

42 42 An exmaple of the Save old PDS of PTF (SAVPTF) panel is shown below: Figure 6-5: Save old PDS of PTF (SAVPTF) Panel Press Enter to return to the Toolkit Installation - Main Menu panel. 7. Select option Rename PDS to submit a job to create a JCL with a new PDS containing the last version of the toolkit, and to rename the previously created temporary PDS. You must specifiy the name of the temporary PDS used previously as the first parameter, and the name of the PDS that will contain the latest toolkit as the second parameter. An example of the Rename PDS (RENPDS) panel is shown below: Figure 6-6: Rename PDS (RENPDS) Panel

43 43 Press Enter to return to the Toolkit Installation - Main Menu panel. A job will be stored in the Jobs data set for submission. 8. Exit Data Express. 9. Exit the TSO session to release holds on data sets, and start a new session. 10. Execute the JCL you created using the option Rename PDS. 11. Restart Data Express, and display the Toolkit Installation - Main Menu. 12. On the Installation New Modification Level - Main Menu panel, select option Bind Package (PTF) to submit bind jobs. 13. Select option Linkedit Module to submit linkedit jobs. 14. Select option Create System Tables to submit the creation of the view on systables. Warning: Execute option Create System Tables only if you are installing Data Express for the first time. If you are installing it to upgrade a previous release, do not execute this option.

44 44

45 45 7. Client Module Installation The client consists of three modules: Data, Data Masking, and Data Subset Extraction, which are installed using a classic SETUP procedure. You must have administrator privileges on the PC for which you are installing Data Express.

46 46