| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 841.1 | | CUPOLA::HAKKARAINEN | Dave Barry for President | Fri Aug 21 1987 16:32 | 1 |
| Define tag$local_tags to point to your def'n file.
|
| 841.2 | Bad Question...I'll try again. | COOKIE::CHAVEZ | Dale C. - CXO3 Colo Spgs | Mon Aug 24 1987 10:00 | 8 |
| RE: .0
Bad question on my part. Let me rephrase it. Is there anyway I
can point to two different LSE SDML environment files? I'm going
to create my own environment file that provides expansion for the
tags I've defined here locally.
Dale
|
| 841.3 | LSE manual explains in chapter 6 | VAXUUM::FARR | | Mon Aug 24 1987 12:16 | 6 |
|
You can use LSEDIT/INITIALIZATION=filespec or define
LSE$INITIALIZATION in your login.com file to be your
additional placeholder definitions.
Julie
|
| 841.4 | Use LSE$ENVIRONMENT, see TLE::LSEDIT | TOKLAS::FELDMAN | PDS, our next success | Mon Aug 24 1987 13:01 | 14 |
| LSE also permits multiple environment files. The simplest way is
to define LSE$ENVIRONMENT to be a search list. Since LSE uses two
different logical names, namely LSE$ENVIRONMENT and
LSE$SYSTEM_ENVIRONMENT, your personal stuff should go into
LSE$ENVIRONMENT, while you leave LSE$SYSTEM_ENVIRONMENT alone.
LSE loads things correctly, so that items in your personal environment
file will override any items in the system environment file. The
trick is to build your environment file correctly. See the help
on the SAVE ENVIRONMENT command.
Questions specific to LSE should go into the TLE::LSEDIT conference.
Gary
|
| 841.5 | | COOKIE::CHAVEZ | Dale C. - CXO3 Colo Spgs | Mon Aug 24 1987 16:32 | 5 |
| RE:< Note 841.4 by TOKLAS::FELDMAN "PDS, our next success" >
Thanks, that did the trick.
Dale
|