From what I understand, when you want to move a program to minidisk
> MNT19E 19E Y/S to make it available to all other users, you have to
> (re)save the CMS system.
A useful way to avoid having to resave CMS all the time is to have an
additional program disk to hold locally installed stuff that's not part
of the base CMS installation. We used a minidisk that was owned by
MAINT, and ensured that it was accessed by all users as 'P'.
An additional handy thing to know is that RENAME is atomic, so you can
add files to the P disk, or _update_ them there, with impunity, if you
do it right:
- Link the P disk M as some additional mode other than P.
- COPY the new or updated file there with a temp name.
- RENAME the old file (if any) to e.g. a versioned oldname.
- RENAME the new or updated file to the intended name.
- RELEASE the disk.
- Have all logged in users reACCESS P.
Until they reaccess, they will get the old version of an updated file.
If you use MR mode for the link, you may get an R link if someone else
has an M (or W, naughty) link, which is why I suggest M mode. (We had a
script for this, so it was desirable to avoid the issue rather than to
try to detect it and clean it up.)
De
