[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
3966.0. "no logical names with MCC" by BLG03::ROSSI () Mon Oct 26 1992 10:34
Hi,
I have my customer using MCC BMS 1.2 on VMS 5.5-1.
The problem is related to logical names using MCC.
We use at about 100 rules and we specify an "alarm fired procedure"
that is a .com in a directory named mcc$com. At rule definition time
we inserted mcc$com:command_file_name.com as file specification.
Changing the disk where command files are, we thougt that was sufficient
to change the logical name contents, defining mcc$com properly.
Mistake!
We discover that mcc stores the translation of old mcc$com, it means we have
to define again all the rules.
Fortunately we have the utility that creates an FCL command file that define
all the rules. Editing that command file is possible to insert new file
specifications. Deleting all the rules and executing the command file is
possible to have new rules with a correct path to .com files.
Is there a simpler way to do it?
Why is not possible to use logical name as normally used in other applications?
Thanks
Giuseppe Rossi
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3966.1 | A security issue | NANOVX::ROBERTS | Keith Roberts - Network Management Applications | Mon Oct 26 1992 15:34 | 7 |
| Expanding and storing the file specification was done for security. So that
no one could come along and change a logical and cause different scripts
to be executed.
But - this is probably the effect you want to happen! 8(
/keith
|