ED710 --> UADDMBX

I'm thinking it would probably be beneficial to define exactly what you mean by "started blowing up", including specific error-messages and any other related information that would be helpful in diagnosing your problem.

Error Message is below.  The issue I would like to resolve is actually updating the CL program correctly to use the UADDMBX API rather than the obsolete ED710 program.

                                                                               
Message ID . . . . . . :   RNQ0202       Severity . . . . . . . :   99        
Message type . . . . . :   Inquiry                                            
Date sent  . . . . . . :   07/21/15      Time sent  . . . . . . :   13:00:16  
                                                                               
Message . . . . :   The call to *LIBL/CED711 ended in error (C G D F).        
Cause . . . . . :   RPG procedure EM710NN in program EDI4XXPGM/ED710NN at      
  statement 2956 called program or procedure *LIBL/CED711, which ended in      
  error. If the name is *N, the call was a bound call by procedure pointer.    
Recovery  . . . :   Check the job log for more information on the cause of the
  error and contact the person responsible for program maintenance.            
Possible choices for replying to message . . . . . . . . . . . . . . . :      
  D -- Obtain RPG formatted dump.                                              
  S -- Obtain system dump.                                                    
  G -- Continue processing at *GETIN.                                          
  C -- Cancel.                                                                
                                                                       More...
Messages in joblog:

            Ownership of object M001F17AAA in QTEMP type *USRSPC changed.              
 Cannot resolve to object M001F17AAA. Type and Subtype X'1934' Authority    
   X'0000'.                                                                
 Function check. MCH3401 unmonitored by MED710 at statement *N, instruction
   X'0745'.                                                                
  21900 - RCLRSC                                                            
  22000 - RCVMSG RMV(*NO) MSGDTA(&MSGDTA) MSGID(&MSGID) RTNTYPE(&RTNTYPE)  
   MSGF(&MSGF) MSGFLIB(&MSGFLIB)                                            
  22400 - SNDPGMMSG MSGID(CPF9999) MSGF(*LIBL/QCPFMSG)                      
   MSGDTA(X'D4C3C8F3F4F0F1D4C5C4F7F1F04040404007450000072C5CD54040404040404
   040D4C5C4F7F1F0') MSGTYPE(*ESCAPE)                                      
 Function check. MCH3401 unmonitored by MED710 at statement *N, instruction
   X'0745'.                                                                
 Function check. CPF9999 unmonitored by ED710NN at statement 0000002956,    

Thanks for responding so quickly.

~sc

What OS version needs to be supported? Is UADDMBX a *PGM or a procedure? The CL can be easily supplied if we know those answers.

Tom

@Tom:  This is TrustedLink for iSeries version 6.3.2, according to the original post.  UADDMBX is a *PGM.  OS version is probably moot.

@Gary: Was thinking of potential CL niceties for data structures if the OS was V5R4 or later. That'd make the "single parm" cleaner. I haven't worked w/EDI in recent years, so don't know OS requirements for TrustedLink.

Tom

Good point.  I've been assuming this is an older system from the original post, but it could certainly be newer hardware/OS running older applications.  

I've got another client on V7R1 running S/36 environment code, so you sure can't tell from the applications.

@Gary and @Tom thanks so much for your assistance.  Gary I was able to update our CL to call UADDMBX with the correct parameters  - but some how our programs are looping back to the old programs and I get the CED711 errors.  Iam going to try debug this afternoon.  Tom this is an older model AS400 at OS V6R1.  This is just one of the obstacles we need to overcome to prepare for new hardware and V7R1 in the 4th quarter.  Again thanks
RPG-400-FORMATTED-DUMP.txt
ILE-RPG-FORMATTED-DUMP-EM710NN.txt

(Entire cl program in attachment. )

The OP mentions an attachment, but I haven't seen one for the CL. I know you have it "working", but it might help if we can review it if "looping" is somehow involved.

The dumps aren't useful without the source for the RPG programming. More useful would probably be the full sections of joblog surrounding the problem area.