savlib IBM how often?
Mike Buglass
news:a9f8h1$it5$1...@azure.nl.gxn.net:
> Hi,
>
> Is it necessary to regularly Savlib *IBM, even when no
> Ptf's/Licensed programs have been added or removed since the last
> Savsys?
>
> Is it okay to Rstlib *IBM from a Savsys Tape, when no changes have
> been made to Ptf's/Licensed Programs since the last time that
> Savsys was made, even though that Savsys (and obviously also the
> Savlib *IBM) might be several months old?
> Or are there problems that might occur when this is done?
>
> thanks again
> martijn
>
Martijn,
The SAVLIB *IBM (and SAVSYS if you are doing the SAVCFG and SAVSECDTA
daily) will only need to be done after a release upgrade or applying
PTFs - unless you are using the libraries to store user data. As long
as you can ensure that you have valid backups of these it is OK to
leave them out of your regular backup schedule. Having said that, the
SAVLIB *IBM does not require restricted state and does not normally
take a long time so unless you are on a tight backup window you might
as well back it up regularly anyway.
--
Mike Buglass
Kim Kuras
> Hi,
>
> How often should a Savlib *IBM be made?
> Currently only a Savlib *Allusr is made on a daily basis (as well as a
> Savcfg/Savsecdta/Savdlo/Sav).
>
> Is it necessary to regularly Savlib *IBM, even when no Ptf's/Licensed
> programs have been added or removed since the last Savsys?
>
> Is it okay to Rstlib *IBM from a Savsys Tape, when no changes have been made
> to Ptf's/Licensed Programs since the last time that Savsys was made, even
> though that Savsys (and obviously also the Savlib *IBM) might be several
> months old?
> Or are there problems that might occur when this is done?
>
> thanks again
> martijn
To the best of my knowledge (which is debatable!), the SAVLIB *IBM
processes the IBM libraries as well security data, configuration data,
and IBM directories. Unless I'm applying alot of PTF's, I do not
process a SAVSYS. However I do process daily saves of SAVSECDTA &
SAVCFG, both of which can be done while users are on the system. I
also process an entire system save on a monthly basis (option
21...saves everything). You can restore from your last SAVSYS but
you'll need to know the QSECOFR password which that save was done
with. If you don't savsecdta or savcfg, and restore with your last
savsys, you'll loose any changes made in the interim. Hope this makes
sense but it's early!
Kim Kuras
Hi Mike. I have never processed a SAVLIB *IBM save without the system
bring in a restricted state. However, we always use option 22 to
process this save. Option 22 ends all the subsystems and puts the
system in a restricted state. My question...how are you getting the
*IBM saved without a restricted system? I would love to be able to do
this as downtime here is a major inconvenience on our employees and
web customers. Thanks in advance for any information you could
provide (I'm on an 820/2397/7.5 gb storage/245+ gb DASD).
Mike Buglass
news:8c532b9f.0204...@posting.google.com:
>
> Hi Mike. I have never processed a SAVLIB *IBM save without the
> system bring in a restricted state. However, we always use option
> 22 to process this save. Option 22 ends all the subsystems and
> puts the system in a restricted state. My question...how are you
> getting the *IBM saved without a restricted system? I would love
> to be able to do this as downtime here is a major inconvenience on
> our employees and web customers. Thanks in advance for any
> information you could provide (I'm on an 820/2397/7.5 gb
> storage/245+ gb DASD).
>
Kim,
While SAVLIB *IBM does not require restricted state it does require
that the objects in the libraries are not holding locks that prevent
the save. If you are having problems because of what other things are
running then only do the *IBM save when you do a SAVSYS. Unless you are
using the IBM libraries to store user objects - and this is not a good
idea - then you only need to back them up after an upgrade or PTFs have
been applied.
--
Mike Buglass