Re: GO SAVE - 21

i had this recently on a V7R2 box - in two outq, sometimes a single spoolfile
got damaged which stopped the Save21 (failure after QUSRSYS in BRMS).

Solution tip from IBM:

create new outq, copy all needed spool files, delete old outq.
They suppose it is an issue in the outq object and ask to
open a ticket if this happens.

-h

Am 19.08.2021 um 16:52 schrieb Rob Berendt <rob@xxxxxxxxx>:

Regular objects have an object damaged flag. However I cannot find it, and other priorities are calling me. Used to have to deal with this quite often. IDK if individual spool files have this. A casual glance did not show this in the sql services.

But the big problem was this object damaged flag was often off and not turned on until an attempt was made to save the object. It used to be bad enough on Management Central data queues that I would try to save these to a save file prior to a full system save just to delete the damaged ones to avoid the error in a full system save. After years of complaining and several releases of the OS IBM finally got that fixed and the data queues were no longer getting damaged.

The fact that the object damaged flag is not set until an attempt is made to save the object is documented somewhere.

Again, IDK if the same thing applies to spool file entries.