The following MQI calls have no equivalent procedures in the gateway because the Oracle database and the gateway automatically perform the functions of these MQI calls:

• MQBACK

  Transaction control is handled by the Oracle transaction coordinator. The Oracle application does not need to invoke a separate MQBACK call to undo the changes sent to WebSphere MQ.

• MQCONN

  A connection to a queue manager is established by the Oracle database and the gateway whenever an Oracle application refers to a gateway procedure. The database link name that is used when calling the gateway procedure determines which queue manager the gateway connects to.

• MQCMIT

  Transaction control is handled by the Oracle transaction coordinator. An Oracle application does not need to invoke a separate MQCMIT call to commit the changes sent to WebSphere MQ.

• MQDISC

  Connections to a queue manager are closed by the Oracle database and gateway. An Oracle application does not need to close the connection with the queue manager. Ending the current Oracle session or dropping the database link causes the queue manager connection to end.

They are:

• MQINQ

• MQPUT1

• MQSET

DG4MQ data types and RPC API prototypes are changed to meet the requirements of the gateway infrastructure.

When upgrading DG4MQ to Oracle 10g release 2 or higher, Oracle recommends that you install the newer version of DG4MQ on a separate development Oracle system. After you have finished with system configuration and testing, transfer all of the COBOL copy books and regenerate and recompile MIPs using the Oracle Visual Workbench. For customized codes, make necessary changes and recompile.

Migrating DG4MQ Releases 8 and 9 PL/SQL Applications

To migrate DG4MQ releases 8 and 9 PL/SQL applications:

1. In the PL/SQL declarative section, remove dblink references from the following DG4MQ data types:

   • PGM8.MQOD

   • PGM8.MQMD

   • PGM8.MQPMO

   • PGM8.MQGMO

   Then remove the following PGM8.MQ*RAW data types:

   • PGM8.MQODRAW

   • PGM8.MQMDRAW

   • PGM8.MQPMORAW

   • PGM8.MQGMORAW

2. In the PL/SQL declarative section, change the data type of the handle of the queue, the third argument of PGM.MQOPEN, from BINARY_INTEGER to PGM.MQOH and replace the package name PGM8 with PGM.

   Change the data type of the handles of the queue, the third argument of PGM.MQOPEN, from BINARY_INTEGER to PGM.MQOH.

   For example, for version 8 and 9 change the following data types to those listed for Oracle 10g:

   objdesc    PGM8.MQOD;
   msgdesc    PGM8.MQMD;
   putmsgopts PGM8.MQPMO;
   getmsgopts PGM8.MQGMO;
   hobj       BINARY_INTEGER;
   mqodRaw    PGM8.MQODRAW;
   mqmdRaw    PGM8.MQMDRAW;
   mqpmoRaw   PGM8.MQPMORAW;
   mqgmoRaw   PGM8.MQGMORAW;
   

   The data types for Oracle 10g release 2 and higher:

   objdesc     PGM.MQOD;
   msgdesc     PGM.MQMD;
   putmsgopts  PGM.MQPMO;
   getmsgopts  PGM.MQGMO;
   hobj        PGM.MQOH;
   

3. In the PL/SQL executable section, remove dblink references from the following DG4MQ procedures:

   PGM8.MQOPEN@dblink()
   PGM8.MQPUT@dblink()
   PGM8.MQGET@dblink()
   PGM8.MQCLOSE@dblink()
   

   Then define the dblink in the new PGM.MQOD type where the object queue name is defined.

   For example, for version 8 and 9:

   objdesc.objectname := 'QUEUE1';
   

   For Oracle 10g release 2 and higher:

   objdesc.objectname := 'QUEUE1';
   objdesc.dblinkname := 'dblink';
   

4. If necessary, change the package name PGM8 of all DG4MQ procedures to PGM.

   For example, for version 8 and 9:

   PGM8.MQOPEN@dblink();
   PGM8.MQPUT@dblink();
   PGM8.MQGET@dblink();
   PGM8.MQCLOSE@dblink();
   

   For Oracle 10g release 2 and higher:

   PGM.MQOPEN;
   PGM.MQPUT;
   PGM.MQGET;
   PGM.MQCLOSE;
   

5. In the PL/SQL executable section, remove all statements starting with PGM_UTL8.RAW_TO_*, remove all PGM_UTL8.TO_RAW statements, and replace all references to the MQ*RAW data types with their matching MQ* data types in the following DG4MQ procedures:

   • PGM.MQOPEN;

   • PGM.MQPU;

   • PGM.MQGET;

   • PGM.MQCLOSE;

   For example, for versions 8 and 9:

   mqodRaw := PGM_UTL8.TO_RAW(objdesc);
   PGM8.MQOPEN@dblink(mqodRaw, options, hobj);
   objdesc := PGM_UTL8.RAW_TO_MQMD(mqodRaw);
   mqmdRaw := PGM_UTL8.TO_RAW(msgdesc);
   mqpmoRaw := PGM_UTL8.TO_RAW(putmsgopts);
   PGM8.MQPUT@dblink(hobj, mqmdRaw, mqpmoRaw, putbuffer);
   putmsgopts := PGM_UTL8.RAW_TO_MQPMO(mqpmoRaw);
   msgdesc := PGM_UTL8.RAW_TO_MQMD(mqmdRaw);
   
   mqmdRaw := PGM_UTL8.TO_RAW(msgdesc);
   mqgmoRaw := PGM_UTL8.TO_RAW(getmsgopts);
   PGM8.MQGET@dblink(hobj, mqmdRaw, mqgmoRaw, putbuffer);
   getmsgopts := PGM_UTL8.RAW_TO_MQGMO(mqgmoRaw);
   msgdesc := PGM_UTL8.RAW_TO_MQMD(mqmdRaw);
   

   For Oracle 10g release 2 and higher:

   PGM.MQOPEN(objdesc, options, hobj);
   PGM.MQPUT(hobj, msgdesc, putmsgopts, putbuffer);
   PGM.MQGET(hobj, msgdesc, getmsgopts, getbuffer);
   

6. In PL/SQL executable section, remove all statements that reference the old MQ*RAW data types.

Migrating DG4MQ Release 4.0.1.*.* PL/SQL Applications

To migrate applications:

It also contains information about how the message is handled by the queue manager or by the receiving application. PGM.MQMD describes the attributes of the message being retrieved.

You can use the default values for PGM.MQMD fields or change the fields for your application requirements. For example, to change a field value, do the following:

mqmd.field_name := field_value;

where:

• mqmd is the PGM.MQMD object data type and it describes the attributes of the message being retrieved

• field_name is a field name of the PGM.MQMD object type definition. You can set as many fields as necessary. Refer to Table A-2 for field names and descriptions.

• field_value is the value to assign to field_name. You can specify a value or use a PGM_SUP constant to assign a value.

Use PGM.MQGMO to specify option and control information about how the message is retrieved from a queue. You can use the default values for PGM.MQGMO fields or change the fields for your application requirements. For example, to change a field value:

mqgmo.field_name := field_value

where:

• mqgmo is the PGM.MQGMO object data type, and it specifies option and control information about how the message is retrieved from a queue.

• field_name is a field name of the PGM.MQGMO type definition. You can set as many fields as necessary. Refer to Table A-3 for names and field descriptions.

• field_value is the value to assign to field_name.  You can specify a value or use a PGM_SUP constant to assign a value.

You can use the default values for PGM.MQOD fields or change the fields for your application requirements. For example, you can change a field value as follows:

mqod.field_name := field_value

where:

• mqod is the PGM.MQOD data type and specifies the object to open.

• field_name is a field name of the PGM.MQOD type definition. You can set as many fields as necessary. Refer to Table A-4 for field names and descriptions.

• field_value is the value to assign to field_name.  You can specify a value or use a PGM_SUP constant to assign a value.

It specifies option and control information for processing a message.

You can use the default values for PGM.MQPMO fields or change the fields for the application requirements. For example, to change a field value:

mqpmo.field_name := field_value

where:

• mqpmo is the PGM.MQPMO data type and specifies option and control information about how the message is processed and put into a queue.

• field_name is a field name of the PGM.MQPMO type definition. You can set as many fields as necessary. Refer to Table A-5 for field names and descriptions.

• field_value is the value to assign to field_name. You can specify a value or use a PGM_SUP constant to assign a value.

For example, the constant PGM_SUP.MQ_ACCOUNTING_TOKEN_LENGTH specifies that the maximum length for PGM.MQMD.ACCOUNTINGTOKEN is 32 characters.

MQ_ABEND_CODE_LENGTH         constant binary_integer :=  4;
MQ_ACCOUNTING_TOKEN_LENGTH   constant binary_integer :=  32;
MQ_APPL_IDENTITY_DATA_LENGTH constant binary_integer :=  32;
MQ_APPL_ORIGIN_DATA_LENGTH   constant binary_integer :=  4;
MQ_ATTENTION_ID_LENGTH       constant binary_integer :=  4;
MQ_AUTHENTICATOR_LENGTH      constant binary_integer :=  8;
MQ_CANCEL_CODE_LENGTH        constant binary_integer :=  4;
MQ_CLUSTER_NAME_LENGTH       constant binary_integer :=  48;
MQ_CORREL_ID_LENGTH          constant binary_integer :=  24;
MQ_CREATION_DATE_LENGTH      constant binary_integer :=  12;
MQ_CREATION_TIME_LENGTH      constant binary_integer :=  8;
MQ_DATE_LENGTH               constant binary_integer :=  12;
MQ_EXIT_NAME_LENGTH          constant binary_integer :=  128;
MQ_FACILITY_LENGTH           constant binary_integer :=  8;
MQ_FACILITY_LIKE_LENGTH      constant binary_integer :=  4;
MQ_FORMAT_LENGTH             constant binary_integer :=  8;
MQ_FUNCTION_LENGTH           constant binary_integer :=  4;
MQ_GROUP_ID_LENGTH           constant binary_integer :=  24;
MQ_LTERM_OVERRIDE_LENGTH     constant binary_integer :=  8;
MQ_MFS_MAP_NAME_LENGTH       constant binary_integer :=  8;
MQ_MSG_HEADER_LENGTH         constant binary_integer :=  4000;
MQ_MSG_ID_LENGTH             constant binary_integer :=  24;
MQ_MSG_TOKEN_LENGTH          constant binary_integer :=  16;
MQ_NAMELIST_DESC_LENGTH      constant binary_integer :=  64;
MQ_NAMELIST_NAME_LENGTH      constant binary_integer :=  48;
MQ_OBJECT_INSTANCE_ID_LENGTH constant binary_integer :=  24;
MQ_NAME_LENGTH               constant binary_integer :=  48;
MQ_PROCESS_APPL_ID_LENGTH    constant binary_integer :=  256;
MQ_PROCESS_DESC_LENGTH       constant binary_integer :=  64;
MQ_PROCESS_ENV_DATA_LENGTH   constant binary_integer :=  128;
MQ_PROCESS_NAME_LENGTH       constant binary_integer :=  48;
MQ_PROCESS_USER_DATA_LENGTH  constant binary_integer :=  128;
MQ_PUT_APPL_NAME_LENGTH      constant binary_integer :=  28;
MQ_PUT_DATE_LENGTH           constant binary_integer :=  8;
MQ_PUT_TIME_LENGTH           constant binary_integer :=  8;
MQ_Q_DESC_LENGTH             constant binary_integer :=  64;
MQ_Q_MGR_DESC_LENGTH         constant binary_integer :=  64;
MQ_Q_MGR_IDENTIFIER_LENGTH   constant binary_integer :=  48;
MQ_Q_MGR_NAME_LENGTH         constant binary_integer :=  48;
MQ_Q_NAME_LENGTH             constant binary_integer :=  48;
MQ_REMOTE_SYS_ID_LENGTH      constant binary_integer :=  4;
MQ_SERVICE_NAME_LENGTH       constant binary_integer :=  32;
MQ_SERVICE_STEP_LENGTH       constant binary_integer :=  8;
MQ_START_CODE_LENGTH         constant binary_integer :=  4;
MQ_STORAGE_CLASS_LENGTH      constant binary_integer :=  8;
MQ_TIME_LENGTH               constant binary_integer :=  8;
MQ_TRAN_INSTANCE_ID_LENGTH   constant binary_integer :=  16;
MQ_TRANSACTION_ID_LENGTH     constant binary_integer :=  4;
MQ_TP_NAME_LENGTH            constant binary_integer :=  64;
MQ_TRIGGER_DATA_LENGTH       constant binary_integer :=  64;
MQ_USER_ID_LENGTH            constant binary_integer :=  12;

Error Code -29400: Data Cartridge Error

This error code indicates that the MQI opcode implemented in DG4MQ fails. Refer to IBM WebSphere reference manual for information about the cause by looking up the opcode and its completion code and reason code.

MQI opcode failed. completion code=xxxx. reason code=xxxx.