CONTENTS Title Page Copyright Page Send Us Your Comments Preface 1 Planning for the Gateway for DB2 Server 1.1 Gateway for DB2 Server Software 1.2 Required IBM Software 1.3 Tasks Performed by the IBM System Administrator 1.4 Exchanging Information for Gateway Administration 1.4.1 Getting Information from the Client Gateway Coordinator 1.4.2 Supplying Information to the Client Gateway Coordinator 1.4.3 Supplying Information to the DEC SNA Gateway Administrator 1.5 Upgrading to a New Version of Gateway for DB2 Server 1.5.1 Client and Server Software Version Compatibility 1.5.2 Using Different Client Versions on the Network 1.5.3 Considerations for Upgrading the Server 1.5.4 Steps for Upgrading the Server 2 Installing the Gateway for DB2 Server Software 2.1 Preparing to Install Gateway for DB2 Server Software 2.1.1 STEP1A-Verify Prerequisite Software 2.1.2 STEP1B-Check the VTAM Logon Mode Table Entry 2.1.3 STEP1C-Check VTAM and NCP Entries for Your Gateway 2.1.4 STEP1D-Check the CICS Definitions for LU 6.2 Sessions 2.1.5 STEP1E-Check the Gateway for DB2 Server Installation Tape 2.1.6 STEP1F-Plan Space Allocation for Data Sets 2.1.6.1 SMP/E Data Sets (Conditional) 2.1.6.2 Target Libraries 2.1.6.3 Distribution Libraries 2.1.7 STEP1G-Determine the Data Set Names for Your CICS and DB2 System Libraries 2.1.8 STEP1H-Determine Security for Gateway for DB2 Server 2.1.9 STEP1I-Plan for DB2 Resources 2.2 Installing the Gateway for DB2 Server 2.2.1 STEP2A-Create the Installation Data Set 2.2.2 STEP2B-Review the Program Directory 2.2.3 STEP2C-Allocate Gateway for DB2 Server Target and Distribution Libraries 2.2.4 STEP2D-Allocate SMP/E Data Sets and Define SMP/E Environment (Conditional) 2.2.5 STEP2E-Create the SMP PROC (Conditional) 2.2.6 STEP2F-Initialize the SMP/E Environment with Gateway for DB2 Server SMP/E DDDEF Statements (Conditional) 2.2.7 STEP2G-Perform SMP/E RECEIVE Processing 2.2.8 STEP2H-Create Dummy Load Module 2.2.9 STEP2I-Perform SMP/E APPLY Processing 2.2.10 STEP2J-Perform SMP/E ACCEPT Processing 2.3 Customizing the Gateway for DB2 Server Environment 2.3.1 STEP3A-Create DB2 Metadata Views, Synonyms, and Grant SELECT Privilege on Views 2.3.2 STEP3B-Modify Metadata View Names (Conditional) 2.3.3 STEP3C-Changing Server System Names and Run-Time Options (Conditional) 2.3.3.1 DB2INFO System Name 2.3.3.2 VIDAJOUR System Name 2.3.3.3 WRITEFLG System Name 2.3.3.4 READCS, READRR, WRITECS, WRITERR System Names 2.3.4 STEP3D-Run Gateway for DB2 Server Link-Edit Job (Conditional) 2.3.5 STEP3E-Making the Load Module Available to CICS 2.3.6 STEP3F-Bind Gateway for DB2 Server Plan and Packages 2.3.7 STEP3G-Bind Write Packages (Conditional) 2.3.8 STEP3H-Grant Execute Authority to Gateway for DB2 Server Application Plan and Packages 2.3.9 STEP3IA-Modify CICS Table Entries 2.3.9.1 Modifying the Program Properties Table 2.3.9.2 Modifying the Program Control Table 2.3.9.3 Modifying the Terminal Control Table 2.3.9.4 Defining the Gateway for DB2 Server Logging Facility to the Journal Control Table 2.3.10 STEP3IB-Modify CICS Resource Definition Entries 2.3.10.1 Defining Gateway for DB2 Server Load Modules to CICS 2.3.10.2 Defining Gateway for DB2 Server Transactions to CICS 2.3.10.3 Defining Terminals to CICS 2.3.11 STEP3J-Modify Resource Control Table Entries 2.3.12 STEP3K-Define and Initialize CICS Journal Used by the Gateway for DB2 Server Logging Facility (Conditional) 2.4 Building the PERSONNL Sample Database 2.4.1 STEP4A-Copy PERSONNL Sequential Files from Tape to Disk 2.4.2 STEP4B-Create the DB2 Environment for the PERSONNL Database 2.4.3 STEP4C-Create the PERSONNL Tables 2.4.4 STEP4D-Grant Select Privilege on PERSONNL Tables 2.4.5 STEP4E-Create Synonyms for PERSONNL Tables (Optional) 2.4.6 STEP4F-Load PERSONNL Tables 2.4.7 STEP4G-Remove the PERSONNL Database Environment (Optional) 3 Customizing the Gateway for DB2 Server Views 3.1 Gateway for DB2 Server Views 3.2 Customizing a View 3.2.1 Modifying View Names 3.2.1.1 Modify Installation Data Set Member (STEP3A) 3.2.1.2 Modify Installation Data Set Member (STEP3B) 3.2.1.3 Run Link-Edit and Make Load Modules Available to CICS (STEP3D and STEP3E) 3.2.1.4 Bind Gateway for DB2 Server Packages and Plans (STEP3F and STEP3G) 3.2.2 Replacing DB2 Catalog Table Names 4 Gateway for DB2 Server Operations 4.1 Changing View Definition 4.2 Changing Server Run-Time Options 4.3 Authorizing New Users 4.3.1 User IDs and Passwords 4.3.2 Access to Transactions, Packages, and Plans 4.3.3 Access to DB2 Tables 4.4 Maintaining Gateway for DB2 Server Packages 4.4.1 DBRMs Supplied with the Gateway for DB2 Server 4.4.2 How Gateway for DB2 Server Selects a Package Name 4.4.3 How Gateway for DB2 Server Uses Collection-id Names 4.4.4 How Gateway for DB2 Client Controls Collection-id Name Selection 5 Security with the Gateway for DB2 Server 5.1 Security Within the CICS Intercommunication Environment 5.1.1 Bind-Time Security 5.1.2 Attach-Time Security 5.2 CICS Security 5.2.1 Using CICS Default Security 5.2.2 Using RACF with CICS 5.2.3 Using ACF2 with CICS 5.2.3.1 Using ACF2 with ATTACHSEC 5.2.3.2 Using ATTACHSEC(VERIFY) or ATTACHSEC(IDENTIFY) 5.3 DB2 Security 5.3.1 Limiting the Capabilities of gateway for DB2 Server 5.3.2 Limiting EXECUTE Access to Gateway for DB2 Server Packages 5.3.3 Limiting Access to DB2 Objects A Gateway for DB2 Server Installation Tape B Fully Qualified Data Set Names Worksheet for Gateway for DB2 Server C JCL Strings Worksheet for Gateway for DB2 Server D Copy of Gateway for DB2 Server Install STEP2C Through STEP2J E Copy of Gateway for DB2 Server Install STEP3A Through STEP3K F Copy of Gateway for DB2 Server Install STEP4A Through STEP4G