Re: QGYOLSPL & QGYGTLE APIs

["Carsten Flensburg" <flensburg@xxxxxxxxxx>]

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 Flensburg




----- Original Message -----
From: <rpg400-l-admin@midrange.com>
To: <rpg400-l@midrange.com>
Sent: Friday, October 19, 2001 11:51 PM
Subject: QGYOLSPL & QGYGTLE APIs


> But, since the Receiver Variable is the first paramenter, and the length
of
> the receiver variable is the second paramenter, I'm thinking this won't
> work.
> How is the API call going to know where to find the length of the receiver
> variable since it does not know how far down to look for it, and if it did
> have some way to know how far down to look for it, It wouldn't be needed
> anyway!