ED710 --> UADDMBX

I work for a company that has legacy systems (1990's early 2000's).  I was recently tasked with applying Trusted Link upgrade 6.3.2 on the Test partition. Immediately our program that sends 850's started blowing up.  Placing a call to TLi(Open Text) only resulted with them informing me th program ED710 has long been obsolete and was replace by an API UADDMBX or command ADMBX.  The were unable to tell me how to make the replacement within our programs.  This is the code within our CL that is now in error:  (Entire cl program in attachment. )  

0121.00 /* Move from APLUS into Trusted Link Transaction Center             */  
0122.00 /*------------------------------------------------------------------*/  
0123.00                                                                        
0124.00              CHGVAR     VAR(&DATA) VALUE(*BLANKS)                      
0125.00                                                                        
0126.00              /* DOCUMENT ID */                                          
0127.00              CHGVAR     VAR(%SST(&DATA 16 3)) VALUE('850')              
0128.00              /* DOCUMENT TYPE */                                        
0129.00              CHGVAR     VAR(%SST(&DATA 22 2)) VALUE('PO')              
0130.00              /* DOCUMENT SWITCH */                                      
0131.00              CHGVAR     VAR(%SST(&DATA 24 1)) VALUE('Y')                
0132.00              /* USER FILE DEFINITION NUMBER */                          
0133.00              CHGVAR     VAR(%SST(&DATA 65 3)) VALUE('000')              
0134.00              /* USER FILE DEFINITION NAME */                            
0135.00              CHGVAR     VAR(%SST(&DATA 211 5)) VALUE('EO850')          
0136.00                                                                        
0138.00              CALL       PGM(CED710) PARM(&DATA)    

I anyone can remember going through this change so many years ago - I would vey much appreciate help in converting our CL program to use the new API or just the command to add the document to the mailbox.

Proudly bringing you North America's best-selling
MCI coaches and Europe's top luxury brand, Setra.
Stephanie Cox
MCS Programmer/System
Adm-Sr Motor Coach Industies
Motor Coach Industries
7001 Universal Coach Drive
Louisville, KY 40258
Office: 502-318-3211
E-Mail: Stephanie.Cox@mcicoach.com
www.mcicoach.com
www.setra-coaches.com
scox34Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave FordSoftware Developer / Database AdministratorCommented:
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.
0
scox34Author Commented:
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
0
Gary PattersonVP Technology / Senior Consultant Commented:
Stephanie, the format of the parameters for the UADDMBX API call is documented in the TLI API Reference Manual.  You should have this as a component of your TLI documentation, or you should be able to get a copy from GXS.  

There are only two required subfields:

UADDMBX, Parameter 1:

Positions 1-3       Input   Packed (5,0)   Parameter length        Required
Positions 4-13      Input   Char (10)      User file definition name   Required

So if you pass x'00015F' + 'EO850     ' as the first parameter, that should add everything in your EO850 file to the mailbox.  First 3 bytes contain packed number 15, for the total  length of the parameter being passed, and the next 10 bytes contain the user file definition name.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

tliottaCommented:
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
0
Gary PattersonVP Technology / Senior Consultant Commented:
@Tom:  This is TrustedLink for iSeries version 6.3.2, according to the original post.  UADDMBX is a *PGM.  OS version is probably moot.
0
tliottaCommented:
@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
0
Gary PattersonVP Technology / Senior Consultant Commented:
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.
0
scox34Author Commented:
@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
0
tliottaCommented:
(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.
0
Gary PattersonVP Technology / Senior Consultant Commented:
When TrustedLink completes the UADDMBX API, it runs the Add-to-Transaction Center Session Exit Programs, if any exist.  Other exit programs are called at other points in document processing.

The TrustedLink Application Program and Interface Guide explains the various exit points that are available.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IBM System i

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.