Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Read spool files in an OUTQ

395 views
Skip to first unread message

Falco

unread,
Apr 6, 2010, 10:42:56 AM4/6/10
to
I have a small task to save spool files after they print and then have
hem automatically delete after 10 minutes for certain OUTQs. I though
I could associate a DTAQ with the OUTQs and use the QRCVDTAQ API.
However doesn't the DTAQ only receive entries for new spool files that
enter a *RDY status?

I could do a WRKOUTQ OUTQ(QPRINT) OUTPUT(*PRINT), copy the spool file
to a PF and read the file deleting the appropriate spool files.

Does anyone know if there is a way to maybe read an OUTQ or anybetter
way of accomplishing this task?

Thanks

Message has been deleted

JTF

unread,
Apr 6, 2010, 11:27:34 AM4/6/10
to

there is a free tool DLTOLDSPLF....It may be what you are looking
for...
http://www.hkrebs.dk/dltoldsplf.html

Falco

unread,
Apr 6, 2010, 1:39:59 PM4/6/10
to
Thank You! That is it what I need.

CRPence

unread,
Apr 6, 2010, 2:55:47 PM4/6/10
to
Falco wrote:
> I have a small task to save spool files after they print and then
> have them automatically delete after 10 minutes for certain
> OUTQs. I though I could associate a DTAQ with the OUTQs and use
> the QRCVDTAQ API. However doesn't the DTAQ only receive entries
> for new spool files that enter a *RDY status?
>
> I could do a WRKOUTQ OUTQ(QPRINT) OUTPUT(*PRINT), copy the spool
> file to a PF and read the file deleting the appropriate spool
> files.
>
> Does anyone know if there is a way to maybe read an OUTQ or
> any better way of accomplishing this task?
>

IIRC a data queue entry is sent for any spool file which achieves
RDY status, regardless if that spooled file had already been tracked
for achieving RDY status in the past; i.e. I believe the *DTAQ would
receive an entry for any "old" spool file that attains RDY status.

I just verified on a v5r3 system that for a SPLF previously
tracked, then held, when it was released, a new message was enqueued
on the data queue for that same\old file.

There are spool APIs that should be able to list the spool files
and status of the spooled files on an *OUTQ. However without
something like the data queue entry to notify of a spooled file, any
moment when a list is generated [by API or WRKOUTQ spooled output]
could miss files that had already printed; i.e. unless the writer &
output queue were controlled in a manner to prevent that, for
example, by the application that would also list the spooled files.

Regards, Chuck

JTF

unread,
Apr 6, 2010, 3:23:25 PM4/6/10
to
On Apr 6, 1:39 pm, Falco <cwhit...@hotmail.com> wrote:
> Thank You!  That is it what I need.

No problem.....It hasn't been maintained for quite a while, but should
still work...

prasa...@gmail.com

unread,
Apr 22, 2013, 5:54:38 AM4/22/13
to
0 new messages