|
On Tue, 1 Jul 2003 WyvernGod@xxxxxxx wrote: > > ok this is my question.. well one of a couple questions.... I'm trying > to find informaton on how to get a list of the outq's and the spool > files in each one and then the info on each spool file aka job number > file number user data(a must have for what i'm doing) and all that other > stuff.. A friend said he;s seen it done in rpg but soemoen else said > the best way was cl both useing api's so anyway.. if anyone can give me > some insight as to what to do or where to ask just let me know... Do you really have wyvern's that worship you? I'd recommend doing this in RPG using APIs. It would be much more difficult to use the same APIs in CL, since APIs generally work best if you use pointers/offsets to access the structures. Doing it in CL would be more difficult, and would require very careful design to avoid hard-coding offsets (which could break upward compatability) > > my gold is to take selected spool files and convert them into physical > files.. somethign i can already do.. > Using CPYSPLF or QwpzHostPrintTransform()? I find that the latter does a better job, but the former is certainly easier to use. > just my problem is geting a set list of all the files and their info so > i "can" do it automaticly The QUSLSPL API is probably all you need. This API can be used to list just the spooled files for a given queue, or to list all of the spooled files on the system, etc... That API returns the results in a user space, which you can then process in your RPG program. If you need to know more about each file, the QUSRSPLA API can be used to get specifics about each spooled file, and finally, you can use QCMDEXC to run the CPYSPLF command if that's what you elect to use. If you're new to APIs and need an example, just ask...
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.