| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 863.1 | missing Notification FM | TOOK::HAO | | Wed Apr 03 1991 08:54 | 12 |
| It appears that you're missing the Notification FM. Somewhere along
the way during installation, it wasn't enrolled properly. When the
Iconic Map PM comes up, it does a test to see if it's there. If not,
it displays a message if appropriate, and dims out any pulldown menu
entries that has to do with notification, since the Iconic Map cannot
access the notification functions.
Try enrolling the Notification FM from FCL: "Enroll
mcc_notification_fm"
Christine
|
| 863.2 | what was the install error? | TOOK::CALLANDER | | Wed Apr 03 1991 08:54 | 9 |
| the notification module is dependent upon the services of the
alarms module. If the alarms module did not install correctly
then you will have a problem with notification. (BTW: there is
no register command on notificiation, I believe the message is
trying to tell you to enroll the service module.)
But it really looks like something failed at installation time and
the kit is not correctly there. Do you know what the error message is?
|
| 863.3 | Enroll didn't help, IVP still fails | SLOVAX::BREINHOLT | Reb Breinholt | Wed Apr 03 1991 10:20 | 59 |
| I tried registering the FM as suggested in .1 which resulted in the
following message:
! MCC> enroll mcc_notification_fm
! %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and
! replaced
Subsequent invocation of 'Manager/enterprise/interface=DECwindows'
causes the following message window:
! Map Window Message: Notification is unavailable. Please check that the
! Notification FM is enrolled.
Running the IVP for BMS shows the following:
! $ @sys$test:mcc_bms_ivp
!
!
! The IVP for DECmcc BMS will now be run.
!
! DECmcc (V1.1.0)
!
!
! MCC 0
! AT 3-APR-1991 08:10:38
!
! Test Successful
! DECmcc (V1.1.0)
!
!
! MCC 0 FCL
! AT 3-APR-1991 08:10:49
!
! Test Successful
! DECmcc (V1.1.0)
!
(other success messages .....)
! MCC 0 SAMPLE_AM
! AT 3-APR-1991 08:12:14
!
! Test successful.
! DECmcc (V1.1.0)
!
! %MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
! %MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
!
! The following command failed.
!
! "MANAGE/ENTERPRISE TEST MCC 0 ALARMS, TO FILE = MCCBMS$OUT.TXT"
!
! DECmcc BMS V1.1.0 Installation Failed
!
!
! %MCC-F-FAILED, fatal DECmcc error
!
Any ideas?
|
| 863.4 | May be picking up and old dictionary file... | TOOK::GUERTIN | I do this for a living -- really | Wed Apr 03 1991 10:50 | 8 |
| Is this the first installation of MCC on your machine?
Sounds like you may have an old dictionary someplace. Look in
SYS$SPECIFIC:[*...]MCC*.* for any MCC files on your system specific
disk. There should be NONE. Also do a show logical MCC_SPECIFIC,
MCC_COMMON, and MCC_SYSTEM. Please post the relevent result here.
-Matt.
|
| 863.5 | This is the first installation | SLOVAX::BREINHOLT | Reb Breinholt | Wed Apr 03 1991 11:19 | 209 |
| I started with a backup/image of the VMS 5.4 distribution. I installed
DECnet, then DNS and then the MCCBMS011. So any MCC files should have
come from the MCC backup sets.
There is a lot of stuff that shows up in sys$specific:
$ dir sys$specific:[*...]mcc*.*/da
Directory SYS$SPECIFIC:[MCC]
MCC_DNS_SETUP.DEF;2
3-APR-1991 08:56:44.49
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON]
MCC.DIR;1 1-APR-1991 16:38:25.05
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON.MCC]
MCCBMS$OUT.TXT;10 3-APR-1991 08:12:25.97
MCCBMS$OUT.TXT;9 3-APR-1991 08:12:12.93
MCCBMS$OUT.TXT;8 3-APR-1991 08:12:02.17
MCCBMS$OUT.TXT;7 3-APR-1991 08:11:49.07
MCCBMS$OUT.TXT;6 3-APR-1991 08:11:36.30
MCCBMS$OUT.TXT;5 3-APR-1991 08:11:23.36
MCCBMS$OUT.TXT;4 3-APR-1991 08:11:11.24
MCCBMS$OUT.TXT;3 3-APR-1991 08:10:59.63
MCCBMS$OUT.TXT;2 3-APR-1991 08:10:47.99
MCCBMS$OUT.TXT;1 3-APR-1991 08:10:35.62
MCC_ALARMS_BROADCAST_ALARM.COM;1
20-FEB-1991 21:48:59.35
MCC_ALARMS_BROADCAST_EXCEPTION.COM;1
20-FEB-1991 21:50:38.36
MCC_ALARMS_FM.HELP;1
21-NOV-1990 10:30:50.66
MCC_ALARMS_LOG_ALARM.COM;1
22-FEB-1991 15:59:45.53
MCC_ALARMS_LOG_EXCEPTION.COM;1
22-FEB-1991 16:09:44.81
MCC_ALARMS_MAIL_ALARM.COM;1
20-FEB-1991 22:00:00.90
MCC_ALARMS_MAIL_EXCEPTION.COM;1
20-FEB-1991 22:03:55.71
MCC_ALARMS_SAMPLE_RULES.COM;1
22-FEB-1991 17:29:20.65
MCC_ALARMS_SECURITY.COM;1
20-FEB-1991 22:07:35.67
MCC_AUSTRALIA.MCC_BACKDROP;1
16-JAN-1991 09:20:02.51
MCC_BRIDGE_AM.HELP;1
14-JAN-1991 13:48:03.00
.
30-JAN-1991 16:27:09.30
MCC_PA_FM.HELP;1 30-JAN-1991 07:41:28.36
MCC_PTB_PARSER.BPT;1
1-FEB-1991 15:33:05.90
MCC_SAMPLE_ICON.DAT;1
6-APR-1990 16:58:25.30
MCC_SNMP_ICON.DAT;1
25-JAN-1991 15:25:39.00
MCC_SNMP_TCP_IP_HOST_ICON.DAT;1
1-MAY-1990 13:15:34.00
MCC_SNMP_WS_ULTRIX_IP_ICON.DAT;1
18-SEP-1990 15:16:05.00
MCC_STATION_ICON.DAT;1
19-APR-1990 13:43:51.68
MCC_UNITED_STATES.MCC_BACKDROP;1
20-JUN-1990 15:28:40.73
MCC_WESTERN_EUROPE.MCC_BACKDROP;1
16-JAN-1991 16:19:00.20
MCC_WORLD.MCC_BACKDROP;1
20-JUN-1990 15:28:20.16
Total of 87 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYS$STARTUP]
MCC_LOGICAL_DIR.COM;1
1-APR-1991 16:44:31.24
MCC_STARTUP_BMS.COM;1
4-FEB-1991 13:49:23.49
MCC_STARTUP_DIR.COM;1
31-JAN-1991 15:01:07.24
MCC_STARTUP_DNA4_EVL.COM;1
14-NOV-1990 14:27:47.67
Total of 4 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSEXE]
MCC_ALARMS_EXTRACT_RULES.EXE;1
24-FEB-1991 14:47:20.18
MCC_DAP_MAIN.EXE;1 24-FEB-1991 12:02:51.53
MCC_DEL_GS_POOL.EXE;1
24-FEB-1991 13:11:26.99
MCC_DNS_SETUP.EXE;1
24-FEB-1991 13:17:19.51
MCC_ENIM_CONVERT_MAIN.EXE;1
24-FEB-1991 14:59:34.88
MCC_EXPORTER_FM_BG.EXE;1
25-FEB-1991 10:50:05.77
MCC_EXPORTER_FM_WRITER.EXE;1
25-FEB-1991 10:50:39.74
MCC_HFB_MAIN.EXE;1 24-FEB-1991 14:17:14.47
MCC_HISTORIAN_FM_BG.EXE;1
25-FEB-1991 09:44:06.94
MCC_MAIN.EXE;1 24-FEB-1991 13:14:27.93
MCC_MIR_CVT_MAIN.EXE;1
24-FEB-1991 13:35:45.23
MCC_RBMS_CONVERT_MAIN.EXE;1
24-FEB-1991 14:59:15.98
Total of 12 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSHLP]
MCCBMS011.RELEASE_NOTES;3
6-MAR-1991 14:49:37.71
MCCDIR011.RELEASE_NOTES;1
6-MAR-1991 14:49:50.11
MCC_CHARACTER_CELL_HELP.HLB;1
25-FEB-1991 11:01:08.57
MCC_DAP_HELP.HLB;1 24-FEB-1991 12:03:00.29
MCC_DECWINDOWS_HELP.HLB;1
25-FEB-1991 11:01:08.87
MCC_TBD_HELP.HLB;1 24-FEB-1991 13:16:23.07
Total of 6 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSHLP.EXAMPLES]
MCC.DIR;1 1-APR-1991 16:38:30.70
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSHLP.EXAMPLES.MCC]
MCC_YOURMM.EXE;1 24-FEB-1991 14:26:03.88
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSLIB]
MCC_ALARMS_FM.EXE;1
28-FEB-1991 09:59:23.81
MCC_BRIDGE_AM.EXE;1
24-FEB-1991 14:59:50.91
MCC_CONFIG_FM.EXE;1
24-FEB-1991 15:02:41.56
MCC_CONTROL_FM.EXE;1
24-FEB-1991 13:18:40.54
MCC_DNA4_AM.EXE;1 24-FEB-1991 15:34:58.43
MCC_DNA4_EVL.EXE;1 24-FEB-1991 15:36:17.87
MCC_DNA5_AM.EXE;1 24-FEB-1991 16:25:32.70
MCC_DOMAIN_FM.EXE;1
26-FEB-1991 23:00:50.30
MCC_ENET_AM.EXE;1 24-FEB-1991 16:37:31.35
MCC_EXPORTER_FM.EXE;1
28-FEB-1991 11:13:13.66
MCC_FCL_PM.EXE;1 24-FEB-1991 14:14:37.63
MCC_HISTORIAN_FM.EXE;1
25-FEB-1991 09:41:04.21
MCC_ICONIC_MAP_PM.EXE;1
5-MAR-1991 16:11:56.17
MCC_KERNEL_INIT.OBJ;1
24-FEB-1991 12:20:23.04
MCC_KERNEL_SHR.EXE;1
24-FEB-1991 13:13:05.81
MCC_MTS_PRIV_SHR.EXE;1
1-APR-1991 16:45:35.40
MCC_NOTIFICATION_FM.EXE;1
MCC_PTB.EXE;1 24-FEB-1991 14:06:15.08
MCC_RESOURCE.DAT;1 23-JAN-1991 16:04:26.82
MCC_SAMPLE_AM.EXE;1
24-FEB-1991 14:30:13.13
MCC_UI_TBD.EXE;1 24-FEB-1991 13:16:18.27
Total of 22 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSMGR]
MCC_EXPORTER_BACKGROUND.COM;1
4-JAN-1991 20:38:57.91
MCC_HISTORIAN_BACKGROUND.COM;1
4-JAN-1991 20:38:14.59
Total of 2 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSMSG]
MCCMSG.EXE;1 22-FEB-1991 15:03:25.34
MCCTBDMSG.EXE;1 24-FEB-1991 13:16:29.05
Total of 2 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSTEST]
MCC.DIR;1 1-APR-1991 16:38:28.85
MCC_BMS_IVP.COM;1 17-JAN-1991 15:20:34.88
MCC_DIR_IVP.COM;1 7-JAN-1991 14:21:44.84
Total of 3 files.
Grand total of 12 directories, 142 files.
|
| 863.6 | MCC logical assignments are here | SLOVAX::BREINHOLT | Reb Breinholt | Wed Apr 03 1991 11:22 | 11 |
| I forgot to include the MCC logicals in the previous entry, they are:
$ show log mcc_specific
"MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)
$ show log mcc_common
"MCC_COMMON" = "SYS$COMMON:[MCC]" (LNM$SYSTEM_TABLE)
$ show log mcc_system
"MCC_SYSTEM" = "MCC_SPECIFIC" (LNM$SYSTEM_TABLE)
= "MCC_COMMON"
1 "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)
1 "MCC_COMMON" = "SYS$COMMON:[MCC]" (LNM$SYSTEM_TABLE)
|
| 863.7 | Workaround but no solution | SLOVAX::BREINHOLT | Reb Breinholt | Wed Apr 03 1991 14:41 | 9 |
| I just finished re-installing (VMSINSTAL) the distribution but included
the DECmcc Reports Package and the problem disappeared. The IVP
completed normally, when I bring up the window, the message window does
not show up as was previously the case.
Do I really need the report option? Can I move it to another disk?
Thanks for your suggestions.
|
| 863.8 | So far so good... | TOOK::GUERTIN | I do this for a living -- really | Wed Apr 03 1991 14:56 | 12 |
| Unfortunately, you removed the most interesting files from the listing.
In particular the size and dates of the following files are
significant:
$ directory/secur/date/size=all mcc_system:mcc_d*.dat
$ directory/secur/date/size=all mcc_system:mcc_mir*.dat
Everything else looks fine. Do you have the BMS License loaded on that
system?
-Matt.
|
| 863.9 | Reports?? | TOOK::GUERTIN | I do this for a living -- really | Wed Apr 03 1991 15:01 | 4 |
| This is getting very strange. The reports package should have nothing
to do with the rest of the BMS kit. It is strictly layer on top.
-Matt.
|
| 863.10 | Directory list of data files | SLOVAX::BREINHOLT | Reb Breinholt | Wed Apr 03 1991 16:36 | 86 |
| The BMS license is loaded.
I am including 2 directory lists as specified in note .8. The first is
of the disk that now comes alive, the other is of the disk that was
loaded yesterday and will not work.
-
The no-workie data files:
! $ dir
! dka300:[sys0.syscommon.mcc...]mcc_d*.dat,mcc_mir*.dat/date/sec/siz=all
!
! Directory DKA300:[SYS0.SYSCOMMON.MCC]
!
! MCC_DEFINITION.DAT;1
! 13323/13323 28-JAN-1991 21:42:11.47 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_DICTIONARY.DAT;1
! 21438/21438 28-JAN-1991 21:42:10.31 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_DISPATCH_TABLE.DAT;1
! 450/450 26-MAR-1991 14:39:38.84 [SYSTEM]
! (RWED,RWED,RE,)
! MCC_DOMAIN_DELNI_ICON.DAT;1
! 4/6 1-MAY-1990 13:53:17.00 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_DOMAIN_DEMPR_ICON.DAT;1
! 4/6 1-MAY-1990 13:55:44.00 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_DOMAIN_DESPR_ICON.DAT;1
! 4/6 1-MAY-1990 13:56:03.00 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_DOMAIN_ICON.DAT;1
! 3/3 5-APR-1990 12:19:37.29 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_MIR_ATTRIBUTE.DAT;1
! 81/81 28-JAN-1991 21:42:08.96 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_MIR_DIRECTORY.DAT;1
! 66/66 28-JAN-1991 21:42:08.01 [SYSTEM]
! (RWED,RWED,RWED,R)
!
! Total of 9 files, 35373/35379 blocks.
!
And now the files that work
!
!
! $ dir
! dkb100:[sys0.syscommon.mcc...]mcc_d*.dat,mcc_mir*.dat/date/sec/siz=all
!
! Directory DKB100:[SYS0.SYSCOMMON.MCC]
!
! MCC_DEFINITION.DAT;2
! 13323/13323 28-JAN-1991 21:42:11.47 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_DICTIONARY.DAT;2
! 21438/21438 28-JAN-1991 21:42:10.31 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_DISPATCH_TABLE.DAT;1
! 450/450 3-APR-1991 12:22:04.61 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_DOMAIN_DELNI_ICON.DAT;2
! 4/6 1-MAY-1990 13:53:17.00 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_DOMAIN_DEMPR_ICON.DAT;2
! 4/6 1-MAY-1990 13:55:44.00 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_DOMAIN_DESPR_ICON.DAT;2
! 4/6 1-MAY-1990 13:56:03.00 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_DOMAIN_ICON.DAT;2
! 3/3 5-APR-1990 12:19:37.29 [SYSTEM]
! (RWED,RWED,RWED,RE)
! MCC_MIR_ATTRIBUTE.DAT;2
! 81/81 3-APR-1991 12:17:16.28 [SYSTEM]
! (RWED,RWED,RWED,R)
! MCC_MIR_DIRECTORY.DAT;2
! 66/66 3-APR-1991 12:17:12.61 [SYSTEM]
! (RWED,RWED,RWED,R)
!
! Total of 9 files, 35373/35379 blocks.
!
Does that help?
|
| 863.11 | Notice order of previous file lists | SLOVAX::BREINHOLT | Reb Breinholt | Wed Apr 03 1991 16:50 | 7 |
| Just to be sure you noticed - I included the directory listings in the
reverse order of what I said I would. The first list is of the files
that do not work, the second list is of the files that do work. The
only outward difference between them is the version number and creation
time. Are the bad files loaded and then purged when the DECmcc Report
option is loaded on the system?
|
| 863.12 | This problem has NOTHING to do with REPORTS. | TOOK::KOHLS | Ruth Kohls | Thu Apr 04 1991 10:24 | 20 |
| >Are the bad files loaded and then purged when the DECmcc Report
> option is loaded on the system?
Sorry. The reports option has NOTHING to do with alarms.
To answer a previous question: the reports option is
set of files intended for use with DATATRIEVE. (Datatrieve will
use them to format reports from data exported from DECmcc.) These files
are put in a distinct directory. This directory may be anywhere you want-
move the files and redefine the logical: MCC_REPORTS_FILES
(system table, executive mode) and edit SYS$STARTUP:MCC_LOGICAL_BMS.COM
to change the logical at Mcc startup. See the PA documentation
for how to use them. Or, if they are of no use to you, delete them.
I think that something went wrong with the files the Alarms FM requires,
most likely the dictionary or alarms MIR, as Matt indicated, on your
first installation. I think this because Alarms enrolled, but its IVP
failed.
Ruth
|
| 863.13 | I am seeing the same problem | CSC32::ORTIZ | | Wed Jul 10 1991 18:09 | 1005 |
| I have a specialist onsite that is seeing the same problem as above. We
get the following when we do a MANAGER/ENTER/INTERFACE=DECWINDOWS
NOTIFICATION IS UNAVAILABLE. PLEASE CHECK THAT THE NOTIFICATION FM
IS ENROLLED
The IVP worked fine in my case. We reinstalled BMS and the problem is
still there. Is this a bug in the installation or what?
Here are my listings, which incluse files, logicals, and bms
installation with IVP:
MCC_DNS_SETUP.DEF;3 9-JUL-1991 15:32:26.25
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON]
MCC.DIR;1 18-JUN-1991 12:59:01.99
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON.MCC]
MCC_ALARMS_BROADCAST_ALARM.COM;1
7-JUN-1990 16:15:32.28
MCC_ALARMS_BROADCAST_EXCEPTION.COM;1
7-JUN-1990 16:16:17.88
MCC_ALARMS_FM.HELP;1
7-JUN-1990 15:49:26.10
MCC_ALARMS_LOG_ALARM.COM;1
7-JUN-1990 16:17:47.49
MCC_ALARMS_LOG_EXCEPTION.COM;1
7-JUN-1990 16:18:40.07
MCC_ALARMS_MAIL_ALARM.COM;1
7-JUN-1990 15:58:38.77
MCC_ALARMS_MAIL_EXCEPTION.COM;1
7-JUN-1990 15:57:47.48
MCC_ALARMS_RULES.COM;1
19-JUN-1991 08:48:32.10
MCC_ALARMS_SAMPLE_RULES.COM;1
5-JUL-1990 10:05:23.26
MCC_ALARMS_SECURITY.COM;1
7-JUN-1990 16:06:21.19
MCC_BRIDGE_AM.HELP;1
27-AUG-1990 13:30:07.00
MCC_BUILD_HELP.COM;1
6-SEP-1990 13:22:40.69
MCC_COMMANDS.CLD;1 14-JUN-1990 15:06:10.02
MCC_CONTROL_FM.HELP;1
4-AUG-1989 17:26:25.80
MCC_CREATE_MCC_GES.COM;1
28-JUN-1990 15:04:24.23
MCC_DEFINITION.DAT;1
12-SEP-1990 05:59:10.09
MCC_DICTIONARY.DAT;1
12-SEP-1990 05:55:38.37
MCC_DISPATCH_TABLE.DAT;1
18-JUN-1991 13:26:59.50
MCC_DNA4_AM.HELP;1 25-JUL-1990 09:31:15.38
MCC_DNA5AM_HELP.HELP;1
15-JUN-1990 09:58:51.26
MCC_DNS_BASIC_SETUP.COM;1
8-AUG-1990 16:41:58.88
MCC_DNS_SETUP.COM;1
26-JUL-1990 17:28:45.41
MCC_DNS_SETUP_DIR.COM;1
26-JUL-1990 15:26:11.51
MCC_DNS_SETUP_IDP.COM;1
26-JUL-1990 13:13:36.13
MCC_ENET_AM.HELP;1 19-JUN-1990 10:04:11.00
MCC_ENROLL_BMS.COM;1
14-JUN-1990 22:21:54.00
MCC_ENROLL_DIR.COM;1
20-JUN-1990 09:45:07.81
MCC_GENERAL_HELP.HELP;1
4-SEP-1990 15:50:58.15
MCC_KERNEL_AM.HELP;1
7-JUN-1990 17:09:11.81
MCC_MANAGE.HLP;1 7-JUN-1990 17:26:23.31
MCC_META_DEFINITION.DAT;1
18-JUN-1990 16:26:11.17
MCC_META_DICTIONARY.DAT;1
18-JUN-1990 16:26:09.38
MCC_MIR_ATTRIBUTE.DAT;1
31-AUG-1990 17:03:34.10
MCC_MIR_DIRECTORY.DAT;1
31-AUG-1990 17:03:32.38
MCC_NODE4_LOAD.COM;1
28-JUN-1990 16:34:01.70
MCC_PTB_PARSER.BPT;1
12-SEP-1990 07:08:22.59
Total of 36 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYS$STARTUP]
MCC_LOGICAL_BMS.COM;2
10-JUL-1991 11:45:42.77
MCC_LOGICAL_DIR.COM;5
10-JUL-1991 12:57:58.49
MCC_STARTUP_BMS.COM;3
4-FEB-1991 13:49:23.49
MCC_STARTUP_DIR.COM;5
31-JAN-1991 15:01:07.24
MCC_STARTUP_DNA4_EVL.COM;4
14-NOV-1990 14:27:47.67
Total of 5 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSEXE]
MCC_ALARMS_EXTRACT_RULES.EXE;3
24-FEB-1991 14:47:20.18
MCC_DAP_MAIN.EXE;5 24-FEB-1991 12:02:51.53
MCC_DEL_GS_POOL.EXE;5
24-FEB-1991 13:11:26.99
MCC_DNS_SETUP.EXE;5
24-FEB-1991 13:17:19.51
MCC_ENIM_CONVERT_MAIN.EXE;3
24-FEB-1991 14:59:34.88
MCC_EXPORTER_FM_BG.EXE;2
25-FEB-1991 10:50:05.77
MCC_EXPORTER_FM_WRITER.EXE;2
25-FEB-1991 10:50:39.74
MCC_HFB_MAIN.EXE;5 24-FEB-1991 14:17:14.47
MCC_HISTORIAN_FM_BG.EXE;2
25-FEB-1991 09:44:06.94
MCC_MAIN.EXE;5 24-FEB-1991 13:14:27.93
MCC_MIR_CVT_MAIN.EXE;5
24-FEB-1991 13:35:45.23
MCC_RBMS_CONVERT_MAIN.EXE;3
24-FEB-1991 14:59:15.98
Total of 12 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSHLP]
MCCBMS010.RELEASE_NOTES;1
25-SEP-1990 12:06:09.31
MCCBMS011.RELEASE_NOTES;8
6-MAR-1991 14:49:37.71
MCCDIR010.RELEASE_NOTES;1
25-SEP-1990 12:07:57.29
MCCDIR011.RELEASE_NOTES;6
6-MAR-1991 14:49:50.11
MCCSMS020.RELEASE_NOTES;3
17-OCT-1990 10:34:24.60
MCC_CHARACTER_CELL_HELP.HLB;5
25-FEB-1991 11:01:08.57
MCC_DAP_HELP.HLB;5 24-FEB-1991 12:03:00.29
MCC_DECWINDOWS_HELP.HLB;5
25-FEB-1991 11:01:08.87
MCC_TBD_HELP.HLB;5 24-FEB-1991 13:16:23.07
Total of 9 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSHLP.EXAMPLES]
MCC.DIR;1 18-JUN-1991 12:59:08.31
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSHLP.EXAMPLES.MCC]
MCC_YOURMM.EXE;5 24-FEB-1991 14:26:03.88
Total of 1 file.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSLIB]
MCC_ALARMS_FM.EXE;3
28-FEB-1991 09:59:23.81
MCC_BRIDGE_AM.EXE;3
24-FEB-1991 14:59:50.91
MCC_BRIDGE_AM_MGT_IF.H;1
11-SEP-1990 11:46:57.93
MCC_BRIDGE_AM_MGT_IF.PAS;1
11-SEP-1990 11:47:00.33
MCC_BRIDGE_AM_SVC_IF.H;1
11-SEP-1990 11:46:42.29
MCC_BRIDGE_AM_SVC_IF.PAS;1
11-SEP-1990 11:46:44.75
MCC_COMMON_DEFINITIONS.H;1
11-SEP-1990 07:02:37.01
MCC_COMMON_DEFINITIONS.PAS;1
11-SEP-1990 07:03:12.61
MCC_CONFIG_FM.EXE;5
24-FEB-1991 15:02:41.56
MCC_CONTROL_FM.EXE;5
24-FEB-1991 13:18:40.54
MCC_DESCRIP.H;1 3-FEB-1990 14:07:14.42
MCC_DNA4_AM.EXE;5 24-FEB-1991 15:34:58.43
MCC_DNA4_AM_ANODE_SVC_IF.H;1
11-SEP-1990 11:07:39.86
MCC_DNA4_AM_ANODE_SVC_IF.PAS;1
11-SEP-1990 11:07:42.61
MCC_DNA4_AM_AREA_SVC_IF.H;1
11-SEP-1990 11:16:26.58
MCC_DNA4_AM_AREA_SVC_IF.PAS;1
11-SEP-1990 11:16:30.69
MCC_DNA4_AM_CIRC_SVC_IF.H;1
11-SEP-1990 11:06:25.55
MCC_DNA4_AM_CIRC_SVC_IF.PAS;1
11-SEP-1990 11:06:32.07
MCC_DNA4_AM_LINE_SVC_IF.H;1
11-SEP-1990 11:09:16.24
MCC_DNA4_AM_LINE_SVC_IF.PAS;1
11-SEP-1990 11:09:19.62
MCC_DNA4_AM_LINK_SVC_IF.H;1
11-SEP-1990 11:15:25.89
MCC_DNA4_AM_LINK_SVC_IF.PAS;1
11-SEP-1990 11:15:28.56
MCC_DNA4_AM_LSINK_SVC_IF.H;1
11-SEP-1990 11:12:13.01
MCC_DNA4_AM_LSINK_SVC_IF.PAS;1
11-SEP-1990 11:12:15.87
MCC_DNA4_AM_MGT_IF.H;1
11-SEP-1990 11:18:53.32
MCC_DNA4_AM_MGT_IF.PAS;1
11-SEP-1990 11:19:00.57
MCC_DNA4_AM_NODE4_SVC_IF.H;1
11-SEP-1990 11:02:45.47
MCC_DNA4_AM_NODE4_SVC_IF.PAS;1
11-SEP-1990 11:02:48.40
MCC_DNA4_AM_OBJ_SVC_IF.H;1
11-SEP-1990 11:17:51.74
MCC_DNA4_AM_OBJ_SVC_IF.PAS;1
11-SEP-1990 11:17:56.41
MCC_DNA4_AM_OSTREAM_SVC_IF.H;1
11-SEP-1990 11:10:10.53
MCC_DNA4_AM_OSTREAM_SVC_IF.PAS;1
11-SEP-1990 11:10:12.53
MCC_DNA4_AM_RNODE_SVC_IF.H;1
11-SEP-1990 11:04:05.99
MCC_DNA4_AM_RNODE_SVC_IF.PAS;1
11-SEP-1990 11:04:07.48
MCC_DNA4_AM_RSINK_SVC_IF.H;1
11-SEP-1990 11:14:29.12
MCC_DNA4_AM_RSINK_SVC_IF.PAS;1
11-SEP-1990 11:14:30.88
MCC_DNA4_EVL.EXE;4 24-FEB-1991 15:36:17.87
MCC_DNA5AM_CSMACD.H;1
11-SEP-1990 12:03:41.68
MCC_DNA5AM_CSMACD.PAS;1
11-SEP-1990 12:03:44.61
MCC_DNA5AM_DDCMP.H;1
11-SEP-1990 12:05:42.54
MCC_DNA5AM_DDCMP.PAS;1
11-SEP-1990 12:05:44.70
MCC_DNA5AM_DEVICE.H;1
11-SEP-1990 12:07:04.75
MCC_DNA5AM_DEVICE.PAS;1
11-SEP-1990 12:07:06.21
MCC_DNA5AM_EVENT.H;1
11-SEP-1990 12:25:52.44
MCC_DNA5AM_EVENT.PAS;1
11-SEP-1990 12:25:53.80
MCC_DNA5AM_FRAME.H;1
11-SEP-1990 12:08:40.05
MCC_DNA5AM_FRAME.PAS;1
11-SEP-1990 12:08:41.23
MCC_DNA5AM_HDLC.H;1
11-SEP-1990 12:10:30.45
MCC_DNA5AM_HDLC.PAS;1
11-SEP-1990 12:10:33.15
MCC_DNA5AM_LAPB.H;1
11-SEP-1990 12:11:49.49
MCC_DNA5AM_LAPB.PAS;1
11-SEP-1990 12:11:50.66
MCC_DNA5AM_LOOPBACK.H;1
11-SEP-1990 12:26:31.27
MCC_DNA5AM_LOOPBACK.PAS;1
11-SEP-1990 12:26:32.63
MCC_DNA5AM_MODEM.H;1
11-SEP-1990 12:13:44.84
MCC_DNA5AM_MODEM.PAS;1
11-SEP-1990 12:13:46.49
MCC_DNA5AM_MOM.H;1 11-SEP-1990 12:47:48.46
MCC_DNA5AM_MOM.PAS;1
11-SEP-1990 12:47:51.25
MCC_DNA5AM_MOP.H;1 11-SEP-1990 12:33:11.49
MCC_DNA5AM_MOP.PAS;1
11-SEP-1990 12:33:12.66
MCC_DNA5AM_NAMECLERK.H;1
11-SEP-1990 12:15:25.92
MCC_DNA5AM_NAMECLERK.PAS;1
11-SEP-1990 12:15:27.14
MCC_DNA5AM_NAMESERVER.H;1
11-SEP-1990 12:17:13.61
MCC_DNA5AM_NAMESERVER.PAS;1
11-SEP-1990 12:17:17.49
MCC_DNA5AM_NODE.H;1
11-SEP-1990 12:01:58.26
MCC_DNA5AM_NODE.PAS;1
11-SEP-1990 12:01:59.99
MCC_DNA5AM_NSP.H;1 11-SEP-1990 12:18:42.44
MCC_DNA5AM_NSP.PAS;1
11-SEP-1990 12:18:43.77
MCC_DNA5AM_ROUTING.H;1
11-SEP-1990 12:22:17.67
MCC_DNA5AM_ROUTING.PAS;1
11-SEP-1990 12:22:19.06
MCC_DNA5AM_SESSION.H;1
11-SEP-1990 12:28:35.19
MCC_DNA5AM_SESSION.PAS;1
11-SEP-1990 12:28:36.35
MCC_DNA5AM_TRANSPORT.H;1
11-SEP-1990 12:30:28.34
MCC_DNA5AM_TRANSPORT.PAS;1
11-SEP-1990 12:30:29.76
MCC_DNA5AM_X25ACCESS.H;1
11-SEP-1990 12:37:51.24
MCC_DNA5AM_X25ACCESS.PAS;1
11-SEP-1990 12:37:55.34
MCC_DNA5AM_X25CLIENT.H;1
11-SEP-1990 12:39:08.10
MCC_DNA5AM_X25CLIENT.PAS;1
11-SEP-1990 12:39:10.68
MCC_DNA5AM_X25PROT.H;1
11-SEP-1990 12:41:32.75
MCC_DNA5AM_X25PROT.PAS;1
11-SEP-1990 12:41:34.15
MCC_DNA5AM_X25SERVER.H;1
11-SEP-1990 12:42:58.41
MCC_DNA5AM_X25SERVER.PAS;1
11-SEP-1990 12:43:00.04
MCC_DNA5_AM.EXE;5 24-FEB-1991 16:25:32.70
MCC_DOMAIN_FM.EXE;4
26-FEB-1991 23:00:50.30
MCC_ENET_AM.EXE;3 24-FEB-1991 16:37:31.35
MCC_ENET_AM_MGT_IF.H;1
11-SEP-1990 13:11:51.91
MCC_ENET_AM_MGT_IF.PAS;1
11-SEP-1990 13:11:53.97
MCC_ENET_AM_SVC_IF.H;1
11-SEP-1990 13:11:36.99
MCC_ENET_AM_SVC_IF.PAS;1
11-SEP-1990 13:11:39.68
MCC_ENROLL.MLB;1 11-SEP-1990 06:55:41.99
MCC_EXPORTER_FM.EXE;2
28-FEB-1991 11:13:13.66
MCC_FCL_PM.EXE;5 24-FEB-1991 14:14:37.63
MCC_FM_ALARMS_MGT_IF.H;1
11-SEP-1990 11:21:58.44
MCC_FM_ALARMS_MGT_IF.PAS;1
11-SEP-1990 11:22:16.90
MCC_FM_ALARMS_SVC_IF.H;1
11-SEP-1990 11:22:45.37
MCC_FM_ALARMS_SVC_IF.PAS;1
11-SEP-1990 11:23:01.78
MCC_FM_CONFIG_MGT_IF.H;1
11-SEP-1990 12:07:34.87
MCC_FM_CONFIG_MGT_IF.PAS;1
11-SEP-1990 12:07:35.58
MCC_FM_CONTROL_MGT_IF.H;1
11-SEP-1990 10:58:36.32
MCC_FM_CONTROL_MGT_IF.PAS;1
11-SEP-1990 10:58:37.08
MCC_HISTORIAN_FM.EXE;2
25-FEB-1991 09:41:04.21
MCC_ICONIC_MAP_PM.EXE;4
5-MAR-1991 16:11:56.17
MCC_INTERFACE_DEF.H;1
11-SEP-1990 06:56:16.59
MCC_INTERFACE_DEF.L32;1
11-SEP-1990 06:56:22.00
MCC_INTERFACE_DEF.MAR;1
11-SEP-1990 06:56:02.61
MCC_INTERFACE_DEF.PAS;1
11-SEP-1990 06:56:27.41
MCC_INTERFACE_DEF.PEN;1
11-SEP-1990 06:56:30.77
MCC_INTERFACE_DEF.R32;1
11-SEP-1990 06:56:19.67
MCC_KERNEL_AM_MGT_IF.H;1
11-SEP-1990 09:46:51.32
MCC_KERNEL_AM_MGT_IF.PAS;1
11-SEP-1990 09:46:52.59
MCC_KERNEL_INIT.OBJ;5
24-FEB-1991 12:20:23.04
MCC_KERNEL_SHR.EXE;5
24-FEB-1991 13:13:05.81
MCC_MSG.H;1 17-SEP-1990 11:39:36.05
MCC_MSG.L32;1 17-SEP-1990 11:39:46.01
MCC_MSG.MAR;1 17-SEP-1990 11:39:54.93
MCC_MSG.PAS;1 17-SEP-1990 11:40:03.01
MCC_MSG.PEN;1 17-SEP-1990 11:40:10.12
MCC_MSG.R32;1 17-SEP-1990 11:40:18.43
MCC_MTS_PRIV_SHR.EXE;5
10-JUL-1991 12:59:22.35
MCC_NOTIFICATION_FM.EXE;2
24-FEB-1991 14:21:32.70
MCC_PA_FM.EXE;2 24-FEB-1991 17:30:11.77
MCC_PM_FCL_MGT_IF.H;1
11-SEP-1990 10:46:07.19
MCC_PM_FCL_MGT_IF.PAS;1
11-SEP-1990 10:46:07.88
MCC_PTB.EXE;5 24-FEB-1991 14:06:15.08
MCC_RESOURCE.DAT;4 23-JAN-1991 16:04:26.82
MCC_SAMPLE_AM.EXE;5
24-FEB-1991 14:30:13.13
MCC_UI_TBD.EXE;5 24-FEB-1991 13:16:18.27
MCC_VEA_DEF.H;1 17-SEP-1990 11:35:00.65
MCC_VEA_DEF.L32;1 17-SEP-1990 11:35:20.28
MCC_VEA_DEF.MAR;1 17-SEP-1990 11:35:29.43
MCC_VEA_DEF.PAS;1 17-SEP-1990 11:35:38.63
MCC_VEA_DEF.PEN;1 17-SEP-1990 11:35:48.09
MCC_VEA_DEF.R32;1 17-SEP-1990 11:35:56.25
Total of 132 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSMGR]
MCC_EXPORTER_BACKGROUND.COM;2
4-JAN-1991 20:38:57.91
MCC_HISTORIAN_BACKGROUND.COM;2
4-JAN-1991 20:38:14.59
Total of 2 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSMSG]
MCCMSG.EXE;5 22-FEB-1991 15:03:25.34
MCCTBDMSG.EXE;5 24-FEB-1991 13:16:29.05
Total of 2 files.
Directory SYS$SPECIFIC:[SYSCOMMON.SYSTEST]
MCC.DIR;1 18-JUN-1991 12:59:06.17
MCC_BMS_IVP.COM;3 17-JAN-1991 15:20:34.88
MCC_DIR_IVP.COM;5 7-JAN-1991 14:21:44.84
Total of 3 files.
Directory SYS$SPECIFIC:[SYSCOMMON.VUE$LIBRARY.USER]
MCCSMS$PROFILE.VUE$DAT;1
13-JUL-1990 16:57:45.85
Total of 1 file.
Directory SYS$SPECIFIC:[SYSMGR]
MCC.LOG;1 10-JUL-1991 11:01:47.94
MCCBMS011.LOG;2 10-JUL-1991 11:20:28.71
MCCBMS011.LOG;1 10-JUL-1991 11:16:30.40
MCCDIR011.LOG;2 10-JUL-1991 12:33:26.48
MCCDIR011.LOG;1 10-JUL-1991 11:42:29.81
MCC_0529000400AA000001CA3EB870F6AF80.MCC_MAP_OCSIS;2
10-JUL-1991 17:06:52.73
MCC_0529000400AA000001CA3EB870F6AF80.MCC_MAP_OCSIS;1
10-JUL-1991 13:55:43.42
MCC_RESOURCE.DAT;4 10-JUL-1991 17:06:42.98
MCC_RESOURCE.DAT;3 10-JUL-1991 10:48:15.23
MCC_RESOURCE.DAT;2 10-JUL-1991 10:09:40.65
MCC_RESOURCE.DAT;1 9-JUL-1991 16:39:01.64
Total of 11 files.
Directory SYS$SPECIFIC:[SYSMGR.SMITH]
MCC_0529000400AA000001CA3E1E0A21AAC0.MCC_MAP_OCSIS;1
10-JUL-1991 10:44:41.79
Total of 1 file.
Grand total of 15 directories, 218 files.
$ SHO LOG *MCC*
(LNM$PROCESS_TABLE)
(LNM$JOB_805F9C00)
(LNM$GROUP_000001)
(LNM$SYSTEM_TABLE)
"MCC_COMMON" = "OCSMCC$DKA200:[MCC]"
"MCC_ICONS" = "MCC_COMMON"
"MCC_MAPS" = "SYS$DISK:[]"
= "MCC_COMMON"
"MCC_NODE_IDP" = "49::"
"MCC_REPORTS_FILES" = "OCSMCC$DKA200:[MCC.MCC_REPORTS_FILES]"
"MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]"
"MCC_SYSTEM" = "MCC_SPECIFIC"
= "MCC_COMMON"
"MCC_TDF" = "-4:00"
"MCC_UIL" = "MCC_COMMON"
(DECW$LOGICAL_NAMES)
$ MANAGER/ /ENTERPRING
DECmcc (V1.1.0)
)0[4l=>)0[4l=>
MCC> TEST MCC0 0 NOTIVI FICATION _FM
MCC 0 NOTIFICATION_FM
AT 10-JUL-1991 17:50:00
Test Successful
MCC> ENTROL
MCC> MCC
MCC> ENROLL MCC_NOTIFICATION_FM
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
MCC>
%MCC-I-CANCEL, cancel
MCC> 7[7m Exit [m8
>>
$ SET DEF SYS$MANAGER
$ DIR *MCC*
Directory SYS$SYSROOT:[SYSMGR]
MCC.LOG;1 MCCBMS011.LOG;2 MCCBMS011.LOG;1 MCCDIR011.LOG;2
MCCDIR011.LOG;1 MCC_0529000400AA000001CA3EB870F6AF80.MCC_MAP_OCSIS;2
MCC_0529000400AA000001CA3EB870F6AF80.MCC_MAP_OCSIS;1 MCC_RESOURCE.DAT;4
MCC_RESOURCE.DAT;3 MCC_RESOURCE.DAT;2 MCC_RESOURCE.DAT;1
Total of 11 files.
Directory SYS$COMMON:[SYSMGR]
MCC_EXPORTER_BACKGROUND.COM;2 MCC_HISTORIAN_BACKGROUND.COM;2
Total of 2 files.
Grand total of 2 directories, 13 files.
$ TYPE MCC* C.LOG
(LNM$PROCESS_TABLE)
(LNM$JOB_805F3900)
(LNM$GROUP_000001)
(LNM$SYSTEM_TABLE)
"MCC_COMMON" = "OCSMCC$DKA200:[MCC]"
"MCC_ICONS" = "MCC_COMMON"
"MCC_MAPS" = "SYS$DISK:[]"
= "MCC_COMMON"
"MCC_NODE_IDP" = "49::"
"MCC_REPORTS_FILES" = "OCSMCC$DKA200:[MCC.MCC_REPORTS_FILES]"
"MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]"
"MCC_SYSTEM" = "MCC_SPECIFIC"
= "MCC_COMMON"
"MCC_TDF" = "-4:00"
"MCC_UIL" = "MCC_COMMON"
(DECW$LOGICAL_NAMES)
$ TYUPE PE MCCBMS011.LOG;2
Welcome to VAX/VMS V5.4-2
Username: SYSTEM
Password:
Welcome to VAX/VMS version V5.4-2 on node OCSMCC
Last interactive login on Wednesday, 10-JUL-1991 11:16
Last non-interactive login on Wednesday, 10-JUL-1991 08:53
Z
[c
[62"p F
>
$ @SYS$UPDATE:VMSINSTAL MCCBMS011 DAD2:[MCCBMS011.KIT]
VAX/VMS Software Product Installation Procedure V5.4-2
It is 10-JUL-1991 at 11:22.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-ACTIVE, The following processes are still active:
DNS$TA
DNS$BACK
* Do you want to continue anyway [NO]? Y
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:
MCCBMS V1.1
Beginning installation of MCCBMS V1.1 at 11:22
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
************************************************************
* *
* DECmcc BMS V1.1.0 *
* Integrated Package *
* *
* Installation Procedure *
* *
************************************************************
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
DECmcc requires a directory where the DECmcc common files
will be installed. If the logical MCC_COMMON is defined, the
default is for the files to be installed in that directory.
If the logical is not defined, the default is for the files
to be installed in a directory on the system disk called
SYS$COMMON:[MCC]. The installer may override the default.
The target directory for the files as it is now defined is
shown below.
Press RETURN to use the value shown or enter a new disk and
directory specification.
* Target directory for DECmcc Common files [OCSMCC$DKA200:[MCC]]:
* Do you want to run the DECmcc BMS IVP after the installation [YES]?
* Do you want to purge files replaced by this installation [YES]?
The Time Differential Factor (TDF) is the difference between
your time zone and the international standard Coordinated
Universal Time (UTC)
A negative (-) TDF value means that this node is west of UTC
A positive (+) TDF value means that this node is east of UTC
The range is from -12:00 to +13:00. The format is +hh:mm or
-hh:mm with hh indicating the number of hours and mm
indicating the number of minutes. For example:
California (Pacific Standard Time) is -8:00 hours from UTC.
Oklahoma (Standard Time) is -6:00 hours from UTC.
Eastern Standard Time is -5:00 hours from UTC.
Eastern Daylight Time is -4:00 hours from UTC.
Ontario, west of longitude W.63 degrees is -5:00
hours from UTC.
Ontario, east of longitude W.63 degrees is -4:00
hours from UTC.
Newfoundland is -3:30 hours from UTC.
Great Britain, Iceland, Portugal, Upper Volta are
at UTC or 0:0.
Great Britain, Summer Time +1:00 hour from UTC.
Greece is +2:00 hours from UTC.
India is +5:30 hours from UTC.
Singapore is +7:30 hours from UTC.
Japan is +9:00 hours from UTC.
Australian Capital Territory is +10:00 hours from UTC.
* Time Differential Factor [-4:00]:
You must specify the IDP (or network address initial domain
part) for your network. This must either be the default
value of "49::", or a value explicitly allocated for your
network by one of the recognized allocation authorities.
The format is:
afi:idi:
where:
afi = The "authority and format identifier". This is two
decimal digits indicating the IDP allocation
authority
idi = The "initial domain identifier". This is a string of
decimal digits that has been allocated specifically
for your network.
An IDP of "49::" may be used if your network will not be
interconnected with other OSI networks (there is no "idi"
associated with this "afi").
* Initial Domain Part [49::]:
The DECmcc Reports Package consists of files that allow you
to use DATATRIEVE to create reports using data exported from
DECmcc. Please see the Reports Package section of the
DECmcc Performance Analyzer Use manual for information
on using the DECmcc Reports Package with DATATRIEVE.
The Reports package requires 1100 blocks.
* Do you want to install the DECmcc Reports Package [No]? Y
* Target directory for DECmcc Reports files [OCSMCC$DKA200:[MCC.MCC_REPORTS_FILE
S]]:
Product: DECMCC-BMS
Producer: DEC
Version: 1.1
Release Date: 28-FEB-1991
* Does this product have an authorization key registered and loaded? Y
VMSINSTAL asks no additional questions.
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VMSINSTAL-I-RESTORE, Restoring product save set D ...
Following the copying of the files, the DECmcc BMS startup
command procedure(s) will be invoked. Operational tables
will be created by this procedure.
To automatically set up DECmcc BMS on your system,
edit your local system start-up command procedure
SYS$MANAGER:SYSTARTUP_V5.COM
so that it invokes the DECmcc BMS start-up command
procedure. Add:
@SYS$STARTUP:MCC_STARTUP_BMS.COM
after the statement that invokes the DECnet start-up
command file (STARTNET.COM).
NOTE: If you have previously installed the DECmcc DIRECTOR
on this system, you should REMOVE the line:
@SYS$STARTUP:MCC_STARTUP_DIR.COM
from your SYS$MANAGER:SYSTARTUP_V5.COM procedure.
NOTE: The DECdns clerk must also be started up before
the MCC_STARTUP_BMS command procedure is invoked.
Following the DECmcc BMS start-up the DECmcc BMS
postinstallation command procedure will be invoked.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
Beginning DECmcc BMS Postinstallation Procedure ...
Deleting obsolete DECmcc verbs...
The MCC_STARTUP_BMS startup procedure for DECmcc V1.1.0 is now running.
DECmcc (V1.1.0)
MCC 0 ALARMS RULE __dummy_test
AT 10-JUL-1991 12:01:29
Entity created successfully.
MCC 0 ALARMS RULE __dummy_test
AT 10-JUL-1991 12:01:35
Entity deleted successfully.
The MCC_STARTUP_BMS startup procedure for DECmcc V1.1.0 is now ending.
Completing DECmcc BMS Postinstallation Procedure ...
Beginning DECmcc BMS Installation Verification Procedure ...
The IVP for DECmcc BMS will now be run.
DECmcc (V1.1.0)
MCC 0
AT 10-JUL-1991 12:01:52
Test Successful
DECmcc (V1.1.0)
MCC 0 FCL
AT 10-JUL-1991 12:02:02
Test Successful
DECmcc (V1.1.0)
MCC 0 CONFIG_FM
AT 10-JUL-1991 12:02:12
Test Successful
DECmcc (V1.1.0)
MCC 0 CONTROL_FM
AT 10-JUL-1991 12:02:22
Test Successful
DECmcc (V1.1.0)
MCC 0 DNA4_AM
AT 10-JUL-1991 12:02:34
Test Successful
DECmcc (V1.1.0)
MCC 0 DNA5_AM
AT 10-JUL-1991 12:02:45
Test Successful.
DECmcc (V1.1.0)
MCC 0 ICONICMAP
AT 10-JUL-1991 12:02:56
Test Successful
DECmcc (V1.1.0)
MCC 0 DOMAIN_FM
AT 10-JUL-1991 12:03:06
Test Successful
DECmcc (V1.1.0)
MCC 0 SAMPLE_AM
AT 10-JUL-1991 12:03:17
Test successful.
DECmcc (V1.1.0)
MCC 0 ALARMS
AT 10-JUL-1991 12:03:28
Test successful.
DECmcc (V1.1.0)
MCC 0 BRIDGE_AM
AT 10-JUL-1991 12:03:38
Test successful.
DECmcc (V1.1.0)
MCC 0 ETHERNET_AM
AT 10-JUL-1991 12:03:49
Test successful.
DECmcc (V1.1.0)
MCC 0 HISTORIAN_FM
AT 10-JUL-1991 12:03:59
Test Successful
DECmcc (V1.1.0)
MCC 0 PA
AT 10-JUL-1991 12:04:10
MCC PA Test Successful
DECmcc (V1.1.0)
MCC 0 EXPORTER_FM
AT 10-JUL-1991 12:04:21
Test Successful
DECmcc (V1.1.0)
MCC 0 NOTIFICATION_FM
AT 10-JUL-1991 12:04:32
Test Successful
DECmcc BMS V1.1.0 Installation Successful
Completing DECmcc BMS Installation Verification Procedure ..
Installation of MCCBMS V1.1 completed at 12:04
VMSINSTAL procedure done at 12:04
$ LO
SYSTEM logged out at 10-JUL-1991 12:33:17.75
$
$ LOG
SYSTEM logged out at 10-JUL-1991 17:54:24.43
Local -011- Session 1 disconnected from OCSMCC
Local> C OCSMCC
Local -010- Session 1 to OCSMCC established
Welcome to VAX/VMS V5.4-2
Username: SYSTEM
Password:
Welcome to VAX/VMS version V5.4-2 on node OCSMCC
Last interactive login on Wednesday, 10-JUL-1991 17:46
Last non-interactive login on Wednesday, 10-JUL-1991 16:05
Z[c[62"p F>
$ SET PROC/PRIV=ALL
$
$ DIR/SECUR/DATE/SIEZE ZE=ALL MMC_S CC_SYSTEM:MCC_D*.DAT
Directory OCSMCC$DKA200:[MCC]
MCC_DEFINITION.DAT;4
13323/13323 28-JAN-1991 21:42:11.47 [SYSTEM]
(RWED,RWED,RWED,R)
MCC_DICTIONARY.DAT;4
21438/21438 28-JAN-1991 21:42:10.31 [SYSTEM]
(RWED,RWED,RWED,R)
MCC_DISPATCH_TABLE.DAT;1
450/450 10-JUL-1991 13:06:47.22 [SYSTEM]
(RWED,RWED,RWED,R)
MCC_DOMAIN_DELNI_ICON.DAT;4
4/6 1-MAY-1990 13:53:17.00 [SYSTEM]
(RWED,RWED,RWED,RE)
MCC_DOMAIN_DEMPR_ICON.DAT;4
4/6 1-MAY-1990 13:55:44.00 [SYSTEM]
(RWED,RWED,RWED,RE)
MCC_DOMAIN_DESPR_ICON.DAT;4
4/6 1-MAY-1990 13:56:03.00 [SYSTEM]
(RWED,RWED,RWED,RE)
MCC_DOMAIN_ICON.DAT;4
3/3 5-APR-1990 12:19:37.29 [SYSTEM]
(RWED,RWED,RWED,RE)
Total of 7 files, 35226/35232 blocks.
$ DIR/SECUR/DATE/SIZE=ALL MCC_SYSTEM:MCC_MIR*.DAT
Directory OCSMCC$DKA200:[MCC]
MCC_MIR_ATTRIBUTE.DAT;4
81/81 10-JUL-1991 12:59:03.89 [SYSTEM]
(RWED,RWED,RWED,R)
MCC_MIR_DIRECTORY.DAT;4
66/66 10-JUL-1991 12:59:00.46 [SYSTEM]
(RWED,RWED,RWED,R)
Total of 2 files, 147/147 blocks.
|
| 863.14 | thanks for the well formed input | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Thu Jul 11 1991 14:59 | 13 |
| Everything looks fine (files that is), if possible could you please
send a contact phone number to Jim Lemmon. Jim is the project lead
for the iconic map team, he will help get you going. You can contact
Jim at (TOOK::LEMMON) or DTN 226-5329.
Also, I noticed you did a self management command against the notification
FM, did you also validate that the NOTIFY command worked? and, when it
died from the iconic map did you check to see if any other modules could
be invoked?
thanks
jill
|
| 863.15 | re 863.13 | BARREL::LEMMON | | Wed Jul 17 1991 12:10 | 3 |
| I am lookinto 863.13. Will get back with results.
/Jim
|
| 863.16 | Not an installation problem but a DECMCC startup problem | POLE::LEMMON | | Mon Jul 22 1991 12:59 | 32 |
| re: 863.13
The message appears if either of the following occurs:
1. The dictionary does not contain the DOMAIN RULE entity
class information.
2. A test call to the notification fm fails. The call made
is SHOW DOMAIN XXX RULE YYY. If this call returns
a MCC_S_RESPONSE status or the no such entity common
exception, the notification fm is there.
In most cases this problem is caused by the notification fm's not
being enrolled. Usually the MCC_STARTUP_BMS.COM startup procedure
exits prematurely before the MCC> DO ENROLL MCC_SYSTEM:MCC_ENROLL_BMS.COM
is executed.
If you encounter this problem try manually enrolling the notification
fm by typing
MCC> ENROLL MCC_NOTIFICATION_FM
If you do not see a message saying something along the lines of
duplicate dispatch entries found, there is a good chance that DECmcc
did not start up correctly. I suggest that you re-execute the
MCC_STARTUP_BMS.COM file and watch for any errors. One example
of where I saw it fail on a VS2000 was when it tried installing
MCC_MTS_PRIV_SHR.EXE. The INSTALL utility generated a IDP
error and the startup procedure exited at this point.
|