Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: DCLTABLES changes
Message-ID: <5512@ucbvax.ARPA>
Date: Fri, 15-Mar-85 12:41:34 EST
Article-I.D.: ucbvax.5512
Posted: Fri Mar 15 12:41:34 1985
Date-Received: Sat, 16-Mar-85 05:22:58 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 34

From: GKN%OAK.SAINET.MFENET@LLL-MFE.ARPA


SYS$LIBRARY:DCLTABLES.EXE is INSTALLed as a shared image.  When you create
a new version via SET COMMAND, you must also INSTALL this new version.

When your process was created, LOGINOUT decided what CLI and command tables
to map into your address space based upon the data in SYSUAF and/or what
you told it to do.  The version of the command tables (usually DCLTABLES;
who uses MCR ?) which was mapped by LOGINOUT when your process was created
will remain there for the life of your process.  To have new commands you've
added to SYS$LIBRARY:DCLTABLES.EXE become available to your process you
have two options:

        1.  Log out and log back in again.  This will map the fresh copy pof
            (of) SYS$LIBRARY:DCLTABLES.EXE into your P1 space.
        2.  Use SET COMMAND to update the current copy of DCLTABLES in your
            address space (i.e. - omit the /Tables and /Output qualifiers).

I don't believe that the documentation for V3 or V4 explicitly states that
you must re-INSTALL SYS$LIBRARY:DCLTABLES.EXE and log out and back in again
to remap the fresh copy.  However, this has been the behavior of SET COMMAND
since time imemorial.


gkn

------------------------------------------
Arpa:   GKN%OAK.SAInet@LLL-MFE
USPS:   Gerard K. Newman
        Science Applications International
        800 Oak Ridge Turnpike
        Oak Ridge, TN  37830
AT&T:   (615) 482-9031