Teradata Tools and Utilities. Installation Guide for IBM z/os

Transcription

1 Teradata Tools and Utilities Installation Guide for IBM z/os Release B A August 2007

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, DB2, MVS, RACF, Tivoli, and VM are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademarks of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a collective membership mark and a service mark of Unicode, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as Feedback ) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata Corporation. All Rights Reserved.

3 Preface Purpose This book provides information about installing Teradata Tools and Utilities software for z/os on an IBM compatible mainframe. Teradata Tools and Utilities is a group of products designed to work with Teradata Database. Audience This book is intended for use by: System and application programmers System administrators Database administrators and relational database developers System operators and other database specialists Supported Releases This book supports the following releases: Teradata Database Teradata Tools and Utilities For the most current information about supported releases, do the following: 1 Go to 2 Navigate to General Search>Publication Product ID. 3 Enter Open the version of the Teradata Tools and Utilities ##.##.## Supported Versions spreadsheet associated with this release. The spreadsheet includes supported Teradata Database versions, platforms, and product release numbers. Prerequisites The following prerequisite knowledge is required for this product: Teradata Tools and Utilities Installation Guide for IBM z/os 3

4 Preface Changes to This Book IBM system terminology How to install software using SMP/E How to define and allocate channels and device addresses Basic concepts and facilities of the Teradata Database and servers Changes to This Book The following changes were made to this book in support of the current release. Changes are marked with change bars. For a complete list of changes to the product, see the Teradata Tools and Utilities Release Definition associated with this release. Date and Release August 2007 Teradata Tools and Utilities July 2007 Teradata Tools and Utilities Description Added Step 9: Provide DDDEF Entries on page 45 that was inadvertently removed from this installation guide in a previous release. Updated version numbers. Updated tape ordering (BCD) reference numbers. Additional Information Additional information that supports this product and Teradata Tools and Utilities is available at the web sites listed in the table that follows. In the table, mmyx represents the publication date of a manual, where mm is the month, y is the last digit of the year, and x is an internal publication code. Match the mmy of a related publication to the date on the cover of this book. This ensures that the publication selected supports the same release. Type of Information Description Access to Information Release overview Late information Use the Release Definition for the following information: Overview of all of the products in the release Information received too late to be included in the manuals Operating systems and Teradata Database versions that are certified to work with each product Version numbers of each product and the documentation for each product Information about available training and the support center 1 Go to 2 Select the General Search check box. 3 In the Publication Product ID box, type Click Search. 5 Select the appropriate Release Definition from the search results. 4 Teradata Tools and Utilities Installation Guide for IBM z/os

5 Preface Additional Information Type of Information Description Access to Information Additional product information CD-ROM images Ordering information for manuals General information about Teradata Use the Teradata Information Products Publishing Library site to view or download specific manuals that supply related or additional information to this manual. Access a link to a downloadable CD-ROM image of all customer documentation for this release. Customers are authorized to create CD-ROMs for their use from this image. Use the Teradata Information Products Publishing Library site to order printed versions of manuals. The Teradata home page provides links to numerous sources of information about Teradata. Links include: Executive reports, case studies of customer experiences with Teradata, and thought leadership Technical information, solutions, and expert advice Press releases, mentions, and media resources 1 Go to 2 Select the Teradata Data Warehousing check box. 3 Do one of the following: For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities and then select a release or a specific title. Select a link to any of the data warehousing publications categories listed. Other books related to this installation process are: Teradata Director Program Reference B mmyx IBM IMS/DC Interface for Teradata Reference B mmyx IBM CICS Interface for Teradata Reference B mmyx 1 Go to 2 Select the General Search check box. 3 In the Title or Keyword box, type CD-ROM. 4 Click Search. 1 Go to 2 Select the How to Order check box under Print & CD Publications. 3 Follow the ordering instructions. 1 Go to Teradata.com. 2 Select a link. Teradata Tools and Utilities Installation Guide for IBM z/os 5

6 Preface Additional Information 6 Teradata Tools and Utilities Installation Guide for IBM z/os

7 Table of Contents Preface Purpose Audience Supported Releases Prerequisites Changes to This Book Additional Information Chapter 1: Introduction Teradata Tools and Utilities Product Dependencies Installation Kit Contents Software Installation Recommendations New Installation Upgrade Installation Installation Overview IBM Utility Programs Used Types of Software Releases Release Tape Software Software Naming Conventions Reading the Release Tape Labels Technical Assistance Tape Ordering Reference Numbers Chapter 2: Before You Install Review the Release Definition Emergency Release Tape Teradata Tools and Utilities Installation Guide for IBM z/os 7

8 Table of Contents Chapter 3: Configuring the MVS Client Overview of the Teradata Director Program (TDP) Data Flow Sequence TDP Configurations Using Test and Production TDPs Sample TDP Configurations TDP and Data Set Naming Conventions TDP Naming Convention Data Set Naming Convention Step 1: Verify the MVS Client System Requirements Step 2: Verify the MVS Client Disk Storage Requirements Step 3: Verify License Requirements Step 4: Specify I/O Devices Step 5: Define SVC Numbers Step 6: Define TDP Subsystems Step 7: Add TDP to the PPT Step 8: Authorize Teradata Libraries and Programs Step 9: Perform IPL Chapter 4: Installing the Software Step 1: Review the Release Tape Format Step 2: Load the JCL Library Step 3: Customize the JCL Used for Installation of Teradata Tools and Utilities Step 4: Modify and Copy the SMP/E JCL Procedure Step 5: Using the #INSTALL job to Allocate and Define Data Sets Step 6: Load All Non-SMP/E Data Sets Step 7: Allocate SMP/E Datasets, Define and Initialize the SMP/E CSI Step 8: Allocate SMP/E Target and Distribution Libraries Step 9: Provide DDDEF Entries Step 10: Perform SMP/E RECEIVE Step 11: Perform SMP/E APPLY Step 12: Perform SMP/E ACCEPT Teradata Tools and Utilities Installation Guide for IBM z/os

9 Table of Contents Chapter 5: Customizing the Teradata Tools and Utilities Software for MVS Customizing Teradata Tools and Utilities Software A Note on SMP USERMODs Sample Jobs for Installing USERMODs A Note on the Two-Phase Commit Protocol Step 1: Install the TSO CLISTs Step 2: Install the Batch Procedures Step 3: Establish the Communication Interface Step 4: Copy the HCI Modules Into System Libraries Step 5: Customize the TDPPARM Data Set Step 6: Install TDP Procedures Step 7: Customize System Parameter Blocks & User Exits (Optional) Step 8: Install the CICS Interface Step 9: Customize CICS for TS/API Step 10: Install the IMS/DC Interface Chapter 6: Putting the Software Into Production Step 1: Put the Test System Into Production Step 2: Move the Teradata Server Software to Production Step 3: Tune TDP Cells to Optimize Performance Appendix A: Using the Master Scheduler Starting TDP Under the Master Scheduler Introduction Master Scheduler Limitations Starting TDP TDP Joblog Index Teradata Tools and Utilities Installation Guide for IBM z/os 9

10 Table of Contents 10 Teradata Tools and Utilities Installation Guide for IBM z/os

11 List of Figures Figure 1: Installing Teradata Tools and Utilities for MVS Figure 2: Release Tape Label for Teradata Tools and Utilities for MVS Figure 3: Configuration 1: Two TDPs and One Teradata Server Figure 4: Configuration 2: Two TDPs and Two Teradata Servers Figure 5: Configuration 3: Two Clients and One Teradata Server Teradata Tools and Utilities Installation Guide for IBM z/os 11

12 List of Figures 12 Teradata Tools and Utilities Installation Guide for IBM z/os

13 List of Tables Table 1: Tape ordering reference numbers Table 2: MVS Client Installation History Table 3: Teradata for MVS Tape Files Table 4: Software Needed Table 5: Sample Job Functions Table 6: Suffixes for Multiple Versions Table 7: Names of SMP USERMOD Samples Table 8: Macro Parameters Used by HSISPB Teradata Tools and Utilities Installation Guide for IBM z/os 13

14 List of Tables 14 Teradata Tools and Utilities Installation Guide for IBM z/os

15 CHAPTER 1 Introduction This chapter describes background information you need before installing the Teradata Tools and Utilities software for MVS systems. This chapter contains the following: Teradata Tools and Utilities Installation Kit Contents Software Installation Recommendations Installation Overview Technical Assistance Tape Ordering Reference Numbers Teradata Tools and Utilities Teradata Tools and Utilities is a set of integrated warehouse management and utility software products designed for Teradata Database that enable users to get data from any source, extract and load the data quickly, then analyze the data in any way required. Definitions of Client and Server Before you begin, it may be helpful to review the definitions of the following terms: Term Teradata client software for MVS Teradata server Definition Teradata software that is installed and executed on an IBM (or IBMcompatible) mainframe under the MVS operating system, and that allows access to a Teradata Database. System running the Teradata Database. Product Dependencies None. Teradata Tools and Utilities Installation Guide for IBM z/os 15

16 Chapter 1: Introduction Installation Kit Contents Installation Kit Contents The installation materials that you receive includes the following: Teradata Tools and Utilities software for z/os on magnetic tape cartridge Release Notice Documentation CD-ROM for Teradata Database and Teradata Tools and Utilities Software Installation Recommendations New Installation Upgrade Installation If you have a new site or have received a new Teradata server, the Teradata software has been installed at the factory. However, you still need to install the Teradata Tools and Utilities software for MVS from the release tape supplied. For sites installing Teradata software for the first time, the following recommendations apply: Schedule one working day for the installation. This amount of time should suffice as long as all MVS preconditioning has been performed, DASD space is available, and all relevant literature has been reviewed. An experienced system programmer or system administrator who is familiar with the MVS operating environment should be present. The Teradata software package must have been received. The release tape contents must be installed in their entirety. If you are updating your current software to a new version, the following recommendations apply: For maintenance updates, the installation process automatically determines which software to install to bring the existing system to a new release level. All prerequisite software levels indicated on the Release Definition must be installed before the new software is installed. All installation procedures must be performed as described in this book, as well as the release specific Release Definition. The document includes any necessary additional information, such as special installation issues and what modules are on the tape. Note: If you decide to discontinue running the new release, contact the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC) before attempting to revert to the previous release. 16 Teradata Tools and Utilities Installation Guide for IBM z/os

17 Chapter 1: Introduction Installation Overview Installation Overview IBM Utility Programs Used The Teradata release tape contains software that you must first load from the release tape to disk. The installation process utilizes the standard IBM utility programs and SMP/E. Program IEBCOPY SMP/E Description Loads data sets not managed through SMP/E. These data sets are referred to in this book as non-smp data sets. Loads data sets that contain client software, referred to in this book as SMP data sets. Test System and Production System The installation process creates both a test system and a production system. A new release is initially installed on the test system, where the software is exercised and verified, then the software is moved to the production system. Figure 1: Installing Teradata Tools and Utilities for MVS MVS CLIENT Release Tape Test System Production System The installation, which flows from tape to test to production, is the subject of this book. The data set names provided distinguish between release tape, test, and production libraries. Note: A Teradata software installation should not affect current production client sessions until an IPL is performed. For users, the install process is essentially transparent except during the time that the IPL is performed to incorporate the new software into the client environment. Types of Software Releases There are four types of software releases: FZAPB068 Release type Major Description Features substantial functional enhancements to your existing software. Teradata Tools and Utilities Installation Guide for IBM z/os 17

18 Chapter 1: Introduction Installation Overview Release type Minor Maintenance Emergency Description Features significant, but fewer, functional enhancements to your current software. Fixes software discrepancies discovered since the current major, minor, or previous maintenance release was issued, and may include high priority enhancements. A release issued in response to a specific problem that has been reported by a customer. Release Tape Software The following describes the types of release tapes: Major, Minor, or Maintenance Tape A major, minor, or maintenance release tape for the Teradata Tools and Utilities software for MVS contains the following items: A listing file describing how to get a copy of the Release Definition from the Web Teradata Tools and Utilities software for MVS, which consists of the base release of the software and all subsequent minor or maintenance releases Sample files and source code to customize the client software Emergency Tape In contrast, an emergency release tape contains a Release Definition, and only the changes required to fix a specific problem reported by a customer. Software Naming Conventions Teradata software uses the following naming conventions: Release number SYSMOD name The naming conventions are described in the sections that follow. Release Number The release number is commonly used in hardcopy documents and general communication regarding Teradata software. It is in the following form: Release Name Release xx.nn.mm Release Name Major Release Minor Release Maintenance Release 18 Teradata Tools and Utilities Installation Guide for IBM z/os

19 Chapter 1: Introduction Installation Overview For example, the first maintenance release for the major release 8.2 for Teradata Tools and Utilities would be named: Teradata Tools and Utilities Release SYSMOD Name The SYSMOD name identifies the level of Teradata software. The conventions for this number vary depending on the content of the software that is shipped. These conventions are as follows: SYSMOD name Maintenance Software (PTF) Emergency Fix (APAR) Description A SYSMOD name can indicate a maintenance software upgrade (PTF). PTF numbers refer to the Teradata maintenance software. The PTF number always begins with the letter P, followed by six alphanumeric characters. For example, a PTF number could be PW A SYSMOD name also can indicate an emergency fix (APAR). An APAR number consists of two letters and a five digit number that corresponds to the discrepancy report (DR) number. For example, the number of the APAR that contains the fix to the problem reported in DR would be QW Reading the Release Tape Labels Figure 2 on page 20 shows the tape label for this release of the Teradata Tools and Utilities software for MVS. The tape label contains the following information: Product title and release number Release tape volume serial (volser) number BCD media ordering number Volume number Release date Function modification identifiers Teradata Tools and Utilities Installation Guide for IBM z/os 19

20 Chapter 1: Introduction Technical Assistance Figure 2: Release Tape Label for Teradata Tools and Utilities for MVS Media Ordering Number Product Component Product Title: Teradata Tools and Utilities for IBM MVS TTU 12.0 Volser: VH0701 BCD # BCD Volume: 1 of 1 Release Date: 16-JULY-2007 Base: FMID - TDP0701 CICS: FMID - TDC0701 IMS: FMID - TDI0701 API: FMID - TDA0701 API: FMID - TDX0701 MQ: FMID - TDQ0701 TPT: FMID - TPT0701 Copyright 2007 NCR, INC. All Rights Reserved Function Modification Identifier 2458E003 Volser Number VH0701 Tape Sequence Number 00 through 99, A0 through A9 AA through AZ, B0 through B9, BA through BZ, and so on to ZZ Year 07 = 2007 Operating System G=VM H = MVS Tape Type V=GCA (General Customer Availability) B=ICI (Initial Certified Installation) E=Emergency X=EFT (Engineering Field Trial) Technical Assistance Technical assistance is available from the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For contact information, see the Teradata Tools and Utilities Release Definition. Tape Ordering Reference Numbers Table 1: Tape ordering reference numbers Order Number BCD BCD Description TTU 12.0 MVS 3480 Cartridge TTU 12.0 MVS 3590 Cartridge 20 Teradata Tools and Utilities Installation Guide for IBM z/os

21 CHAPTER 2 Before You Install Before installing the software review the current Release Definition, as described in this chapter. Review the Release Definition Emergency Release Tape The Teradata Tools and Utilities Release Definition for this release is included in the product CD-ROM and describes the overall release. Review the release definition to learn about each product in the release. A smaller Release Definition file is in each Emergency Release Tape (E-Tape), and has information specific to the particular E-Tape. The E-Tape Release Definition may contain the following information: Emergency Release Tape identification Tape contents identification A list of the new software packages and updates Migration issues Specific recommendations, if any, for installing the release A description of the major differences between the new release and the installed release, including a complete list of new client files A parts list of software updates A list of changes implemented in this release The overall release definition supplements some of the information contained in the Emergency Release Tape Release Definition. In MVS Client Installation History table in the Client Release tape lists the tape volume serial number and the software levels on the tape. Table 2: MVS Client Installation History Volume Serial # Date Issued Base SYSMOD CICS SYSMOD IMS SYSMOD EH TDP0701 TDC0701 TDI0701 API SYSMOD API SYSMOD MQ SYSMOD TPT SYSMOD TDA0701 TDX0701 TDQ0701 TPT0701 Teradata Tools and Utilities Installation Guide for IBM z/os 21

22 Chapter 2: Before You Install Review the Release Definition 22 Teradata Tools and Utilities Installation Guide for IBM z/os

23 CHAPTER 3 Configuring the MVS Client This chapter contains information on preparing the MVS client for the software and hardware. You can complete the tasks in this chapter before the release tape arrives at your site. In most cases, you need to perform the steps in this chapter only when you initially install or modify the Teradata software. This chapter contains the following sections: Overview of the Teradata Director Program (TDP) TDP and Data Set Naming Conventions Step 1: Verify the MVS Client System Requirements Step 2: Verify the MVS Client Disk Storage Requirements Step 3: Verify License Requirements Step 4: Specify I/O Devices Step 5: Define SVC Numbers Step 6: Define TDP Subsystems Step 7: Add TDP to the PPT Step 8: Authorize Teradata Libraries and Programs Step 9: Perform IPL Note: Technical assistance during installation is available from the Teradata Solutions Customer Services Remote Services Center (TSCS-RSC). For more information, see the Teradata Tools and Utilities Release Definition for the current release. Overview of the Teradata Director Program (TDP) The Teradata Director Program (TDP) manages communication between the client application programs, which process data, and the Teradata server. The functions of TDP include the following: Session initiation and termination Logging, verification, recovery, and restart Physical input to and output from the Teradata server Security Teradata Tools and Utilities Installation Guide for IBM z/os 23

24 Chapter 3: Configuring the MVS Client Overview of the Teradata Director Program (TDP) Data Flow Sequence TDP Configurations TDP runs as a subsystem in its own address space. For a detailed description of TDP, see Teradata Director Program Reference. Data and information flow between the MVS client and the Teradata server is processed as shown in the following sequence: 1 An application on the MVS client sends Teradata SQL statements, data, and control information to TDP. 2 TDP directs this information to the Teradata server. 3 The Teradata server performs the activity requested by the MVS client application (such as selecting, updating, or deleting data) and returns the resulting information to TDP. 4 TDP routes the response information back to the application. Figure 3, Figure 4, and Figure 5 show the relationship between TDP and a Teradata server. This relationship can be summarized as follows: A TDP manages traffic between a client and one Teradata server. A TDP communicates with one or more pairs of devices, each pair being known as a Channel Processor (CP). The implementation of a CP may vary on different servers, but the behavior of all CPs is the same. Because the original implementation of an Interface Processor (IFP) embodied the functions of a CP, the pair of devices were referred to as an IFP. For compatibility, this usage continues, especially in the existing TDP command syntax. A Teradata server can communicate with one or more TDPs, each of which can be running on the same or different MVS clients. Each CP in a Teradata server communicates with only one TDP. Several versions of TDP can exist on MVS to accommodate the following situations: Production environment Test environment Multiple Teradata servers Using Test and Production TDPs To allow orderly migration to new releases of Teradata software, a minimum of two TDPs should be defined: a production system and a test system. As new software versions are released, the test system exercises the new software while the production system runs the currently operational production software. An application selects the TDP with which it communicates either by default, which is defined in the System Parameter Block, or by specifying a TDP subsystem through Call-Level Interface (CLI) routines. 24 Teradata Tools and Utilities Installation Guide for IBM z/os

25 Chapter 3: Configuring the MVS Client Overview of the Teradata Director Program (TDP) The examples provided in this document assume that the test and production systems use the following Tdpids: TDP0 (production TDP) TDP1 (test TDP) Sample TDP Configurations Figure 3 is an illustration of a Teradata configuration where multiple clients on a mainframe computer are attached to one Teradata server via a TDP on each client. Figure 3: Configuration 1: Two TDPs and One Teradata Server MVS CLIENT Address Space Application Call-Level Interface Address Space Application Call-Level Interface Address Space Application Call-Level Interface Host Software Interface (HSIT) Composed of either TRDTMAS-with-HSIOSSI or TDPNSPCI-with-HSISXMS TDP 0 Teradata Director Program (TDP) TDP 1 Teradata Director Program (TDP) CP CP CP CP SERVER FZAPB070 Teradata Tools and Utilities Installation Guide for IBM z/os 25

26 Chapter 3: Configuring the MVS Client Overview of the Teradata Director Program (TDP) Figure 4 is an illustration of a Teradata configuration where multiple clients on a mainframe computer are attached to two Teradata servers via a TDP on each client. Figure 4: Configuration 2: Two TDPs and Two Teradata Servers MVS CLIENT Address Space Application Call-Level Interface Address Space Application Call-Level Interface Address Space Application Call-Level Interface Host Software Interface (HSIT) Composed of either TRDTMAS-with-HSIOSSI or TDPNSPCI-with-HSISXMS TDP 0 Teradata Director Program (TDP) TDP 1 Teradata Director Program (TDP) CP CP CP CP CP CP CP CP SERVER SERVER FZAPB Teradata Tools and Utilities Installation Guide for IBM z/os

27 Chapter 3: Configuring the MVS Client Overview of the Teradata Director Program (TDP) Figure 5 is an illustration of a Teradata configuration where multiple client mainframe computers (with VM, MVS, or both environments) are attached to one Teradata server via a TDP on each client. Note: For information on installing the Teradata Tools and Utilities for VM products, see Teradata Tools and Utilities Installation Guide for IBM VM. Figure 5: Configuration 3: Two Clients and One Teradata Server User Virtual Machine 1 Application Call-Level Interface VM CLIENT User Virtual Machine 1 Application Call-Level Interface Address Space Application Call-Level Interface MVS CLIENT Address Space Application Call-Level Interface Host Software Interface (HSIT) TDP 0 Teradata Director Program (TDP) TDP 0 Teradata Director Program (TDP) CP CP CP CP SERVER FZAPB067 Teradata Tools and Utilities Installation Guide for IBM z/os 27

28 Chapter 3: Configuring the MVS Client TDP and Data Set Naming Conventions TDP and Data Set Naming Conventions TDP Naming Convention The TDP identifier (sometimes referred to as Tdpid) has the format TDPn, where n can be 0-9, A-Z, $, The default TDP name in the System Parameter Block (HSISPB and HSHSPB) is TDP0, but any of 39 possible TDP names (TDP0 through TDP9, TDPA through TDPZ, TDP$, TDP#, or TDP@) may be used as the default TDP name. If you wish to use a different tdpid, you must then substitute the selected tdpid in the System Parameter Block. Users can log on using either the full four-character TDP name, or just the suffix character of the name (such as A, B, 1, 2). The logon string without either the full TDP name or suffix character is automatically assigned the default TDP name in the System Parameter Block. Data Set Naming Convention All Teradata Tools and Utilities and software is installed into MVS partitioned data sets (PDSs). The names of the data sets presented in this document are identified by both of the following: Identifier DBC prefix Descriptive qualifier Description The prefix must be one or more qualifiers and is defined according to the requirements of your site for the naming of Teradata software. In the sample JCL and in this document, the symbol <dbcpfx> is used to represent your DBC prefix. Use the naming conventions of your site to determine the DBC prefix. In addition, the prefix can include the qualifiers DBCTEST and DBC to differentiate between the test and production systems. The descriptive qualifier has meaning to Teradata software and should not be modified. It corresponds to the ddname in the SMP installation process. Examples of a descriptive qualifier are PROCLIB and SAMPLIB. You can easily modify the DBC prefix. However, you must not modify the descriptive qualifier. For example, consider the following data set name: VENDOR.TERADATA.DBCTEST.PROCLIB This data set name has the modifiable DBC prefix of VENDOR.TERADATA.DBCTEST, and the descriptive qualifier of PROCLIB. 28 Teradata Tools and Utilities Installation Guide for IBM z/os

29 Chapter 3: Configuring the MVS Client Step 1: Verify the MVS Client System Requirements Step 1: Verify the MVS Client System Requirements Requirement Verify that the MVS client meets the hardware and software requirements described in the Teradata Tools and Utilities Release Definition for the current release. Step 2: Verify the MVS Client Disk Storage Requirements Requirement You need approximately 450 cylinders of 3390 DASD space to accommodate one copy of the Teradata Tools and Utilities software for MVS release tape programs. Some of this space is used for temporary storage of work data sets, and can be recovered upon completion of the installation. Step 3: Verify License Requirements Teradata Requirements The MVS Client tape contains software for various Teradata products. A site must obtain the appropriate licenses to the products which are to be installed. One license is required per installed product per system. Additional licenses are not required to: Access additional Teradata servers Have multiple instances of a product on a system Step 4: Specify I/O Devices Requirements Teradata server I/O devices must be included when the I/O configuration for the MVS channel subsystem is defined. Configurations or features not described are not supported. If this MVS system is operating as a virtual machine, the I/O devices may also need to be defined to VM. Only Channel Processors (CP) are defined to the MVS system. Other Teradata server hardware and peripherals are not. Teradata Tools and Utilities Installation Guide for IBM z/os 29

30 Chapter 3: Configuring the MVS Client Step 4: Specify I/O Devices Device Connection Devices are connected to the client through a channel. Each CP is identified by a pair of consecutive even-odd device numbers. The first number, for the output device, must be even (low-order bit = 0). The second, for the input device, must be odd (low-order bit = 1). A Teradata device: Is dedicated to a single TDP through a single channel interface. Can be online to only one MVS system at a time. Does not support multiple channel connections. Can be used by different TDPs at different times. The physical implementation of a Teradata device may vary in different Teradata servers. Each physical processor has a single channel interface that provides the only channel interface for all device pairs associated with that processor. For purpose of defining the I/O configurations, a CP is effectively a control unit that has one input and one output device associated with it. Physical implementation examples include: One physical processor implements a single pair of devices. See Figure 3. One physical processor implements multiple pairs of devices. See Figure 4. Two physical processors implement a single pair of devices. See Figure 5. Physical Connection There are three types of physical connections to a Teradata server: Block Multiplexer Enterprise Systems Connection (ESCON) Fibre-channel Connection (FICON) Each FICON Bridge supports up to eight different ESCON CUs. Whenever possible, place Block Multiplexer devices on dedicated channels. If the devices are attached to channels that also support disk or tape devices, I/O interference can result. You must define the CPs to both the hardware and the operating system. The following samples show how to accomplish this task. Note: If using the MVS Storage Management Subsystem (SMS), be sure that the Teradata devices are not included in an SMS Storage Group with other types of devices. Otherwise, the Automatic Class Selection (ACS) routines might change the specification of a Teradata device to some other type of device. It is imperative that an ACS routine never change the specification of a Teradata device. Methods of Defining Teradata Server Devices This section outlines issues to consider when defining Teradata server devices: 30 Teradata Tools and Utilities Installation Guide for IBM z/os

31 Chapter 3: Configuring the MVS Client Step 4: Specify I/O Devices Using Hardware Configuration Definition Hardware Configuration Definition (HCD) is a program used to define the I/O configuration to both MVS and the channel subsystem. HCD is primarily an interactive tool and therefore uses a hierarchy of displays known as panels instead of the control statements of older methods. This section presents an overview of the hierarchy of relevant panels, followed by examples of information to be specified on those panels. Define the Channel Path The channel path to which the CP is connected should be defined first, by selecting the appropriate panels and options as described in the following procedure: 1 On the HCD Hardware Configuration panel, select Define, Modify or View Configuration Data. 2 On the Define, Modify or View Configuration Data panel, select Processors. 3 On the Processors panel, specify action code S for the appropriate processors, then use the Add function key to display the Add Channel Path panel. 4 On the Add Channel Path panel, specify the channel path information, then press Enter to display the Define Access List panel. 5 On the Define Access List panel, associate the channel path with a partition by preceding each with a slash (/), then do one of the following: If only one partition is listed, skip to Step 7. If more than one partition is listed, and the channel path is not defined as shared by multiple partitions, select one partition by preceding it with a slash (/). If the channel path is shared, multiple partitions may be selected by preceding each with a slash (/). 6 If all partitions are not selected for a reconfigurable or shared channel path, the Define Candidate List panel is displayed, listing the other partitions. Select any partitions that are permitted to dynamically configure the channel path by preceding each with a slash (/). 7 Press Enter to complete the definition. Define the Control Unit Next, the control unit associated with the CP should be defined as described in the following procedure: 1 On the HCD Hardware Configuration panel, select Define, Modify or View Configuration Data. 2 On the Define, Modify or View Configuration Data panel, select Control Units. 3 On the Control Unit List panel, press Add to display the Add Control Unit panel. 4 On the Add Control Unit panel, specify the appropriate information, then press Enter to display the Select Processor/Control Unit panel. 5 On the Select Processor/CU panel, specify action code S for the processor to which the control unit is attached. This displays a different Add Control Unit panel. Teradata Tools and Utilities Installation Guide for IBM z/os 31

32 Chapter 3: Configuring the MVS Client Step 4: Specify I/O Devices Server Connections 6 On this Add Control Unit panel, enter the control unit information, then press Enter to return to the Select Processor/CU panel. 7 Press Enter again to complete the definition. Define the CP Devices Finally, the pair of devices for a CP may be defined as follows: 1 On the HCD Hardware Configuration panel, select Define, Modify or View Configuration Data. 2 On the Define, Modify or View Configuration Data panel, select I/O Devices. 3 On the I/O Device List panel, press Add to display the Add Device panel. 4 On the Add Device panel, specify the information appropriate for the channel subsystem, then press Enter. If any Control Unit connections were specified then the Device/Processor Definition panel is displayed. On the Device/Processor Definition panel, optional channel subsystem information may be specified. Note: If the channel path is shared by multiple partitions, access to each CP device must be restricted to one partition. This is accomplished by entering YES in the Explicit Device Candidate List field. The Define Device Candidate List panel will then be displayed, and one partition must be selected by preceding it with a slash (/). Press Enter to display the Define Device to Operating System Configuration panel. 5 On the Define Device to Operating System Configuration panel, specify action code S to select the relevant operating system Define Device Parameters/Features panel. 6 On the Define Device Parameters/Features panel, specify the appropriate features, then press Enter to display the Assign/Unassign Device to Esoteric panel. Teradata devices should not be assigned an esoteric name, so simply press Enter to return to the Define Device to OS Configuration panel, then press Enter again to complete the definition. There are two types of physical connections to a Teradata Server: Block Multiplexer ESCON While not every Teradata server supports both types, the HCD specifications differ for the two types. For example, when using Block Multiplexer connections to define a CP whose device numbers are 310 and 311, you would supply the following information: Add Channel panel Channel path ID: 3 Number of CHPIDs: 1 Channel path type: channel_path_type (first) Add Control Unit panel Control unit number: 310 Control unit type: DUMMY 32 Teradata Tools and Utilities Installation Guide for IBM z/os

33 Chapter 3: Configuring the MVS Client Step 4: Specify I/O Devices (second) Add Control Unit panel Channel path IDs: 3 Unit address: 10 Number of units: 2 Protocol: protocol_type I/O concurrency level: 2 Add Device panel Device number: 310 Number of devices: 2 Device type: DUMMY Connected to CUs: 310 Where variable... is... channel_path_type BL if a Bus and Tag channel is used. CVC if the Block Multiplexer device is connected to an ESCON channel through the use of an ESCON converter, such as an IBM 9034 protocol_type S for all servers with the channel interface set for data streaming at 3 MB per second S4 for all servers with the channel interface set for data streaming at 4.5 MB per second When using ESCON connections to define a CP whose device numbers are 310 and 311, not connected through an ESCON Director, you would supply the following information: Add Channel panel Channel path ID: 3 Number of CHPIDs: 1 Channel path type: CNC (first) Add Control Unit panel Control unit number: 310 Control unit type: DUMMY (second) Add Control Unit panel Channel path IDs: 3 Unit Address: 10 Number of units: 2 Add Device panel Device number: 310 Number of devices: 2 Device type: DUMMY Connected to CUs: 310 When using ESCON connections to define a CP whose device numbers are 310 and 311, connected to port C0 of an ESCON Director, you would supply the following information: Add Channel panel Channel path ID: 3 Number of CHPIDs: 1 Channel path type: CNC Dynamic switch ID: 00 Teradata Tools and Utilities Installation Guide for IBM z/os 33

34 Chapter 3: Configuring the MVS Client Step 4: Specify I/O Devices (first) Add Control Unit panel Control unit number: 310 Control unit type: DUMMY Connected to switches: 00 Ports: C0 (second) Add Control Unit panel Channel path IDs: 3 Link address: C0 Unit Address: 10 Number of units: 2 Add Device panel Device number: 310 Number of devices: 2 Device type: DUMMY Connected to CUs: 310 Note: CP devices cannot be shared by multiple channel paths; therefore, when using an ESCON Director, sharing, or even potential sharing, must be prevented. This can be done by dedicating the ports for the channel path and CP devices, or by prohibiting connections from other channel ports to the CP device port. The Dedicated and Prohibited attributes are assigned to ports either directly from the ESCON Director console, or indirectly from software such as ESCON Manager on MVS. When using ESCON connections to share a channel path without an ESCON Director between two partitions, with CP device numbers 310 through 317 for a partition named LPAR1, and CP device numbers 318 through 31F for a partition named LPAR2, you would supply the following information: Add Channel Path panel Channel path ID: 3 Number of CHPIDs: 1 Channel path type: CNC Operation Mode: SHR Define Access List /: LPAR1... /: LPAR2... (first) Add Control Unit panel Control unit number: 310 Control unit type: DUMMY (second) Add Control Unit panel Channel path IDs: 3 Link address: 10 Number of units: 16 Add Device panel Device number: 310 Number of devices: 8 Device type: DUMMY Connected to CUs: 310 Device/Processor Definition Explicit Device Candidate List: YES 34 Teradata Tools and Utilities Installation Guide for IBM z/os

35 Chapter 3: Configuring the MVS Client Step 4: Specify I/O Devices UCW Assignment Define Device Candidate List /: LPAR1... Add Device panel Device number: 318 Number of devices: 8 Device type: DUMMY Connected to CUs: 310 Device/Processor Definition Explicit Device Candidate List: YES Define Device Candidate List /: LPAR2... No matter what the configuration, the Unit Address value on the Device/Processor Definition panel is optional if the last two digits of the Device Number value are also the physical unit address; otherwise, the Unit Address value is required. No matter what the configuration, on the Define Device Parameter/Features panel, the OFFLINE, DYNAMIC (present beginning with MVS/SP4.2), and LOCANY (present beginning with MVS/SP5) parameters may be specified as either YES or NO, at the discretion of the customer. While a Block Multiplexer channel allows multiple control units to be physically connected on a single channel, ESCON does not; only one control unit can be connected to an optical cable. To provide such flexibility, an ESCON CP can be considered as multiple logical control units. At the discretion of the customer, the Logical address value on the second Add Control Unit panel may be specified, allowing multiple control units to specify the same Link Address but be differentiated by their logical address values. For a complete description of HCD, refer to the MVS HCD Guide. Although the mechanism that defines CP devices in the server is outside the scope of this document, the address used is either the Unit Address value from the Device/Processor Definition panel, or, if the Unit Address was not specified, the last two hexadecimal digits of the Device Number value. Remember that the Device/Processor Definition panel may define multiple devices, each of which must be defined to the server. If your System/370 processor requires UCWs (Unit Control Word), define two unshared UCW addresses for each CP, because each represents a pair of even-odd device numbers. You can define UCW addresses at any time. UCW addressing is described in the IBM Channel Characteristics manual for your CPU. Teradata Tools and Utilities Installation Guide for IBM z/os 35