|
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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.