× 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: Re: API receiver variable limit
  • From: Mel Rothman <melrothman@xxxxxxxx>
  • Date: Thu, 28 Sep 2000 15:04:25 -0500

Buck, my experience has been that the compiler always stores the occurrences one
after the other.  If this still makes you nervous, you could allocate storage
for indField dynamically.  For example:

D indField        s          32767    based(indField@) 
C                   alloc     64000             indField@
C                   call      'QDBRTVFD'          
C                   parm                    indField
...

IndField does not have to be 32767.  Make it as big as the biggest piece you
will be processing at a time, using a work pointer.

Nah, don't use C.


Mel Rothman


Buck Calabro wrote:
> 
> Hello!
> 
> I'm writing a boilerplate for QDBRTVFD (Retrieve file description API).  The
> maximum RPG IV string size is 32kb.  The FILD0200 request for a particular
> file is returning 49kb of data.  I've used a multiple occurrence data
> structure and a based pointer to move an internal data structure around
> (which works), but can I rely on the compiler always storing the occurrences
> one after the other (to form one block of contiguous API populated memory?)
> Is there a better way? (I hope so!)  Should I use C? (sigh)
> 
> D indField        s          32767    based(indField@)
> D indField@       s               *
> D QDBRV           ds         32767    occurs(2)
> C                   call      'QDBRTVFD'
> C                   parm                    QDBRV
> ...
> C                   eval      indField@ = %addr(QDBRV) + fieldOffset
> 
> Buck Calabro
> Aptis; Albany, NY
> "We are what we repeatedly do.
>  Excellence, then, is not an act, but a habit." --Aristotle
> 
> Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
> +---
> | 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
> +---
+---
| 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 ...

Replies:

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.