The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact firstname.lastname@example.org.
I'm working on a System-Link POC and I have found the source for a program that does the standard XML parsing. It is USRLPI1R in source file #PSIMQSSMP in AMXLIBx. I have not used it yet, but I was interested in whether the "sessionHandle" and "workHandle" have a fixed length. With this "Procedure" it may resolve our problems. Have a look at it.
P O Box 786341, SANDTON, 2146, South Africa
Mobile: +27 (0)82 453 7990 | Fax: +27 (0)86 685 8284
E-mail: A.McKenzie@xxxxxxxxxxxxxxxxx | Skype: RhinoMcK
“To err is human; to forgive, divine.” Alexander Pope
Please consider the environment before printing this mail
1. XML-INTO - new to this... (Wyatt, Chris (FGWA-IL))
D* Local fields
D retField S N inz(*off)
D LoginResponse DS qualified
D Succeeded 10
// was the login request successful?
retField = *on;
I'm getting this error...
The XML document does not match the RPG variable; reason code 1.
Cause . . . . . : While parsing an XML document, the parser found that the
XML document does not correspond to RPG variable loginresponse and the
options do not allow for this. The reason code is 1. The exact subfield for
which the error was detected is loginresponse. The options are
"path=System-Link/LoginResponse case=any doc=string". The XML document name
is *N; *N indicates that the XML document was not an external file.
In the process of trial and error, I've also received reason code 4 and 5.
What am I doing wrong?!? I've messed with the path, the options, the DS. It's making me crazy.
Thank you for your help.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.