×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 10-Jun-2014 10:23 -0500, Charles Wilt wrote:
Why don't my QAUDJRN receivers have a valid save date and time yet
have a status of saved?
Journal . . . . : QAUDJRN Library . . . . : QSYS
Threshold (K) . : 1500000 Size (K) . . . . : 200900
Attach date . . : 12/28/13 Attach time . . : 05:06:07
Detach date . . : 01/04/14 Detach time . . : 04:47:47
Save date . . . : 00/00/00 Save time . . . : 00:00:00
Auxiliary storage pool . . . . . . . . . . . : 1
Status . . . . . . . . . . . . . . . . . . . : SAVED
I'm on v7.1 TR 7
Objects saved with Save System (SAVSYS) do not have that "save
history" portion of the Object Information Record (OIR) updated. This
is primarily for performance reasons; i.e. effectively, the request to
save QSYS is made with Update History (UPDHST) specified as *NO.
To get that information updated for the noted object [or other
objects in QSYS], a Save Object (SAVOBJ) [or equivalent] would have to
be performed. That would not be very helpful nor appropriate,
generally, for a proper B&R setup. So...
More likely of interest, is that the historical reflection of the
"save history" effects of the SAVSYS request, are made available for
review via the QSAVSYS *DTAARA object in QSYS. That is, the following
request would reflect when the QAUDJRN *JRN object in QSYS was saved
with a SAVSYS; the information presented under the heading of
"Save/Restore information":
DSPOBJD QSYS/QSAVSYS *DTAARA *FULL
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
