| Oracle Procedural Gateway® for APPC User's Guide 10g Release 2 (10.2) for UNIX Part Number B16210-01 |
|
|
View PDF |
| Oracle Procedural Gateway® for APPC User's Guide 10g Release 2 (10.2) for UNIX Part Number B16210-01 |
|
|
View PDF |
PGAU generates complete and operational TIPs for most circumstances. TIP internals information is provided to assist you in diagnosing problems with PGAU-generated TIPs, and in writing custom TIPs, if you choose to do so.
If your gateway is using the SNA communication protocol:
This appendix refers to a sample called pgadb2i. The source for this TIP is in file pgadb2i.sql in the $ORACLE_HOME/pg4appc/demo/CICS directory.
If your gateway is using the TCP/IP communication protocol:
This appendix refers to a sample called pgaims. The source for this TIP is in file pgtflipd.sql in the $ORACLE_HOME/pg4appc/demo/IMS directory.
This appendix contains the following sections:
Several topics are important to understanding TIP operation and development; following is a list of concepts that are key to TIP operation and suggested sources to which you can refer for more information.
For information about PL/SQL Packages, refer to the PL/SQL User's Guide and Reference.
For information about PGA Application Concepts, refer to the following chapters in this guide:
If your communication protocol is SNA: refer to Chapter 4, "Client Application Development (SNA Only)";
If your communication protocol is TCP/IP: refer to Chapter 7, "Client Application Development (TCP/IP Only)".
For information about PGA RPC Interface, refer to Appendix B, "Gateway RPC Interface".
For information about PGA UTL_PG/UTL_RAW Interface, refer to Appendix C, "The UTL_PG and UTL_RAW Interface".
PGAU GENERATE writes each output TIP into a standard PL/SQL package specification file and body file. This separation is beneficial and important. Refer to the Oracle Database Application Developer's Guide and the PL/SQL User's Guide and Reference for more information. Also refer to "GENERATE" in Chapter 2, "Procedural Gateway Administration Utility" for more information about building the PL/SQL package.
TIPs are PL/SQL packages. Any time a package specification is recompiled, all objects which depend on that package are invalidated and implicitly recompiled as they are referenced, even if the specification did not change.
Objects which depend on a TIP specification include client applications that call the TIP to interact with remote host transactions.
It might be important to change the TIP body for the following reasons:
Oracle ships maintenance which affects the TIP body, or
Oracle ships maintenance for the UTL_RAW or UTL_PG conversion functions upon which the TIP body relies.
Refer to Appendix C, "The UTL_PG and UTL_RAW Interface" for more detailed information about these functions.
if the remote host network or program location parameters have changed. Refer to "DEFINE TRANSACTION" in Chapter 2, "Procedural Gateway Administration Utility" for more information
Provided that the TIP specification does not need to change or be recompiled, the TIP body can be regenerated and recompiled to pick up changes without causing invalidation and implicit recompilation of client applications that call the TIP.
Therefore, PGAU now separates output TIPs into specification and body files. Refer to "GENERATE" in Chapter 2, "Procedural Gateway Administration Utility" for a discussion of file identification.
Independent TIP body changes are internal and require no change to the TIP specification. Examples of such changes include: a change in UTL_RAW or UTL_PG conversions, inclusion of diagnostics, or a change to network transaction parameters.
In these cases, when PGAU is used to regenerate the TIP, the new TIP specification file can be saved or discarded, but should not be recompiled. The new TIP body should be recompiled under SQL*Plus. Provided that the TIP body change is independent, the new body compilation completes without errors and the former TIP specification remains valid.
To determine if a specification has remained valid, issue the following statements from SQL*Plus, depending upon your communication protocol:
If your gateway is using the SNA communication protocol, issue the following:
SQL> column ddl_date format A22 heading 'LAST_DDL' SQL> select object_name, 2 object_type, 3 to_char(last_ddl_time,'MON-DD-YY HH:MM:SS') ddl_date, 4 status 5 from all_objects where owner = 'PGAADMIN' 6 order by object_type, object_name; OBJECT_NAME OBJECT_TYPE LAST_DDL STATUS ----------- ----------- -------------------- --------- PGADB2I PACKAGE NOV-24-1999 09:09:13 VALID PGADB2I PACKAGE BODY NOV-24-1999 09:11:44 VALID DB2IDRIV PROCEDURE DEC-30-1999 12:12:14 VALID DB2IDRVM PROCEDURE DEC-30-1999 12:12:53 VALID DB2IFORM PROCEDURE DEC-14-1999 11:12:24 VALID
The LAST_DDL column is the date and time at which the last DDL change against the object was done. It shows that the order of compilation was:
PGADB2I PACKAGE (the specification) DB2IDRVM PROCEDURE (1st client application depending on PGADB2I) DB2IFORM PROCEDURE (2nd client application depending on PGADB2I) DB2IDRIV PROCEDURE (3rd client application depending on PGADB2I) PGADB2I PACKAGE BODY (a recompilation of the body)
Note that the recompilation of the body does not invalidate its dependent object, the specification, or the client application indirectly.
If your gateway is using the TCP/IP communication protocol, issue the following fro SQL*Plus:
SQL> column ddl_date format A22 heading 'LAST_DDL' SQL> select object_name, 2 object_type, 3 to_char(last_ddl_time,'MON-DD-YY HH:MM:SS') ddl_date, 4 status 5 from all_objects where owner = 'PGAADMIN' 6 order by object_type, object_name; OBJECT_NAME OBJECT_TYPE LAST_DDL STATUS ----------- ----------- -------------------- --------- PGTFLIP PACKAGE APR-24-03 03:04:58 VALID PGTFLIP PACKAGE BODY APR-24-03 03:04:02 VALID PGTFLIPD PROCEDURE APR-24-03 03:04:09 VALID
The LAST_DDL column is the date and time at which the last DDL change against the object was done. It shows that the order of compilation was:
PGTFLIP PACKAGE (the specification) PGTFLIPD PROCEDURE (client application depending on PGADB2I) PGTFLIP PACKAGE BODY (a recompilation of the body)
Note that the recompilation of the body does not invalidate its dependent object, the specification, or the client application indirectly.
You can also change the data structures or call exchange sequences of the remote host transaction. However, this kind of change is exposed to dependent client applications because the public datatypes or functions in the TIP specification will also change and necessitate recompilation, which in turn causes the Oracle server to recompile such dependent client applications.
If your gateway is using the SNA communication protocol, issue the following:
SQL> column ddl_date format A22 heading 'LAST_DDL' SQL> select object_name, 2 object_type, 3 to_char(LAST_DDL_TIME,'MON-DD-YY HH:MM:SS') ddl_date, 4 status 5 from all_objects where owner = 'PGAADMIN' 6 order by object_type, object_name; OBJECT_NAME OBJECT_TYPE LAST_DDL STATUS ---------- ----------- --------------------- --------- PGADB2I PACKAGE NOV-24-1999 09:09:13 VALID PGADB2I PACKAGE BODY NOV-24-1999 09:11:44 INVALID DB2IDRIV PROCEDURE DEC-30-1999 12:12:14 INVALID DB2IDRVM PROCEDURE DEC-30-1999 12:12:53 INVALID DB2IFORM PROCEDURE DEC-14-1999 11:12:24 INVALID
If your gateway is using the TCP/IP communication protocol, issue the following:
SQL> column ddl_date format A22 heading 'LAST_DDL' SQL> select object_name, 2 object_type, 3 to_char(LAST_DDL_TIME,'MON-DD-YY HH:MM:SS') ddl_date, 4 status 5 from all_objects where owner = 'PGAADMIN' 6 order by object_type, object_name; OBJECT_NAME OBJECT_TYPE LAST_DDL STATUS ---------- ----------- --------------------- --------- PGTFLIP PACKAGE APR-24-03 03:04:58 VALID PGTFLIP PACKAGE BODY APR-24-03 05:03:52 INVALID PGTFLIP PROCEDURE APR-24-03 05:04:29 INVALID
Note that the recompilation of the specification has invalidated its dependent objects, the three client applications in addition to the package body. To complete these changes, the body must be recompiled to bring it into compliance with the specification and then the three client applications could be compiled manually, or the Oracle server compiles them automatically as they are referenced.
If the client applications are recompiled by the Oracle server as they are referenced, there is a one-time delay during recompilation.
Recompilation errors in the client application, if any, are due to:
customer changes in the client application source
an altered PG DD definition for the TIP if the TIP has been regenerated
the wrong version being generated from multiple transaction entry versions saved in the PG DD if the TIP has been regenerated
If you make a mistake when you generate a tip (for example, if you alter a PG DD transaction definition, or if you've inadvertently specified the wrong version during regeneration), then the recompiled body will not match the stored specification; as a result, the Oracle Integrating Server would invalidate the specification and any dependent client applications.
You may have to regenerate and recompile the TIP and its dependent client applications to restore correct operation.
Refer to "Listing Dependency Management Information," in the Oracle Database Server Application Developer's Guide for more information.
