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 IMS and MVS. You should skip those installation steps that do not pertain to the option or options you have chosen to install.
The InstallShield wizard runs only on Windows.
Installing from the InstallShield wizard
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.
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.
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.
Enter the license keys for the components you purchased.
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.
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.
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.
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.
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.
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.
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.
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:
Client Option for CICS
Server Option for CICS
DB2 UDB Option for CICS
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.
Completing the installation for IMS
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.
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.
IxHOST: This job 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: This job generates PSBs.
IxCAPPC: This job defines APPC VSAM datasets.
IxUAPPC: This job inserts entries into the APPC VSAM datasets.
IxDELETE: This optional job deletes the data sets in the TSO XMIT format used for the installation.
Run the following jobs if you wish to compile and link edit the sample applications provided with the Server Option for IMS:
P1RDO: This job creates sample CICS LU 6.2 RDO entries to be used with IMS.
SAPBIND: This job contains the DB2 binds for sample programs that use DB2.
SAPBMPC: This job contains the BMP region JCL for the SYICSAV2 sample application.
SAPBMPP: This job contains the BMP region JCL for the SYIPSAV1 sample application.
SAPCOB1: This job compiles and links COBOL samples that do not use DB2.
SAPCOB2: This job compiles and links COBOL samples that use DB2.
SAPDB: This job generates IMS data for sample applications.
SAPIMSA: This job compiles and links the IMSASYCH sample application.
SAPPLI1: This job compiles and links PL/1 samples that do not use DB2.
SAPPLI2: This job compiles and links PL/1 samples that use DB2.
SAPTPPRF: This job contains TP profiles for implicit and explicit sample applications.
Completing the installation for MVS
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.
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.
IxHOST: This job 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: This job defines APPC VSAM datasets.
IxDELETE: This optional job deletes the data sets in the TSO XMIT format used for the installation.
Run the following jobs if you wish to compile and link edit the sample applications provided with the Server Option for MVS:
P1RDO: This job creates sample CICS LU 6.2 RDO entries to be used with MVS.
SAPAPPC: This job contains APPC TP profiles for the sample applications.
SAPBIND: This job contains the DB2 binds for the sample applications that use DB2.
SAPCOB1: This job compiles and links non-VSAM COBOL sample applications.
SAPCOB2: This job compiles and links COBOL sample applications that use DB2.
SAPPLI1: This job compiles and links non-VSAM PL/1 sample applications.
SAPPLI1: This job compiles and links PL/1 sample applications that use DB2.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
