× 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 support@midrange.com.


  • Subject: QSYSINC not in V3R7M0 what to do?
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Mon, 02 Oct 2000 17:37:48 -0500
  • Organization: Pacer International

I'm attempting to write an API interface for the QSPRWTRI API.  So far I have 
coded the
parameter specs, but then I get to the Error Code which is a pointer character 
to an error
structure.  Reading the manual on the API points me to "Error Code Parameter" 
in the System
API Reference.  Going there, there are 2 possible structures that can be 
returned, and to
make it even more fun, yet another character pointer the the Exception data is 
used.

One of the possible error returns is 17 bytes long, the other is 36 bytes long 
(I believe,
if a pointer character is 4 bytes long).  To make things easy, IBM provides a 
/COPY member
QUSEC in QRPGLESRC in QSYSINC which, of course, does not come with V3R7M0.

If possible I would like to get a copy of this structure without violating 
IBM's copyright
on the source code.  Barbara, Hans, any solutions?  Or am I just going to have 
to write it 
from scratch?

Regards,

Jim Langston
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.