Re: QUSRSPLA

within a RPG you can use the printer file DS like this :

D DS_PRT          DS
D  PRT_LMAX             188    189B 0
Ligne OverFlow
D  PRT_Lcur             367    368B 0
Ligne en cours impr.
D  PRT_File             103    112
Fichier impression
D  PRT_Numf             123    124B 0
N° fichier Spoule
D  PRT_SplN              83     92
nom Spoule

I don't know any cmd usable directly, but the way (i think) is SPL API
The DAtaQ attched with an outq give you also the full name of a spool
(jobnam, jobnum, usram, splnam, splnum)

----- Original Message ----- 
From: "Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, August 11, 2005 6:17 PM
Subject: RE: QUSRSPLA


> So the catch is the Spool File Number. Is there an equivalent to RTVJOBA
> for spool files?
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard ECUYER
> Sent: Thursday, August 11, 2005 11:00 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: QUSRSPLA
>
>
>
> 1- QUSLSPL will list spool for you (by outq, user ...) into a userspace
> Just take the data from the userspace.
>
> 2- another solution (if you can), make a change in the PGm that make the
> spool to get the spl number.
>
> 3- Another one, add a dataQueue to the outq, and you will be able to get
> infos that you want.
>
> NB : you don't need internal spool or internal job, with qualified job
> and
> spool name and spool number it is ok.
>
> hope this help
>
> ----- Original Message ----- 
> From: "Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Thursday, August 11, 2005 5:42 PM
> Subject: QUSRSPLA
>
>
> > When calling QUSRSPLA, how can I obtain the following required
> > parameters:
> > - Internal Job Identifier
> > - Internal Spooled file Identifier
> > - Spooled File Number (in the program I am referring to *LAST), but
> this
> > wants a BINARY(4)
> >
> >
> >
> > -- 
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>