Oracle Application Server Adapters User Manual
Oracle® Application Server
Adapters for IMS/DB User’s Guide
10g Release 3 (10.1.3.4)
E13832-01
December 2008
Oracle Application Server Adapters for IMS/DB User's Guide, 10g Release 3 (10.1.3.4)
E13832-01
Copyright © 2005, 2008, Oracle and/or its affiliates. All rights reserved.
Primary Author: Jeanne Wiegelmann, David Goldman
Contributors: Yishai Hadas, , Adeeb Massad, Dror Harari, , Meera Srinivasan, Bo Stern, Shashi Suravarapu,
Costi Zaboura, Sheela Vasudevan
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and
license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of
the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software
License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications which may
create a risk of personal injury. If you use this software in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use
of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of
this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.
This software and documentation may provide access to or information on content, products, and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services.
Contents
Preface ................................................................................................................................................................. xi
Audience....................................................................................................................................................... xi
Documentation Accessibility..................................................................................................................... xi
Related Documents .................................................................................................................................... xii
Conventions ................................................................................................................................................ xii
1 Introduction
OracleAS Adapter for IMS/DB Overview........................................................................................... 1-1
OracleAS Adapter for IMS/DB Architecture ...................................................................................... 1-2
Integration Flow from Oracle Application Server to the Legacy Application.......................... 1-2
2 Installing and Configuring the OracleAS Adapter for IMS/DB
Preinstallation Tasks................................................................................................................................ 2-1
IBM z/OS Hardware and Software Requirements....................................................................... 2-1
Hardware Requirements............................................................................................................ 2-1
Software Requirements.............................................................................................................. 2-2
Installing Oracle Connect on an IBM z/OS Series Platform............................................................ 2-2
Installation Worksheet....................................................................................................................... 2-3
Preinstallation Tasks.......................................................................................................................... 2-4
Importing the Installation Kit........................................................................................................... 2-5
Installation Instructions..................................................................................................................... 2-5
Post-Installation Instructions............................................................................................................ 2-8
Post-Installation Procedures...................................................................................................... 2-8
Starting the Daemon................................................................................................................ 2-10
Setting Up Oracle Connect for Reentrancy .......................................................................... 2-10
Setting Up Oracle Connect to Update IMS/DB Data ......................................................... 2-11
Updating an Existing Oracle Connect Installation with IMS/DB ............................................... 2-11
Installing Oracle Studio....................................................................................................................... 2-12
Oracle Studio Requirements.......................................................................................................... 2-12
Installing Oracle Studio on Windows.......................................................................................... 2-13
Installing Oracle Studio on Linux................................................................................................. 2-13
Installing Oracle Studio with the Wizard (SH installation)............................................... 2-13
Installing with a Silent Installation (RPM) ........................................................................... 2-13
Configuring Oracle Connect ............................................................................................................... 2-13
Setting Up the IBM z/OS Platform in Oracle Studio................................................................. 2-14
v
Securing Access to Oracle Connect .............................................................................................. 2-15
Setting Password Access to Oracle Studio........................................................................... 2-15
Specifying Users with Administrative Rights ..................................................................... 2-16
Setting Up Run-Time User Access to the IBM z/OS Platform.......................................... 2-17
Modeling Interactions for OracleAS Adapter for IMS/DB........................................................... 2-19
Setting Up the IMS/DB Data Source............................................................................................ 2-19
Configuring the Data Source Driver ............................................................................................ 2-21
Configuring the Data Source Driver Advanced Properties............................................... 2-23
Importing Metadata for the IMS/DB Data Source..................................................................... 2-25
Selecting the Imput Files......................................................................................................... 2-25
Applying Filters ....................................................................................................................... 2-27
Selecting Tables ........................................................................................................................ 2-29
Matching DBD to COBOL ...................................................................................................... 2-29
Import Manipulation............................................................................................................... 2-30
Metadata Model Selection ...................................................................................................... 2-38
Import the Metadata................................................................................................................ 2-40
Setting Up an Oracle Connect Adapter ....................................................................................... 2-41
Generating Outbound Interactions .............................................................................................. 2-42
Modifying Existing Interactions.................................................................................................... 2-45
3 Integrating OracleAS Adapter for IMS/DB with OC4J
Integrating OracleAS Adapter for IMS/DB with OC4J .................................................................... 3-1
Configuring the J2CA 1.5 IMS/DB Adapter........................................................................................ 3-2
Using the CCI API to Develop Applications ...................................................................................... 3-3
Configuring Multiple Adapters ............................................................................................................ 3-4
Updating Configuration Information .................................................................................................. 3-4
4
Integrating OracleAS Adapters for IMS/DB with Oracle BPEL Process Manager
Integrating OracleAS Adapters for IMS/DB with Oracle BPEL Process Manager ..................... 4-1
Configuring Oracle BPEL Process Manager ....................................................................................... 4-2
Setting up the Connection to the Oracle Connect Server............................................................. 4-2
Checking Metadata Availability Using Oracle JDeveloper ......................................................... 4-2
Configuring the WSDL for Outbound Applications .................................................................... 4-2
5 BPEL Process Manager Examples
Getting Started.......................................................................................................................................... 5-1
Deploy a BPEL Outbound Process........................................................................................................ 5-2
Beginning Tasks ................................................................................................................................. 5-2
Design-Time Configuration.............................................................................................................. 5-3
Create a BPEL Project for a BPEL Outbound Process............................................................ 5-3
Create a Database Adapter to Read the Doctor Table........................................................... 5-4
Design a BPEL Outbound Process to Read the String........................................................... 5-5
Create a Partner Link to the Database Adapter...................................................................... 5-6
Edit the Invoke_1 Activity......................................................................................................... 5-7
Edit the Assign_1 Activity......................................................................................................... 5-8
vi
Runtime Configuration ..................................................................................................................... 5-9
6 Configuring an OracleAS Adapter for IMS/DB for Outbound Interactions
Creating Outbound Interactions with the OracleAS Adapter for IMS/DB .................................. 6-1
Requirements...................................................................................................................................... 6-1
Adding the IMS/DB Hospital Data Source......................................................................................... 6-1
Prepare the System............................................................................................................................. 6-1
Set up Machine Access to Oracle Connect...................................................................................... 6-2
Add an IMS/DB Data Source........................................................................................................... 6-2
Import the Metadata.......................................................................................................................... 6-3
Create the findDoctor and findPatient Interactions.......................................................................... 6-4
Add a Database Adapter................................................................................................................... 6-4
Create Interactions ............................................................................................................................. 6-4
7 Troubleshooting OracleAS Adapter for IMS/DB
Troubleshooting the Daemon ................................................................................................................ 7-1
Starting the Daemon.......................................................................................................................... 7-1
Task: Starting the Daemon ........................................................................................................ 7-2
Shutting Down the Daemon............................................................................................................. 7-2
Monitoring the Daemon During Run Time.................................................................................... 7-2
Daemon (Computer) Options ................................................................................................... 7-2
Workspace Options .................................................................................................................... 7-3
Server Options............................................................................................................................. 7-4
Daemon Logs...................................................................................................................................... 7-4
The Daemon Log Monitor ......................................................................................................... 7-5
The Workspace Log Monitor..................................................................................................... 7-5
The Server Log Monitor............................................................................................................. 7-5
Resolving Communication Errors......................................................................................................... 7-6
Resolving Specific Errors........................................................................................................................ 7-6
8 Advanced Features of OracleAS Adapter for IMS/DB
Configuring the Daemon for High Availability ................................................................................ 8-1
Adding a New Daemon Workspace Configuration...................................................................... 8-1
Editing the Workspace ...................................................................................................................... 8-2
Configuring the Server Mode........................................................................................................... 8-2
Configuring a Binding Environment ................................................................................................... 8-6
Debug................................................................................................................................................... 8-7
General................................................................................................................................................. 8-8
Language ............................................................................................................................................. 8-8
Modeling ............................................................................................................................................. 8-9
ODBC ................................................................................................................................................... 8-9
OLEDB................................................................................................................................................. 8-9
Optimizer ............................................................................................................................................ 8-9
Query Processor ................................................................................................................................. 8-9
Parallel Processing ............................................................................................................................. 8-9
Transactions ........................................................................................................................................ 8-9
vii
Tuning............................................................................................................................................... 8-10
XML................................................................................................................................................... 8-10
Migration Considerations.................................................................................................................... 8-11
Security Considerations ....................................................................................................................... 8-11
Setting Design Time Security ........................................................................................................ 8-12
Setting Runtime Security................................................................................................................ 8-12
Transaction Support.............................................................................................................................. 8-13
A Advanced Tuning of the Metadata
Metadata for the IMS/DB Data Source ............................................................................................... A-1
General Tab........................................................................................................................................ A-2
Columns Tab...................................................................................................................................... A-3
Column Definition Section ....................................................................................................... A-4
Column Properties..................................................................................................................... A-5
Indexes Tab ........................................................................................................................................ A-7
Table Information ...................................................................................................................... A-7
Properties .................................................................................................................................... A-8
Statistics Tab....................................................................................................................................... A-8
Generating Statistics ................................................................................................................ A-10
Advanced Tab.................................................................................................................................. A-11
Adapter Metadata.................................................................................................................................. A-13
Adapter Metadata General Properties......................................................................................... A-13
Adapter Metadata Interactions ..................................................................................................... A-15
Interaction Advanced Tab ...................................................................................................... A-16
Adapter Metadata Schema Records ............................................................................................. A-18
Adapter Metadata XML ................................................................................................................. A-20
B Back-end Adapter Data Type Support
Data Type Mapping ................................................................................................................................ B-1
C Advanced Tuning of the Daemon
Control....................................................................................................................................................... C-1
Logging...................................................................................................................................................... C-3
Security..................................................................................................................................................... C-5
Workspac es ............................................................................................................................................... C-7
General................................................................................................................................................ C-7
Server Mode..................................................................................................................................... C-11
Security ............................................................................................................................................. C-16
D Supported SQL Syntax and SQL Enhancements
Supported SQL Statements ................................................................................................................... D-1
Supported Operators .............................................................................................................................. D-1
Supported Functions............................................................................................................................... D-2
SQL Enhancements................................................................................................................................. D-3
Generating Hierarchical Results ..................................................................................................... D-3
Accessing Hierarchical Data Using SQL........................................................................................ D-4
viii
Flattening Hierarchical Data Using SQL ....................................................................................... D-4
Using an Alias ............................................................................................................................ D-4
E Globalization Settings
Defining the Language and Codepage................................................................................................ E-1
Index
ix
x
Audience
Preface
This guide is the primary source of user and reference information on OracleAS
Adapters for IMS/DB, which enables client applications to access transactions running
under IMS/DB through the Sun J2EE Connector Architecture (J2CA) API.
This document describes the features of OracleAS Adapters for IMS/DB.
This preface covers the following topics:
■ Audience
■ Documentation Accessibility
■ Related Documents
■ Conventions
This manual is intended for Oracle integration administrators who perform the
following tasks:
■ Installing and configuring OracleAS Adapters for IMS/DB
■ Diagnosing errors
■ Using OracleAS to access IMS/DB transactions
Note: You should understand the fundamentals of OracleAS,
OC4J, the UNIX and Microsoft Windows operating system before
using this guide to install or administer OracleAS Adapters for
IMS/DB.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible to all users, including users that are disabled. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at http://www.oracle.com/accessibility/.
xi
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an
otherwise empty line; however, some screen readers may not always read a line of text
that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or
organizations that Oracle does not own or control. Oracle neither evaluates nor makes
any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer
Assistant will relay information between the customer and Oracle Support Services at
1.800.223.1711. Complete instructions for using the AT&T relay services are available at
http://www.consumer.att.com/relay/tty/standard2.html. After the
AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support
Services engineer will handle technical issues and provide customer support according
to the Oracle service request process.
Related Documents
For more information, see the following documents in the Oracle Other Product One
Release 7.0 documentation set or in the Oracle Other Product Two Release 6.1
documentation set:
Conventions
■ Oracle Application Server Adapter Concepts Guide
■ Oracle Application Server Adapter Installation Guide
■ Oracle Application Server Adapter Concepts Guide
■ Oracle Application Server Containers for J2EE User’s Guide
■ Oracle Application Server Containers for J2EE Services Guide
■ Oracle Application Server Containers for J2EE Security Guide
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
xii
Oracle Application Server Adapter for IMS/DB (OracleAS Adapter for IMS/DB)
provides connectivity and runs interactions on an Information Management System Data Base (IMS/DB) system. This section provides an overview of the features and
architecture of OracleAS Adapter for IMS/DB.
This section contains the following topics:
■ OracleAS Adapter for IMS/DB Overview
■ OracleAS Adapter for IMS/DB Architecture
OracleAS Adapter for IMS/DB Overview
IMS/DB (Information Management System - Data Base) is a high-performance
hierarchical database. The data access API to IMS/DB is called DL/I, which is a
function by which the IMS/DB database can be traversed and operated on. Working
with DL/I requires the caller to run under the control of IMS/DB. APIs are also
available to enable access to IMS/DB from CICS and IMS/TM transactions.
1
Introduction
OracleAS Adapter for IMS/DB includes the following feature:
■ Captures and maintains a metadata schema for IMS/DB by importing various IMS
definition files such as a PSB file, DBD files, and COBOL copybooks. These are
transformed into mapping definition for Oracle Connect for IMS/DB on the z/OS
computer.
■ Uses an enterprise application integration (EAI) model. Users of a requesting
application can model the interactions that they want implemented, specifying
what each interaction does, when it occurs, and the inputs and outputs expected
for each interaction. Moreover, the OracleAS Adapter for IMS/DB maps data
structures, facilitating access to IMS/DB data from within Oracle Application
Server.
■ Implements interactions as parameterized SQL with the parameters forming the
input record, and with the output (in cases where there is an output) aggregated
into an XML document forming the output record.
■ Includes the options to access IMS/DB data managed by CICS, IMS/TM, or
directly.
■ Does support global transactions under CICS and can fully participate in a
distributed transaction.
Introduction 1-1
OracleAS Adapter for IMS/DB Architecture
OracleAS Adapter for IMS/DB Architecture
OracleAS Adapter for IMS/DB includes the following components:
■ J2CA 1.5 IMS/DB adapter: The J2CA IMS/DB adapter is a standard resource
adapter that is compliant with J2EE Connector Architecture, therefore, providing
J2EE components connectivity.
■ Oracle Connect: Oracle Connect runs on the legacy system and handles requests
from the J2CA 1.5 IMS/DB adapter, that runs within Oracle Application Server
Containers for J2EE (OC4J).
■ Oracle Studio: Oracle Studio is the configuration tool for Oracle Connect.
Configuration tasks using Oracle Studio are performed on a Windows or Linux
compuer. Oracle Studio uses perspectives that enables you to generate specific
information necessary to model OracleAS Adapter for IMS/DB.
The following figure illustrates the components of OracleAS Adapter for IMS/DB.
See Also: Oracle Application Server Adapter Concepts Guide
Integration Flow from Oracle Application Server to the Legacy Application
The J2CA 1.5 IMS/DB adapter converts the J2CA interaction invocation received from
Oracle Application Server to the XML format and passes the XML format to Oracle
Connect on the legacy server. The daemon listens for the request coming from the
J2CA 1.5 IMS/DB adapter client and assigns a server process to handle the request.
The properties of the server process, such as connection pooling requirements, are
defined by a workspace definition within the daemon.
The server process includes an instance of the application engine, which converts the
XML format into standard SQL which is passed to the data engine. The data engine
processes the SQL to create an efficient strategy for retrieving the data from IMS/DB
and then passes the SQL and execution strategy to the database back-end adapter. The
database back-end adapter passes the SQL to the back-end driver, which converts the
SQL to the language understood by IMS/DB and passes it to IMS/DB to be executed.
The results of the SQL statement are passed back to the application engine, through
the back-end adapter, where these results are converted to XML and passed back to the
client.
1-2 Oracle Application Server Adapters for IMS/DB User's Guide
2
Installing and Configuring the OracleAS
Adapter for IMS/DB
This section describes how to install Oracle Connect and Oracle Studio, and how to
configure Oracle Connect using Oracle Studio.
Note: In addition to the installation procedures described in this
section, the J2CA 1.5 IMS/DB adapter must be installed with Oracle
Application Server. Installing the J2CA 1.5 IMS/DB adapter is
described in Oracle Application Server Adapter Installation Guide.
This section includes the following topics:
■ Preinstallation Tasks
■ Installing Oracle Connect on an IBM z/OS Series Platform
■ Updating an Existing Oracle Connect Installation with IMS/DB
■ Installing Oracle Studio
■ Configuring Oracle Connect
Preinstallation Tasks
Before installing OracleAS Adapter for IMS/DB, ensure that your computer meets the
following requirements:
■ IBM z/OS Hardware and Software Requirements
IBM z/OS Hardware and Software Requirements
This section describes the following requirements for installing Oracle Connect on an
IBM z/OS platform:
■ Hardware Requirements
■ Software Requirements
Hardware Requirements
The following table summarizes the hardware requirements for Oracle Connect.
Installing and Configuring the OracleAS Adapter for IMS/DB 2-1
Installing Oracle Connect on an IBM z/OS Series Platform
Table 2–1 Oracle Connect Hardware Requirements
Hardware Component Requirements
Processor An IBM zSeries computer.
Memory The minimum requirement is 4MBfor each connection. A
connection is defined as a connection to a server process or
daemon. The actual memory requirement depends on such
things as the size of the database and the number of databases
accessed.
Disk Space (3380 and
150 cylinders.
3390 disks)
Software Requirements
The following table summarizes the software requirements for Oracle Connect:
Table 2–2 Oracle Connect Software Requirements
Software Component Requirements
Operating System IBM z/OS
CICS TP Monitor (if
accessing IMS/DB data
under CICS)
TCP/IP The operating system must support the TCP/IP protocol for
C Runtime Library The C runtime library has all the standard C runtime programs.
Oracle Application
Server
V4R1 or higher (recommended to use CICS V6R1 or higher)
CICS EXCI support must be installed and IRCSTRT=YES must
be specified in the CICS initialization parameters, so that the IRC
(Inter Region Communication) starts.
You can also set the IRC to open by issuing the following
command: CEMT SET IRC OPEN. Also the IBM group
DFH$EXCI (or an equivalent user-defined group) must be
installed in the CICS region: using the CEDA RDO facility.
using the Internet
Oracle Application Server 10g (10.1.3.4).
Installing Oracle Connect on an IBM z/OS Series Platform
This section explains how to install Oracle Connect. This section includes the
following:
■ Installation Worksheet
■ Preinstallation Tasks
■ Importing the Installation Kit
■ Installation Instructions
■ Post-Installation Instructions
2-2 Oracle Application Server Adapters for IMS/DB User's Guide
Installing Oracle Connect on an IBM z/OS Series Platform
Note: If you have an Oracle Connect back-end adapter already
installed on the IBM z/OS platform, follow the instructions
described in "Updating an Existing Oracle Connect Installation
with IMS/DB" on page 2-11.
The other back-end adapters that run on an IBM z/OS platform
include:
■ OracleAS Adapter for CICS
■ OracleAS Adapter for IMS/TM
■ OracleAS Adapter for VSAM
Installation Worksheet
Verify that you have all the information detailed in the following installation
worksheets, so you can refer to it during the configuration process.
Table 2–3 Preinstallation Information
Topic Required Information Default Comment
General Operating system - z/OS
- Disk space - 150 cylinders.
- Memory - The minimum requirement is 4MBfor each
connection. A connection is defined as a
connection to a server process or daemon.
The actual memory requirement depends on
such things as the size of the database and
the number of databases accessed.
- Installation high-level
qualifier
-Volume - -
- Unit 3390 SMS only: unit where SMS resides.
OCL10134 -
- Output class A -
- JCL job card - An optional card (up to 6 lines) to replace
the prefix job (entered as it will appear in
the job).
- ISPF load library name ISP.SISPLOAD -
CICS CICS EXCI load library name CICS.CICS.SDFHEXCI To access IMS/DB data under CICS.
Table 2–4 Required Permissions
Permission
Permission to define an APF-authorized library
Permission to write to an active proclib, such as user.proclib
Permission to read the CICS EXCI library (when accessing IMS/DB data under CICS)
Permission to update the security manager, such as RACF
Optionally, permission to specify an output class for Oracle Connect output
Installing and Configuring the OracleAS Adapter for IMS/DB 2-3
Installing Oracle Connect on an IBM z/OS Series Platform
Table 2–5 Installation Checklist
Step Comment/Outputs
tso profile noprefix Ensures that the user name is not used as part of
the dataset name allocated in the next steps.
Allocate dataset: {HLQ}.TRANSMIT.KIT 130 tracks (3390), format=FB, record length=80,
block size=3120
Allocate dataset: {HLQ}.TRANSMIT.LOAD 500 tracks (3390), format=FB, record length=80,
block size=3120
FTP files to z/OS FTP using binary mode.
RECEIVE INDSNAME('{HLQ}.TRANSMIT.KIT') -
da('{HLQ}.TRANSMIT.LIB') UNIT(unit) VOLUME(volume) -
EX {HLQ}.TRANSMIT.LIB(PREPARE) Successful MAXCC is 0, 4 or 8
BUILDKIT.SRC, BUILDKIT.LOAD and
BUILDKIT.GENDEMO created.
EX {HLQ}.BUILDKIT.SRC(NAVINST) Successful MAXCC is 0 or 4.
Preinstallation Tasks
Before starting the installation, ensure that you have the following information
available:
■ The output class for the installation output if you do not want to use the default
value, which is A
■ If you use SMS to manage all datasets (you cannot provide unit and volume
information), then the unit where SMS resides.
Before starting the installation, ensure that you have the following permissions:
■ Permission to define an APF-authorized library.
■ Permission to write to an active proclib, such as user.proclib.
■ Permission to read the CICS EXCI library, when accessing IMS/DB data under
CICS.
■ Permission to update the security manager, such as RACF.
Note: Optionally, ensure that you have permission to specify an
output class for Oracle Connect output. Assigning a device which is
set on HOLD prevents the loss of log information when Oracle
Connect started tasks finish.
Oracle Connect for the IBM z/OS platform is contained in the following datasets:
■ OCL10134.TRANSMIT.KIT
■ OCL10134.TRANSMIT.LOAD
These datasets are provided in the following directory.
Oracle_Connect\IMSDB_Legacy_Adapter
2-4 Oracle Application Server Adapters for IMS/DB User's Guide
Importing the Installation Kit
Perform the following steps on the mainframe to import Oracle Connect installation
kit to the mainframe:
1. Run the following command:
tso profile noprefix
The user name will not be used as part of the dataset name. On some systems this
is the default.
2. Allocate datasets with the following space for each of these files:
■ OCL10134.TRANSMIT.KIT = 130 tracks (3380 and 3390 disks)
■ OCL10134.TRANSMIT.LOAD = 500 tracks (3380 and 3390 disks)
For each dataset: RECFM=FB and LRECL=80. The block size is 3120.
3. Using FTP, copy OCL10134.TRANSMIT.KIT and OCL10134.TRANSMIT.LOAD in
binary mode to the mainframe. You can replace the OCL10134 high-level qualifier
to any qualifier you want.
Installation Instructions
Perform the following steps to install Oracle Connect:
Installing Oracle Connect on an IBM z/OS Series Platform
1. Run the following command at the TSO prompt:
RECEIVE INDSNAME('nnn.TRANSMIT.KIT')
Where nnn represents the high-level qualifier you want to assign for the Oracle
Connect installation. Assign the high-level qualifier you specified in step 7 of the
preinstallation tasks. The default value is OCL10134.
Note: You can use more than one high-level qualifier (such as
ACME.DEV.OCL10134) with the following conditions:
■ The total length must be less than or equal to twenty characters.
■ The words transmit and buildkit cannot be used as high-level
qualifiers.
2. Enter the following command when prompted for the restore parameters:
da('nnn.TRANSMIT.LIB') [UNIT(unit) VOLUME(volume)]
This extracts the nnn.TRANSMIT.LIB library from the nnn.TRANSMIT.KIT kit
to the specified unit and volume. If a unit and volume are not specified the library
is extracted to the current unit and volume.
3. Execute the PREPARE member of the nn.TRANSMIT.LIB library:
ex PREPARE
Follow the instructions in the Response column in Tab le 2– 6 for each entry in the
Screen column.
Installing and Configuring the OracleAS Adapter for IMS/DB 2-5
Installing Oracle Connect on an IBM z/OS Series Platform
Table 2–6 Installation Prepare Job Prompts and Responses
Screen Response
DO YOU WANT TO USE SMS MANAGED
STORAGE FOR THIS INSTALLATION Y/N [N] :
ENTER THE STORCLASS FOR INSTALLATION
TEMP DATASETS [ ] :
ENTER THE UNIT NAME FOR INSTALLATION
TEMP DATASETS [3390] :
ENTER THE VOLUME NAME FOR
INSTALLATION TEMP DATASETS :
If you want to manage the storage using SMS, then answer
Y, otherwise answer N.
This prompt is displayed only if SMS is used to manage the
installation (you answered Y to the first prompt).
Enter the storage class.
If a storage class is not specified, then enter the unit name
for temporary datasets used during the installation
procedure.
This prompt is displayed only if SMS is not used to manage
the installation (you answered N to the first prompt).
The volume name for temporary datasets used during the
installation procedure.
ENTER THE OUTPUT CLASS FOR
INSTALLATION OUTPUT [A] :
DO YOU WANT TO USE THE DEFAULT JOB
CARD Y/N [Y]
DO YOU WANT TO PERFORM A MANUAL
(M) OR AUTOMATIC (A) INSTALLATION [A] :
PLEASE REVIEW AND SUBMIT FOR
EXECUTION THE
HLQ.TRANSMIT.LIB(INSTJO)
The following libraries are generated:
nnn.BUILDKIT.LOAD
nnn.BUILDKIT.SRC
nnn.BUILDKIT.GENDEMO
Where nnn is the high-level qualifiers you assigned in step 1.
4. In the nnn.BUILDKIT.SRC library, execute the NAVINST member:
ex NAVINST
Enter the output class only if you do not want the default
class used (the default is A)
A job card is displayed. If you want to use a replacement
card, then it must be entered as it will appear in the job. You
can enter up to six lines. Enter a blank card to end input.
If you do not enter a card, then the Oracle Connect default
card is used.
If you want to review the JCL used to install Oracle Connect,
before it is submitted, then respond M for a manual
installation.
This prompt is displayed only if a manual installation is
requested (you answered M to the previous prompt).
Follow the instructions in the Response column in the following table for each
entry in the Screen column.
2-6 Oracle Application Server Adapters for IMS/DB User's Guide
Table 2–7 Installation Prompts and Responses
Screen Response
DO YOU WANT TO USE SMS MANAGED
STORAGE FOR THIS INSTALLATION Y/N [N] :
THE SOFTWARE WILL BE INSTALLED UNDER
THE HIGH LEVEL QUALIFIER THAT YOU
WILL CHOOSE.
ENTER THE HIGH LEVEL QUALIFIER
["QUALIFIER"] :
ENTER THE STORCLASS FOR TEMP DATASETS
['STORCLASS'] :
ENTER THE UNIT NAME FOR INSTALLATION
TEMP DATASETS [3390] :
ENTER THE VOLUME NAME FOR
INSTALLATION TEMP DATASETS :
If you want to manage the storage using SMS, then answer
Y, otherwise answer N.
The high-level qualifier for the installation (referred to as
INSTROOT throughout this guide).
You can use more than one high-level qualifier (such as
ACME.DEV.VA10). The total length must be less than or
equal to twenty characters. The qualifiers can be the same
as the ones used for the installation (step 1).
The words transmit and buildkit cannot be used as
high-level qualifiers.
This prompt is displayed only if SMS is used to manage the
installation (you answered Y to the first prompt).
Enter the storage class.
The unit name for temporary datasets used during the
installation procedure.
This prompt is displayed only if SMS is not used to manage
the installation (you answered N to the first prompt).
The volume name for temporary datasets used during the
installation procedure.
Installing Oracle Connect on an IBM z/OS Series Platform
PLEASE CONFIRM (YES/NO/QUIT) [YES] : Confirm the entered details.
ENTER THE OUTPUT CLASS FOR
INSTALLATION OUTPUT [A] :
DO YOU WANT TO USE THE DEFAULT JOB
CARD Y/N [Y]
ADDING AND UPDATING ORACLE
CONNECT FOR IMS/DB CONFIGURATION ON
THIS MACHINE, FROM A REMOTE ORACLE
ADMINISTRATION CONSOLE, CAN ONLY BE
DONE BY SOMEONE DEFINED AS AN
ADMINISTRATOR FOR ORACLE CONNECT
ON THIS MACHINE.
ENTER A VALID USER NAME FOR AN
ORACLE CONNECT ADMINISTRATOR [ALL]:
DO YOU WANT TO PERFORM A MANUAL (M)
OR AUTOMATIC (A) INSTALLATION [A]:
PLEASE REVIEW AND SUBMIT FOR
EXECUTION THE DSN1 (INSTJBOR)
Enter the output class for Oracle Connect output. Assigning
a device which is set on HOLD prevents the loss of log
information when the Oracle Connect started tasks finish
(the default is A).
A job card is displayed. If you want to use a replacement
card, then it must be entered as it will appear in the job. You
can enter up to six lines. Enter a blank card to end input.
If you do not enter a card, then the Oracle Connect default
card is used.
To manage Oracle Connect on this computer from Oracle
Studio, you need to enter a user account of a user who will
have administrative authorization, or press Enter to enable
any user to administer Oracle Connect on this computer.
The administrative rights can be changed from within
Oracle Studio after the installation.
If you want to review the JCL used to install Oracle
Connect, before it is submitted, then respond M for a
manual installation.
This prompt is displayed only if a manual installation is
requested (you answered M to the previous prompt).
DSN1 is the dataset name where INSTJBOR is located.
5. In the nnn.BUILDKIT.SRC library, execute the IMSDB member:
ex IMSDB
Follow the instructions in the Response column in for each entry in the Screen
column.
Installing and Configuring the OracleAS Adapter for IMS/DB 2-7
Installing Oracle Connect on an IBM z/OS Series Platform
Table 2–8 IMS/DB Adapter Installation Prompts and Responses
Screen Response
ENTER DBD LIBRARY NAME Enter the IMS DBD Library name for IMS on your system
ENTER PSB LIBRARY NAME Enter the IMS PSB Library name for IMS on your system
ENTER RES LIBRARY NAME Enter the IMS RES Library name for IMS on your system
ENTER PROC LIBRARY NAME Enter the IMS PROC Library name for IMS on your system
ENTER PGM LIBRARY NAME Enter the IMS PGM Library name for IMS on your system
ENTER YOUR PSB NAME Enter the name of the PSB file with the name of your IMS
database.
YOUR DBDLIB IS:
YOUR PSBLIB IS:
YOUR RESLIB IS:
YOUR PROCLIB IS:
YOUR PGMCLIB IS:
This is a summary of the IMS questions. Check the summary
to be sure all is correct. You can select:
■ Yes, to use the IMS database as configured
■ No, to not use the IMS database
■ Quit, to leave the CUST process
YOUR PSBNAME IS:
PLEASE CONFIRM (YES/NO/QUIT) :YES: :
DO YOU WANT ORACLE CONNECT TO
WORK WITH IMS/DB UNDER CICS
ENTER THE CICS EXCI LOAD LIBRARY NAME
[CICSTS13.CICS.SDFHEXCI]:
If you want Oracle Connect to work with IMS/DB under
CICS, then answer Y, otherwise answer N.
Enter the CICS EXCI load library name only if you do not
want the default
PLEASE CONFIRM (YES/NO/QUIT) [YES]: Confirm the entered details
The installation is completed. All JCL jobs and REXX procedures are written to the
INSTROOT.USERLIB library. INSTROOT is the high-level qualifier for the installation.
Post-Installation Instructions
The following post-installation tasks must be done to work with Oracle Connect:
■ Post-Installation Procedures
■ Starting the Daemon
■ Setting Up Oracle Connect for Reentrancy
Post-Installation Procedures
Perform the following procedures after completing the installation to configure Oracle
Connect.
■ Allocate a dataset for INSTROOT.DEF.BRANDBIN, using 1 track and with
RECFM=VB and LRECL=256. The block size is 6233.
INSTROOT is the high-level qualifier where Oracle Connect is installed.
Using FTP, copy the BRANDBIN file, in binary mode, from the
Oracle Connect\IMSDB Legacy Adapter directory to the mainframe, to
INSTROOT.DEF.BRANDBIN.
■ Define the LOADAUT library as an APF-authorized library
2-8 Oracle Application Server Adapters for IMS/DB User's Guide
Installing Oracle Connect on an IBM z/OS Series Platform
Note: To define a DSN as APF-authorized, in the SDSF screen
enter the command:
"/setprog apf,add,dsn=INSTROOT.loadaut,volume=vol002"
where vol002 is the volume where you installed Oracle Connect and
INSTROOT is the high-level qualifier where Oracle Connect is
installed.
If the site uses SMS, then when defining APF-authorization in the
SDSF screen, enter the following command:
"/setprog apf,add,dsn=INSTROOT.loadaut,SMS"
Ensure that the library is APF-authorized, even after an IPL (reboot)
of the computer.
■ Move the INSTROOT.USERLIB(ATTDAEMN) and
INSTROOT.USERLIB(ATTSRVR) members to any active proclib, such as
user.proclib, ATTDAEMN and ATTSRVR are run as started tasks.
If you decide to change the name of the ATTSRVR member when you move it to a
general high-level qualifier, then change the name specified in the
StartupScript parameter in the daemon configuration to the new name:
■ Run INSTROOT.USERLIB(NAVCMD) and enter EDIT DAEMON IRPCDINI at
the prompt.
■ Change the startupScript parameter from ATTSRVR to the new name for
the server:
<Workspace name="Navigator"
startupScript="NEW_NAME"
serverMode="reusable"
... />
■ Exit and save the change.
■ Change the following line in the ATTDAEMN script to include the IP address and
port of the IBM z/OS platform.
For example, before:
// PARM='-B START IRPCDINI'
After:
// PARM='-B -L ip_address:2551 START IRPCDINI'
Where ip_address specifies the IP address of the computer, 2551 is the default
port for starting the daemon and IRPCDINI is the default daemon configuration.
■ The ATTDAEMN and ATTSRVR started tasks need permission to use an Open
Edition TCP/IP stack. The owner must be a user with OMVS segment defined and
OMVS UID= 0000000000.
■ In the security manager, such as RACF, define ATTDAEMN and ATTSRVR with a
started task class and a general profile that enables the following:
■ Permission to issue master console commands.
■ START authority for the ATTSRVR job.
Installing and Configuring the OracleAS Adapter for IMS/DB 2-9
Installing Oracle Connect on an IBM z/OS Series Platform
■ Access to an Open z/OS segment (that defines access to TCP/IP OA sockets).
■ ALTER authority on datasets under INSTROOT (to access to read, write,
allocate and delete datasets under INSTROOT).
■ The installation includes a PS, INSTROOT.DEF.GBLPARMS, that contains global
environment information. This PS is read at startup and the correct software
version is used, based on the details provided in the startup task.
If you change the location of this member, you must also change the relevant cards
in the following jobs to the new locations:
■ ATTSRVR: located in an active proclib, such as user.proclib
■ ATTDAEMN: located in an active proclib, such as user.proclib
■ NAVSQL: located in INSTROOT.USERLIB
■ The input during the installation procedure is written to
nnn.BUILDKIT.SRC(PARS). You can use this file to provide the same inputs if
you rerun the installation, where nnn is the high-level qualifier you assign for the
installation.
■ For information about specifying Oracle Connect as the service using port 2551 in
the TCP/IP network services file, consult TCP/IP documentation.
Starting the Daemon
Activate INSTROOT.USERLIB(ATTDAEMN) as a started task to invoke the daemon.
For example, in the SDSF screen enter the following:
'/s ATTDAEMN'
Where INSTROOT is the high-level qualifier where Oracle Connect is installed.
To submit the daemon as a job, uncomment the first two lines of the ATTDAEMN JCL,
change the PARM line as described earlier, and run the job using the subcommand.
The ATTDAEMN JCL is similar to the following:
//*ATTDAEMN JOB 'RR','TTT',MSGLEVEL=(1,1),CLASS=A,
//* MSGCLASS=A,NOTIFY=&SYSUID,REGION=8M
//STEP1 EXEC PGM=IRPCD,
// PARM='-B START IRPCDINI'
//* PARM='-B -L :8883 START'
//STEPLIB DD DSN=INSTROOT.LOADAUT,DISP=SHR
//SYSPRINT DD SYSOUT=A
//GBLPARMS DD DSN=INSTROOT.DEF.GBLPARMS,DISP=SHR
// EXEC PGM=IRPCD,COND=((1,EQ,STEP1),(2,EQ,STEP1)),
// PARM='-KATTDAEMN START ''INSTROOT.DEF.IRPCDINI'''
//STEPLIB DD DSN=INSTROOT.LOADAUT,DISP=SHR
//SYSPRINT DD SYSOUT=A
//GBLPARMS DD DSN=INSTROOT.DEF.GBLPARMS,DISP=SHR
//SYSDUMP DD DUMMY
Setting Up Oracle Connect for Reentrancy
All Oracle Connect load modules are reentrant to enable sub-tasking. Therefore, move
INSTROOT.LOAD to the Link Pack Area (LPA).
Where INSTROOT is the high-level qualifier where Oracle Connect is installed.
Using the LPA reduces real storage usage (because everyone shares the LPA copy) and
fetch time.
2-10 Oracle Application Server Adapters for IMS/DB User's Guide
Updating an Existing Oracle Connect Installation with IMS/DB
Note: If you intend on using impersonation, so that you can run
in a security context that is different than the context of the process
that owns the server, then do the following:
■ Place the INSTROOT.LOAD(ATYSVCW) member in an
APF-authorized library outside the LPA.
■ Change the ATTSRVR member (located in the active proclib), by
adding the following to the STEPLIB list:
// DD DSN=apf_library,DISP=SHR
Where apf_library is the APF-authorized library outside the
LPA where the ATYSCVW member was moved.
Setting Up Oracle Connect to Update IMS/DB Data
Perform the following to set up Oracle Connect so that you can update IMS/DB data.
IMS/DB Running Under CICS To set up Oracle Connect so that you can update IMS/DB
data from a CICS transaction, copy the ATYDBCTL load module from INSTROOT.LOAD
to a CICS DFHRPL library (such as CICS.USER.LOAD) and then define the ATYDBCTL
program under CICS using any available group such as ORA group:
CEDA DEF PROG(ATYDBCTL) G(ORA) LANG(C) DA(ANY) DE(ORACLE IMSDB UPDATE PROG)
Where INSTROOT is the high-level qualifier where Oracle Connect is installed.
After defining the ATYDBCTL program to a group, install it as follows:
CEDA IN G(ORA)
IMS/DB Not Running Under CICS To enable Oracle Connect to create and delete IMS/DB
data, run the following JCL:
// IDCSYSIN DD DSN=&&IMSDB,DISP=(NEW,DELETE,DELETE),
// SPACE=(TRK,(1)),UNIT=SYSDA,
// DCB=(BLKSIZE=3200,LRECL=80,RECFM=FB)
Updating an Existing Oracle Connect Installation with IMS/DB
Verify that you have all the information detailed in the following installation
worksheets, so you can refer to it during the configuration process.
Table 2–9 Preinstallation Information
Topic Required Information Default Comment
CICS CICS EXCI load library name CICS.CICS.SDFHEXCI -
Table 2–10 Required Permissions
Permission
Permission to read the CICS EXCI library
In the nnn.BUILDKIT.SRC library, execute the IMSDB member:
ex IMSDB
Installing and Configuring the OracleAS Adapter for IMS/DB 2-11
Installing Oracle Studio
Follow the instructions in the Response column in for each entry in the Screen column.
Table 2–11 IMS/DB Adapter Installation Prompts and Responses
Screen Response
ENTER DBD LIBRARY NAME Enter the IMS DBD Library name for IMS on your system
ENTER PSB LIBRARY NAME Enter the IMS PSB Library name for IMS on your system
ENTER RES LIBRARY NAME Enter the IMS RES Library name for IMS on your system
ENTER PROC LIBRARY NAME Enter the IMS PROC Library name for IMS on your system
ENTER PGM LIBRARY NAME Enter the IMS PGM Library name for IMS on your system
ENTER YOUR PSB NAME Enter the name of the PSB file with the name of your IMS
database.
YOUR DBDLIB IS:
YOUR PSBLIB IS:
YOUR RESLIB IS:
YOUR PROCLIB IS:
YOUR PGMLIB IS:
YOUR PSBNAME IS:
PLEASE CONFIRM (YES/NO/QUIT) :YES: :
This is a summary of the IMS questions. Check the summary
to be sure all is correct. You can select:
■ Yes, to use the IMS database as configured
■ No, to not use the IMS database
■ Quit, to leave the CUST process
DO YOU WANT ORACLE CONNECT TO
WORK WITH IMS/DB UNDER CICS
ENTER THE CICS EXCI LOAD LIBRARY NAME
[CICSTS13.CICS.SDFHEXCI]:
If you want Oracle Connect to work with IMS/DB under
CICS, then answer Y, otherwise answer N.
Enter the CICS EXCI load library name only if you do not
want the default
PLEASE CONFIRM (YES/NO/QUIT) [YES]: Confirm the entered details
The installation is completed. All JCL jobs and REXX procedures are written to the
INSTROOT.USERLIB library. INSTROOT is the high-level qualifier for the installation.
After completing the installation, perform post-installation tasks, as described in
"Post-Installation Instructions" on page 2-8, as required.
Installing Oracle Studio
This following sections explain how to install Oracle Studio.
■ Oracle Studio Requirements
■ Installing Oracle Studio on Windows
■ Installing Oracle Studio on Linux
Note: If you have Oracle Studio version 10.1.3.4 or higher
installed on your computer because you are using an Oracle AS
legacy adapter or OracleAS CDC adapter , you do not need to
reinstall it. If you have an older version of Oracle Studio, you must
install the newest version.
Oracle Studio Requirements
The following are the hardware requirements for Oracle Studio:
■ Processor: Intel or 100% compatible computer, based on a Pentium processor.
2-12 Oracle Application Server Adapters for IMS/DB User's Guide
■ Memory: 256 MB
■ Disk space: 120 MB of free disk space
You can install Oracle Studio on the following operating systems:
■ Windows XP with Service Pack 2 or higher
Windows 2003
Windows Vista
■ Linux OS with GTK
Installing Oracle Studio on Windows
Oracle Studio is installed with a standard install wizard. Do the following to install
Oracle Studio.
■ Run the installation file, either using the Run option in the Windows Start menu or
through Windows Explorer. Follow the instructions on the wizard screen.
Installing Oracle Studio on Linux
The Oracle Studio installation on Linux can be caried out by one of the following:
Configuring Oracle Connect
■ Installing Oracle Studio with the Wizard (SH installation)
■ Installing with a Silent Installation (RPM)
Installing Oracle Studio with the Wizard (SH installation)
You can install Oracle Studio by using the installation wizard. This allows you to
easily carry out any standard or custom installation. Do the following for the Linux SH
installation.
1. Install into a directory where you have permission.
2. Change the mode to execute mode. Type in:
Chmod +x <file name>
3. Enter the following:
./ <file name>
If you are not installing to the current directory, enter the full path.
Installing with a Silent Installation (RPM)
You can use the Linux RPM method to install Oracle Studio. Do the following to carry
out a silent installation on Linux.
■ Enter the following:
rpm -i <file name>
You can use RPM parameters to create a custom inslallation.
Configuring Oracle Connect
All modeling of Oracle Connect is performed using Oracle Studio. To use Oracle
Studio, you first configure it to enable access to the IBM z/OS platform where the
IMS/DB data resides.
To configure Oracle Connect, refer to the following sections:
■ Setting Up the IBM z/OS Platform in Oracle Studio
Installing and Configuring the OracleAS Adapter for IMS/DB 2-13
Configuring Oracle Connect
■ Securing Access to Oracle Connect
■ Modeling Interactions for OracleAS Adapter for IMS/DB
Note: The following tasks assume you have permission to access
the IBM z/OS platform and that the Oracle Connect daemon is
running on this computer.
Check with the system administrator to ensure these requirements
are fulfilled.
Setting Up the IBM z/OS Platform in Oracle Studio
Using Oracle Studio, perform the following steps to configure the IBM z/OS platform:
1. From the Start menu, select Programs, Oracle, and then select Studio. Oracle
Studio opens, displaying the Design perspective.
2. Right-click Machines in the Configuration Explorer and select Add Machine. The
Add Machine screen is displayed (see Figure 2–1).
3. Enter the name of the computer you want to connect to, or click Browse to select
the computer from the list of computers that is displayed and which use the
default port (2551).
4. Specify the username and password of the user who was specified as the
administrator when Oracle Connect was installed.
Note: Selecting Anonymous connection enables anyone having
access to the computer to be an administrator, if this was defined
for the computer.
The Add Machine screen is shown in the following figure:
Figure 2–1 The Add Machine screen
Click Finish.
5.
2-14 Oracle Application Server Adapters for IMS/DB User's Guide
The computer is displayed in the Configuration Explorer.
Securing Access to Oracle Connect
Oracle Studio includes mechanisms to secure access to Oracle Connect both during
modeling and at run time.
During modeling, the following security mechanisms can be applied:
■ Setting Password Access to Oracle Studio
■ Specifying Users with Administrative Rights
At run time client access to Oracle Connect is provided by the user profile:
■ Setting Up Run-Time User Access to the IBM z/OS Platform
Setting Password Access to Oracle Studio
Initially, any operation performed using Oracle Studio does not require a password.
You can set a password so that the first operation that involves accessing the server
from Oracle Studio requires a password to be entered.
Perform the following steps to set password access to Oracle Studio:
1. From the Start menu, select, Programs, Oracle, and then select Studio. Oracle
Studio opens.
Configuring Oracle Connect
2. From the Window menu, select Preferences. The Preferences screen is displayed.
3. Select Studio as shown in the following figure:
Figure 2–2 The Preferences screen
4.
Click Change Studio Master Password. The Change Master Password screen is
displayed, as shown in the following figure:
Installing and Configuring the OracleAS Adapter for IMS/DB 2-15
Configuring Oracle Connect
Figure 2–3 The Change Master Password Screen
5.
6. Confirm the password.
7. Click OK.
Specifying Users with Administrative Rights
By default, only the user who was specified during the installation as an administrator
has the authorization to modify settings on that computer from Oracle Studio. This
user can then authorize other users to make changes or to view the definitions for a
selected computer. Adding a computer to Oracle Studio is described in "Setting Up the
IBM z/OS Platform in Oracle Studio" on page 2-14.
Leave the Enter Current Master Password field blank and type a new master
password.
Note: The default during installation is to enable all users to be
administrators.
1. From the Start menu, select, Programs, Oracle, and then select Studio. Oracle
Studio opens.
2. In the Design perspective Configuration view, Right-click the computer and select
Administration Authorization.
The Administration Authorization screen is displayed as shown in the following
figure:
2-16 Oracle Application Server Adapters for IMS/DB User's Guide
Loading...