|
Dave Leland wrote: >This entire discussion started with >you wanting a SAV/RST function >from IBM (see subject line), and >claiming that IBM should be able >to easily do it. Ken Graap started the thread. I chipped in with reply number 22... Honest! >I was countering that by making the >statement that it would not be that easy >if done right. I completely concur. Your points about restoring the job structure (which is what the spooled files are a part of) are something to ponder. >Now your part of the discussion has >turned into something entirely different. >What do you really want/need? A >SAV/RST function or a spool file >archiving function with all the >capabilities you discuss below? I'm in favour of a spool file extract function; one which is similar to a SAV, but allows the programmer access to the datastream. It isn't completely different - see below. >I assure that what you are asking for >would never be included in a >SAV/RST function that IBM provided. Again, I agree with you. Ken's original note was (in part) "To start off the discussion.... I was asked for an opinion by IBM and passed along the following after thinking about it for a few minutes...." I chipped in my thoughts when the discussion moved toward "why not use CPYSPLF or the existing APIs?" As is all to normal for me, I wasn't clear in what I was trying to get across. Let me try one more time, then I'll be quiet (promise!) SAV/RST spooled file. Why? 1) Moving to a different physical system/disk array and don't want to lose the contents of the OUTQ's. 2) Want to take existing spooled output and "do something" with it programmatically (email/FAX/HTML-ise/send to spreadsheet) Ken's note directly addressed number 1: "The current limitation with recovery though is the losing of some of the original attributes of the spool file since the spool files aren't really restored, they are recreated. This is the main problem I'd like to see a base OS SAV/RST function for spool files address... " I am trying to address number 2 - program access to spooled file data. I can use a program to "read" database files, data areas, user spaces, device descriptions, file descriptions, etc. Everything except AFP spooled files. It really isn't that important I guess, since nobody else chimed in with a similar need. And that's a good enough reason for me to end my part of the discussion. Thanks for all your insights Dave - and your patience! I'm sorry to have tied up the list with this. Buck Calabro Aptis; Albany, NY "We are what we repeatedly do. Excellence, then, is not an act, but a habit." --Aristotle Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.