| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1287.1 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu May 02 1996 16:51 | 13 |
| Steve,
Excellent question and thanks for pointing out the flaw in the
documentation. The answer is
We will search in the following order:
CONSOLE$USER_DEFAULTS:
SYS$LOGIN:
Current directory
Dan
|
| 1287.2 | Suggestion | OPCO::TSG_SJM | Steve McGinley - Sydney Australia | Thu May 02 1996 22:05 | 8 |
| Dan
Suggestion...perhaps it should be the other way around. If a site has a
common CONSOLE$MONITOR_INIT.DAT file in CONSOLE$USER_DEFAULTS, if
SYS$LOGIN was search first, then an individual, and boy there are lots
of them, could have his/her own init file.
Steve
|
| 1287.3 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu May 02 1996 23:53 | 13 |
| And you still can have your own. Define CONSOLE$USER_DEFAULTS
to SYS$LOGIN or you may use the /INIT qualifier to specify
the init file you want.
I do like your search order best though. What we have to think about is
impact to the customers that are used to the current search order.
What we could do pretty easily is implement a logical that would
allow the search order to be changed and leave the default search order
as it is. Hmmmmmmm.....
Dan
|
| 1287.4 | console$monitor_init.dat and C3 | KERNEL::NICHOLSONA | rackin frackin varmit | Wed May 08 1996 12:16 | 9 |
|
Further onto this note, could you tell me if you are using an
initialization script would you expect the keys defined within this
file to be picked up when using the console monitor via the C3
interface?
Thanks
Avril
|
| 1287.5 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed May 08 1996 17:49 | 9 |
| >Further onto this note, could you tell me if you are using an
> initialization script would you expect the keys defined within this
> file to be picked up when using the console monitor via the C3
> interface?
Absolutely!
Regs,
Dan
|
| 1287.6 | | WOTVAX::WATSONR | Lambs... so cute... but so tasty ! | Tue Aug 13 1996 07:58 | 21 |
| 1287.7 | | WOTVAX::WATSONR | Lambs... so cute... but so tasty ! | Tue Aug 13 1996 08:02 | 4 |
| 1287.8 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue Aug 13 1996 17:32 | 13 |
| Well Ross,
Someone else asked me this question last Friday as they have the same
behavior you do. I went into the C3 code and lo and behold the /NOINIT
qualifier is specified so what we are experiencing is intended
behavior. The only reason I can think of for doing that is thaat
MONITOR interfaces created from the C3 are MONITORing a single
system and the init file could contain commands that don't apply
to that system.
At least we know.
Regards,
Dan
|
| 1287.9 | | WOTVAX::WATSONR | Lambs... so cute... but so tasty ! | Wed Aug 14 1996 06:10 | 14 |
| 1287.10 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Aug 15 1996 16:06 | 26 |
| >I think its a bug really. The C3 interface should handle an
>initialisation file. Of course, it would be interesting to see which has
> precedence, the initialisation file, or the C3 definition for the
>control keys.
Ross,
What the C3 does is just SPAWN a decterm giving it a command of
CONSOLE MONITOR /BREAK=whatever etc.
The command-line qualifier takes precendence over the init file and of
course this is true if you create a MONITOR from the C3 or from the DCL
command line.
Since there will always be those customers that want to have their cake
and eat it too, I would suggest you submit an request for enhancement
for a new button within the C3 that says whether or not the /NOINIT
qualifier is used. Since we've already determined that the command line
qualifiers take precedence over the init file, if the button is
selected, the selections for the various keys in the C3 customizations
menus would be stippled out and thus disabled.
Regards,
Dan
thus disabled.
|