The Client 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, be sure to have this information ready:

• Product name

• Order number

• For the machine you are using:

  • Serial number

  • Machine type

  • Model number

• A valid e-mail address

The following two procedures describe the installation steps necessary to install all Mainframe Connect options from the installation program (installer) and to complete the installation for the Client Option for IMS and MVS. You should skip those installation steps that do not pertain to the options you have chosen to install.

1. Start the installer 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 installation program. 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. Click Next, and provide this JCL and system information:

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

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

   • Volume – indicates where generated data sets are cataloged.

   • Unit – 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 (PDSEs) 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 have chosen to install 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 – high-level qualifier for CICS system data sets is used to locate SDFHLOAD and other CICS libraries.

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

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

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

   • DB2 system datasets hlq: – used for DB2 system data sets.

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

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

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

   Click Next.

6. If you have chosen to install an API component, provide this 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, used here to locate data sets like CEELKED.

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

   • COBOL Compiler Loadlib – system LOADLIB in which your COBOL compiler module resides.

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

   • PLI Compiler Loadlib – system LOADLIB in which your PLI compiler module resides.

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

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

   Click Next.

7. 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 – 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 DSN name for the remote server.

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

   Click Next.

8. 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 – 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.

   Click Next to continue.

9. Click Next until the installer 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 installer displays a dialog box for FTP information. Provide this data to establish 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 DSN name.

    • FTP Port – the control port used by your mainframe FTP server, usually 21.

    • VOL/UNIT Assignment – 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 operations until the mainframe responds to a message requesting that the volume be mounted.

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

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

11. Close the installation program.

To complete the installation of your Mainframe Connect components, review and submit JCL from TSO. If you are installing multiple components, Sybase strongly suggests that you install in this 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 Client Option for IMS. If you are installing the Client Option for MVS, skip to the next procedure.

1. Locate the installation JCL for the Client Option for IMS in hlq.OCC150.IMS.JCL, where hlq is the high-level qualifier you specified in step 5.

2. Run these jobs in the order they are described here:

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

   • IxHOST – assembles and links the Client Option for IMS 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.

   • IxDELETE – (optional) deletes the data sets in the TSO XMIT form used for the installation.

3. Run these jobs if you want to compile and link-edit the sample applications provided with the Client Option for IMS:

   • SCTCOB1 – compiles and links the sample COBOL applications that use the Client Option interface.

   • SCTCOB2 – compiles and links the sample COBOL applications that act as Server Option applications that make Client Option calls.

     This job can be run only if the Server Option has been installed.

   • SCTC1 – compiles and links the sample C applications that use the Client Option interface.

   • SCTMAP – generates MFS maps for the sample programs.

   • SCTPLI1 – compiles and links the sample PL/1 applications that use the Client Option interface.

   • SCTPLI2 – compiles and links the sample PL/1 applications that act as Server Option applications that make Client Option calls.

     This job can be run only if the Server Option has been installed.

   • SCTPSB – generates IMS PSBs for the sample programs.

   • SCTPSB – creates and initializes the IMS database for the sample programs.

1. Locate the installation JCL for the Client Option for MVS in hlq.OCC150.MVS.JCL, where hlq is the high-level qualifier you specified in step 5.

2. Run these jobs in the order they are described here:

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

   • IxHOST – assembles and links the Client Option for MVS 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.

   • IxDELETE – (optional) deletes the data sets in the TSO XMIT form used for the installation.

3. Run these jobs if you want to compile and link-edit the sample applications provided with the Client Option for MVS:

   • SCTISQL – contains the JCL for executing the SYISQL program.

   • SCTMCOB – compiles and links the sample COBOL application programs that use the Client Option.

   • SCTMPA5 – contains the JCL for executing the SYCTMPA5 application program.

   • SCTMPB5 – contains the JCL for executing the SYCTMPB5 application program.

   • SCTMPC5 – contains the JCL for executing the SYCTMPC5 application program.

   • SCTMPD5 – contains the JCL for executing the SYCTMPD5 application program.