John Burke writes...
> ...
> - edit the file (say udc.pub.sys), making your changes and
> keeping it as, for example, udcnew.pub.sys.
>
> - use the posix move command to replace udc with udcnew:
>
> :mv.hpbin.sys "/SYS/PUB/UDCNEW /SYS/PUB/UDC"
>
> Respond "yes" to the question about replacing udc. All
> subsequent logons
> will get the new version of the udc. I use this trick all the time to
> replace files in use.
>
> John Burke
>
>
And a cute trick it is indeed, at least to this Posix pre-neophyte.  How
does it work, that is, what's really happening with the files?  I have to
assume the SET/SHOWCATALOG settings remain pointed to the original version;
does mv just build a link, or???

Tracy Pierce





> > -----Original Message-----
> > From: Steve Hammond [mailto:[log in to unmask]]
> > Sent: Wednesday, November 22, 2000 7:09 AM
> > To: [log in to unmask]
> > Subject: [HP3000-L] UDC theory
> >
> >
> > Just a sanity check on my udc theory, which is a little rusty.
> >
> > When I upgrade from 5.5 to 6.0, I need to make one change to
> > my PowerHouse udc. This udc is set account by account.
> >
> > If no one is logged on into any of the accounts that use the
> > udc, I only need to make the modification to the udc file and
> > keep it. Then the changes are there the next time someone
> > logs into that account.
> >
> > Is this correct?
> >
> > TIA
> >
> > steve
> >
>