[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 |
591.0. "FDA Install Problems" by VINO::LUNDGREN (John - ISB/ASAP SSE - 297-5537) Fri Jan 04 1991 18:08
I am having a problem with the IVP of the latest DECnet Phase IV
Diagnostic Assistant FM (T1.0.1) that was just announced in note 3.42.
Before the installation, I had an older version (17-OCT-1990) of FDA
installed. When I execute the IVP I get the following message:
The IVP for DECmcc DECnet Phase IV Diagnostic Assistant FM will now be run.
DECmcc (T1.1.0)
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed
DECmcc DECnet Phase IV Diagnostic Assistant FM V1.0 Installation Successful
The IVP does a MANAGE/ENTERPRISE TEST MCC 0 DN4_DIAG_ASSIST_FM. I believe that
the only entry in the parse table is MANAGE/ENTERPRISE TEST MCC 0
DECNET_IV_DIAGNOSE_FM. This directive does work. Included is a portion of
my installation:
* Do you want to update the MCC Dictionary [YES]?
* Do you want to update the MCC parse tables [YES]?
* Do you want to update the MCC Help file [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
Product: DECMCC-DECNET-DIAGNOSIS
Producer: DEC
Version: 1.0
Release Date: 15-NOV-1990
* Does this product have an authorization key registered and loaded? YES
Following the copying of the files, the DECmcc DECnet Phase
IV Diagnostic Assistant FM start-up command procedure(s)
will be invoked. Operational tables will be created by this
procedure.
To automatically set up DECmcc DECnet Phase IV Diagnostic
Assistant FM on your system, edit your local system start-up
command procedure
SYS$MANAGER:SYSTARTUP_V5.COM
so that it invokes the DECmcc DECnet Phase IV Diagnostic
Assistant FM start-up command procedure. Add:
@SYS$STARTUP:MCC_STARTUP_FDA.COM
after the statement that invokes the DECmcc BMS start-up
command file (MCC_STARTUP_BMS.COM)
Following the DECmcc DECnet Phase IV Diagnostic Assistant FM
start-up the DECmcc DECnet Phase IV Diagnostic Assistant FM
post install command procedure will be invoked.
VMSINSTAL asks no additional questions.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
Beginning DECmcc DECnet Phase IV Diagnostic Assistant FM
Post Installation Procedure ...
Ignore the following message:
%MCC-E-NOENTITY, No corresponding entity instance exists
DECmcc Dictionary Administrator Program Version T1.1.0
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-ENTEXIST, specified entity definition exists already
%DAP-I-LINENUMB, At or near line number 2.
%DAP-I-CMD_LINE, Command: CREATE CLASS MCC SUBCLASS DN4_DIAG_ASSIST_FM CODE 009
%MCC-E-ENTEXIST, specified entity definition exists already
DECmcc Parse Table Builder
Component Version: T1.1.0
Parse Table filename: MCC_PTB_PARSER.BPT
Command Log Data filename: MCC_PTB_PARSER.DAT
Processing entity 1
Processing entity 1 1
Processing entity 1 1 0
Processing entity 1 1 1
Processing entity 1 1 1 0
Processing entity 1 2
Processing entity 1 2 0
Processing entity 1 2 1
Processing entity 1 3
Processing entity 1 3 0
Processing entity 1 3 1
Processing entity 1 3 1 0
Processing entity 1 4
Processing entity 1 4 0
Processing entity 1 4 1
Processing entity 1 4 2
Processing entity 1 4 2 0
Processing entity 1 4 2 1
Processing entity 1 4 3
Processing entity 1 4 4
Processing entity 1 5
Processing entity 1 5 0
Processing entity 1 5 0 0
Processing entity 1 5 1
Processing entity 1 6
Processing entity 1 6 0
Processing entity 1 6 1
Processing entity 1 6 1 0
Processing entity 1 7
Processing entity 1 7 0
Processing entity 1 7 1
Processing entity 1 7 1 0
Processing entity 1 7 2
Processing entity 1 7 3
Processing entity 1 8
Processing entity 1 8 0
Processing entity 1 8 1
Processing entity 1 8 4
Processing entity 1 8 5
Processing entity 1 9
Processing entity 1 9 1
Processing entity 1 9 2
Processing entity 1 12
Processing entity 1 12 0
Processing entity 1 12 1
Processing entity 1 12 2
Processing entity 1 12 3
Processing entity 1 14
Processing entity 1 14 0
Processing entity 1 14 1
Processing entity 1 14 1 1
Processing entity 1 14 2
Processing entity 1 14 2 0
Processing entity 1 15
Processing entity 1 16
Processing entity 1 16 0
Processing entity 1 16 1
Processing entity 1 16 1 0
Processing entity 1 16 1 1
Processing entity 1 17
Processing entity 1 17 0
Processing entity 1 18
Processing entity 1 18 0
Processing entity 1 18 1
Processing entity 1 20
Processing entity 1 20 0
Processing entity 1 21
Processing entity 1 21 0
Processing entity 1 21 1
Processing entity 1 21 2
Processing entity 1 21 3
Processing entity 1 21 4
Processing entity 1 21 5
Processing entity 1 21 6
Processing entity 1 21 6 5
Processing entity 1 22
Processing entity 1 25
Processing entity 1 25 0
Processing entity 1 25 1
Processing entity 1 27
Processing entity 1 27 1
Processing entity 1 29
Processing entity 1 29 0
Processing entity 1 29 1
Processing entity 1 29 1 0
Processing entity 1 42
Processing entity 1 42 1
Processing entity 1 99
Processing entity 1 99 0
Processing entity 1 99 0 0
Processing entity 1 99 1
Processing entity 7
Processing entity 7 1
Processing entity 7 1 5
Processing entity 7 4
Processing entity 7 5
Processing entity 7 6
Processing entity 7 7
Processing entity 7 8
Processing entity 7 9
Processing entity 7 10
Processing entity 7 13
Processing entity 7 14
Processing entity 7 17
Processing entity 7 18
Processing entity 7 19
Processing entity 7 20
Processing entity 7 25
Processing entity 7 33
Processing entity 7 38
Processing entity 8
Processing entity 8 5
Processing entity 8 88
Processing entity 9
Processing entity 9 11
Processing entity 9 11 44
Processing entity 9 11 45
Processing entity 9 11 46
Processing entity 9 12
Processing entity 9 21
Processing entity 9 21 36
Processing entity 9 21 37
Processing entity 11
Processing entity 12
Processing entity 12 3
Processing entity 12 10
Processing entity 12 11
Processing entity 12 11 40
Processing entity 12 17
Processing entity 12 18
Processing entity 12 26
Processing entity 12 44
Processing entity 12 47
Processing entity 12 47 45
Processing entity 15
Processing entity 15 1
Processing entity 18
Processing entity 18 31
Processing entity 18 31 30
Processing entity 18 32
Processing entity 18 33
Processing entity 18 33 33
Processing entity 18 34
Processing entity 18 37
Processing entity 18 37 35
Processing entity 18 37 36
Processing entity 18 38
Processing entity 18 39
Processing entity 18 40
Processing entity 18 40 41
Processing entity 18 43
Processing entity 18 43 44
Processing entity 18 43 45
Processing entity 18 43 46
Parse table build complete.
DECmcc Help File Builder
Component Version: T1.1.0
Processing file USER2:[MCC]MCC_ALARMS_FM.HELP
Processing file USER2:[MCC]MCC_BRIDGE_AM.HELP
Processing file USER2:[MCC]MCC_CONTROL_FM.HELP
Processing file USER2:[MCC]MCC_DNA4_AM.HELP
Processing file USER2:[MCC]MCC_DNA5AM_HELP.HELP
Processing file USER2:[MCC]MCC_DOMAIN_FM.HELP
Processing file USER2:[MCC]MCC_ENET_AM.HELP
Processing file USER2:[MCC]MCC_FDA_FM.HELP
Processing file USER2:[MCC]MCC_GENERAL_HELP.HELP
Processing file USER2:[MCC]MCC_KERNEL_AM.HELP
Processing file USER2:[MCC]MCC_PA_FM.HELP
Processing file USER2:[MCC]MCC_SAMPLE_AM.HELP
Processing file USER2:[MCC]MCC_TCPIP_AM.HELP
Sorting character cell help topics.
Sorting windows help topics.
Verifying hierarchy...
Verifying for character cell
Verifying for windows
Processing file(s)....
MCC help files updated.
MCC help files updated.
Cleaning up intermediate files.
The MCC_STARTUP_FDA startup procedure for DECmcc V1.0 is now running.
DECmcc (T1.1.0)
%MCC-W-ENRDUPLENTNOTEQ, enrollment successful; duplicate entries found and repla
ced (different enroll IDs)
The MCC_STARTUP_FDA startup procedure for DECmcc V1.0 is now ending.
Completing DECmcc DECnet Phase IV Diagnostic Assistant FM
Post Installation Procedure ...
Beginning DECmcc DECnet Phase IV Diagnostic Assistant FM
Installation Verification Procedure
The IVP for DECmcc DECnet Phase IV Diagnostic Assistant FM will now be run.
DECmcc (T1.1.0)
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed
DECmcc DECnet Phase IV Diagnostic Assistant FM V1.0 Installation Successful
Completing DECmcc DECnet Phase IV Diagnostic Assistant FM
Installation Verification Procedure
Installation of MCCFDA V1.0 completed at 13:36
Updating list of installed software products ...
VMSINSTAL procedure done at 13:37
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 591.1 | thanks... | GOSTE::CALLANDER | | Mon Jan 07 1991 17:46 | 3 |
| Thanks for your input, the information has been passed along to
the appropriate group.
|
| 591.2 | problem caused by FDA name changes | MKNME::MUNDRA | | Thu Jan 10 1991 17:39 | 18 |
| The above is due to the following:
The install procedure tried to delete the old definition of DN4_DIAG_ASSIST_FM
from the dictionary but it didn't get deleted because there was no such
definition in the dictionary (which is okay).
It then tried adding the new definition of DN4_DIAG_ASSIST_FM but that failed
because the code (9) used by DN4_DIAG_ASSIST_FM was already in the dictionary
(used by DECNET_IV_DIAGNOSE_FM, the last name used by FDA). As a result, the
test command issued by the IVP failed.
The solution to the above problem is to delete all the various past names used
by FDA from the dictionary (whether or not the corresponding definitions are in
the dictionary).
I will modify the install procedure to delete all the various names
that were used by FDA in the past.
sm
|