TPMC Exit Point RPG Procedure Error

TPMC Exit Point RPG Procedure Error


Scenario:

We are calling a Trading Partner Message Class Exit Point to copy data from one data set to another, after the data is translated.

Issue:

When EXTOL splits the data into the DB2 tables, an error occurs after translation. The error is due to pointer not being correctly set

EXTOL error message:



Message . . . . :   Pointer or parameter error (C G D F).
Cause . . . . . : RPG procedure EXTMV860 in program SHOPPE/EXTMV860 at
statement *INIT had an error due to a pointer not being correctly set. The
cause of the error is most likely one of the following:
-- A basing pointer was not set.
-- A procedure pointer was not set.
-- The pointer was set, but the object it referenced has been destroyed.
-- A parameter was not passed to the program containing the procedure.
-- A parameter was not passed to the procedure by its caller within the
program.
-- A pointer offset was greater than the size of the space the pointer was


Error Screenshot:


EXTOL EDI Integrator (EEI) TPMC Exit Point RPG Procedure pointer not being set correctly

Resolution:

User needs to update the Parm Type. If the value is a 1, change it to a 2; and vice-versa if the value is a 2.



EXTOL EDI Integrator (EEI) TPMC Exit Point change parma type




By: on
EXTOL Business Partner Logo

More EXTOL Examples

We have over 300+ examples of how EXTOL can be customized to meet your organization's needs

Each of our examples are free to review and use.