Index
C
- CALL correspondence
- call correspondence order restrictions
- CICS 1.8.1
- CICS Transaction Server
- gateway starts communication with 1.8.2.1
- client application development
- calling a TIP
- customized TIPs for remote host transaction 4.4
- declaring TIP variables 4.7.1, 7.4.1
- error handling
- examples and samples 1.4
- exchanging data 4.8
- on gateway using TCP/IP 7.5
- executing 4.9, 7.7
- granting execute authority 4.8.3, 7.5.3
- on gateway using TCP/IP 7
- overriding TIP initializations 4.7.2.2
- on gateway using TCP/IP 7.4.2.2
- overview 4.1
- preparation 4.2
- remote host transaction types
- requirements 4.5
- declare RHT/TIP data to be exchanged 4.5
- exchange data with RHT using TIP user function 4.5
- initialize RHT for multi-conversational applications 4.5
- initialize RHT using TIP initialization function 4.5
- repetitively exchange data with RHT using TIP user function 4.5
- terminate RHT using TIP termination function 4.5
- security considerations 4.7.2.3, 7.4.2.3
- terminating the conversation 4.8.1, 7.5.1
- TIP and remote transaction program correspondence 4.6, 7.3
- TIP CALL correspondence 4.6.2
- TIP content and purpose 4.3.1
- TIP DATA correspondence 4.6.1, 7.3.1
- TIP TRANSACTION correspondence
- client application development for gateway using TCP/IP
- overview 7.1
- client application development on gateway using TCP/IP
- preparing 7.2
- COBOL 4.2, 7.2, D.2, D.2.4
- COMMIT command 2.2.1, 2.2.2
- user responsibility 2.2.1
- commit-confirm 5.1
- COMMIT processing 2.2.1
- communication
- compiling a TIP 3.4
- CONNECT command 2.3, 2.6.1
- control file
- conversation sharing, see APPC conversation sharing 4.10
- creating a TIP
D
- database link 1.6
- data conversion
- errors 8.4
- DATA correspondence 4.6.1, 7.3.1
- data dictionary, see PG DD 1.3
- data exchange
- PGAXFER function 1.7.1.2
- data format conversion D
- datastores
- gateway access to 1.1
- datatype
- RAW C
- datatype conversion D
- COBOL editing symbols D.2.1
- convert length D.1
- duplicate names D.2.4
- expected length D.1
- format conversion D.2.1
- parameters over 32K in length D.1.1
- PL/SQL D.2.4
- naming algorithms D.2.4
- receive length D.1
- removing support for parameters over 32K in length D.1.1
- See USAGE (PASS), USAGE (ASIS). USAGE (SKIP), and PL/SQL Naming Algorithms D.2.1
- send length D.1
- truncated and non-unique names D.2.4
- datatype conversions
- COBOL symbols interpreted by PGAU D.2.1
- DBCS
- DBMS_PIPE PL/SQL package 3.1
- debugging tool
- PGATRAC function B.5
- DEFINE CALL 2.1
- DEFINE CALL parameters 2.6.2
- DEFINE CALL statement ("command") 1.8.3.1, 1.9.3.1, 3.2.6, 4.10.4, F.2
- DEFINE DATA 2.1
- DEFINE DATA statement ("command") 1.8.3.1, 1.9.3.1, 2.6.15, 3.2.6, 4.6.1, 4.10.4, 7.3.1, A.2.3.7, F.1
- DEFINE TRANSACTION parameters 2.6.4
- DEFINE TRANSACTION statement ("command") 3.2.6, 4.10.4, F.3
- defining and generating a TIP 3.3
- definition versioning 2.5.2
- deleting and inserting rows into PGA_TCP_IMSC table 6.5
- DESCRIBE command 2.6.5
- dg4pwd utility
- definition 1.3
- DISCONNECT command 2.6.6
- double byte character sets (DBCS)
- driver procedure
E
G
- gateway
- gateway sample files
- gateway server 5.5.1
- gateway server trace 8.9, 8.9.2
- GENERATE 2.1
- GENERATE statement ("command") 1.8.3.1, 1.9.3.1, 3.2.6, 3.3, 4.6.1, 7.3.1, E.2, F.4
- GLOBAL_TRAN_ID 5.6.2
- Globalization Support
- granting privileges for creating TIPs 3.1
- GROUP statement (PGAU) 3.3
I
- I/O PCB 1.9.2, 3.2.1, 7.1
- implicit APPC 4.12
- implicit versioning
- sample definitions F.5
- IMS 1.1
- communication with Integrating Server
- using TCP/IP 1.9.2.2
- communication with Integrating Server
- IMS/TM
- communication through the gateway 1
- IMS inquiry
- location of sample file 1.4
- initialization files
- see gateway initialization files, also see PGA parameters 1.3
- initiating remote transactions 1.7.1.1
- initsid.ora file 1.3, 8.9.1, 8.9.2, 8.9.2.1
- parameters to run pg4tcpmap tool 6.4
M
- MAKE_NUMBER_TO_RAW_FORMAT function C.1.5
- MAKE_RAW_TO_NUMBER_FORMAT function C.1.4
- mapping parameters
- from SNA to TCP/IP 6.1
- mapping table
- PGA_TCP_IMSC 1.9.2.2
- MBCS, See multi-byte character sets 4.11, 7.8
- MODE_NAME 5.6.2
- multi-byte character sets (MBCS) 4.11, 7.8
- multi-conversational transactions 4.3.2.3, 4.5
- multi-conversational transaction type
- for gateway using SNA 1.8.1
O
- OCCURS DEPENDING ON D.2.1
- OLTP
- and TCP/IP 1.3, 1.5
- commit-confirm transaction log 5.3
- definition 1.3
- forget/recovery transaction 5.3
- functional requirements of the gateway 5.4
- in commit-confirm 5.1
- in gateway architecture featuring SNA 1.5
- in gateway using TCP/IP 1.5
- logic flow for successful commit 5.6
- only IMS supported on gateway using TCP/IP 1.2, 1.3
- remote 1
- security considerations 4.7.2.3, 7.4.2.3
- transaction logging code 5.3
- one-shot transaction types 1.8.1, 4.3.2.1, 4.5, 5.4
- online transaction processor
- See OLTP 1.5
- operating system
- role in gateway installation 1.5
- Oracle database 1.7.1.2
- Oracle Database Gateway for APPC
- Oracle global transaction ID 5.1, 5.3, 5.4, 5.6.2
- Oracle integrating server 4.1
- Oracle Net 1.3, 4.13, 7.9, C
- restrictions for data conversion C
- overrides 4.7.2.2, 7.4.2.2
P
- package
- UTL_PG 3.1
- parameters
- persistent socket transaction type
- for TCP/IP for IMS Connect 1.9.1
- persistent transactions 4.3.2.2, 4.5, 5.4
- persistent transaction type, for gateway using SNA 1.8.1
- pg4tcpmap tool 1.9.2.2, 3.2.5, 7
- calling, to map DEFINE TRANSACITON parameters 7.6
- commands to operate PGA_TCP_IMSC table 6.5
- definition 1.3
- description and function in the gateway 1.2
- function 1.2
- in mapping input parameters 6.1
- function in remote transaction initiation 1.7.1.1
- preparation for populating PGA_TCP_IMSC table 6.1
- setting parameters in initsid.ora 6.4
- to map SideProfile name 2.6.4
- PGA
- pga_call_parm table A.2.3.6
- pga_call table A.2.3.5
- PGA_CC_PENDING table
- commit-confirm transaction log 5.6.2
- pga_compilers table A.1.2.5
- pga_data_attr A.2.3.9
- pga_data_values table A.2.3.10
- pga_data table A.2.3.7
- pga_datatype_attr table A.1.2.7
- pga_datatype_values table A.1.2.8
- pga_datatypes table A.1.2.6
- pga_env_attr table A.1.2.3
- pga_env_values table A.1.2.4
- pga_environments table A.1.2.2
- pga_fields table A.2.3.8
- pga_maint table A.1.2.1
- pga_modes constant A.1.2.10
- PGA_TCP_IMSC table 1.9.2.2, 3.2.5, 6.1, 6.2, 7, 7.1, 7.3.3
- PGA_TCP_PASS 6.2
- PGA_TCP_USER 6.2
- pga_trans_attr table A.2.3.2
- pga_trans_calls table A.2.3.4
- pga_trans_values table A.2.3.3
- pga_trans table A.2.3.1
- pga_usage A.1.2.9
- pga_usage constant A.1.2.9
- PGAADMIN 3.1
- pgadb2i.pkb 1.4
- pgadb2i.pkb file 1.4, 1.8.3.1, 4.3.1
- pgadb2i.pkh file 1.4, 1.8.3.1
- pgadb2i.sql file 4.3.1, E
- pgadb2id.sql file 4.3.1
- PGAINIT 1.7.1.1, B.1
- role in mapping SNA parameters to TCP/IP 6.1
- PGAINIT function 1.3, 1.7.1.1
- PGATCTL B.4
- PGATERM B.3
- PGATERM function 1.3, 1.7.1.1
- PGATRAC B.5
- PGAU 4.1
- accesses definitions in PG DD 1.3
- commands- also called "statements" 2.6
- COMMIT processing 2.2.1
- defining and testing a TIP 2.5
- definition 2
- used to generate TIP specifications 1.3
- definition names 2.5.1
- definitions 2.4
- definition versioning 2.5.2
- functions 2.1
- -generated TIP specifications 1.6
- generation 2.4
- interpretation of COBOL symbols in datatype conversion D.2.1
- invoking 2.3
- keywords 2.5.3
- overview 2.1
- purpose of PGDL 1.3
- role in calling TIPs, on gateway using TCP/IP 7.1
- ROLLBACK processing 2.2.2
- sample input F
- writing statements 3.2.6
- pgau.trc file 2.6.9
- PGAU commands 1.8.3.1, 1.9.3.1
- CONNECT 2.3, 2.6.1
- CONNECT, parameters 2.6.1
- DEFINE CALL 2.6.2, 2.6.15, 3.2.6, 4.10.4
- DEFINE DATA 2.6.3, 2.6.15, 3.2.6, 4.6.1, 4.10.4, 7.3.1, A.2.3.7
- DEFINE DATA, datatype conversions
- DEFINE PGAU, call list 3.2.3
- DEFINE TRANSACTION 1.8.3.1, 2.1, 2.6.4, 3.2.6, 4.10.4
- DEFINE TRANSACTION, parameters 2.6.4, 3.2.4
- defining correlation between TIP and RTP 2.1
- DESCRIBE 2.6.5
- DESCRIBE, parameters 2.6.5
- DISCONNECT 2.6.6
- DISCONNECT, parameters 2.6.6
- EXECUTE 2.6.7
- EXECUTE, parameters 2.6.7
- EXIT 2.6.8
- EXIT, parameters 2.6.8
- formatting of Call and Transaction reports 2.6.15
- four main types, in control file 1.8.3.1, 1.9.3.1
- GENERATE 2.6.9, 3.2.6, 3.3, 3.5, 4.6.1, 7.3.1, E.2
- GROUP 2.6.10, 3.3
- HOST 2.6.11
- parameters 2.6.11
- on gateway using SNA 1.8.3.1
- PRINT 2.6.12
- REDEFINE DATA 2.6.13, A.2.3.7
- sample F.6
- REM 2.6.14
- REM, parameters 2.6.14
- REPORT 2.6.15
- REPORT, parameters 2.6.15
- SET 2.6.16
- SET, parameters 2.6.16
- SHOW 2.6.17
- SHOW, parameters 2.6.17
- SPOOL 2.6.18
- SPOOL, parameters 2.6.18
- TRANSACTION 2.6.15
- UNDEFINE, sample F.7
- UNDEFINE CALL 2.6.19
- UNDEFINE CALL, parameters 2.6.19
- UNDEFINE DATA 2.6.20
- UNDEFINE DATA, parameters 2.6.20
- UNDEFINE TRANSACTION 2.6.21
- UNDEFINE TRANSACTION, parameters 2.6.21
- VARIABLE 2.6.22
- VARIABLE, parameters 2.6.22
- PGAU script file
- PGAXFER 7.3.2.2, B.2
- PGAXFER function 1.3, 1.7.1.1, 1.7.1.2, 4.3.1, 7.2.1
- PGDD (Data Dictionary)
- environment sequence numbers A.1.1
- PG DD (Data Dictionary) 2.1, 2.6.4
- active dictionary A.2
- active dictionary tables
- data definitions for parameters over 32K in length D.1.1
- datatype conversion support for COBOL D.2
- definition 1.3
- definition names
- valid characters in 2.5.1
- diagnostic
- entries, creating a TIP 3.3
- environment dictionary tables A.1, A.1.2, A.1.2.1
- in writing PGAU statements 3.2.6
- keyword form in storage 2.5.3
- maintenance 2.3
- overview A
- preparing client application
- purpose of REPORT command 2.6.15
- relationship to PGAU 2.1
- remote transaction definitions 2.4
- ROLLBACK command 2.2.1
- select scripts 8.3
- storage of information needed for PGAU GENERATE to perform 4.6.1, 7.3.1
- transaction attributes 4.7.2.2, 7.4.2.2
- USAGE (SKIP) D.2.3
- version definition tables 2.5.2
- pgddausr.sql file 4.13, 7.9
- pgddcr8.sql file 2.5.2, A.2
- PGDL (Procedural Gateway Definition Language) 2.1, B
- definition 1.3
- pgtflip.pkb file 1.9.3.1, 7.2.1
- pgtflip.pkh file 1.9.3.1
- pgtflip.sql file 7.2.1
- pgtflipd.sql 7.4.1
- pgtflipd.sql file 7.2.1
- PIC 9 8.4
- PIC G 8.4
- PIC G datatype conversions D.2.1
- PIC G datatypes D.2.1
- PIC X datatypes D.2.1
- PIC X data types 8.4
- PKGEX(DC) diagnostic option 8.5
- PL/SQL 1.3
- call A.2.3.4, A.2.3.5
- code B
- code generator 1.2, 8.4
- data length limits 8.8
- datatypes 1.6, 4.5, 4.6.1, F.4, F.5
- converted to RAW 1.7.1.2
- developing TIPs D
- enabling a trace 8.9.2.2
- function in the gateway 1.1, 1.6
- invoking DG4APPC 1.8.2, 1.9.2
- naming algorithms D.2.4
- parameters 4.7.1, 7.4.1
- record format F.5
- stored procedure 1.8.2.1
- transferring data
- using RAW datatype C
- UTL_PG package function 1.3
- UTL_RAW function 1.3
- variable names D.2.4
- datatype conversion D.2.4
- variables 3.5, D.2.1, D.2.4
- PL/SQL package 2.3, 2.6.2, 2.6.19, 2.6.21, 3.1, 4.3.1, 8.2, B, E.2
- PL/SQL stored procedure 5.5.2
- PL/SQL stored procedure specification
- PRINT command 2.6.12
- privileges
- needed to use TIPs 4.13
- problem analysis
- Procedural Gateway Administration
- see PGA 1.3
- Procedural Gateway Administration Utility
- see PGAU 1.6
R
- RAW_TO_NUMBER FORMAT function C.1.6
- RAW_TO_NUMBER function C.1.2
- recompilation errors
- causes E.2.2.1
- REDEFINE DATA statement A.2.3.7, F.6
- REM command 2.6.14
- remote host transactions (RHT)
- APPC conversation sharing 4.10
- attributes needed 4.6.3, 7.3.3
- client application 4.5
- defined using the PGAU DEFINE TRANSACTION statement 4.6.3, 7.3.3
- evaluating 3.2
- multi-conversational, client applications 4.5
- one-shot, client applications 4.5
- persistent, client applications 4.5
- requirements
- understanding 4.3
- steps involved in 4.5
- types
- remote procedural call
- See RPC 1.1
- remote procedural call (RPC) A.2.3.5
- remote procedure
- definition 1.3
- remote transaction initiation
- remote transaction program
- See RTP 1.1
- remote transaction termination
- REPORT statement 3.2.6
- RHT, See remote host transactions 3.2.1
- ROLLBACK command 2.2.1, 2.2.2
- ROLLBACK processing 2.2.2
- RPC
- RPC interface
- RTP
- runtime traces 8.5
S
- sample
- sample definitions
- implicit versioning F.5
- script file 3.2.7
- sequence objects
- in the PGDD environment dictionary A.1.1
- SET command 2.6.16
- SET LOG_DESTINATION parameter 8.8, 8.9.1
- SET TRACE_LEVEL parameter 8.8, 8.9.1, 8.9.2.1, 8.9.2.2
- SIDE_NAME 5.6.2
- Side Information Profile 2.6.4, B.1
- simple DG4APPC communication
- on gateway using SNA 1.8.2
- SNA
- and gateway components 1.5
- communication between mainframe and Oracle database 1.8.2
- communications function 1.8.2
- creating a TIP 1.8.3
- determining validity of TIP specification E.2.1.1
- examples and sample files used in this guide 1.4
- flexible call sequence 4.6.2.1
- function in the gateway 1.1
- gateway transaction types 1.8.1
- implementing commit-confirm 5
- overview of the gateway, using 1.1
- parameters 1.7.1.1
- PGAU DEFINE TRANSACTION command 3.2.4
- remote transaction initiation 1.7.1.1
- remote transaction termination on the gateway 1.7.1.3
- steps to connecting Oracle database and mainframe 1.8.2.1
- supported remote host languages 3.2.1
- TIP internals E
- uses APPC to access all systems 1.1
- writing TIPs 1.8.3
- socket file descriptor
- returned by TCP/IP network to PGAINIT 1.7.1.1
- specification file
- SPOOL command 2.6.18
- SQL*Plus
- statements
- see PGAU commands 2.6
- SYNCHRONIZED LEFT D.2.1
T
- TCP/IP for IMS Connect 1.9.2, 7.4.2.1
- and gateway components 1.5
- and PGA_TCP_IMSC parameter table 6.2
- and PGAINIT 6.1
- and Remote Transaction Initiation 1.7.1.1
- Client application overview 7.1
- communication between gateway and Oracle database 1.9.2
- content of PGA_TCP_IMSC table 6.3
- creating a TIP 7
- determining validity of TIP specification E.2.1.1
- elements of TIP-RTP correspondence 7.3
- examples and sample files used in this guide 1.4
- function in the gateway 1.1
- gateway support for, description 1.2
- IMS enabled 1.3
- mapping parameters using pg4tcpmap tool 7.6
- mapping SNA parameters to TCP/IP 6.1
- non-persistent socket transaction type 1.9.1
- OLTP in gateway architecture 1.5
- persistent socket transaction type 1.9.1
- PGAU DEFINE TRANSACTION command 3.2.5
- remote host languages supported 3.2.1
- remote transaction initiation 1.7.1.1
- remote transaction termination 1.7.1.3
- SENDs and RECEIVEs
- TIP CALL correspondence 7.3.2
- setting initsid.ora parameters 6.4
- simple communication
- between gateway and integrating server 1.9.2
- steps to communication between server and IMS 1.9.2.2
- steps to writing a TIP 1.9.3.1
- supports only IMS as OLTP 1.2, 1.3
- TIP granting privileges needed 7.9
- TIP internals E
- TRANSACTION correspondence 7.3.3
- transaction types 1.9.1
- terminal-oriented transactions
- modifying 4.12
- terminating a TIP conversation 4.8.1, 7.5.1
- terms, gateway terms defined 1.3
- TIP 1.4, 4.1, 7.1
- APPC conversation sharing 4.10.1, 4.10.3
- background references E.1
- CALL correspondence 4.6.2
- calling
- calling and controlling
- client application development
- compiling 3.4
- content documentation (tipname.doc) 3.5
- content file sections
- control file 2.1
- controlling
- conversation sharing used to circumvent large TIPs 4.10.4
- conversion 1.2, 4.11, 7.8
- converting PL/SQL datatypes to RAW 1.7.1.2
- creating 3
- customized interface for each remote host transaction (RTP) 4.4
- custom TIP writing E
- DATA correspondence 4.6.1
- on gateway using TCP/IP 7.3.1
- datatype conversion support for COBOL D.2
- declaring variables to create a TIP 4.7.1, 7.4.1
- defining, with PGAU 2.5
- defining and generating 3.3
- definition 1.3
- definition errors 8.1
- dependent TIP body or specification changes E.2.2
- diagnostic parameters 4.10.6
- driver procedures
- flexible call sequence 4.6.2.1
- four steps to generate
- functions
- in Oracle database 1.7.1.2
- generated by PGAU 4.1
- granting privileges to use 3.1, 4.13, 7.9
- independent TIP body changes E.2.1
- initializations 4.7.2.2, 7.4.2.2
- overriding 4.7.2.2
- initializing the conversation 4.7.2, 7.4.2
- internals E
- override parameters 4.10.6
- overriding
- on gateway using TCP/IP 7.4.2.2
- overriding default attributes 4.7.2.2, 7.4.2.2
- overview 1.8.3, 1.9.3
- privileges needed 3.1, 4.13
- public functions
- recompiling E.2, E.2.1, E.2.2
- remote transaction
- correspondence 4.6
- remote transaction correspondence, on gateway using TCP/IP 7.3
- remote transaction initiation (PGAINIT) 1.7.1.1
- requirements for corresponding with RHT
- requirements of the client application 4.5
- service 4.10.1
- specification file 3.3
- specifications
- generated by PGAU 1.6
- steps to writing
- terminating the conversation 4.8.1, 7.5.1
- trace controls 8.6
- tracing 8.8
- TRANSACTION correspondence 4.6.3, 7.3.3
- on gateway using SNA 4.6.3
- using transaction instance parameter
- on gateway using TCP/IP 7.4.2.1
- writing
- TIP control file commands 1.8.3.1, 1.9.3.1
- on gateway using TCP/IP 1.9.3.1
- tipname.doc file 3.5, 4.5, 7.4.1
- tipname.pkb file 8.5
- TIP specification 4.1, E.2, E.2.1
- TIP warnings and tracing
- suppressing 8.7
- TP_NAME 5.6.2
- TRACE_LEVEL 8.9.1
- trace option 8
- TIP definition errors 8.1
- traces 8.6.2, 8.6.3, 8.6.4, 8.6.5
- TRANSACTION correspondence
- transaction instance parameter
- Transaction Interface Package
- See TIP 1.3
- transaction socket
- transaction type for TCP/IP 1.9.1
- transaction types
- one-shot, persistent and multi-conversational, for SNA 1.8.1
- transparency