T.R | Title | User | Personal Name | Date | Lines |
---|
2716.1 | is MSG_LOCATION being set? | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Wed Apr 08 1992 13:00 | 7 |
| Have you "sourced" the file /usr/mcc/mcc_system/mcc_login.csh?
That file sets the environmental variable MSG_LOCATION, which
points to the message files.
Also, what is a 5240? It isn't a multi-processor, by any chance?
-- Erik
|
2716.2 | we try ...but | LFOIS1::ALIE | | Wed Apr 08 1992 13:21 | 12 |
| we try a
setenv MSG_LOCATION /usr/mcc/mcc_system
the file *msg*.plib exist and seems to have the right size...
(we have compare with a working system and we have the same size and
date 20-dec-1990)
we try to reboot the system
but... nothing to do
|
2716.3 | The name of the MSL message file: | TOOK::L_GROSSMAN | | Wed Apr 08 1992 14:40 | 4 |
|
Please make sure you have the explicit message file for MSL
msg1263.plib
|
2716.4 | Yes we have | LFOIS1::ALIE | | Thu Apr 09 1992 05:01 | 3 |
| Yes we have the file msg1263.plib.
it seems that Decmcc lose the link between those file and his kernel.
|
2716.5 | it is working | LFOIS1::ALIE | | Thu Apr 09 1992 06:37 | 12 |
| we try a
#setenv MSG_LOCATION /usr/mcc/mcc_system
my customer do until today a setenv MCC_MSG_LOCATION as told in his VMS
documentation ...
So it is working now
Thank you very much for your help and your quick answer...
|
2716.6 | Better to use the login file | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Thu Apr 09 1992 08:46 | 14 |
| I'm glad it is working.
However, you shouldn't explicitely "setenv" anything.
The file /usr/mcc/mcc_system/mcc_login.csh (or .sh)
does that for you. Each user should put
source /usr/mcc/mcc_system/mcc_login.csh
in their .cshrc
(or . /usr/mcc/mcc_system/mcc_login.sh in their .profile)
-- Erik
|