RE: QGYOLSPL & QGYGTLE APIs

Thanks, Carsten.

After posting the message and looking through the API a bit,
I realized I was thinking in RPG III terms and not ILE terms.
Then I realized the same thing you stated, that these were
two separate parameters and C would see them as two separate
pointers, so it wasn't a problem.

Hmm.. That is an idea I hadn't thought of, of attaching a
Data Queue to the output queue and have a job read records
from the Data Queue.  That would actually be a lot simpler
than the way I am going about it.  I think I might go that
route, especially since I've written and read records to/from
a data queue before.

Thanks.

Jim Langston

-----Original Message-----
From: Carsten Flensburg [mailto:flensburg@novasol.dk]
Sent: Saturday, October 20, 2001 2:59 AM
To: rpg400-l@midrange.com
Subject: Re: QGYOLSPL & QGYGTLE APIs


Hello Jim,

The receiver variable and receiver variable length are 2 individual
parameters and as such passed as 2 individual addresses (pointers) - as
opposed to a structure having a number of subfields and passed as a single
address.  To know how much storage it is safe to reference for the first
parameter the QGYOLSPL API will simply resolve the integer value referenced
by the second parameter.

To monitor an output queue you could also attach a data queue (see the DTAQ
parameter on the CHGOUTQ command) and have a job waiting on the data queue
to process the spooled files as they hit the output queue and enters the RDY
status. HLD spooled files won't show up in the data queue though, to catch
those the API approach is required.

Best regards,
Carsten Flens