Re: How the SQL Server World Lives

That makes sense except I'm a little confused because you said

"Object Information Record (OIR) which is separate part of the composite *LIB object"

and then

"is not an update to the headers of the objects, not even the *LIB object."

So if the OIR is a part of the composite *LIB object, then how can the *LIB object not be updated?

On 1/30/2013 12:42 PM, CRPence wrote:

On 30 Jan 2013 10:10, Peter Dow wrote:

What about this information (seen with DSPOBJD)?

Save/Restore information:
Save date/time . . . . . . . . . . . : 01/27/13 18:43:14
Restore date/time . . . . . . . . . : 12/12/97 14:23:22
Save command . . . . . . . . . . . . : SAVLIB
Device type . . . . . . . . . . . . : Tape
Sequence number . . . . . . . . . . : 83
Volumes . . . . . . . . . . . . . . : DAILY
File label ID . . . . . . . . . . . : GLCONVERT
Save format . . . . . . . . . . . . : Serial

Isn't this stored in the object header? Doesn't the save process update it?

On 1/30/2013 9:04 AM, CRPence wrote:

<<SNIP>> Even the /update history/ which, if included, is written
in a separate location from the object; i.e. in the OIR, and after
the object is saved. <<SNIP>>

That is the /history/ information [UPDHST(*YES)] that is in the
Object Information Record (OIR) which is separate part of the composite
*LIB object, and that is updated after the save of the object. The
update is to the *OIRS [OIR space] object only. So as part of a SAVLIB
the saved library object with its OIR will save the unchanged image;
i.e. the image before a change to update the history. However, the
write activity for that history will be before the SAVLIB request
returns control to the user; that is post-save [from the perspective of
the OS] and optional [as requested by the user], and is not an update to
the headers of the objects, not even the *LIB object.