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