The Server Option for IMS and MVS requires a permanent authorization key. However, Sybase includes a temporary key, which is valid for 30 days, within the order at installation time. To avoid interrupting your operations, call Customer Service at 1-800-8Sybase (1-800-879-2273), select Option 3, then select Option 3 again, and request a permanent key.

When speaking with Customer Service, please have the following information ready:

• Product name

• Order number

• For the machine you are using:

  • Serial number

  • Machine type

  • Model number

• A valid e-mail address

The two procedures in this section describe the installation steps you need to install all Mainframe Connect options from the InstallShield wizard and to complete the installation for the Server Option for IMS and MVS. Skip those installation steps that do not pertain to the options you have chosen to install.

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

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

2. 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. Click Next.

3. Select the components you want to install and click Next.

   If you are installing the Server Option for CICS or the DB2 UDB Option for CICS, the Server Option for CICS runtime component will be automatically selected as you go to the next window.

4. Provide the following JCL and system information:

   • JCL Line 1-3 – a valid jobcard used to run the final installation jobs in TSO.

   • High Level Qualifier – used as a prefix for all data sets generated during installation.

   • Volume – the volume serial number that indicates where generated data sets are cataloged.

   • Unit – unit parameter value that indicates the device requirements for cataloging generated data sets.

   • Work Unit – for the use of temporary work data sets.

   • Customer CICS, IMS and MVS Loadlibs – 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.

5. If you are installing an option that uses CICS, DB2 UDB, 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 that is used to locate SDFHLOAD and other CICS libraries.

   • RDO Dataset – the name of the CICS RDO (DFHCSD) containing the application resource definitions used by your CICS region.

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

   • CICS Region Applid – the VTAM APPLID for your CICS region.

   • DB2 system datasets hlq – the high-level qualifier that is used for DB2 system data sets.

   • DB2 Exit Dataset – the name of the DB2 exit data set used by your DB2 region.

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

   • IMS datasets hlq – the high-level qualifier for IMS system data sets that is used to locate IMS libraries.

   Click Next.

6. If you are installing 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 – used for the Language Environment 370 and is used here to locate data sets like CEELKED.

   • COBOL Compiler Name – the module used to execute COBOL in your environment.

   • COBOL Compiler Loadlib – 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 system LOADLIB in which your PLI compiler module resides.

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

   • TCP/IP datasets hlq – used to locate data sets like SEZATCP.

   Click Next.

7. If you are installing 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 – the name of your TCP/IP region.

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

   • Server TCP Host Name – the DNS name for the remote server.

   • Server TCP Host Port – the TCP/IP port used by the remote server.

   Click Next.

8. If you are installing 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 – the name of your TCP/IP region.

   • Listener Port – 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.

9. 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.

10. 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 – the mainframe user ID for the FTP SESSION.

    • Password – the password for the FTP SESSION.

    • Mainframe Host Name – the mainframe DNS name.

    • FTP Port – 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 suspends operation until the mainframe responds to a message requesting that the volume be mounted.

    • Log FTP Commands – indicates where FTP log information will be written. This log information may be useful in troubleshooting FTP problems.

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

11. 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 for the Server Option for IMS. If you are installing the Server Option for MVS, skip to the next procedure.

1. Locate the installation JCL for the Server Option for IMS in hlq.OSC126.IMS.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 – runs IKJEFT01 to use the TSO RECEIVE command to build and populate the product libraries.

   • IxHOST – assembles and links the Server Option customization module, character sets, licensing, and remote host definitions. You may rerun this job at any time to change configuration and character sets or to add, remove, or modify remote host definitions.

   • IxPSB – generates PSBs.

   • IxCAPPC – defines APPC VSAM datasets.

   • IxUAPPC – inserts entries into the APPC VSAM datasets.

   • IxDELETE – (optional) 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 Server Option for IMS:

   • P1RDO – creates sample CICS LU 6.2 RDO entries to be used with IMS.

   • SAPBIND – contains the DB2 binds for sample programs that use DB2.

   • SAPBMPC – contains the BMP region JCL for the SYICSAV2 sample application.

   • SAPBMPP – contains the BMP region JCL for the SYIPSAV1 sample application.

   • SAPCOB1 – compiles and links COBOL samples that do not use DB2.

   • SAPCOB2 – compiles and links COBOL samples that use DB2.

   • SAPDB – generates IMS data for sample applications.

   • SAPIMSA – compiles and links the IMSASYCH sample application.

   • SAPPLI1 – compiles and links PL/1 samples that do not use DB2.

   • SAPPLI2 – compiles and links PL/1 samples that use DB2.

   • SAPTPPRF – contains TP profiles for implicit and explicit sample applications.

1. Locate the installation JCL for the Server Option for MVS in hlq.OSC126.MVS.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 – runs IKJEFT01 to use the TSO RECEIVE command to build and populate the product libraries.

   • IxHOST – assembles and links the Server Option customization module, character sets, licensing, and remote host definitions. You may rerun this job at any time to change configuration and character sets or to add, remove, or modify remote host definitions.

   • IxCAPPC – defines APPC VSAM datasets.

   • IxDELETE – (optional) 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 Server Option for MVS:

   • P1RDO – creates sample CICS LU 6.2 RDO entries to be used with MVS.

   • SAPAPPC: contains APPC TP profiles for the sample applications.

   • SAPBIND – contains the DB2 binds for the sample applications that use DB2.

   • SAPCOB1 – compiles and links non-VSAM COBOL sample applications.

   • SAPCOB2: – compiles and links COBOL sample applications that use DB2.

   • SAPPLI1 – compiles and links non-VSAM PL/1 sample applications.

   • SAPPLI1 – compiles and links PL/1 sample applications that use DB2.