Installation

The following two procedures describe the installation steps necessary to install all Mainframe Connect options from the InstallShield wizard and to complete the installation for the Server Option for CICS. You should skip those installation steps that do not pertain to the option or options you have chosen to install.

Installing from the InstallShield wizard

1. Start the InstallShield wizard from CD by executing setupwin.exe, which is in the root directory.

   The initial dialog box displays the options available for installation. Click Next and Back to navigate through the wizard. To cancel the installation, click Cancel.

2. Click Next, and accept the terms of the user-license agreement by selecting your country in the drop-down list and selecting the option to indicate that you agree with the terms.

3. Click Next, and select the components you want to install.

   If you are installing the Server Option for CICS API or the DB2 UDB Option for CICS, the Server Option for CICS Runtime component will be automatically selected as you proceed to the next screen.

4. Enter the license keys for the components you purchased.

5. Click Next, and provide the following JCL and system information:

   • JCL Line 1-3: Enter a valid jobcard. This is used to run the final installation jobs in TSO.

   • High Level Qualifier: The high-level qualifier is used as a prefix for all data sets generated during installation.

   • Volume: The volume serial number indicates where generated data sets are cataloged.

   • Unit: The unit parameter value indicates the device requirements for cataloging generated data sets.

   • Work Unit: This is for the use of temporary work data sets.

   • Customer CICS, IMS, and MVS Loadlibs: These are pre-cataloged partitioned data sets (PDSs) or partitioned data sets extended (PDSE) into which configuration modules and sample programs are to be linked. For CICS, this data set should be in the DFHRPL configuration ahead of other Sybase libraries.

   Click Next.

6. If you have chosen to install an option that uses CICS, DB2, or IMS, provide the following information where it applies. Otherwise, skip to the next step.

   • CICS system datasets hlq: The high-level qualifier for CICS system data sets is used to locate SDFHLOAD and other CICS libraries.

   • RDO Dataset: The RDO data set name is the name of the CICS RDO (DFHCSD) containing the application resource definitions used by your CICS region.

   • RDO Group List: The RDO group list is the RDO group list used by your CICS region when executing an initial start.

   • CICS Region Applid: The CICS region APPLID is the VTAM APPLID for your CICS region.

   • DB2 system datasets hlq: The DB2 system data sets high-level qualifier is used for DB2 system data sets.

   • DB2 Exit Dataset: This is the name of the DB2 exit data set used by your DB2 region.

   • DB2 DSN Name: This is the data set name (DSN) of your DB2 region.

   • IMS datasets hlq: The high-level qualifier for IMS system data sets is used to locate IMS libraries.

   Click Next.

7. If you have chosen to install an API component, provide the following compiler information, which is used to configure JCL for compiling sample programs. Otherwise, skip to the next step.

   • LE/370 datasets hlq: The LE370 high-level qualifier is used for the Language Environment 370 and is used here to locate data sets like CEELKED.

   • COBOL Compiler Name: The COBOL compiler name is the module used to execute COBOL in your environment.

   • COBOL Compiler Loadlib: The COBOL compiler LOADLIB is the system LOADLIB in which your COBOL compiler module resides.

   • PLI Compiler Name: The PLI compiler name is the module used to execute PLI in your environment.

   • PLI Compiler Loadlib: The PLI compiler LOADLIB is the system LOADLIB in which your PLI compiler module resides.

   • C compiler datasets hlq: The C compiler data sets high-level qualifier is the high-level qualifier used for C and is used to locate data sets like SBCCMP.

   • TCP/IP datasets hlq: The TCP/IP data sets high-level qualifier is used to locate data sets like SEZATCP.

   Click Next.

8. If you have chosen to install the Client Option for CICS, provide the following information for configuring a host connection definition for the Client Option. Otherwise, skip to the next step.

   • TCP Address Space Name: This is the name of your TCP/IP region.

   • Server Name: This is the name by which your Client Option applications refers to the remote server.

   • Server TCP Host Name: This is the DNS name for the remote server.

   • Server TCP Host Port: This is the TCP/IP port used by the remote server.

   Click Next.

9. If you have chosen to install the Server Option for CICS or the DB2 UDB Option for CICS, provide the following information for configuring a TCP/IP listener for these options. Otherwise, skip to the next step.

   • TCP Address Space Name: This is the name of your TCP/IP region.

   • Listener Port: This is the port on which the option listens.

     The Server Option for CICS and the DB2 UDB Option for CICS share the same TCP/IP listener.

   Click Next.

10. Click Next until the wizard displays the information you entered in steps 5 through 8. Review this information and, if necessary, click Back to return to previous screens and make corrections.

11. Click Next until the wizard displays a dialog box for ftp information. Provide the following data for establishing an ftp session to your mainframe:

    • Userid: This is the mainframe user ID for the ftp session.

    • Password: This is the password for the ftp session.

    • Mainframe Host Name: This is the mainframe DNS name.

    • FTP Port: This is the control port used by your mainframe ftp server, usually 21.

    • VOL/UNIT Assignment: Specify either a volume serial number and unit assignment for ftp, or allow ftp to use default values.

      If you specify a volume serial number that does not exist, ftp hangs until the mainframe responds to a message requesting that the volume be mounted.

    • Log FTP Commands: This indicates where ftp log information is to be written. This log information may be useful in troubleshooting ftp problems.

    The InstallShield wizard will create JCL and upload the selected components to your mainframe once you click Next.

12. Close the InstallShield wizard.

To complete the installation of your Mainframe Connect components, review and submit JCL from TSO. If you are installing multiple components, Sybase strongly suggests you install in the following sequence:

1. Client Option for CICS

2. Server Option for CICS

3. DB2 UDB Option for CICS

4. Any other options

Use the following procedure to complete your installation.

Completing the installation

1. Locate the installation JCL for the DB2 UDB Option for CICS in hlq.AMD2126.CICSDB2.JCL, where hlq is the high-level qualifier you specified in step 5.

2. Run the following jobs in the order they are described here, where x is an integer that denotes the order in which the job is to be run in the overall sequence of jobs. Ignore jobs that are not present or relevant to the option you are installing.

   • IxRECV: This job runs IKJEFT01 to use the TSO RECEIVE command to build and populate the product libraries.

   • IxRDO: This job runs the CICS Resource Definition Utility, DFHCSDUP, to define the transaction, program, and file entries for the DB2 UDB Option for CICS. If your CICS region has had a previous version of the DB2 UDB Option, you may need to uncomment or change the DELETE and REMOVE entries at the top of the RDO input.

   • IxVSAM: This job allocates the VSAM data sets used for error and trace logging.

   • IxLIC: This job populates the license data set for the DB2 UDB for CICS. Since this data set is used for all of the Mainframe Connect IPS options, the Create step may fail if the data set has already been defined. This error may be safely ignored.

   • IxRPC: This job adds definitions to the SYRPCFIL dataset, which is created during the installation of the Server Option and required for the DB2 UDB Option. If DB2 is not to be used in this CICS region, run the IxRPC1 job instead.

   • IxBIND: This job binds the DB2 plans required for the DB2 UDB Option.

     

     • The asterisk and period (*.) before AMD2PKG.* in the PKLIST parameter of the BINDPLAN job may not be required on your DB2 system.

     • In the Server Option for CICS configuration module SYGWXCPH, there is a parameter called CHARSETSRV that can be set to "iso_1" or "utf8". The DB2 UDB Option for CICS works with the CHARSETSRV parameter. This parameter determines which of two DB2 packages, AMD2DB2 or AMD2DBA, are used. If the value of CHARSETSRV is "iso_1," the DB2 packages must be bound with ENCODING(EBCDIC), which is the default. If the value of CHARSETSRV is "utf8," the DB2 packages must be bound with ENCODING(1208).

   • IxDELETE: This optional job deletes the data sets in the TSO XMIT format used for the installation.

3. Run the following jobs if you want to compile and link-edit the sample applications provided with the DB2 UDB for CICS:

   • PAMDCAMX: This job assembles and links the message module for the DB2 UDB Option.

   • PAMDPXIT: This job compiles and links the parser exit module.

   • PASMEXIT: This job assembles and links various exits for the DB2 UDB Option.

4. If you are migrating from a previous version of the DB2 UDB Option for CICS, use the TRSDROP member in the CTRL library as input to SPUFI to drop the old catalog stored procedure (CSP) tables and views.

5. Create tables and views for the CSPs as input to SPUFI using member TRSCREAT or TRSCREA2 in the CTRL library. The following points will help you decide which member to use:

   • TRSCREAT verifies whether the current user has some privilege on a requested object using the current sqlid. If the current sqlid does not have permissions on an object, granted either explicitly or to PUBLIC, then the CSPs do not return information for that object.

   • TRSCREA2 enables faster CSP processing because it does not verify that the current user has a privilege on a requested object.

     The following conditions apply when using TRSCREA2:

     • Anyone who can execute the CSP can obtain information about all DB2 objects, even if that user does not have privileges on those objects.

     • The accessible_table column in sp_server_info is ineffective.

6. Edit and run the TRSGRANT member of CTRL using SPUFI to grant authorization for users to run the CSPs.

7. Create a collection ID by issuing the following SQL command to DB2 (using a utility like TSO batch or SPUFI):

   GRANT PACKADM ON COLLECTION AMD2PKG TO userid
   

8. For each additional DB2 subsystem to be accessed by the DB2 UDB Option for CICS, repeat steps 2 (IxBIND), 4, 5, 6, and 7.

9. Edit the CICS start-up procedure to include the DB2 UDB Option for CICS LOADLIB library in the DFHRPL concatenation. This library should be placed before the load library for the Server Option for CICS.

10. This step is optional. Alter the message table using the AMD2CAMX member of SOURCE as a prototype. Assemble and link the message table using the AMD2CAMX member of JCL. For details on changing the message table, see Chapter 5, “Customizing the DB2 UDB Option for CICS Messages.”

11. Recycle your CICS region.

12. For each additional CICS region in which the DB2 UDB Option is to be installed, repeat steps 2 (IxRDO), 9, 10, and 11, making adjustments to the JCL where appropriate.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF