2-16 Setting Up Oracle Connect for IMS, VSAM, and Adabas Gateways to Update VSAM, IMS, or Adabas Data 2-17. The gateway requires Oracle Database Server, Oracle Connect for IMS, VSAM, and Adabas Gateways, and Oracle Studio for IMS, VSAM, and Adabas Gateways.
Gateway Architecture
Gateway Process Flow
Oracle Connect for IMS, VSAM, and Adabas Gateways converts the Oracle SQL statement into a data access operation understood by the data source. Oracle Connect for IMS, VSAM and Adabas Gateways converts the retrieved data into a format compatible with the Oracle database server.
Setup Flow
The gateway sends the query to Oracle Connect for IMS, VSAM and Adabas Gateways. See Oracle Database Gateway for IMS, VSAM, and Adabas Installation and Configuration Guide for Microsoft.
Overview of Oracle Database Gateway for IMS, VSAM, and Adabas
This chapter guides you through the installation procedure of Oracle Connect for IMS, VSAM, and Adabas Gateways. You configure Oracle Connect for IMS, VSAM, and Adabas Gateways through Oracle Studio for IMS, VSAM, and Adabas Gateways.
System Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways
Hardware Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways
Software Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways
Accessing the Installation Software
Downloading Oracle Software from the Oracle Technology Network Web Site
Downloading the Installation Archive File
Extracting the Installation Files
Copying the Oracle Software to a Hard Disk
Mounting Discs
Check that the files you downloaded are the same size as the corresponding files on the OTN. In these cases, /cdrom and /SD_CDROM are the mount point directories for the disk drive.
Installing Oracle Connect for IMS, VSAM, and Adabas Gateways
Installation Worksheet
Preinstallation Instructions
Optional permission to specify an output class for Oracle Connect output for IMS, VSAM, and Adabas Gateways. Assigning a device that is set to HOLD prevents loss of log data when Oracle Connect jobs for IMS, VSAM, and Adabas Gateways are completed.
Kit Installation Instructions
Transferring the Kit to the Dataset
Installation Instructions
If you want to review the JCL used to install Oracle Connect for IMS, VSAM, and Adabas Gateways before it is. This message is only displayed if SMS is used to manage the installation (you answered Y to the first message).
Data Source Configuration Instructions
Enter the name of the EXCI LOAD library only if you do not want to use the default. Enter the name of the ISPF load library only if you do not want to use the default. ENTER DBD LIBRARY NAME [IMS.DBDLIB]: Enter the name of the IMS DBD library for IMS on your system only if you do not want to use the default.
ENTER PSB LIBRARY NAME [IMS.PSBLIB]: Enter only the IMS PSB library name for IMS on your system if you do not wish to use the default. ENTER RES LIBRARY NAME [IMS.SDFRESL]: Enter only the IMS RES library name for IMS on your system if you do not wish to use the default. ENTER YOUR PSB NAME [HOSPPSB]: Only enter the PSB name if you do not wish to use the default.
ENTER ADABAS SVC NUMBER [249]: Enter the SVC number only if you do not want to use the default number. Enter the name of the Adabas load library only if you do not want to use the default library.
Postinstallation Instructions
Postinstallation Tasks
If you decide to change the name of the ATTSRVR member when you move it to a high-level general qualifier, you must change the name specified in the To use the global transaction function, define each steplib library in the ATTSRVR JCL as a APF authorized library. In the security manager, such as RACF, create the STARTED class general resource profiles ATTDAEMN, ATTSRVR, and NVIMSSRV.
ALTER authorization on datasets under INSTROOT.hlq (to gain access to read, write, assign and delete datasets under INSTROOT.hlq). Note: If you change the name of the ATTSRVR member, be sure to use this new name in all related tasks. This data set is read at startup and the correct software version is used, based on the details of the startup task.
If you change the location of this data set, you must also change the relevant DD map in the used start tasks and scripts. Consult TCP/IP documentation for information about specifying Oracle Connect for IMS, VSAM, and Adabas Gateways as the service that uses port 2551 in the TCP/IP network services file.
Starting the Daemon
You can use this file to provide the same input if you run the installation again, where INSROOT is the high-level qualifier you assign for the installation.
Setting Up Oracle Connect for IMS, VSAM, and Adabas Gateways for Reentrancy
Configuring Additional Settings for Working with CICS
Configuring OTMA for Working with IMS/TM
It is recommended to add the step to run this program to the IMS/TM task that has been started. Set up Oracle Connect for IMS, VSAM, and Adabas gateways to update VSAM, IMS, or Adabas data.
Setting Up Oracle Connect for IMS, VSAM, and Adabas Gateways to Update VSAM, IMS, or Adabas Data
To configure Oracle Connect for IMS, VSAM, and Adabas Gateways so that you can update VSAM data from a CICS transaction. CEDA DEF PROG(UPDTRNS) G(group_name) LANG(C) DA(ANY) DE(DataSource ORACLE UPDATE PROG). Where INSTROOT is the top-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed and the data source is VSAM.
How to configure Oracle Connect for IMS, VSAM, and Adabas Gateways to update IMS/DB data from a CICS transaction. CEDA DEF PROG(ATYDBCTL) G(groupname) LANG(C) DA(ANY) DE(ORACLE data source UPDATE PROG). Where INSTROOT is the high level qualification where Oracle Connect to IMS, VSAM and Adabas Gateways are installed and the data source is IMS.
Troubleshooting Overview
Troubleshooting Methods
Using the NAV_UTIL CHECK SERVER Utility
By running this program, you can detect network and configuration problems and get a better idea of the point where the error occurs.
Using the NAV_UTIL CHECK DATASOURCE Utility
Using Trace Log Files
Expand a machine with the binding you are working with in Oracle Studio for IMS, VSAM, and Adabas Gateways Design Perspective Configuration View.
Log Traces
Common Errors and Solutions
Explanation: The daemon was unable to create the irpcd[_port].pid file in the BIN directory, which is located in the directory where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed. Explanation: A non-Oracle Connect for IMS, VSAM, and Adabas Gateway program tries to connect to the daemon. Increase the ConnectTimeout value for the server workspace in the Workspace section of the daemon configuration.
Explanation: An Oracle Connect server for IMS, VSAM, and Adabas Gateways started by a daemon could not connect to or register back with the daemon. Verify that the client and server are using the same version of Oracle Connect for IMS, VSAM, and Adabas Gateways. If the server contains user code such as the Oracle Connect process for IMS, VSAM, and Adabas Gateways, a.
Explanation: The Oracle Connect for IMS, VSAM and Adabas Gateways daemon (IRPCD) on the server machine cannot start a server process to serve the client. Specify the codepage environment variable in the Oracle Connect environment settings for IMS, VSAM, and Adabas Gateways.
Running NAV_UTIL
This section explains how to run the NAV_UTIL utility and describes the available commands.
Activating NAV_UTIL
Basic NAV_UTIL Syntax
ADD_ADMIN
CHECK
DELETE
Deleting Data Source Objects
EDIT
The object is exported to an XML file that is automatically displayed in a text editor. When the text editor is closed, the XML file is saved back to the repository. However, you cannot delete a repository entry by deleting it from a text editor with this command.
You can change the editor in the various environment settings either by using Oracle Studio for IMS, VSAM and Adabas Gateways or by running a command. This option is only relevant for displaying the definition of a local table or procedure (when the obj_type value is local_table or local_procedure).
EXECUTE
EXECUTE Overview
If no binding is specified, the default Oracle Connect binding for IMS, VSAM, and Adabas Gateways is used. Enter the tdp command with the new name you want as the default data source.
Running SQL Statements
On-the-fly
From a File
Perform the following procedure to run all queries on the dataset without the overhead of displaying query information on the screen for each query. In this case, only queries that fail cause information to be displayed on the screen during execution. After all queries are executed a message appears, stating the number of queries that succeeded and the number that failed.
From within a Transaction
EXECUTE Commands
If the index is specified, a visual representation of the record structure is displayed where available (this structure can be made available by running the NAV_UTIL . EXPORT command). You can list details about specific columns of the data source and about columns in specific tables that belong to the data source.
EXPORT
This option is only relevant for exporting a table or stored procedure (when the obj_type parameter is a table or procedure). If the data source is an ADD data source, the metadata is retrieved from the repository and from the driver-specific information for that data source, which is usually obtained from the data source at runtime. Use the following table to determine the name of the obj_item to render, depending on the value of obj_type, or use * for all objects of the specified type.
GEN_ARRAY_TABLES
IMPORT
IMS_MERGE
IRPCDCMD
LOCAL_COPY
PASSWORD
TEST
UPDATE
Removing Metadata Statistics
If you want information about all indices and only some partial indices, you can run the utility twice: once with the -All option and once with +i1, +i2,. The result is based on the number of nRows specified as part of the metadata for the data source and the amount of available memory as specified by the dsmMaxBufferSize parameter of the environment settings. If the value given here is the correct value or close to the correct value, the time to calculate the statistics is reduced.
UPD_DS
UPD_SEC
VERSION
VERSION_HISTORY
VIEW
This option is only relevant for viewing the definition of a table or stored procedure (when the obj_type value is table or procedure). The XML command sends an XML request directly to Oracle Connect for IMS, VSAM, and Adabas Gateways for processing, just as execute sends an SQL query directly to Oracle Connect for IMS, VSAM, and Adabas Gateways. XML is particularly useful for troubleshooting by allowing system administrators and DBAs to monitor how the Oracle Connect for IMS, VSAM, and Adabas Gateways XML dispatcher handles queries specified in XML documents.
XML Samples
