Re: Save Outq -Contents- to tape (was re: trimming trailing blanks in spooled output...)

GO SAVE has preset options, in which GO SAVE 21 gets the most stuff.
GO RESTORE options are the opposite, to recover corresponding menu collection

SAVOBJ  OBJ(OUTQ1  OUTQ2)  LIB(QGPL)  DEV(*SAVF)  OBJTYPE(*OUTQ)
SAVF(yourlib/yoursavf)  SPLFDTA(*ALL)

Michael--

The only difference between saving the definition of an output queue
and saving its contents is the  SPLFDTA({*ALL|*NONE})  parameter.

This example uses a *SAVF; you can only save objects from a single
library in a *SAVF.

If you use SAVLIB to tape you can specify SPLFDTA(*YES) as well, and
save the libraries, output queues, as well as the -contents- of the
output queues!

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx


>I said:
>
>  > If you're on v5r4, you can now save the -contents- of an output queue!
>  > This will let you use SAVOBJ and write the output queues concerned to
>>  tape!  Chances are, they never really -look- at the reports from over a
>  > year ago, so maybe you can sneak them onto tape while no one's looking!
>
>Michael asked:
>
>Would you mind posting an example of a SAVOBJ command for backup up reports
>from specific outqueues to tape? Thanks for your response.
--
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.