Re: The problem with SAVCHGOBJ . . .

CRPence wrote:

- Consider /enhancing/ the CRTLIB instead; e.g. to either issue or schedule a SAVLIB.? Rather than intercepting the CL command
CRTLIB, activating the save could be in response to some object
auditing; e.g. T-CO entry for the object type *LIB.

- Another relatively simple approach is to, just before the SAVCHGOBJ request, list the object details of the *LIB objects target of the upcoming SAVCHGOBJ request, e.g. from the request to:

DSPOBJD *N/*ALLUSR *LIB *FULL
OUTPUT(*OUTFILE) OUTFILE(QTEMP/ODUSRLIBS)

And then e.g.

SELECT ExecCmd('SAVLIB ' CONCAT ODOBNM CONCAT SavlibParms())
FROM QTEMP/ODUSRLIBS
WHERE ODSDAT=''

The given SELECT alludes to effecting, after having issued within
the job CRTSAVF QTEMP/NULLSAVF, something like:

SAVLIB EachUnSavedLibNam *SAVF SAVF(QTEMP/NULLSAVF)
CLEAR(*ALL) UPDHST(*YES) OMITOBJ((*ALL *ALL))

<<SNIP>>

Hmmm, I noticed the second approach in my above quoted reply had incorrectly combined two concepts. The SAVLIB omitting all objects and saving into a temporary save file would be used only for a timely request to effect save-after-CRTLIB merely to establish a saved-date; saved into a temporary save file as a /trick/ to enable objects to be saved in an upcoming SAVCHGOBJ request, regardless that no legitimate save of the library had ever transpired. With that however, the caveat that a DR would need to pre-create the library for a restore from the save-changed media, since the libraries of saved objects had never been saved and thus would not [yet] have been restored.

The SAVLIB in the second approach should instead be a typical save of the library, with its intended effect to /replace/ the upcoming SAVCHGOBJ activity against the same library name; i.e. the SAVLIB request should include all objects by OMITOBJ(*NONE), and probably use the same media of the upcoming save-changed activity. In so doing, the media that will be used for the SAVCHGOBJ will have the SAVLIB requests preceding the upcoming SAVCHGOBJ which will not include any objects from those libraries because they have just been saved. The DR would then have a saved library activity from which a RSTLIB is performed before any RSTOBJ from any later save-changed activity.

Regards, Chuck