RE: Retrieving Spool File Name in RPG

[Evan Harris <spanner@xxxxxxxxxx>]

This is pretty much what I had resigned myself to, however I will also be 
using the spool number and other data from the INFDS to ensure I get the 
correct spool file details - this will cater for those situations where 
more than one spool file is open for the job.

Cheers
Evan Harris

At 15:56 01/06/2000 +1200, you wrote:
>Jon,
>The QUSRSPL API can be used to populate a user space with a list of the
>spool files for the current job. The last entry will relate to the current
>spool file, and the corresponding data structure that is returned contains
>an element for the spool file name to which the printer file was overridden.
>Cheers,
>Peter Connell
>
>-----Original Message-----
>From: Jon Erickson [mailto:jerickson@800.com]
>Sent: Thursday, June 01, 2000 10:25 AM
>To: 'RPG400-L@midrange.com'
>Subject: RE: Retrieving Spool File Name in RPG
>
>
>It seems the SPOOLER, (QSPL) uses the name from the override/file spec to
>create the SPOOL File from its Spool Data Base File Members, (e.g.
>Q04079N005(Q874397369)).  I see the correct spool file number and library,
>but the name always comes up with Qxxxxxxxxx.  I'm on V4R4 behind 1-2 Cumes.
>
>Sorry,...
>Regards,
>Jon A. Erickson
>Sr. Programmer Analyst
>800.COM Inc.
>1516 NW Thurman St
>Portland, OR  97209-2517
>
>Direct: 503.944.3613
>Fax: 503.944.3690
>Web: http://800.com
>
>
>
>-----Original Message-----
>From: Evan Harris [mailto:spanner@ihug.co.nz]
>Sent: Wednesday, May 31, 2000 1:20 PM
>To: RPG400-L@midrange.com
>Subject: Re: Retrieving Spool File Name in RPG
>
>
>Barbara/Buck
>
>You both suggested the INFDS using:
>
> >   Spool file name:     103 - 112A
> >   Spool file library:  113 - 122A
> >   Spool file number:   123 - 124I 0
>
>The INFDS fields did not seem to retrieve what I was after. It appeared
>what they retrieved was actually the name of the printer file. I want to
>get the actual spool file name.
>
>Try this: prompt an OVRPRTF use command 10 and scroll through the choices.
>There is an option to override the spool file name. This overridden value
>does not appear to be returned via the INFDS.
>
>By the way, I did test to see if the Retrieve Overrides API would retrieve
>what I wanted. It wouldn't. I presume it's probably because the override is
>not a file override as such because only the spool file name has been
>changed.
>
>My problem, is that to create something generic that will allow me to
>change spool file attributes I need to retrieve the spool file name as
>pretty much all of the spool file commands require it.
>
>I had thought this would be relatively simple. It is easy enough to say
>that shop standards control this stuff (and they should) but shop standards
>do not provide absolute bullet proof assurances, especially when the shop
>has a history of sloppy practises.  If I supply a method, procedure or
>code, I want it to work under any circumstance, not be beholden to a "oh to
>be sure that works you have to...."
>
>Hope this explains my challenge further
>
>Thanks for the advice anyway ;)
>
>Regards
>Evan Harris
>
>+---
>| 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
>+---
>
>**********************************************************************************************************
>Privileged / Confidential Information may be contained in this message. If 
>you are not the addressee indicated in this message (or responsible for 
>delivery of the message to such person), you may not copy or deliver this 
>message to anyone. In such case, you should destroy this message, and 
>please notify us immediately.
>
>Please advise immediately if you or your employer does not consent to 
>Internet e-mail for messages of this kind. Opinions and other information 
>expressed in this message are not given or endorsed by my firm or employer 
>unless otherwise indicated by an authorised representative independent of 
>this message.
>+---
>| 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
+---