SQL ACCESS FOR SUPRA SERVER PDM

Transcription

1 SQL ACCESS FOR SUPRA SERVER PDM Installation Guide P

2 SQL Access for SUPRA Server PDM Installation Guide Publication Number P , 2007, 2009, 2011 Cincom Systems, Inc. All Rights Reserved This document contains unpublished, confidential, and proprietary information of Cincom. No disclosure or use of any portion of the contents of these materials may be made without the express written consent of Cincom. See for a list of Cincom trademarks and other trademarks that may appear in Cincom product documentation. All other trademarks are trademarks or registered trademarks of their respective companies. Cincom Systems, Inc. 55 Merchant Street Cincinnati, Ohio USA PHONE: (513) FAX: (513) WORLD WIDE WEB: Attention: Some Cincom products, programs, or services referred to in this publication may not be available in all countries in which Cincom does business. Additionally, some Cincom products, programs, or services may not be available for all operating systems or all product releases. Contact your Cincom representative to be certain the items are available to you.

3 Release information for this manual SQL Access for SUPRA Server PDM Installation Guide, P , is dated September 1, This document supports Release 2.0 of SQL Access for SUPRA Server PDM. Cincom Technical Support for SQL Access for SUPRA Server PDM All customers Web: U.S.A customers Phone: Fax: (513) Attn: SQL Access for SUPRA Server PDM Support Mail: Cincom Systems, Inc. Attn: SQL Access for SUPRA Server PDM Support 55 Merchant Street Cincinnati, OH USA Outside of U.S.A. All: Visit the support links at to find contact information for your nearest Customer Service Center. Using this manual $ORDB refers to the directory identified by the ORDB environment variable. This will be set to the installation directory. This document may use both UNIX ($ORDB/..) and Windows (%ORDB%\..) notations. Please adjust the environment variable and slashes accordingly for your platform.

4 Contents 1. Overview of SQL Access... 5 Overview SQL Access installation... 6 Site requirements... 6 Upgrading to SQL Access on Windows... 9 Installing SQL Access on Windows Pre-installation tasks The CID Adapter Server installation option The SQL Access Server installation option The SQL Access Client installation option Installing the MVS or CICS CID Adapter Server Installing the OpenVMS CID Adapter Server Installing the UNIX CID Adapter Server Testing the CID Adapter Server installation Installing SQL Access on UNIX Pre-installation tasks Set environment variables Install SQL Access Set up communication services Define TCP port numbers Install additional product components Test the installation Access your PDM or VSAM data Index Installation Guide, P Contents

5 1. Overview of SQL Access Overview SQL Access for SUPRA Server PDM (SQL Access) enables dynamic access to your PDM and/or VSAM data in real time using ODBC, JDBC, or OLE DB interfaces. There is no need to extract the data and transform it into a relational database and write custom code. SQL Access allows you to easily access your PDM and/or VSAM data using ODBC, JDBC, or OLE DB client applications. You can find a more detailed description of SQL Access in Chapter 1 of the SQL Access for SUPRA Server PDM Administration Guide, P Installation Guide, P Chapter: 1. Overview of SQL Access Section: Overview

6 2. SQL Access installation Site requirements SQL Access for SUPRA Server PDM (SQL Access) is a multi-platform product. The CID Adapter Server component will execute on MVS, CICS, OpenVMS, or UNIX. The SQL Access Server and Client will execute on Windows or IBM AIX. Consider the following before installing and executing SQL Access: SQL Access runs as a client/server system on Windows or UNIX, which requires at least two processes. SQL Access Client processes and the SQL Access Server process may run on the same or different machines. Typically, each process runs on a different machine. The network protocol for TCP/IP must be available on all platforms. Installation Guide, P Section: Site requirements

7 Recommended memory and disk space: Windows - A minimum of 64 MB of main memory is recommended to run the SQL Access Server. - The target disk selected for the installation must have a sufficient amount of free disk space available. Approximately 145 MB of application space plus 80 MB of temp space is needed. - Each client machine will require a minimum of 20 MB of main memory. UNIX - A minimum of 16 MB of main memory is recommended to run UNIX and the first SQL Access process. For each additional SQL Access process running on the same machine, an additional 4 MB, plus buffer space, is recommended. Buffer space is configured with the num_data_buffers and the sr_buffers parameters for server processes, and ax_block_size and max_block_count parameters for client processes in the ordbinit.txt file. For information on configuring the ordbinit.txt file, refer to the SQL Access for SUPRA Server PDM Administration Guide, P The target disk selected for the installation must have approximately 400 MB of free disk space available for the application plus 65 MB for temp space. - The following platform and environment is supported on UNIX: Platform IBM RS/6000 running AIX version 5.3 Environment IBM XL C/C++ compiler version Installation Guide, P Section: Site requirements

8 The CID Adapter Server has the following requirements: MVS or CICS - MVS/XA 2.2 and higher - MVS/ESA 3.1 and higher - CICS Transaction Server 1.3 or higher - Z/OS - all versions - TCP/IP 2.21 and higher - SUPRA Server PDM Release 2.7 OpenVMS - OpenVMS/Alpha 8.2 and higher - UCX 3.3 and higher - SUPRA Server PDM Release 2.4 and higher UNIX - HP-UX and higher - SUPRA Server PDM Release 1.2.3a and higher (1.3.1h and higher is recommended) WINDOWS The following site requirements are needed for Windows: - You must use Intel-based machines. - If you plan to access servers on other machines, you will need a network interface card. The procedures provided in this installation guide assume a default installation. The procedures have been tested and verified on clean systems but cannot be guaranteed to work on systems that have been extensively customized. Installation Guide, P Section: Site requirements

9 Upgrading to SQL Access on Windows If you are upgrading from SUPRA Relational Access to SQL Access, you will need to choose the CID Adapter Server installation option and continue to the SQL Access Server installation. Setup will detect the SUPRA Relational Access version and prompt you to upgrade it. If you choose not to upgrade, setup will terminate. If you choose to upgrade, however, the ODBC data sources from the SUPRA Relational Access product version defined on the server machine, if any, will be maintained, and you will be prompted to uninstall the SUPRA Relational Access version. You must enter the DBA username and password for the SUPRA Relational Access server being upgraded. If it is password protected, you must also enter the server password. Failure to supply the correct information will result in a failed upgrade. Cincom recommends that you uninstall the SUPRA Relational Access version while upgrading. This will maintain the ODBC data sources, if any, from the SUPRA Relational Access product version. Uninstalling the SUPRA Relational Access version later may require you to redefine certain environment variables and settings. If you want to migrate a database prior to SUPRA Relational Access 1.0, you will need to issue the unloaddb command prior to the upgrade (refer to the SQL Access for SUPRA Server PDM Administration Guide, P ). After you have completed the installation of SQL Access Server, you can then use the loaddb command in this new product version to load the database (refer to the SQL Access for SUPRA Server PDM Administration Guide, P ). Installation Guide, P Section: Upgrading to SQL Access on Windows

10 Installing SQL Access on Windows You should read through the entire installation procedure before starting to help ensure a successful installation. SQL Access is a multi-platform product. There are three installation options: CID Adapter Server - FTPs CID Adapter Server to the PDM or VSAM host machine. - Optionally, you can also install the SQL Access Server (SQL Access Server option) at the end of this installation. SQL Access Server - Installs SQL Access Server on the Windows machine. - Installs SQL Access Client, ODBC and JDBC driver, and OLE DB Provider on the Windows machine. SQL Access Client, ODBC, JDBC, and OLE DB - Installs SQL Access Client, ODBC and JDBC driver, and OLE DB Provider on the Windows machine. Installation Guide, P

11 Pre-installation tasks Prior to installing SQL Access, perform the following tasks: Gather the following information: - Host name for MVS/OpenVMS/UNIX. This is the name that TCP/IP can use for communication with the PDM host machine. - Port number on the host that TCP/IP can use for communication. Alternatively, on OpenVMS and UNIX a port number will be assigned during the CID Adapter Server setup process. MVS CICS - DBM parameter in the CSIPARM file for the SUPRA PDM you wish to access. For CICS VSAM without PDM you will enter CICS. OPENVMS UNIX - Dbmod name for the SUPRA PDM dbmod you wish to access. Check that TCP/IP is available on the host. Ensure that you have the ability to FTP files from this Windows machine to the MVS/OpenVMS/UNIX host machine. MVS CICS Create the MVS Destination Library prior to installing the Server. This is a PDS that will be used to receive the JCL members and the files for the MVS CID Adapter Server. The PDS should be created with recfm=fb, lrecl=80. blksize=32000, dsorg=po, cyls=(450,10,30). This will be referred to in the installation instructions as the MVS Destination Library. OPENVMS Create the OpenVMS Destination Directory prior to installing the Server. This is a directory on the OpenVMS machine that will receive the CID Adapter Server zip file sent using FTP. Perform the following steps: a. Log in to an OpenVMS system account. The account must have the following privileges: CMKRNL, SYSNAM, DETACH, LOG_IO, PRMGBL, SHARE, SHMEM, PRMMBX, and SYSPRV b. Create an install directory to receive the install media. For example: CREATE/DIRECTORY [V1DRIVER_INSTALL] UNIX Create the UNIX Destination Directory prior to installing the Server. This is a directory on the UNIX machine that will receive the CID Adapter Server files sent using FTP. Installation Guide, P

12 Cincom recommends that you install the SQL Access Server component of SQL Access on a separate Windows machine. All users will need to install the SQL Access Client component of SQL Access and will need network access to this machine. The CID Adapter Server installation option To install the CID Adapter Server software, the files must first be sent to the host machine using FTP. Follow these steps to FTP the files (the SQL Access Server install can be selected after the FTP): 1. Create the Destination Library or Directory described in "Pre-installation tasks" on page 11, if not already created. 2. Insert the CD-ROM into your PC. The install should start automatically. If not, run Win32\Setup.exe from the CD-ROM. 3. You are prompted to select an installation option. Choose CID Adapter Server. 4. Choose a PDM or VSAM Host Platform (MVS, OpenVMS or UNIX) when prompted. 5. You are then prompted for FTP information: MVS - Port Number Used for TCP/IP communication. This port number is substituted into the files prior to being sent via FTP. It is not needed to successfully FTP the files. - PDM or VSAM Host Name Domain name of the MVS/OpenVMS/UNIX machine, which is used for TCP/IP communication. - Host Username MVS/OpenVMS/UNIX host username. This username must have write permission to the Destination Library / Directory below. - Host Password Password for the Host Username. - Destination Library or Directory Destination on the PDM or VSAM host for the files being sent via FTP. This was created in step 1 of this procedure. 6. Setup then attempts to ping the PDM or VSAM Host Name you supplied. If it is unsuccessful, you will get a chance to enter a different name. If you choose not to correct the PDM or VSAM Host Name, the installation ends. Try this installation again when you have resolved the Host name problem. 7. You are prompted for the directory in which to install the software. By default, this is C:\Program Files\Cincom DAK<release_number>\ORDB (e.g., C:\Program Files\Cincom DAK1.0.03\ORDB). You may change this directory as needed. Installation Guide, P

13 8. The files are sent via FTP to the PDM or VSAM host. If the transfer fails, a message box displays telling you to reference the log file ftpscript.log in the installation directory for the product (see step 7) for further details. You are given a chance to correct the FTP information based on the log. If you choose not to correct the problem, the installation ends. Try the installation again when you have resolved the problem. 9. Before you can access the PDM or CICS VSAM data, you must install and set up the CID Adapter Server on the PDM or VSAM host and install the SQL Access Server on Windows. You can continue this installation and set up the SQL Access Server now and set up the CID Adapter Server later, or terminate setup and come back later to install the SQL Access Server after setting up the CID Adapter Server. If you choose No when prompted to install the SQL Access Server, setup will terminate. If you choose Yes, setup will continue and step you through the SQL Access Server installation. See "The SQL Access Server installation option" that follows, skipping steps 1, 2 and 3. Installation Guide, P

14 The SQL Access Server installation option Follow these steps to install the SQL Access Server, SQL Access Client, ODBC and JDBC driver, and OLE DB Provider on Windows. 1. Insert the CD-ROM into your PC. The install should start automatically. If not, run Win32\Setup.exe from the CD-ROM. If you previously followed the CID Adapter Server installation option using this PC, setup will display a Maintenance dialog. Choose Modify. 2. Choose SQL Access Server when prompted for an installation option. 3. If you have not previously installed the CID Adapter on this PC, you are prompted for the directory in which to install the software. By default, this is C:\Program Files\Cincom DAK<release_number>\ORDB (e.g., C:\Program Files\Cincom DAK1.0.03\ORDB). You may change this directory as needed. 4. The setup program searches for the Java Runtime Environment. If it is not found, you are prompted to install it (it is included on the CD-ROM). You have three options: - Yes, I want to install it now. (default selection) - No, I will not install it. - No, I have JRE installed and will supply the location now. If Java Runtime Environments are found, the first three are displayed and you have the following options: - Use <jre_release_number> in <jre_location> - Use <jre_release_number> in <jre_location> (if found) - Use <jre_release_number> in <jre_location> (if found) - Install JRE 1.5.0_11 from CD - Type or browse to location of another JRE (default selection) - Skip this step The Java Runtime Environment (JRE) is NOT required for SQL Access, although the Visual Administration Tool and JDBC driver do require it. The Visual Administration Tool can be very helpful but is not required. If you have space limitations, you may choose not to install the JRE. Installation Guide, P

15 5. You are prompted for the Program Folder for the software. By default, this is SQL Access <release_number> (e.g., SQL Access ). You may change this Program Folder as needed. 6. You are then prompted for the type of Program group. Cincom recommends Install for All Users program group, which is the default. The setup program loads all of the SQL Access Server and SQL Access Client installation files. 7. The setup program searches for the Adobe Acrobat Reader. If not found, you are prompted to install it from the CD. Adobe Acrobat Reader installation is not required. You can use the Acrobat Reader in the installation directory or your own reader to read the user documentation. 8. You are then prompted to read the online documentation. You may view the manuals now or later. To view them later click the Documentation link in the SQL Access Program Group. 9. You will be asked if you want to restart your computer now, or later. The setup will complete the installation when you reboot. Please leave the CD- ROM in the CD drive. It is needed after restart to complete the installation. 10. After restart, the installation will automatically continue. 11. The SQL Access Master, which is necessary for accessing the PDM or CICS for VSAM, will attempt to start. If it cannot start, a message displays and you should contact Cincom Support. Installation Guide, P

16 12. The setup will then create a SQL Access Server and register the CID Foreign Database to that server. You are prompted to supply the following: - Port Number Required for TCP/IP communications. - PDM / Dbmod Name Varies by platform: MVS OPENVMS UNIX CICS VSAM Enter the DBM name specified in the CSIPARM file. Enter the dbmod name. If the dbmod name is prefixed, enter it as <Prefix>_<dbmod-name> (for example, 001_MRPDBO). For CICS VSAM and no PDM enter CICS. - PDM or VSAM Host Name Domain name of the MVS/OpenVMS/UNIX machine. This is used for TCP/IP communications. - Foreign Database Alias name within SQL Access for the PDM database or CICS VSAM system. You may give this any name you wish. - SQL Access Server The SQL Access Server name. You may give this any name you wish. The Server Name is the only parameter that is absolutely required in order to create a server. The default name of DAK is supplied. If you clear this parameter, you will be prompted to enter a name. If you leave the other fields blank, you will need to register the CID foreign database later. Refer to the SQL Access for SUPRA Server PDM Administration Guide, P If setup detects that a SQL Access Server already exists for the server name you have supplied, you will be prompted to restart or overwrite the server or create a server with a different name. 13. If all fields are entered, the SQL Access Server is then created and the CID Foreign Database is registered. For more information about registering the CID Foreign Database, refer to the SQL Access for SUPRA Server PDM Administration Guide, P Make note of the SQL Access Server and CID Foreign Database names. They will be important to your access later. 14. For security purposes you may wish to create a password for the SQL Access Server. This will prevent unauthorized users from stopping, deleting, etc., the SQL Access Server you just created. To add a password, refer to the utilities information in the SQL Access for SUPRA Server PDM Administration Guide, P Installation Guide, P

17 15. Before retrieving data from the PDM or CICS VSAM, you will need to install and set up the CID Adapter Server using the files that were sent via FTP to the PDM or CICS VSAM host machine. See the section appropriate to your PDM or CICS VSAM operating system: - "Installing the MVS or CICS CID Adapter Server" on page 21 - "Installing the OpenVMS CID Adapter Server" on page 25 - "Installing the UNIX CID Adapter Server" on page If the CID Adapter Server installation has been completed, you can create Foreign Tables using the Visual SQL tool. A Foreign Table is a map of a PDM file, PDM record code or VSAM file. See "Testing the CID Adapter Server installation" on page 28 for instructions. 17. Configure the ODBC Data Source: a. From the Windows Control Panel, select Administrative Tools Data Sources. b. Click the System DSN tab (your ODBC tool may require a User or File Data Source), then click ADD. A list of ODBC Drivers is displayed. c. Select Cincom ORDB 2.4 Driver and click FINISH. You will be prompted for the following: - Data Source Name This can be any name you wish. It is the name that the ODBC tools use. - Description (Optional) Some descriptive text for the Data Source. - User Name Enter dba. This is the only user id that currently exists in the ORDB Server. When you create other ids later, you can change this Data Source, if you wish. - Database Name The name of the SQL Access Server that you created in Step 13 of this procedure. Installation Guide, P

18 The SQL Access Client installation option This installation will place a SQL Access Client, ODBC and JDBC driver, and OLE DB Provider on a PC other than the one where the SQL Access Server is installed. Before testing the SQL Access Client, the SQL Access Server must have been installed on another machine, because the SQL Access Client must connect to the SQL Access Server. You will need to know the name of that machine and the name of the SQL Access Server in order to connect. 1. Insert the CD-ROM into your PC. The install should start automatically. If not, run Win32\Setup.exe from the CD-ROM. 2. You are prompted to select an installation option. Choose SQL Access Client, ODBC, JDBC, and OLE DB. 3. You are prompted for the directory in which to install the software. By default, this is C:\Program Files\Cincom DAK<release_number>\ORDB (e.g., C:\Program Files\Cincom DAK1.0.03\ORDB). You may change this directory as needed. 4. The setup program searches for the Java Runtime Environment. If it is not found, you are prompted to install it (it is included on the CD-ROM). You have three options: - Yes, I want to install it now. (default selection) - No, I will not install it. - No, I have JRE installed and will supply the location now. If Java Runtime Environments are found, the first three are displayed and you have the following options: - Use <jre_release_number> in <jre_location> - Use <jre_release_number> in <jre_location> (if found) - Use <jre_release_number> in <jre_location> (if found) - Install JRE 1.5.0_11 from CD - Type or browse to location of another JRE (default selection) - Skip this step The Java Runtime Environment is NOT required for SQL Access, although the Visual Administration Tool and JDBC driver do require it. The Visual Administration Tool can be very helpful but is not required. If you have space limitations, you may choose not to install the JRE. 5. You are prompted for the Program Folder for the software. By default, this is SQL Access <release_number> (e.g., SQL Access ). You may change this Program Folder as needed. Installation Guide, P

19 6. You are then prompted for the type of Program group. Cincom recommends Install for All Users program group, which is the default. The setup program then loads all of the SQL Access Client installation files. 7. You must define the SQL Access Server, which is on a different Windows machine, to the SQL Access Client before the SQL Access Client can connect to it. Setup asks if you want to create a Server Definition now. If No, setup skips to step Enter the SQL Access Server Definition information. Server name is the name of the SQL Access Server on another Windows machine to which you wish to connect. Host name is the name of that Windows machine. If setup detects that the SQL Access Server Definition server name already exists, you will be prompted to either override the existing server name or create a new Server Definition. This could occur if you have a SUPRA Relational Access version installed with the same Server name defined. If you choose to override the existing server name, this will disable automatic connectivity using the SUPRA Relational Access client environment. 9. The setup program searches for the Adobe Acrobat Reader. If not found, you are prompted to install it from the CD. Adobe Acrobat Reader installation is not required. You can use the Acrobat Reader in the installation directory or your own reader to read the user documentation. 10. You are then prompted to read the online documentation. You may view the manuals now or later. To view them later click the Documentation link in the SQL Access Program Group. 11. You will be asked if you want to restart your computer now, or later. You need to reboot before the client version is available. After restart, the installation setup is complete. Installation Guide, P

20 12. Configure the ODBC Data Source: a. From the Windows Control Panel, select Administrative Tools Data Sources. b. Click the System DSN tab (your ODBC tool may require a User or File Data Source), then click ADD. A list of ODBC Drivers is displayed. c. Select Cincom ORDB 2.4 Driver and click FINISH. You will be prompted for the following: - Data Source Name This can be any name you wish. It is the name that the ODBC tools use. - Description (Optional) Some descriptive text for the Data Source. - User Name Enter dba. This is the only user id that currently exists in the ORDB Server. When you create other ids later, you can change this Data Source, if you wish. - Database Name SQL Access Server name. 13. To test the SQL Access Client installation with ODBC, JDBC, or OLE DB, choose one of your client applications or use MSQuery for ODBC, as described here: a. Search for msqry32.exe in Program Files (create a shortcut to it if you want to use it again), and execute it. b. Select FILE NEW. The dialog box should show the Data Source name you created in step 18 of the Windows Server installation. Click on that name and you will get the Cincom ORDB ODBC Connect dialog box. c. Enter the SQL Access Server name for the Database, your user id, and password. This will connect you to the SQL Access Server. Select the foreign table you created above and select the columns you wish to view. Installation Guide, P

21 Installing the MVS or CICS CID Adapter Server To install and set up the MVS or CICS CID Adapter Server, the files must have been previously transferred via FTP to MVS from Windows. This occurs during the CID Adapter Server installation option. Go to the MVS Destination Library defined in the CID Adapter Server installation. This will contain several shell JCL members that will now be used to complete the installation. You will need to know the following in order to complete this section of the installation: PDM The DSName for the library that contains your MVS Supra PDM CSTEDCMT module PDM The DSName for the CSIPARM for your SUPRA PDM The DSName for your MVS or CICS TCP/IP data file The TCP/IP prefix added to your TCP/IP file names for TCP/IP access The port number on MVS or CICS that TCP/IP can use for communication (same as the one used in the SQL Access Server installation) Valid volume number and unit information to be used to allocate several libraries Installation Guide, P

22 Perform the following steps: 1. Modify the JOBCARD member to meet your company standards. This will be copied into the other JCL members. Be sure to keep the LIBSRCH line in the JOBCARD member. It is required so that the SPARMS parameters will be substituted into the JCL members. 2. Review the SPARMS member: - HLQ will be used as the prefix for names of the libraries required to execute the MVS CID Adapter Server (for example, <HLQ>.LINKLIB). Modify this if necessary. - VOLS will be substituted in the JCL to create these libraries. Provide a valid volume number. - UNITS will be substituted in the JCL to create these libraries. Provide a valid unit. - PORT is the port number. Modify this if necessary. - DBM is the DBM parameter in the CSIPARM file. For CICS VSAM without PDM, this parameter should be CICS. - HOST is the host name of the MVS machine. 3. Select the ALLOCLIB member. Copy the JOBCARD member into the beginning of ALLOCLIB. Run this job. It will allocate libraries needed for the MVS or CICS CID Adapter Server. 4. Select the RECEIVE member. Copy the JOBCARD member into the beginning of RECEIVE. Run this job. It will complete the FTP process for the libraries. Installation Guide, P

23 5. For MVS batch: Select the SERVER member. Copy the JOBCARD member into the beginning of SERVER. This is the job that will bring up the MVS CID Adapter Server, which is the job that will communicate with the PDM. You will need to modify the following: - STEPLIB a. Change the SUPRALIB DSN to be the library that contains the PDM module CSTEDCMT. b. Change the CBC.SCLBDLL DSN to the name of the C++ Runtime library on your machine. - CSIPARM Change this to point to your CSIPARM file. - SYSTCPD Change this to point to your MVS TCP/IP data file. Your MVS system administrator may require a specific jobname or some other security requirement for this job to use the port number for TCP/IP communications. 6. Select the CSV1SHUT member. Copy the JOBCARD member into the beginning of CSV1SHUT. This job will shut down the MVS CID Adapter Server. Refer to the SQL Access for SUPRA Server PDM Administration Guide, P , for more information on defining the MVS CID Adapter Server Shutdown JCL. 7. Open the INIT member and modify the following: - TCP_PREFIX=EH00.TCPIP.V2R21. Substitute your TCP prefix. If the port number was entered during the CID Adapter Server install option, verify that it was correctly substituted for 5050 in this line. If not, put the appropriate port number here: - TCP_LISTEN_PORT= Review the SQL Access for SUPRA Server PDM Administration Guide, P , to determine whether there are additional parameters you would like to specify in the INIT file. 9. Review the section on Tailoring the CID Adapter Server in the SQL Access for SUPRA Server PDM Administration Guide, P , and use it to make any changes necessary. Installation Guide, P

24 10. Bring up the MVS CID Adapter Server using the SERVER JCL member or bring up your CICS, which will start the MVS CICS CID Adapter Server transaction. (For PDM users it is assumed that your Central PDM is started before bringing up the SERVER job or CICS transaction). The SERVER job or CICS transaction should display the following message near the bottom: CSHP522I CID Adapter Server Release <release_number> waiting for connections. You are now ready to test the Installation. See the section "Testing the CID Adapter Server installation" on page 28. The first time (and only the first time) you bring up the SERVER job or CICS you may see the following messages prior to the CSHP522I message above: CSHP536I BIND_SCHEMA option enabled. Building schema from file CSHP537E Unable to open bound schema file. Building schema from directory CSHP539I Writing bound schema to file You will also see the following message after CSHP522I: LSCX503 **** WARNING **** ERRNO = ENFOUND Generated in FOPEN called from line 5790 offset Extended name: read_bound_schema File never created, open failed. Interrupted while: Opening file "SCHEMA" You may ignore these messages. Installation Guide, P

25 Installing the OpenVMS CID Adapter Server To install the CID Adapter Server component on OpenVMS, perform the following steps on the target OpenVMS installation machine. The installation will require approximately 27,000 blocks. 1. Set the default directory to the Destination directory where the file was sent via FTP during the CID Adapter Server installation option on default <directory> 2. Use the unzip utility to unzip the file. The unzip utility is supplied on the freeware CD-ROM from Digital. For example: UNZIP VMSV1DRVnnnnn.ZIP where nnnnn is the CID Adapter Server release number string (for example, 2400). 3. Issue the following V1DRV a. Provide the install directory as the distribution volume directory. b. Provide a User Identification Code (UIC) number or an account user number. This number establishes ownership for all CID Adapter Server files loaded from the tape. Otherwise, the files will be owned by the system. You will be prompted as follows: Please enter in one of the following formats: [ggg,mmm] where ggg is the UIC Group number and mmm is the UIC Group member number or [uuuuuuuu] where uuuuuuuu is the account user. Installation Guide, P

26 c. Supply the CID Adapter Server Root Directory when prompted. This directory will contain all of the CID Adapter Server directories and files. It can be a disk device name and directory (device:[dir]), or it can be a logical name. Based upon the Root directory given, the following subdirectories will be created: device:[dir.v1drv_nnnnnn] device:[dir.v1drv_nnnnnn.clean_exe] device:[dir.v1drv_nnnnnn.burrys] device:[dir.v1drv_nnnnnn.coms] device:[dir.v1drv_nnnnnn.examples] device:[dir.v1drv_nnnnnn.exe] device:[dir.v1drv_nnnnnn.help] device:[dir.v1drv_nnnnnn.patches] device:[dir.v1drv_nnnnnn.patch_work] where nnnnnn is the CID Adapter Server service level. d. You are asked if the directories are acceptable. If the directory structure is acceptable, take the default of YES and press RETURN to continue processing. Otherwise, type NO and press RETURN to re-enter the CID Adapter Server Root Directory. For the next steps to set up the OpenVMS CID Adapter Server, refer to the section on tailoring the OpenVMS CID Adapter Server in the SQL Access for SUPRA Server PDM Administration Guide, P When done, continue with "Testing the CID Adapter Server installation" on page 28. Installation Guide, P

27 Installing the UNIX CID Adapter Server To install the CID Adapter Server component on UNIX: 1. cd to the Destination Directory where the file was sent using FTP during the CID Adapter Server installation option on Windows. 2. Decompress the tar file using the command: gunzip PDMAdapterServer_nnnn.tar.gz 3. Extract the files from the tar file using the command: tar xf PDMAdapterServer_nnnn.tar This will create the directory PDMAdapterServer_nnnn containing the UNIX CID Adapter Server directory and files in the current directory. For the next steps to set up the UNIX Adapter Server, refer to the section on tailoring the UNIX Adapter Server in the SQL Access for SUPRA Server PDM Administration Guide, P When done, continue with the section "Testing the CID Adapter Server installation" that follows. Installation Guide, P

28 Testing the CID Adapter Server installation To test the CID Adapter Server installation, follow these steps: 1. Select START Programs SQL Access <release_number> from the Windows Taskbar. Then click on Visual SQL. This will bring up the Visual SQL tool that can be used to create Foreign Tables, which map a PDM or CICS VSAM file. 2. You will see the dialog box to logon to the SQL Access Server. Enter the SQL Access Server name that you defined during the Windows Server installation (step 13 of "The SQL Access Server installation option" on page 14), if it isn t already displayed. Enter dba for the User Name, leave Password blank, and click Open. The product is delivered without a password. Refer to the Visual SQL chapter of the SQL Access for SUPRA Server PDM SQL Reference Guide, P , to create a password. Installation Guide, P

29 3. The following tree will be displayed. Double-click on Foreign Databases, and you should see the Foreign Database name that you created in Step 13 of "The SQL Access Server installation option" on page 14. Installation Guide, P

30 4. Review the Foreign Database registration information by right-clicking on the Foreign Database name and clicking EDIT. Correct any information as needed, and click Register. Installation Guide, P

31 5. You will now be back at the tree view of the server. Click on the foreign database name and you will see two categories: - Mapped to Foreign Tables - Not Mapped to Foreign Tables The fact that you see these two categories indicates that you have successfully connected to the CID Adapter Server and it has returned a list of files. Click on Not Mapped to Foreign Tables and you will see a list of all your PDM and/or VSAM files. Choose one of the files that you would like to access and click on it to create a foreign table (map of the PDM or VSAM file). Installation Guide, P

32 6. The Create Foreign Table dialog box allows you to modify the foreign table name and foreign table attribute names that will be exposed to the client application. For further details review the Visual SQL chapter of the SQL Access for SUPRA Server PDM SQL Reference Guide, P For the test, you could accept the defaults and click Create Foreign Table. You have already tested the connection to the CID Adapter Server by retrieving the PDM or VSAM file names and field names for the above foreign table. Now you can test the retrieval of data from those files. You can test them in Visual SQL or with a client application. Installation Guide, P

33 7. To test with Visual SQL, click on the Mapped to Foreign Table category. Right-click on the foreign table name you just created and then click TEST. This will SELECT all the fields in the PDM or VSAM file. A maximum of 20 rows will be returned for the TEST function. Once you have examined the results, you will need to click Close Test in order to enter a select into the test window. 8. To test with ODBC, JDBC or OLE DB, choose one of your client applications or use MSQuery for ODBC, as described here: a. Search for msqry32.exe in Program Files (create a shortcut to it if you want to use it again), and execute it. b. Select FILE NEW. The dialog box should show the Data Source name you created in step 18 of the Windows Server installation. Click on that name and you will get the Cincom ORDB ODBC Connect dialog box. c. Enter the SQL Access Server name for Database, and DBA for user name. There is no password, so leave that blank. This will connect you to the SQL Access Server. Select the foreign table you created above and select the columns you wish to view. Installation Guide, P

34 Installing SQL Access on UNIX You should read through the entire installation procedure before starting to help ensure a successful installation. The UNIX installation procedure comprises the following general steps: 1. Set the appropriate environment variables 2. Run the installation program 3. Verify authorization 4. Set up communication services 5. Define TCP port numbers 6. Install additional product components 7. Test the installation 8. Access your PDM or VSAM data Installation Guide, P Section: Installing SQL Access on UNIX

35 Pre-installation tasks Before beginning installation, you should gather the following information: Names of all hosts Names of all users Names of storage devices Directory and database structure For best results: Read this guide before attempting installation. You will then be more likely to complete your installation successfully the first time. Back up your file system beforehand so that you will be able to restore your file system in case of a problem during installation. A system backup is not required, but it is recommended. Pay particular attention to environment variables. Most common installation problems can be avoided if environment variables are set correctly. Be sure that you know the proper name of your CD-ROM device. Instructions are provided in the installation procedure. These default installation procedures place all files in the $ORDB directory, when defined, otherwise in a directory named /opt/ordb. Within this directory, application files and database files are stored in separate subdirectories. You can install files into different subdirectories if you wish. If you choose to use different directory names for SQL Access files, you need to change your environment variables appropriately before installation, because the install script uses the environment variables you define to determine the target subdirectories for files. You can change these subdirectories after installation, but if you do, you must make corresponding changes in all related environment variables. Refer to the SQL Access for SUPRA Server PDM Administration Guide, P , for details on setting environment variables. Installation Guide, P Section: Installing SQL Access on UNIX

36 Set environment variables Complete the following steps to set environment variables for a new product: 1. Set the following environment variables. If using csh, add the following to the.cshrc file using your editor: Environment variable ORDB ORDB_DATABASES ORDB_LANG PATH LD_LIBRARY_PATH Command setenv ORDB /opt/ordb setenv ORDB_DATABASES /opt/ordb/database-directory setenv ORDB_LANG locale where locale is En_US or Ja_JP setenv PATH $ORDB/bin:$ORDB/utilities:${PATH} setenv LD_LIBRARY_PATH \ $ORDB/lib:${LD_LIBRARY_PATH} 2. Save your.cshrc file and read in your new environment variables: source.cshrc 3. If using sh, add the following to your.profile file using your editor: Environment variable ORDB ORDB_DATABASES ORDB_LANG PATH LD_LIBRARY_PATH Command ORDB=/opt/ordb; export ORDB ORDB_DATABASES=/opt/ordb/database-directory; export ORDB_DATABASES ORDB_LANG=locale; export ORDB_LANG where locale is En_US or Ja_JP PATH=$ORDB/bin:$ORDB/utilities:${PATH} export PATH LD_LIBRARY_PATH= \ $ORDB/lib:${LD_LIBRARY_PATH} export LD_LIBRARY_PATH 4. Save your.profile file, and read in your new environment variables:..profile For more information on environment variables, refer to the SQL Access for SUPRA Server PDM Administration Guide, P Installation Guide, P Section: Installing SQL Access on UNIX

37 Install SQL Access 1. Insert the SQL Access distribution disc into your CD drive. 2. Mount the disc on your CD drive mount point. AIX Example $ mount F cdfs o cdcase /dev/dsk/c0t2d0/cdrom /cdrom The root user must do this. The actual syntax may vary depending on your UNIX system. Refer to the UNIX man page on mount for more information. 3. Change the current working directory to the platform directory (i.e., AIX) under the CD mount point. 4. Run the install program from the command line as follows: $./install The installation program displays several interactive screens that allow you to select the product components to install, specify target directories (if they differ from the default directory structure), and enter other information as required for a successful installation. Installation Guide, P Section: Installing SQL Access on UNIX

38 Set up communication services The following steps allow you to set up your communication services and update your /etc/services and /etc/magic files. You may want to make a backup copy of these files before proceeding. 1. Assign a communication service name and a port number in the UNIX network software table. Append the following to the /etc/services file (if it does not already exist and if it does not conflict with any existing entry): DA4SUPRA 1978/tcp When the SQL Access Master starts, it determines what port number to use by reading either the network_service_name or the master_port_id SQL Access system parameters. If the network_service_name is used, the service name and port number must be defined in the /etc/services file on the SQL Access Master machine. When a user starts a client application, a connection to a particular SQL Access Server is requested. The SQL Access Client determines the port number with which to connect to the SQL Access Master using either the network_service_name or the master_port_id SQL Access system parameters. If the network_service_name is used, the service name and port number must be defined in the /etc/services file on the SQL Access Client machine. Refer to the SQL Access for SUPRA Server PDM Administration Guide, P , for additional information. 2. (Optional) The file ordb_magic located in the $ORDB/admin directory can be appended to the site system magic file, so that the UNIX file command can give an informative description of the SQL Access and VisualEditor type files whenever the command is invoked. To append the ordb_magic file, enter the following command at the system prompt: cat $ORDB/admin/ordb_magic >> /etc/magic If your site is running NIS, you should use the ypcat command to determine whether or not the /etc/magic file is a map. (If the file is a map, you should append the ordb_magic file to the map.) The format of the ypcat command is ypcat <mapname>. 3. Parameters in the ordbinit.txt file are automatically configured to the default settings. The network_service_name and master_port_id must be set at this time (see the following section, Define TCP port numbers, for more information). Installation Guide, P Section: Installing SQL Access on UNIX

39 Define TCP port numbers The master_port_id parameter is defined in the file named ordbinit.txt that is located in the $ORDB/admin directory. The default TCP port number used by SQL Access components is Usually, there is no requirement to alter the port number unless the port is already in use. For example, if you will be running more than one SQL Access Server, it is essential that you modify the port number assigned to the master_port_id parameter in the SQL Access initialization file. In addition, it is necessary to modify the same parameter to the same port number on all the platforms where SQL Access is installed. The values of the parameter must correspond to the value assigned in the /etc/services file. The ordbinit.txt file is located in the $ORDB/admin directory. Refer to the SQL Access for SUPRA Server PDM Administration Guide, P , for more information on these parameters and on customizing the ordbinit.txt file. Install additional product components Additional product components may be added after the initial installation is complete by running the CD install program again. The following steps describe this procedure: 1. Mount the SQL Access distribution CD on your CD drive mount point. 2. Change the current working directory to the platform directory (i.e., AIX) under the CD mount point and run the install program from the command line as follows: $./install 3. Choose the product components that you wish to add by selecting additional product options. The installation program then installs the selected components. Installation Guide, P Section: Installing SQL Access on UNIX

40 Test the installation Test your installation using the test database programs located in the $ORDB/demo directory. To build the demo SQL Access Server, enter the following: make_ordb_demo For more information about building the demo SQL Access Server, refer to the SQL Access for SUPRA Server PDM Administration Guide, P After installing SQL Access and successfully running the demo SQL Access Server, you are ready to create your SQL Access Server using the createdb utility. Installation Guide, P Section: Installing SQL Access on UNIX

41 Access your PDM or VSAM data After you have successfully installed SQL Access on UNIX, you will need to complete the following steps in order to access your PDM or VSAM data: 1. Use the createdb utility to create your SQL Access Server on UNIX. Enter the following command to run this utility: createdb <data_access_server_name> For more information about the createdb utility, refer to the SQL Access for SUPRA Server PDM Administration Guide, P Use the CID Adapter Server option of the Windows install to begin the CID Adapter Server installation. See "Pre-installation tasks" on page 11 and "The CID Adapter Server installation option" on page 12 for this information. 3. Create a CID Foreign Database definition and define one or more Foreign Tables that map to the PDM or VSAM files you wish to access. Perform the following steps: a. Install the SQL Access Client on a Windows machine. This SQL Access Client will communicate with the SQL Access Server that you previously installed on UNIX. The SQL Access Client on Windows will give you access to Visual SQL to create the CID Foreign Database and Foreign Table definitions. See "The SQL Access Client installation option" on page 18 for installation instructions. b. Create the CID Foreign Database definition using Visual SQL. Refer to the SQL Access for SUPRA Server PDM SQL Reference Guide, P , for information on how to do this. You can also find information on how to log onto Visual SQL in this same reference guide. c. Create one or more Foreign Tables within this Foreign Database. Refer to the SQL Access for SUPRA Server PDM SQL Reference Guide, P , for information on how to do this. 4. Test these components. See "Testing the CID Adapter Server installation" on page 28 for information on how to do this. Installation Guide, P Section: Installing SQL Access on UNIX

42 Index A Acrobat Reader SQL Access Client installation 19 SQL Access Server installation 15 AIX 7 ALLOCLIB member 22 C C/C++ compiler 7 CID Adapter Server installation 12 CID Adapter Server install 12 CID Adapter Server requirements 8 CID Adapter Server Root Directory 26 CID Foreign Database registration 16 communication services HP-UX 38 Create Foreign Table dialog box 32 CSIPARM 21, 23 CSV1SHUT member 23 D DBM parameter 11 Dbmod name 11 Destination Directory 12 Destination Library 12 E Edit Foreign Database Properties dialog box 30 environment variables LD_LIBRARY_PATH 36 ORDB 36 ORDB_DATABASES 36 ORDB_LANG 36 PATH 36 F Foreign Database registration 16 free space requirements 7 H Host name 11 Password 12 username 12 HP-UX authorizing communication services 38 installation 36 I IBM RS/ installation adding a product 39 options 10 requirements 6 UNIX general procedure 34 hints 35 HP-UX 36, 38 overview 35 J Java Runtime Environment for client installation 18 for SQL Access Server installation 14 JDBC client installation 14 JDBC driver SQL Access Server installation 14 L LD_LIBRARY_PATH environment variable, setting 36 loaddb 9 Installation Guide, P Index