SeanHoppe.com > CLEO Tips > Cleo EDI Integrator How to Test EXTOL Long Parameter External Call Code Tables
How to Test EXTOL Long Parameter External Call Code Tables
16th July 2014
EXTOL EDI Integrator (EEI) allows users to develop external calls to be called via code tables. These external calls can use the short parm list (P1) or the long parm list (P2).
- CLICK HERE to see how to test an EEI External Call
- CLICK HERE to see more information on EEI External Calls
In a previous post (above) we showed how to test an EXTOL External Call. Here we will show how to test a Long Parameter (P2) External Call.
Note:Make sure all the interactive library list contains the correct LIBs for all objects being called, ie, RPG, physical files, logical files and etc.
In the example below we will be working with the code table called: EXT001.
For code tables using the long parameter list (P2), we might need to identify an inbound EDI (x12/EDIFACT) document to pass additional variables into our external call. In order to do this we will hit [F14].
After the correct document/log of message is selected, we will now be able to pass in variables such as:
- P3Tpcd - Trading partner code
- P3Msln - Message log number
- P3Mscl - Message class name
For more information on EXTOL EDI Integrator Tips and Hints
By: Sean Hoppe on