| John,
A quick few questions. Have you installed a previous version of
MCC? and if so what were you using it for (development of management)?
What version of VMS are you running?
The FCL PM is unable to find the parse tables that the installation
procedure should have placed in the mcc_system (logical) directory.
Could you also check to see if the mcc_system logical has been defined,
and what files are located in that directory?
thanks
|
|
Thanks a lot for the pointer to look at the various logicals. In the
startup file MCC_STARTUP_DIR.COM the logical MCC_SYSTEM pointed at
MCC_SPECIFIC and MCC_COMMON.
Changing the line "$ def/syst/exec mcc_system mcc_specific,mcc_common
to
"$ def/syst/exec mcc_system sys$specific:[mcc],sys$common:[mcc]
Resolved the problem. The startup procedure now works as expected,
and I can invoke MCC with the "MANAGE/ENTERPRISE" command.
Thanks for your help,
John
|
| Hi,
you might want to check the MCC_STARTUP_DIR.COM file again. during
the installation, a number of logicals are created (mcc_common, mcc_tdf,
mcc_node_idp, etc.). they are defined based upon user input. the user
is then instructed to uncomment the definition of these logicals in the
MCC_STARTUP_DIR.COM file, with site-specific modifications. in the
MCC_STARTUP_DIR.COM file, before the line that you modified, are the
following lines.
$! Uncomment and modify the next 2 commands to reflect the actual
$! value for mcc_common
$! Call deassign_logical mcc_common <<<<<<<<<<
$! define/system/EXECUTIVE_MODE mcc_common sys$common:[mcc] <<<<<<<<<<
$ Call deassign_logical mcc_specific
$ define/system/EXECUTIVE_MODE mcc_specific sys$specific:[mcc]
$ Call deassign_logical mcc_system
with the 2 commands (annotated by <<<<<<<<<<) appropriately uncommented, and
modified, the line that you modified:
$ define/system/EXECUTIVE_MODE mcc_system mcc_specific,mcc_common
should be okay. if the 2 commands are not appropriately uncommented, your
change will give you a value for mcc_system, but when next you boot, you
will not have a definition for mcc_common. also the mcc_tdf, and mcc_node_idp
logicals are defined in the same manner as mcc_common.
regards,
\steve
<<< Note 202.2 by PANIC::GILL "John, DTN 847-5849" >>>
-< Logicals giving problems - Thanks >-
Thanks a lot for the pointer to look at the various logicals. In the
startup file MCC_STARTUP_DIR.COM the logical MCC_SYSTEM pointed at
MCC_SPECIFIC and MCC_COMMON.
Changing the line "$ def/syst/exec mcc_system mcc_specific,mcc_common
to
"$ def/syst/exec mcc_system sys$specific:[mcc],sys$common:[mcc]
Resolved the problem. The startup procedure now works as expected,
and I can invoke MCC with the "MANAGE/ENTERPRISE" command.
Thanks for your help,
John
|
|
RE: .3
I too got burnt by the logicals having been commented out by
MCC installation procedure. Since the installation procedure
does ask what the values of these logicals should be, I had
EXPECTED the INSTALL procedure to set them up accordingly. Why is the
user asked to do that same thing over by having to go through a
tedious, redundant step to make DECmcc functional.
It may be OK to display the message about the user being able to
change the logicals, if necessary. I suggest that the installation
procedure not comment out the logicals. It's good to know that DECmcc
installation leaves SYSTARTUP_V5.COM alone. However, it should provide
a SINGLE DECmcc startup file that can be used without further tweaks
to start various components. The system manager will then need to add
only a single line in SYSTARTUP to call this file, as is generally the
case with other LPs.
Muhammad
|