|
Uh, concern here: you can't just restore the PF's in QSPL and expect things to work. There's ALOT more majic going on under the covers and you really have to in effect deal with them on a member by member basis with some special processing. Please don't think you can just do a sav/rstobj of the PF's and you're covered....not so! Don in DC On Tue, 25 May 2004, Colin Williams wrote: > Jim, > > possibly as important as backing up the spooled file data to a physical > file, is creating an index entry somewhere for that spooled file that > records the information that you require in the unlikely event of a restore. > You dont know you need it, till you need it. > > cheers > Colin.W > > > > ----- Original Message ----- > From: "Jim Damato" <jdamato@xxxxxxxxxxxxxxxxx> > To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> > Sent: Tuesday, May 25, 2004 1:15 AM > Subject: RE: How to save an Outq > > > > It's been said a few times, but it bears repeating. A spool file is a > > component of a job. Once a job is gone from the system it's gone. In > order > > to restore a spool file you have to deal with the issue of which job it > > belongs to upon restore. The various tools for saving and restoring > spooled > > output reconcile the problem using different methods. > > > > On some other platforms a spool is a temporary file/image used to buffer > > print information as a report is processed from the system to the printer. > > On the System 38, AS/400 etc. the spool file became a more permanent file > > carried along with the job that generated it. It was still meant to be a > > somewhat temporary "object". > > > > I've had to deal with criticism from those folks unaccustomed to the > AS/400. > > Many would complaint that VMS, Unix, etc. allowed you to save report file. > > I've tried to point out that on many Windows client apps the report is a > > temporary object, and the data is what's important. Selecting File/Print > on > > many client/app/server architectures generates a direct-to-print stream. > > Saving the printed output is an option, but not the default. > > > > Even though I've had to implement Broderick Spool Organizer everywhere I > go, > > I'm a strong proponent of not developing a dependency on spool files. > Most > > anything you need to save for reprint should be saved as data in a > database. > > > > -Jim > > > > -----Original Message----- > > From: Graap, Ken [mailto:keg@xxxxxxxxxxxxx] > > Sent: Monday, May 24, 2004 3:02 PM > > To: 'Midrange Systems Technical Discussion' > > Subject: RE: How to save an Outq > > > > > > Don - I'd bet that they will in V5R4 of i5/OS.... > > > > Kenneth > > > > -----Original Message----- > > From: Don [mailto:dr2@xxxxxxxxxxxx] > > Sent: Monday, May 24, 2004 12:02 PM > > To: Midrange Systems Technical Discussion > > Subject: Re: How to save an Outq > > > > > > > > > > Can someone refresh me as to the reason why Rochester doesn't allow SPLF > > save/restore? > > > > Don in DC > > > > _______________________________________________ > > 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 e-mail has been sent by a company of Bertram Group Ltd, whose registered > office is 1 Broadland Business Park, Norwich, NR7 0WG. > This message, and any attachments, are intended solely for the addressee and > may contain privileged or confidential information. If you are not the > intended recipient, any disclosure, copying, distribution or any action taken > or omitted to be taken in reliance on it, is prohibited and may be unlawful. > If you believe that you have received this email in error, please contact the > sender immediately. Opinions, conclusions and statements of intent in this > e-mail are those of the sender and will not bind a Bertram Group Ltd company > unless confirmed in writing by a director independently of this message. > Although we have taken steps to ensure that this email and any attachments > are free from any virus, we advise that in keeping with good computing > practice the recipient should ensure they are actually virus free. > > _______________________________________________ > 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. >
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.