×
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.
FWiW [re Save option-21, specifically about the DSPOBJD "last save
date, time, and location information not being updated for the QSYSOPR
*USRPRF object], the Save Entire System feature uses the CL command
SAVSYS to effect\include the equivalent of the separate requests to
SAVCFG and SAVSECDTA, rather than performing those requests separately
[to produce media that can be installed from directly]. There is no
"Update History" (UPDHST) parameter on the SAVSYS command [like there is
on many other SAVxxx commands]to enable making a choice about the
behavior of the command, whether the save history is updated\recorded.
The Save System (SAVSYS) command, for performance reasons, does not
update the save history information of every system object it saves.
Instead the command updates a separate object to record the /history/ of
the effect [three separate *DTAARA objects], after the completion of the
request:
_i Save System (SAVSYS) i_
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/cl/savsys.htm
"The Save System (SAVSYS) command saves a copy of the Licensed Internal
Code and the QSYS library in a format compatible with the installation
of the operating system. It does not save objects from any other
library. In addition, it saves security and configuration objects that
can also be saved using the Save Security Data (SAVSECDTA) and Save
Configuration (SAVCFG) commands.
To save the system data on offline storage, the system writes a copy of
the objects onto the media. The libraries and objects are not affected
on the system. This command cannot be used to free any space occupied by
these objects. The history information for the data area QSAVUSRPRF in
QSYS is updated with the date, time, and place where user profiles are
saved. The history information for the data area QSAVSYS in QSYS is
updated with the date, time, and place where the system is saved. The
history information for the data area QSAVCFG in QSYS is updated with
the date, time, and place where configuration objects are saved. The
history information is not updated for the individual objects. To
display the information in these data areas, run the Display Object
Description (DSPOBJD) command, and specify DETAIL(*FULL). Save the
information from the display of QSAVUSRPRF for the location where the
user profiles are saved.
When using this command, it is important to use the device on the system
that is defined as the initial program load (IPL) device. The IPL device
was defined by the service representative when the system was installed.
If an IPL device is not used when using this command, then the system
cannot be restored using the SAVSYS media (if densities or media types
are incompatible).
...
"
Regards, Chuck
On 13 Jun 2012 06:22, John McKee wrote:
Some time back, a switch was made to use Go SAVE 21 on the v5r4
system. <<SNIP QSYSOPR DST user reference>>
DSPOBJD shows object QSYSOPR *USRPRF was changed this morning at
04:05:52.. But, Save/Restore shows last save date/time of 8/13/06
00:25:31.
Guess I have two questions:
1) I thought a SAVE 21 saved everything. Does that function not
update the saved date/time for the user profile?
<<SNIP>>
midrange.com
