The following steps describe the Windows-to-mainframe communications process illustrated in Figure 1-3 when your communication protocol is SNA to communicate between the gateway and the mainframe:

Follow these steps to write a TIP.

Step 1    Create a control file:

The user writes the control files. The control file has four main types of PGAU commands:

1. DEFINE DATA. This is used to define input and output fields, using COBOL data definitions.

   • Sample define data:

     define data empno plsdname(empno) usage(pass) language(ibmvscobolii)
                       infile("empno.cob");
     

2. DEFINE CALL. This is used to define PL/SQL functions calls to be generated as part of the package.

   • Sample define call:

     define call db2imain pkgcall(pgadb2i_main) 
                          parms((empno in),(emprec out));
     

3. DEFINE TRANSACTION. This is used to group the preceding functions and specify other parameters on which the TIP depends.

   • Sample define transaction:

     define transaction db2i call(db2imain,db2idiag)
                             sideprofile(CICSPGA) 
                             tpname(DB2I)
                             logmode(oraplu62)
                             synclevel(0)
                             nls_language("american_america.we8ebcdic37c");
     

4. GENERATE. This is used to generate the TIP specification files from the previously stored data, call, and transaction definitions.

   • Sample generate transaction:

     generate db2i pkgname(pgadb2i) pganode(pga) outfile("pgadb2i");
     

Step 2   Execute the control file within PGAU

Running the control file within PGAU will create PG DD entries for the data, call, and transaction definitions, and will generate the specification files (For example, pgadb2i.pkh and pgadb2i.pkb):

For Microsoft Windows:

C:\> pgau
PGAU> CONNECT<userid>/<password>@<database>_specification_string>
PGAU> @pgadb2i.ctl

For UNIX based systems:

$ pgau
PGAU> CONNECT<userid>/<password>@<database>_specification_string>
PGAU> @pgadb2i.ctl

Step 3   Execute the specification files

Running the specification files will create the PL/SQL stored procedures. Note that the header specification file (for example, pgadb2i.pkh) must be run first:

For Microsoft Windows:

C:\> sqlplus<userid>/<password>@<database_specification_string>
SQL> @pgadb2i.pkh;
SQL> @pgadb2i.pkb;

For UNIX based systems:

$ sqlplus<userid>/<password>@<database_specification_string>
SQL> @pgadb2i.pkh;
SQL> @pgadb2i.pkb;

Step 4   Create a driver procedure to run the TIP

The TIP is now ready for use. For convenience, it will usually be called using a driver procedure (for example, db2idriv). This driver will then call the individual stored procedures in the correct order. Create the driver procedure and run it:

For Microsoft Windows:

C:\> sqlplus <userid>/<password>@<database_specification string> 
SQL> @pgadb2id.sql
SQL> execute db2idriv('000320');

For UNIX based systems:

$ sqlplus <userid>/<password>@<database_specification string> 
SQL> @pgadb2id.sql
SQL> execute db2idriv('000320');

The following steps describe the communications process, as illustrated in Figure 1-4 when your communication protocol is TCP/IP:

Figure 1-4 illustrates the communications process described in the previous Steps 1 through 5.

Figure 1-4 Communication Between Oracle Database and Mainframe, Using TCP/IP

Description of "Figure 1-4 Communication Between Oracle Database and Mainframe, Using TCP/IP"

Follow these steps to write a TIP.

Step 1    Create a control file:

The user writes the control files. The control file has four main types of PGAU commands:

1. DEFINE DATA. This is used to define input and output fields, using COBOL data definitions.

   • Sample define data:

     define data flipin plsdname(flipin) usage(pass) language(ibmvscobolii)
     (
       01 msgin pic x(20).
     )
     
     define data flipout plsdname(flipout) usage(pass) language(ibmvscobolii)
     (
       01 msgout pic x(20).
     )
     

2. DEFINE CALL. This is used to define PL/SQL functions calls to be generated as part of the package.

   • Sample define call:

     define call flipmain pkgcall(pgtflip_main) 
                          parms((flipin in),(flipout out));
     

3. DEFINE TRANSACTION. This is used to group the preceding functions and specify other parameters on which the TIP depends.

   • Sample define transaction:

     define transaction imsflip call(flipmain)
                             sideprofile(pgatcp) 
                             tpname(flip)
                             nls_language("american_america.us7ascii");

     Note:

     On a gateway using TCP/IP, the side profile name value is actually the TCP/IP unique name that was defined when the user specified the value, host name, port number and many other IMS Connect values during configuration of the network.

4. GENERATE. This is used to generate the TIP specification files from the previously stored data, call, and transaction definitions.

   • Sample generate transaction:

     generate imsflip pkgname(pgtflip) pganode(pga10ia) outfile("pgtflip") diagnose(pkgex(dc,dr));

Step 2   Execute the control file within PGAU

Running the control file within PGAU will create PG DD entries for the data, call, and transaction definitions and will generate the specification files (for example, pgtflip.pkh and pgtflip.pkb):

For Microsoft Windows:

C:\> cd %ORACLE_HOME%\dg4appc\demo\IMS
C:\> pgau
PGAU> CONNECT userid/password@database_specification_string
PGAU> @pgtflip.ctl

For UNIX based systems:

$ pgau
PGAU> CONNECT userid/password@database_specification_string
PGAU> @pgtflip.ctl

Step 3   Execute the specification files

Running the specification files will create the PL/SQL stored procedures. Note that the header specification file (for example, pgtflip.pkh) must be run first:

For Microsoft Windows:

C:\> sqlplus userid/password@database_specification_string
SQL> @pgtflip.pkh;
SQL> @pgtflip.pkb;

For UNIX based systems:

$ sqlplus userid/password@database_specification_string
SQL> @pgtflip.pkh;
SQL> @pgtflip.pkb;

Step 4   Create a driver procedure to run the TIP

The TIP is now ready for use. For convenience, it will usually be called using a driver procedure (for example, pgtflipd). This driver will then call the individual stored procedures in the correct order. Create the driver procedure and run it:

For Microsoft Windows:

C:\> sqlplus <userid>/<password>@<database_specification string> 
SQL> @pgtflip.sql
SQL> execute pgtflipd('hello');

For UNIX based system:

$ sqlplus <userid>/<password>@<database_specification string> 
SQL> @pgtflip.sql
SQL> execute pgtflipd('hello');