Darren Evans-Young wrote:
>
> On Mon, 22 Nov 1993 11:38:49 EST Mignon Erixon-Stanford said:
> >My normal modus operandi is to manually xedit the lasting globalv and delete
> >the ldbase entries whenever I want to go to another node. This did not present
> >a problem until a couple of weeks ago, when suddenly the LSVPUT passwords for
> >the various lists started disappearing from the bottom lines of my lasting
> >globalv! Some other settings mysteriously disappeared too. We're running
> >Listserv 17F (fix 2) under CMS Rel. 5.  My virtual machine has 3M.
> >
> >        =-=-=-=-=-=-=-IRMSS907@SIVM or @SIVM.SI.EDU-=-=-=-=-=-=
> >                Mignon Erixon-Stanford, Computer Specialist
> >                 Office of Information Resource Management
> >             Voice: 202-357-4243           Fax: 202-786-2687
>
> I can't remember where, but I remember reading something that implied
> it was very unwise to edit your LASTING GLOBALV file with XEDIT.
> The help files say something about screwing up record lengths, but
> I thought it was something in addition to that.
>
> Darren
>
>
It has been a few years since I looked at CMS internals, so
things may be different now.  But historically, manually editting
your LASTING GLOBALV was a strict rule 1 operation.
 
The GLOBALVs are stored in memory and the disk image is updated
from the memory copy whenever any change in their values are
made.  Many programs and especially EXECs update your GLOBALVs,
often without your expecting it.  This can overwrite any changes
you make with a manual edit.  Even worse with the present file
systems only blocks which have changed in the memory copy might
be overwritten.  I use to LOGON, XEDIT LASTING GLOBALV (NOPROF,
#CP LOGOFF.  The LOGOFF without CMS processing or traps is
important.  (Re IPLing CMS from CP works too.)
 
--
John Bacon                              [log in to unmask]