Re: SAVOBJ *OUTQ Results in multiple items in *SAVF

.
I was informed by a developer for save/restore that the noted outcome is working as designed (WAD), and indeed the condition is related to the number of spool files that are _in_ the output queue when the save is performed. Additionally, a reference to that part of the design is noted in the APAR SE28660 which can be searched on the IBM Service website. That APAR provides a recent fix for a problem restoring from such output queues. The specific text from the APAR relating to the condition seen:
... large output queues were saved, and some of the large
output queues are not restored. For the purpose of this problem,
a _large output queue_ is defined as one which had its spooled
files divided into multiple groups when it was saved. A large
output queue is listed more than once when the save/restore
media is displayed (DSPTAP, DSPSAVF, or DSPOPT) to OUTPUT(*).

Regards, Chuck
-- All comments provided "as is" with no warranties of any kind whatsoever.

PaulMmn wrote:

I ran a SAVOBJ command to save an Output Queue to a Save File.

SAVOBJ OBJ(METASENT2) LIB(QGPL) DEV(*SAVF) OBJTYPE(*OUTQ) SAVF(ARCHIVES/METASENT) SPLFDTA(*ALL)

I ended up with multiple items in the Save File:

+-------------------------------------------------------------------
| Display Saved Objects | | Library saved . . . . . . . : QGPL | | Type Options, press Enter. | 5=Display | | Opt Object Type Attribute Owner Size (K) Data | METASENT2 *OUTQ HQPGPEM 217420 YES | METASENT2 *OUTQ HQPGPEM 290052 YES +--------------------------------------------------------------------

The part that has be baffled is why I ended up with multiple objects in the *SAVF!!

Could it be related to the 11,037 spooled files that were in the output queue?

Inquiring minds want to know!

Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx