If users can and do update the library, there is a very different set of
considerations.
Assuming a read-only library for the nonce, though, at worst I would
expect a period of some performance degradation for people who are
logged in using the old library while it is being copied. It might be
enough to notice, or not.
How long it would last depends on how many members the library has and
how big it is, of course. But unless the library is big (FSVO "big," as
multiple factors can play here) I would not necessarily expect it to
happen at all. For example, a large-enough DASD controller cache might
prevent it entirely. If it did happen, I also would not expect it to
last very long--and, if turns out that it lasts longer than you can
tolerate, you can cancel the job at any time to relieve the contention
quickly and try something else. "Something else" could be multiple copy
jobs to copy subsets at a time until done, or restoring the data set
from a backup with a new name, for example.
That aside, already logged-in users will just continue to use the old
library they allocated during logon. People who log on after the change
to the PROC has been saved will allocate the new one. So once the copy
has been made and the PROC updated, there should be no effects any user
can detect.
As the data set is not SMS-managed, you also have the alternative of
uncataloging the new one after the copy, renaming it to match the old
one, and then ALTERing the volume list in the catalog entry to point to
the new volume. Once the old one has been unallocated by everyone, it
can be deleted.
Last but not least, before monkeying with any logon proc, make sure you
have one *you* can log on with that you will (a) not need to edit at the
same time and that (b) does not allocate the libraries you plan to
manipulate. Because locking yourself out by making a mistake that would
otherwise be easy to fix is, well, embarrassing...at best.
zos reader wrote:
Thanks All.
It is ISPF USER SKELETON file.
Copy the contents of the library to a new, larger library. This library
will need to have another name.
- Change your logon procedure to use the new library.
If we try the above method, there might be impact to the users who are
logged in.
yes, its in sysplex and it is allocated in non-sms volume
<snip>
--
John Eells
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
