Re: Save date of user profile Was: QSYSOPR user profile and GO SAVE 21

I differ. I often question home grown back up programs before IBM
supplied utilities. After all, how many shops probably ran for awhile
using programs that didn't have the stream file save of just SAV after
that was introduced? How many shops probably still don't realize that
ENDSBS *ALL doesn't kill all of TCP/IP any more and you really should run
ENDTCP -before- running the ENDSBS?

When IBM shifts library order around on a save, like they did with the
following:
For values *NONSYS and *ALLUSR, libraries QSYS2, QGPL, QUSRSYS,
and QSYS2xxxxx (where xxxxx is an independent ASP number) are
saved first, if they are located on the ASPs specified by the
ASPDEV parameter.
the user's custom programs are probably ok, providing they use *ALLUSR or
*NONSYS and not some utility that generates a list of libraries and
processes that.

We use BRMS. BRMS doesn't 'alert' us if it abnormally terminates. It
catches it and brings itself down. What we do is generate a message using
an exit at the end. If the operator doesn't get that message at the end,
auditing is started. I still have it on my to do list to weed through all
the object not saved messages (normally stream files) and either omit
those or perform actions to ensure they can be saved. Mainly because I've
become numbed to this genre of message:
1078 objects saved from MPLUS. 2 not saved.
which leads to becoming numb to:
Backup *ALLUSR, type *FULL completed with errors.
And, I've become numb to:
Object in use. Object is /QIBM/UserData/OS/OSGi/LWISysIn
Cannot open object /QIBM/UserData/OS/OSGi/LWISysInst/admi
Object in use. Object is /QIBM/UserData/OS/OSGi/LWISysIn
Cannot open object /QIBM/UserData/OS/OSGi/LWISysInst/admi
...
which leads to becoming numb to:
185346 objects saved. 171 not saved.
Save of list *LINK completed with errors.
and these both lead to becoming numb to
Control group TUE_FRI type *BKU completed with errors.

Becoming numb to these type of messages can be hazardous.


Rob Berendt