Index

A B C D E F G H I J K L M N O P Q R S T U V W

Symbols

16, valid AS/400 "Client trace level", 6.3

*ADMIN, valid AS/400 "Client trace level", 6.3

*ARDPGM

relational database directory entry in ADDRDBDIRE Panel 1, 5.4.2

remote location entry in configuration example, 5.3.3

*BATCH, example "Batch/Terminal Compile" on Oracle SQL Package Panel, 6.5

*C, example "Language Type" on Oracle SQL Package Panel, 6.5

*CALLER, used in ACTGRP(*CALLER), for invoking Access Manager program, 1.6

*COBOL, example "Language Type" on Oracle SQL Package Panel, 6.5

*CURRENT, example "Target Release" on Oracle SQL Package Panel, 6.5

*DUW with ROBCNNMTH parameter, known restriction, 2.3.2.2

*FIRST

adding Access Manager library to library list, 6.1

with Access Manager installation library, 4.3.2

*FLOAT

known problem with data type, 2.3.1.1

specifies floating point notation using default precision and scale values, 6.2

*KEEP, setting Commitment-Control Resource Release, example, 6.2

*New, example "Activation Group" on Oracle SQL Package Panel, 6.5

*OFF, valid AS/400 "Client trace level", 6.3

*PGM, example "Object Type" on Oracle SQL Package Panel, 6.5

*PKDEC

known problem with data type, 2.3.1.1

specifies packed decimal notation using default precision and scale values, 6.2

*RELEASE, setting Commitment-Control Resource Release, example, 6.2

*RPG, example "Language Type" on Oracle SQL Package Panel, 6.5

*SECADM special authority, logging on before installing Oracle Access Manager, 4.2

*USER, valid AS/400 "Client trace level", 6.3

A

Access Manager

see Oracle Access Manager

Access Manager Commands Menu panel, 6.1

Access Manager Debugging Options Panel

Panel (1), 6.4

Panel (2), 6.4

Access Manager Default Options Panel

library, 6.2

user ID and password, 6.2

Access Manager Network Parameters Panel

Panel (1), 6.3

Panel (2), 6.3

activation groups

main topic, description, 1.6

ACTGRP(*CALLER) creates Access Manager, 1.6

commands

CRTSQLxxx, 1.6

STRSQL, 1.6

ADD command, adds a server to the list of available servers, 7.7.1

ADDLIBLE command, add Access Manager library to library list

configuration, 6.1

installation, 4.3.2

ADDRDBDIRE command

adding an entry in RDB directory, 5.4.3

defining IBM DRDA connection, 5.2

ADDRDBDIRE Panel_1, 5.4.2

ADDRDBDIRE Panel_2, 5.4.2

addressing protection, provided by an activation group, 1.6

AM400_COM program

defined, 7.1.1

commands

main topic, 7.7.1

ADD, 7.7.1

FORCE, 7.7.1

LIST, 7.7.1

MODIFY, 7.7.1

QUERY, 7.7.1

REMOVE, 7.7.1

SET, 7.7.1

SHUTDOWN, 7.7.1

STARTUP, 7.7.1

STATUS, 7.7.1

privileged ID field, 7.5.4

privileged user IDs, 7.5.4

with LIST command, 7.7.1

AM400_RID program

defined, 7.1.1

altering the environment, 7.7

starting the program, 7.5.5

startup parameter, 7.5.3

with DATAQUEUE_TIMEOUT parameter, 7.5.3

with LIST command, 7.7.1

with resolve-in-doubt transactions, 7.4.1

with two-phase commit, 7.3.1

Application Requester Driver (ARD) interface

data from Oracle server is translated by IBM ARD API, B.2

Oracle Access Manager architecture, 1.2

Oracle Access Manager component interactions, 1.2.1

architecture of Oracle Access Manager

component interactions, 1.2.1

main topic, 1.2

ARD, Application Requester Driver

Access Manager architecture, 1.2

data from Oracle server is translated by IBM ARD API, B.2

ARD, IBM ARD, distributed database environment, 1.5

AS/400 and OS/400, platform names for IBM eServer iSeries servers, Preface

AS/400 application, Access Manager component interactions, 1.2.1

AVG function, precision and scale, 6.2

B

back up any existing Access Manager library before upgrading to a new release, 4.2

blocksize data area, default block size, 6.2

bugs fixed as of this release, 2.2.2

C

CALL command

code example, connecting from an AS/400 precompiled application, 8.1.2

declaring procedures with call to a stored procedure, 8.4.3

stored procedures, results can be committed or rolled back, 8.4

CALL statement

calling a stored procedure by using IBM DB2/400, 8.4

single CALL statement on AS/400 executes entire block of SQL statements, 8.4.1

change

Change or Enter New Server Attributes - panel, 7.5.3

Change Privileged IDs (Relative to AM400_COM) - panel, 7.5.4

Change RID (Resolve In Doubt) Options - panel, 7.5.3

Change RID (Resolve In Doubt) Options Panel, 6.6

changes and enhancements, 2.2

CHAR data type, Oracle data types mapped to DB2/400 data types, 8.5

checklists

enabling two-phase commit, 7.5.1

installation, 4.2.1

Oracle Net, TCP/IP AS/400 configuration, 5.4.1

post-installation, 4.3.1

CHG2PCPRM command

main topic, changing two-phase commit parameters, 6.6

changing AM400_RID Options, 7.5.3

changing RID (Resolve In Doubt) Privileged IDs - panel, 7.5.4

purpose of command, 6.1

CHGSQLDBG command

main topic, opens Access Manager Debugging Options - panel, 6.4

purpose of command, 6.1

CHGSQLDFLT command

changing Access Manager NLS language parameter, B.3

changing Oracle server default user ID and password, when using STRSQL, 8.1.1

changing two-phase commit parameter, 7.1

opening Access Manager Default Options - panel, 6.2

purpose of command, 6.1

CHGSQLNET command

Access Manager commands, 6.1

network parameters panel, 6.3

CHGUSRPRF command

changing default password during installation, 4.2.6

CHKSQLDFLT command, checking STRSQL default data type, precision, and scale values, 2.3.1.1

clause, FOR FETCH ONLY, required for block fetching to be performed, 6.2

CLEANUP_DELAY parameter

AM400_COM program can be used to dynamically alter environment of AM400_RID program, 7.7

AM400_COM QUERY command can query the value of this parameter, 7.7.1

description, a tuning parameter requiring a single numeric value (in seconds), 7.5.3

tuning parameter, Change RID (Resolve In Doubt) Options - panel, 7.5.3

code example

accessing the AM400_COM program, 7.7

adding Access Manager library to your library list

configuring, before using Access Manager commands, 6.1

post installation of Access Manager, 4.3.2

AM400_COM commands, 7.7.1

an extract from an AS/400 C program that calls the Oracle stored procedure GETRESULTS, 8.4.3

changing password after product installation, 4.2.6

completing installation, 4.2.6

connecting to the Oracle server with STRSQL, 8.1.1

declaring procedures when calling an Oracle stored procedure, 8.4.3

editing member TNSNAMES in the ORA file, 5.4.3

instance name of Oracle server, 5.4.3

invalid commands for multiple connections to same RDB name, 8.2

LODRUN command to start installation, 4.2.3

member names, file name mapping, 5.1

message issued if DB2/400 does not recognize a SQLSTATE, 8.6

precision and scale values from SQL statements, 6.2

relationship between Access Manager and AS/400 TCP/IP configuration, 5.3.3

sample Access Manager C program (Appendix A), A.1

sample Access Manager COBOL program (Appendix A), A.2

sample Access Manager RPG program (Appendix A), A.3

SQL0858, protected conversation, 8.2

starting a subsystem to enable two-phase commit processing, 7.5.5

switching between servers using the DB2/400 SET CONNECTION command, 8.2

text format conventions, examples of code input and output, Preface

using CHKSQLDFLT command to check default data type, precision, and scale values, 2.3.1.1

commands

activation groups, CRTSQLxxx, 1.6

ADDLIBLE, before using any Access Manager configuration utilities, 4.3.2

AM400_COM program

main topic, 7.7.1

AM400_COM program, description and code example

ADD, 7.7.1

FORCE, 7.7.1

LIST, 7.7.1

MODIFY, 7.7.1

QUERY, 7.7.1

REMOVE, 7.7.1

SET, 7.7.1

SHUTDOWN, 7.7.1

STARTUP, 7.7.1

STATUS, 7.7.1

CHG2PCPRM

before accessing Change RID Privileged IDs - panel, 7.5.4

changing AM400_RID options, 7.5.3

CHGSQLDFLT, changing two-phase commit parameter, 7.1

CHGUSRPRF

changing default password, 4.2.6

CHKSQLDFLT, known problems, checking default data type precision and scale values, 2.3.1.1

COMMIT

ending a unit of work (SQL commands), 1.5

known restriction, 2.3.2.1

Oracle required privileges, 7.6

prepare phase of two-phase commit transaction, 7.2

when AS/400 receives a prepared to commit message, 7.3.2

COMMIT HOLD, known restriction, 2.3.2.4

CREATE TABLE, job log message, ORA-00901, 8.1.1

CRTORAPKG command, failure due to severity level, 6.5

CRTSQLxxx

calling and running Access Manager, 1.6

known restriction with RDBCNNMTH parameter, 2.3.2.2

DB2/400

CONNECT TO, STRSQL to connect to the Oracle server, 8.1.1

SET CONNECTION, switching between multiple servers, 8.2

DSPJOBLOG, verifying installation, 4.2.6

EDTF, defining TNSNAMES entry, 5.4.3

GO CMDORAAM, displays Access Manager commands menu, 6.1

GRANT, granting privileges to AM400_RID program, 7.6

IBM

CALL, redirecting a procedure with Oracle SQL, 1.3.1

CRTSQL, RDB parameter and connection management, 8.2

LODRUN, starting the installation process, 4.2.3

menu, Access Manager Commands Menu, 6.1

menu, use GO CMDORAAM to display Access Manager commands menu, 6.1

Oracle Access Manager

main topic, 6.1

ADDLIBLE, 6.1

CALL, 8.1.2, 8.4

CHG2PCPRM, 6.6

CHGSQLDBG, 6.4

CHGSQLDFLT, 6.2, 8.1.1, B.3

COMMIT, 6.2

CRTORAPKG, 6.5, 8.1.2, 8.1.2

CRTSQLxxx, 6.2

DESCRIBE TABLE, 8.3

DISCONNECT, 8.2

purposes of commands, 6.1

RELEASE ALL, 8.2

ROLLBACK, 6.2

SELECT, 8.3

RELEASE, connection management, 8.2

ROLLBACK

ending a unit of work, 1.5

if one site is not prepared to commit, 7.3.2

known restriction, 2.3.2.1

Oracle required privileges, 7.6

SQL*Net

ADDRDBDIRE, adding an entry in the RDB directory, 5.4.3

ADDRDBDIRE, defines IBM DRDA connection, 5.2

WRKMBRPDM, editing member TNSNAMES in the ORA file, 5.4.3

STRSBS, enabling two-phase commit processing, 7.5.5

STRSQL, activation groups, 1.6

COMMIT command

commitment control resource, 6.2

ending a unit of work (SQL commands), 1.5

known restriction, 2.3.2.1

Oracle required privileges, 7.6

prepare phase of two-phase commit transaction, 7.2

when AS/400 receives a prepared to commit message, 7.3.2

COMMIT HOLD command, known restriction, 2.3.2.4

commit phase, defined, 7.1.1

commit point site, defined, 7.1.1

COMMIT statement, connection management, 8.2

commitment control resource, 6.2

components, Oracle Access Manager, table of interactions, 1.2.1

configuration parameters, test connectivity before changing any configuration parameters, 4.3.5

configuring

Oracle Access Manager, 6

SQL*Net TCP/IP

configuring your client computers for TCP/IP, 5.4

edit member TNSNAMES in the ORA file, 5.4.3

CONNECT

CONNECT SQL statement, known restriction, 2.3.2.3

CONNECT TO command, IBM DB2/400 command to connect to the Oracle server, 8.1.1

CONNECT TO statement, explicit connection to an Oracle server, 8.2

Oracle CONNECT syntax is not supported by Oracle Access Manager, 8.2

connecting

connect processing with Oracle Access Manager, 1.4

connection management, 8.2

multiple connections with different RDB names, 1.6

multiple connections with same Oracle server, 1.6

test connectivity before changing any configuration parameters, 4.3.5

through Oracle Net, 5.2

through TCP/IP, 5.3.3

to Oracle server from precompiled application, 8.1.2

uniquely identifying a connection, 1.6

conventions, text format for examples of code input and output, Preface

COUNT(*) function, returns NUMBER values with precision and scale set to zero, 6.2

CREATE statement, a DDL statement, if two-phase commit is set to *NO, 6.2

CREATE TABLE command, job log messages, 8.1.1

CRTORAPKG command

caution, ensure that your Oracle server and your network connection are active before running CRTORAPKG, 6.5

displaying the Oracle SQL Package - panel, 6.5

failure due to severity level, 6.5

precompile, compile, and bind sample programs, 8.1.2

purpose of command, 6.1

CRTSQLxxx command

Access Manager default user ID, 6.2

Calling Oracle Access Manager during package creation, 1.4

IBM command for connection management, 8.2

IBM command to pre-process file, 6.5

known restriction with RDBCNNMTH parameter, 2.3.2.2

D

data areas, blocksize, default block size, 6.2

Data Manipulation Language (DML), known restriction with two-phase commit, 2.3.2.3

data types

conversion of Oracle to DB2/400, 8.5

default precision and scale, 2.3.1.1

LONG and LONG RAW, known restriction, 2.3.2.5

Oracle data types mapped to DB2/400 data types, 8.5

TIME, stored procedure limitations, 2.3.1.3

TIMESTAMP, stored procedure limitations, 2.3.1.3

DATAQUEUE_TIMEOUT parameter

AM400_COM program to dynamically alter AM400_RID program, 7.7

description of this tuning parameter, 7.5.3

query the value of, with code example, 7.7.1

tuning parameter caution, 7.5.3

DATE data type, Oracle data types mapped to DB2/400 data types, 8.5

DB2/400

commands

CONNECT TO, 8.1.1

SET CONNECTION, 8.2

CONNECT syntax, Oracle CONNECT syntax not supported, 8.2

conversion of Oracle data types, 8.5

statements, CONNECT TO, 8.2

statements, DECLARE PROCEDURE

example AS/400 C program that calls Oracle stored procedure GETRESULTS, 8.4.3

must be used when calling an Oracle stored procedure, 8.4.3

DEAD_CHECK_COUNTER parameter

description of this tuning parameter, 7.5.3

example query, 7.7.1

tuning parameter caution, 7.5.3

debugging

control string, Debugging Options Panel, 6.4

options

Access Manager Debugging Options Panel (1), 6.4

Access Manager Debugging Options Panel (2), 6.4

DECIMAL data type, Oracle data types mapped to DB2/400 data types, 8.5

DECLARE PROCEDURE statement

DB2/400 statement, stored procedure limitations, 2.3.1.3

example AS/400 C program that calls Oracle stored procedure GETRESULTS, 8.4.3

must be used when calling an Oracle stored procedure, 8.4.3

default

Access Manager

Commands Menu, "Change Oracle Access Manager Default settings" option, 6.1

default blocksize, 6.2

Default Options Panel, 6.2

Default Options Panel, default settings, 6.2

default password, 6.2

default precision, 6.2

default scale, 6.2

default user id, 6.2

NLS language setting, 6.2

activation group, 1.6

auxiliary storage pool ID, Install Access Manager Product Panel, 4.2.4

CD drive for installation, 4.2.3

CHGSQLDFLT, changes Access Manager default settings, 6.1

data types, precision and scale, 2.3.1.1

declaring procedures, CALL to a stored procedure, parameters default to IN OUT, 8.4.3

during installation, Access Manager parameter for two-phase commit processing defaults to *NO, 7.1

enabling two-phase commit, 7.5.2

for NLS_LANG, B.2

installation library name (ORAAM400), 4.2.4

library containing the Access Manager program, 6.2

options in Access Manager Network Parameters Panel, 6.3

position of Access Manager library name, 4.3.2

precision and scale, Access Manager default number format, 6.2

QSECOFR in Privileged ID field, AM400_COM Privileged User IDs, 7.5.4

translating date formats, 1.3.4

user ID and password

with STRSQL commands, 8.1.1

values provided during product installation, 4.2

defining Oracle Access Manager

RDB entry, 5.3.1

TNSNAMES entry, 5.3.2

defining Oracle server to Access Manager, main topic, 5.3

DELETE statement, limitation of Oracle hints, 2.3.1.2

DESCRIBE TABLE command, not issued interactively, 8.3

describing tables, STRSQL restriction, 8.3

description field, changing AM400_RID options, 7.5.3

diagnosing problems, Oracle Access Manager

changing debugging settings, 6.4

if package creation failed, 6.5

DISCONNECT command, protected conversation, 8.2

distributed database environment, 1.5

distributed unit of work, levels of distributed databases, 1.5

documentation, recommended, 3.3

DROP statement, two-phase commit restriction, 6.2

DSPJOBLOG command, verifying installation, 4.2.6

E

EDTF command, defining TNSNAMES entry, 5.4.3

error

error code processing, Oracle Access Manager, 8.6

mapped error code, message and error code processing, 8.6

ORA-0090, invalid CREATE command, 8.1.1

ORA-1017, attempting to CONNECT without user ID, 6.2

ORA-1457, when using STRSQL, 2.3.1.1

ORA-2089, known restriction with two-phase commit, 2.3.2.3

severity level, CRTORAPKG command failure, 6.5

SQL0105, with CRTORAPKG command, 6.5

SQL0969, known restriction with two-phase commit processing, 2.3.2.1

SQL5001, with CRTORAPKG command, 6.5

using SQLCA, message and error code processing, 8.6

eServer, AS/400 and OS/400, platform names for IBM eServer iSeries servers, Preface

examples

illustrations or graphics, see "figures"

Panel illustrations, see panel name or "panels"

samples of code entries, see "code example"

text format conventions, examples of code input and output, Preface

EXEC SQL statement, Oracle hints limitation, 2.3.1.2

F

features

main topic, 1.3

data type conversions, 1.3.4

distributed applications, 1.3.5

leveraging existing applications, 1.3.2

Oracle SQL language, 1.3.1

universal access, 1.3.3

fields

SQLERRMC, message and error code processing, 8.6

SQLSTATE, message and error code processing, 8.6

figures

1-1, "Oracle Transparent Gateway", 1.1

1-2, "Oracle Access Manager", 1.1

1-3, "Oracle Access Manager for AS/400 Architecture", 1.2

5-1, "Native IBM Networking", 5.2

5-2, "Native Oracle Networking", 5.2

5-3, "Oracle Access Manager Networking", 5.2

5-4, "Defining Oracle Access Manager to the Oracle Server", 5.3

files

ORA(TNSNAMES), connecting to an Oracle server, 5.3.2

Oracle Access Manager

QCBLLESRC, installation library that holds sample program file, 8.1.2

QRPGLESRC, installation library that holds sample program file, 8.1.2

QSQLCSRC, installation library that holds sample program file, 8.1.2

FLOAT data type, Oracle data types mapped to DB2/400 data types, 8.5

FOR FETCH ONLY clause, required for block fetching to be performed, 6.2

FORCE option, Oracle required privileges, 7.6

functions

precision and scale

AVG, 6.2

COUNT(*), 6.2

MAX, 6.2

SUM, 6.2

TO_CHAR, IBM precompiler flags any reference to non-IBM functions, 6.5

TO_DATE, IBM precompiler flags any reference to non-IBM functions, 6.5

G

GETRESULTS procedure, example, declaring procedures, 8.4.3

GO CMDORAAM, command to display Access Manager commands menu, 6.1

GRANT command, granting Oracle required privileges, 7.6

H

hardware requirements, 3.1

hints, Oracle hints, general limitations, 2.3.1.2

HOLD parameter, known restriction with EXEC SQL COMMIT HOLD command, 2.3.2.4

host variable, for Oracle hints (known problem), 2.3.1.2

I

IBM

Application Requester Driver (ARD) interface

data from Oracle server is translated by IBM ARD API, B.2

Oracle Access Manager architecture, 1.2

commands

CALL, uses of Oracle SQL language, 1.3.1

CRTSQLxxx, connection management, 8.2

Distributed Relational Databases, 1.5

eServer iSeries servers, platform name, also AS/400 and OS/400, Preface

IBM ARD, distributed database environment, 1.5

identify, uniquely identifying a connection, 1.6

implied commit, defined, 7.1.1

IN OUT parameter, stored procedure parameters, 8.4.2

IN parameter, stored procedure parameters, 8.4.2

in-doubt

automatic processing is controlled by AM400_RID program, 7.7

caution note regarding parameters that govern resolving in-doubt tasks, 7.5.3

changing AM400_RID options, using CHG2PCPRM command, 7.5.3

figure 7-1, "AS/400 In-Doubt Transactions", 7.4.1

FORCE marks jobs, AM400_COM program command, 7.7.1

required privileges for connecting to any Oracle server, 7.6

transactions

main topic, 7.4

resolving, 7.4.1

use of CLEANUP_DELAY parameter, 7.5.3

use of DATAQUEUE_TIMEOUT parameter, 7.5.3

use of DEAD_CHECK_COUNTER parameter, 7.5.3

Install Oracle Access Manager Product - panel, 4.2.4

installation

checklist, 4.2.1

choosing the library, 4.2.4

command to verify successful installation, 4.2.6

default values, 4.2

finishing installation, 4.2.6

installation procedure will not install into a library with existing objects, 4.2.4

logging on to AS/400, 4.2

mounting product CD-ROM, 4.2.2

selecting installation library name, 4.2.4

starting install process, 4.2.3

verifying installation parameters, 4.2.5

INTEGER data type, Oracle data types mapped to DB2/400 data types, 8.5

introduction, Oracle Access Manager, 1

invoking the Oracle Access Manager, 1.6

iSeries, AS/400 and OS/400, platform names for IBM eServer iSeries servers, Preface

J

job log, checking for error messages after installation of Access Manager, 4.2.6

K

known problems and restrictions, main topic, 2.3

L

language

default NLS language setting, 6.2

table of Oracle NLS_LANG values, B.3

types, values

*C, 6.5

*COBOL, 6.5

*RPG, 6.5

library

Oracle Access Manager, adding to library list, 6.1

the installation procedure will not install into a library with existing objects, 4.2.4

LIST command, AM400_COM commands, description and example, 7.7.1

LODRUN command, starting Access Manager installation, 4.2.3

logical boundary

for application cleanup processing, provided by an activation group, 1.6

for message creation, provided by an activation group, 1.6

LONG data type

known restriction, 2.3.2.5

Oracle data types mapped to DB2/400 data types, 8.5

LONG RAW data type

known restriction, 2.3.2.5

Oracle data types mapped to DB2/400 data types, 8.5

M

mapped error code, message and error code processing, 8.6

mapping Oracle data types to DB2/400 data types, 8.5

MAX function, precision and scale of NUMBER values, 6.2

members, name format, mapping file names to members, 5.1

messages, Oracle Access Manager, processing, 8.6

MODIFY command, AM400_COM commands, description and example, 7.7.1

N

network parameters, Access Manager Network Parameters Panel, 6.3

network, requirements, 3.2.2

NLS

default language setting, 6.2

languages, table of Oracle NLS_LANG values, B.3

NUMBER data type, Oracle data types mapped to DB2/400 data types, 8.5

O

operating system requirements, 3.2.1

options

default options in Access Manager Network Parameters Panel, 6.3

FORCE, Oracle required privileges, 7.6

Oracle Access Manager

USER, if not included in CONNECT TO statement, 6.2

USING, if not included in CONNECT TO statement, 6.2

ORA(TNSNAMES) file

connecting to a remote Oracle server, 5.2

defining Access Manager to Oracle server, 5.3.2

ORA-0090 error, invalid CREATE command, 8.1.1

ORA-1017 error, attempting to CONNECT without user ID, 6.2

ORA-1457 error, when using STRSQL, 2.3.1.1

ORA-2089 error, known restriction with two-phase commit, 2.3.2.3

Oracle Access Manager

architecture, 1.2

back up any existing Access Manager library before upgrading to a new release, 4.2

calling, 1.4

checklist

configuring Oracle Net, TCP/IP AS/400, 5.4.1

enabling two-phase commit, 7.5.1

installation, 4.2.1

post-installation, 4.3.1

commands

main topic, 6.1

ADDLIBLE, 6.1

CALL, 8.1.2, 8.4

CHG2PCPRM, 6.6

CHGSQLDBG, 6.4

CHGSQLDFLT, 6.2, 8.1.1, B.3

COMMIT, 6.2

CRTORAPKG, 6.5, 8.1.2

CRTSQLxxx, 6.2

DESCRIBE TABLE, 8.3

DISCONNECT, 8.2

ROLLBACK, 6.2

SELECT, 8.3

Commands Menu, 6.1

commitment control resource, 6.2

configuring, 6

connecting

connect processing, 1.4

connection management, 8.2

from AS/400 precompiled application, 8.1.2

to Oracle server, 8.1

conversion of Oracle data types to DB2/400 data types, 8.5

DB2/400

CONNECT syntax, Oracle CONNECT syntax not supported, 8.2

statements, CONNECT TO, 8.2

debugging, 6.4

debugging control string, Debugging Options Panel, 6.4

Debugging Options, 6.4

defining Oracle server to Access Manager, 5.3

describing tables, 8.3

diagnosing problems

debugging options panel, 6.4

if package creation failed, 6.5

error code processing, 8.6

explicit connection, 8.2

features, 1.3

files

QCBLLESRC, 8.1.2

QRPGLESRC, 8.1.2

QSQLCSRC, 8.1.2

GO CMDORAAM displays commands menu, 6.1

implicit connection, 8.2

installation library

add to your library list, 4.3.2

default position is *FIRST, 6.1

introduction, 1

library

adding to list, 6.1

name, default position, 4.3.2

message processing, 8.6

NLS support, B.1

options

USER, if not included in CONNECT TO statement, 6.2

USING, if not included in CONNECT TO statement, 6.2

package creation, 1.4

parameters

RDB, 8.2

stored procedures, 8.4.2

stored procedures, IN, 8.4.2

stored procedures, IN OUT, 8.4.2

stored procedures, OUT, 8.4.2

performance, SQL*Net trace, 6.3

programs

SAMP1C, 8.1.2

SAMP1CBL, 8.1.2

SAMP1RPG, 8.1.2

sample, C, A.1

sample, COBOL, A.2

sample, RPG, A.3

RELEASE ALL command, 8.2

SQL statement processing, 1.4

statements

CALL, advantages of stored procedures, 8.4.1

CALL, executed interactively or embedded, 8.4

COMMIT, connection management, coordinating transactions, 8.2

COMMIT, connection management, ending all connections, 8.2

COMMIT, with multiple connections open, 8.2

CONNECT TO, Access Manager default user id, 6.2

DDL, CREATE, two-phase commit, 6.2

DDL, DROP, two-phase commit, 6.2

ROLLBACK, connection management, 8.2

ROLLBACK, connection management note, 8.2

ROLLBACK, with multiple connections open, 8.2

SELECT, performing block fetching, 6.2

SELECT, verifying that rows were inserted successfully, 8.1.2

stored procedures

main topic, 8.4

advantages, 8.4.1

declaring, 8.4.3

GETRESULTS, 8.4.3

table of component interactions, 1.2.1

trace file, Debugging Options Panel, 6.4

trace library, Debugging Options Panel, 6.4

tracing values

*ADMIN, 6.3

*OFF, 6.3

*USER, 6.3

16, 6.3

two-phase commit, default options panel, 6.2

Oracle CONNECT syntax is not supported by Oracle Access Manager, 8.2

Oracle hints, general limitations, 2.3.1.2

Oracle Net

Access Manager component interactions, 1.2.1

checklists, TCP/IP AS/400 configuration, 5.4.1

commands

ADDRDBDIRE, adding an entry to the RDB directory, 5.4.3

ADDRDBDIRE, defining IBM DRDA connection, 5.2

WRKMBRPDM, 5.4.3

configuration, TCP/IP, 5.4.1

connecting through Oracle Net, 5.2

file names, 5.1

parameters, TNSNAMES.ORA, 5.1

post-installation configuration, 4.3.4

trace options, 6.3

Oracle server

Access Manager component interactions, 1.2.1

connecting to, 8.1

defining Oracle server to Access Manager, 5.3

Oracle Server Name field, 7.5.3

Oracle SQL Package Panel, 6.5

OS/400 and AS/400, platform names for IBM eServer iSeries servers, Preface

OUT parameter, stored procedure parameters, 8.4.2

P

package creation

checking problems if package creation fails, 6.5

with Oracle Access Manager, 1.4

panels

Access Manager Commands Menu, 6.1

Access Manager Debugging Options Panel (1), 6.4

Access Manager Debugging Options Panel (2), 6.4

Access Manager Default Options Panel, 6.2, 6.2

Access Manager Network Parameters Panel, 6.3, 6.3

ADDRDBDIRE Panel_1, 5.4.2

ADDRDBDIRE Panel_2, 5.4.2

Change or Enter New Server Attributes, 7.5.3

Change Privileged IDs (Relative to AM400_COM), 7.5.4

Change RID (Resolve In Doubt) Options, 7.5.3

Change RID (Resolve In Doubt) Options Panel, 6.6

default values provided during product installation, 4.2

Install Oracle Access Manager Product, 4.2.4

Oracle SQL Package Panel, 6.5

Verify Oracle Access Manager Install, 4.2.5

parameters

CLEANUP_DELAY

caution, changing the AM400_RID options, 7.5.3

changed by AM400_COM program, 7.7

querying the set value, 7.7.1

tuning parameter description, 7.5.3

DATAQUEUE_TIMEOUT

caution, changing the AM400_RID options, 7.5.3

changed by AM400_COM program, 7.7

querying the set value, 7.7.1

tuning parameter description, 7.5.3

DEAD_CHECK_COUNTER

caution, changing the AM400_RID options, 7.5.3

querying the set value, 7.7.1

tuning parameter description, 7.5.3

HOLD, known restriction with EXEC SQL COMMIT HOLD command, 2.3.2.4

Oracle Access Manager

PASSWORD, default options, 6.2

RDB, connection management, 8.2

USER, default options, 6.2

ROBCNNMTH, known restriction, 2.3.2.2

SERVER_STARTUP_TIMEOUT, querying for resolve-in-doubt transaction, 7.7.1

SQL*Net, TNSNAMES.ORA, 5.1

STARTUP

description, 7.5.3

uses of query, AM400_COM commands, 7.7.1

stored procedures

main topic, 8.4.2

IN, 8.4.2

IN OUT, 8.4.2

OUT, 8.4.2

test connectivity before changing any configuration parameters, 4.3.5

TRACE_LEVEL

determines trace level for AM400_RID program, 7.5.3

querying the set value, 7.7.1

verify installation parameters, 4.2.5

password

default user ID and password

with STRSQL commands, 8.1.1

for Oracle IDs field, Change or Enter New Server Attributes Panel, 7.5.3

phrases

SIMPLE CALL WITH NULLS, stored procedure limitations, 2.3.1.3

SIMPLE CALL, stored procedure limitations, 2.3.1.3

platform, iSeries, AS/400 and OS/400, platform names for IBM eServer iSeries servers, Preface

port number of the Oracle Net listener, usually 1521, 5.4.3

position, default position of Access Manager library name, 4.3.2

post-installation

main topic, 4.3

add Oracle Access install library to library list, 4.3.2

checklist, 4.3.1

configure SQL*Net, 4.3.4

configure two-phase commit (optional), 4.3.7

retest connectivity to Oracle server, 4.3.8

test connectivity to Oracle server, 4.3.5

precision

default data type, 2.3.1.1

default precision and scale, Access Manager default number format, 6.2

prepare phase, defined, two-phase commit processing terminology, 7.1.1

PREPARE, with a COMMIT or ROLLBACK command, known restriction, 2.3.2.1

privileged Oracle IDs field, Change or Enter New Server Attributes Panel, 7.5.3

privileges

GRANT command, 7.6

required by Oracle, 7.6

procedures

CALL, declaring procedures, parameter defaults, 8.4.3

GETRESULTS, example, extract from an AS/400 C program, 8.4.3

installation, the installation procedure will not install into a library with existing objects, 4.2.4

processor, requirements, 3.1.1

product set, 2.1

program

SAMP1C program, 8.1.2

SAMP1CBL program, 8.1.2

SAMP1RPG program, 8.1.2

sample programs

Oracle Access Manager, C, 8.1.2, A.1

Oracle Access Manager, COBOL, 8.1.2, A.2

Oracle Access Manager, RPG, 8.1.2, A.3

programs

AM400_COM

main topic, 7.7

dynamically add or remove Oracle server parameters, 7.5.4

AM400_RID

listing servers and connections, 7.7.1

resolving in-doubt transactions, 7.4.1

Oracle Access Manager

SAMP1C, 8.1.2

SAMP1CBL, 8.1.2

SAMP1RG, 8.1.2

sample

C, A.1

COBOL, A.2

RPG, A.3

Q

QCBLLESRC file, sample program files, 8.1.2

QRPGLESRC file, sample program files, 8.1.2

QSECOFR

security administration user ID, 7.5.4

user profile, authority for SECADM (before installing Oracle Access Manager), 4.2

QSQLCSRC file, sample program files, 8.1.2

QTEMP, Access Manager trace library value, 6.4

QUERY command, queries various items within AM400_RID environment, examples provided, 7.7.1

R

RAW data type, Oracle data types mapped to DB2/400 data types, 8.5

RDB

S

SAMP1C program, 8.1.2

SAMP1CBL program, 8.1.2

SAMP1RPG program, 8.1.2

sample programs

Oracle Access Manager

C, A.1

COBOL, A.2

RPG, A.3

scale

default data type, 2.3.1.1

default precision and scale, Access Manager default number format, 6.2

SELECT statement

describing tables (STRSQL), 8.3

limitation of Oracle hints, 2.3.1.2

performing block fetching, 6.2

verifying that rows were inserted successfully, 8.1.2

SERVER_STARTUP_TIMEOUT parameter, 7.7.1

SET command, AM400_COM commands, description and example, 7.7.1

SET CONNECTION command, connection management, 8.2

severity level, CRTORAPKG command failure, 6.5

SHUTDOWN command, description, AM400_COM command, 7.7.1

SIMPLE CALL phrase is supported, stored procedure limitations, 2.3.1.3

SIMPLE CALL WITH NULLS phrase not supported, stored procedure limitations, 2.3.1.3

SMALLINT data type, Oracle data types mapped to DB2/400 data types, 8.5

software requirements, 3.2

SQL

all SQL connections are managed at the activation group level., 1.6

client manager, Access Manager component interactions, 1.2.1

Development Kit, required in order to run STRSQL, 3.2.5

Oracle SQL Package Panel, 6.5

SQL0105 error, with CRTORAPKG command, 6.5

SQL0969 error, known restriction with two-phase commit, 2.3.2.1

SQL5001 error, with CRTORAPKG command, 6.5

SQLCA, message and error code processing, 8.6

SQLERRMC field, message and error code processing, 8.6

SQLSTATE field, message and error code processing, 8.6

statements, processing on Oracle Access Manager, 1.4

STARTUP command, description, AM400_COM command, 7.7.1

STARTUP parameter

enabling two-phase commit processing, 7.5.3

queries, AM400_COM program, 7.7.1

startup parameter field, enabling two-phase commit processing, 7.5.3

statements

CONNECT, known restriction with two-phase commit, 2.3.2.3

DB2/400

CONNECT TO, 8.2

DECLARE PROCEDURE, 8.4.3

DECLARE PROCEDURE, DB2/400 statement, stored procedure limitations, 2.3.1.3

DELETE, 2.3.1.2

EXEC SQL, Oracle hints limitation, 2.3.1.2

Oracle Access Manager

CALL, 8.4, 8.4.1

COMMIT, 8.2, 8.2, 8.2

CONNECT TO, 6.2

DDL, CREATE, 6.2

DDL, DROP, 6.2

ROLLBACK, 8.2, 8.2, 8.2

SELECT, 8.1.2

SELECT, performing block fetching, 6.2

SELECT, 2.3.1.2

SQL, processing, 1.4

UPDATE, 2.3.1.2

STATUS command, requests global connection status of AM400_RID program, 7.7.1

status signal, transmitted for every connect and disconnect, and timeout, 7.5.3

stored procedures

main topic, 8.4

advantages, 8.4.1

declaring procedures, 8.4.3

GETRESULTS procedure, 8.4.3

limitations, 2.3.1.3

parameters

main topic, 8.4.2

IN, 8.4.2

IN OUT, 8.4.2

OUT, 8.4.2

STRSBS command, enabling two-phase commit processing, 7.5.5

STRSQL

activation group, calling Access Manager, 1.6

checking connection status, 6.5

connecting to an Oracle server, 8.1.1

SUM function, precision and scale, 6.2

SYS.PENDING_SESSIONS$ table, 7.6

SYS.PENDING_TRANS$ table, 7.6

system requirements

hardware, 3.1

processor, 3.1.1

software

additional software, 3.2.5

DB2/400 Query Manager, 3.2.5

network, 3.2.2

operating system, 3.2.1

T

tables

1-1, Access Manager Component Interactions, 1.2.1

6-1, Access Manager Commands, 6.1

8-1, Sample Program Files, 8.1.2

8-2, Oracle data types mapped to DB2/400 data types, 8.5

8-3, Error Code Mapping, 8.6

B-1, Oracle Character Set Names, B.2

B-2, Oracle NLS_LANG Values, B.3

SYS.PENDING_SESSIONS$, 7.6

SYS.PENDING_TRANS$, 7.6

TCP/IP

AS/400 configuration

define TNSNAMES entry, 5.4.3

configuring SQL*Net, 5.4

connecting the AS/400 to an Oracle server, 1.2

terminology, two-phase commit

AM400_COM program, 7.1.1

AM400_RID program, 7.1.1

commit phase, 7.1.1

commit point site, 7.1.1

implied commit, 7.1.1

prepare phase, 7.1.1

two-phase commit parameter, 7.1.1

test connectivity before changing any configuration parameters, 4.3.5

text format conventions for code input and output, Preface

TIME data type, stored procedure limitations, 2.3.1.3

timeout, DATAQUEUE_TIMEOUT parameter, description, with AM400_RID program and status signal, 7.5.3

TIMESTAMP data type

Oracle data types mapped to DB2/400 data types, 8.5

stored procedure limitations, 2.3.1.3

TNS (Transparent Networking Substrate), with Oracle Net, 5

TNSNAMES

defining for TCP/IP, 5.4.3

entry, 5.3.2

TNSNAMES.ORA parameter, 5.1

TO_CHAR function, 6.5

TO_DATE function, 6.5

tracing

trace file, Debugging Options Panel, 6.4

trace library, Debugging Options Panel, 6.4

TRACE_LEVEL parameter

on Change RID (Resolve In Doubt) Options Panel, 7.5.3

with QUERY, 7.7.1

values

*ADMIN, 6.3

*OFF, 6.3

*USER, 6.3

16, 6.3

translating date formats, default for IBM AS/400, 1.3.4

Transparent Networking Substrate (TNS), with Oracle Net, 5

tuning parameter, DATAQUEUE_TIMEOUT, description, with AM400_RID program, 7.5.3

two-phase commit

AM400_COM program

adding and removing privileged user IDs, 7.5.4

communicating through a shared data space, 7.7.1

main topic, 7.7

user ID in the Privileged ID field, 7.5.4

AM400_RID program

altering environment with AM400_COM program, 7.7

commit phase, announcing the end of a transaction, 7.3.2

communication with AM400_COM program, 7.7

connecting to a designated server, 7.5.3

connections with servers, 7.7.1

designate connections to Oracle servers (AM400_COM function), 7.5.4

prepare phase, 7.3.1

runs in its own subsystem, 7.4.1

starting the AM400_RID program subsystem with STRSBS, 7.5.5

status signal and timeout, 7.5.3

commands

AM400_COM program, main topic, 7.7.1

AM400_COM program, ADD, 7.7.1

AM400_COM program, FORCE, 7.7.1

AM400_COM program, LIST, 7.7.1

AM400_COM program, MODIFY, 7.7.1

AM400_COM program, QUERY, 7.7.1

AM400_COM program, REMOVE, 7.7.1

AM400_COM program, SET, 7.7.1

AM400_COM program, SHUTDOWN, 7.7.1

AM400_COM program, STARTUP, 7.7.1

AM400_COM program, STATUS, 7.7.1

CHG2PCPRM, 7.5.3, 7.5.4

CHGSQLDFLT, 7.1

COMMIT, phase 2, commit or abort and roll back, 7.3.2

COMMIT, prepare phase, 7.2

COMMIT, privileges, 7.6

GRANT, 7.6

ROLLBACK, phase 2, commit or abort and roll back, 7.3.2

ROLLBACK, privileges, 7.6

STRSBS, 7.5.5

default options panel, 6.2

enabling

main topic, 7.5

add or remove AM400_COM privileged user IDs, 7.5.4

change Oracle Access Manager commit default, 7.5.2

change the AM400_RID options, 7.5.3

checklist, 7.5.1

start the AM400_COM program (optional), 7.5.6

start the subsystem that runs AM400_RID program, 7.5.5

fields

description, 7.5.3

Oracle server name, 7.5.3

password for Oracle ID, 7.5.3

privileged Oracle ID, 7.5.3

startup parameter, 7.5.3

overview, 7.1

panels

Change or Enter New Server Attributes, 7.5.3

change privileged IDs (Relative to AM400_COM), 7.5.4

change RID (Resolve In Doubt) Options, 7.5.3

parameters

CLEANUP_DELAY, 7.5.3, 7.5.3, 7.7, 7.7.1

DATAQUEUE_TIMEOUT, 7.5.3, 7.5.3, 7.7, 7.7.1

DEAD_CHECK_COUNTER, 7.5.3, 7.5.3, 7.7.1

parameter, defined, 7.1.1

SERVER_STARTUP_TIMEOUT, 7.7.1

STARTUP, 7.5.3, 7.7.1

TRACE_LEVEL, 7.5.3, 7.7.1

post-installation, configure two-phase commit (optional), 4.3.7

process

main topic, 7.3

commit phase, 7.3.2

phase 1, 7.3.1

phase 2, 7.3.2

prepare phase, 7.3.1

resolve in-doubt transactions, 7.4.1

restrictions with SQL, 1.3.1

tables

SYS.PENDING_SESSIONS$, 7.6

SYS.PENDING_TRANS$, 7.6

terminology

main topic, 7.1.1

AM400_COM program, 7.1.1

AM400_RID program, 7.1.1

commit phase, 7.1.1

commit point site, 7.1.1

implied commit, 7.1.1

prepare phase, 7.1.1

two-phase commit parameter, 7.1.1

U

unit of work, defined, 1.5

UPDATE statement, limitation of Oracle hints, 2.3.1.2

user ID, default user ID and password

with STRSQL commands, 8.1.1

USER option, if not included in CONNECT TO statement, 6.2

USER parameter, default options, 6.2

V

VARCHAR data type, Oracle data types mapped to DB2/400 data types, 8.5

VARCHAR2 data type, Oracle data types mapped to DB2/400 data types, 8.5

Verify Oracle Access Manager Install - panel, 4.2.5

W

WRKMBRPDM command, command to edit member TNSNAMES in ORA file, with example code, 5.4.3