[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 |
1961.0. "Problems with T1.2.4 with no DNS" by MEO78B::BARNHOORN (here on Cactus Island) Wed Dec 18 1991 01:26
Hi,
I've just installed DECmcc T1.2.4 (kit/pak from note 3.120) on a VAX station
3100 with VMS 5.4, see below for a copy of the install log.
I selected NOT to use DNS and use the local MIR.
DNS is not running or installed on this machine.
When it came to run the IVP it failed because DNS$SHARE.EXE was not installed.
The install guide or release notes didnot mention that the DNS$SHARED had to be
installed.
Trying
$ MAN/ENT
%DCL-W-ACTIMAGE, error activating image DNS$SHARE
-CLI-E-IMGNAME, image file CMGOP1$DKB0:[SYS0.SYSCOMMON.][SYSLIB]DNS$SHARE.EXE;1
-SYSTEM-F-PROTINSTALL, protected images must be installed
$
I didnot install the DNS product, but just installed the file.
eg:
$install add sys$library:DNS$SHARE.EXE/SHARE/PROTECT/OPEN
fixed the above problem.
Then I tried the IVP and got a little further but it produced
%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
after on succesfull Test.
*******************************IVP LOG******************************
$ @MCC_BMS_IVP.COM
The IVP for DECmcc BMS will now be run.
DECmcc (T1.2.4)
MCC 0
AT 18-DEC-1991 10:23:47
Test Successful
DECmcc (T1.2.4)
%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 FCL, TO FILE = MCCBMS$OUT.TXT"
DECmcc BMS T1.2.4 Installation Failed
%MCC-F-FAILED, fatal DECmcc error
$
***************************END LOG***************************************
If I tried any other combination of MAN/ENT TEST MCC 0 DNA4_AM, etc
always produces the same error of:
%MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
What have I done wrong?
Also any command produces the same error.
thanks for any advice.
Mark Barnhoorn
(Australia)
****************************VMS Install Log****************************
$ @sys$update:vmsinstal mccbmst012 disk_1:[users.barnhoorn]
VAX/VMS Software Product Installation Procedure V5.4
It is 17-DEC-1991 at 16:05
Enter a question mark (?) at any time for help
%VMSINSTAL-W-ACTIVE, The following processes are still active:
SERVER_0039
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]? yes
The following products will be processed:
MCCBMST V1.2
Beginning installation of MCCBMST V1.2 at 16:06
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
************************************************************
* *
* DECmcc BMS T1.2.4 *
* 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 [SYS$COMMON:[MCC]]: disk_net:[mcc]
* Do you want to run the DECmcc BMS IVP after the installation [YES]? yes
* Do you want to purge files replaced by this installation [YES]? yes
%VMSINSTAL-I-SYSDIR, This product creates system specific directory [MCC]
If you intend to execute this layered product on other
nodes in your VAXcluster, and you have the appropriate
software license, you must prepare the system-specific
roots on the other nodes by issuing the following command
on each node (using a suitably privileged account):
$ CREATE/DIRECTORY SYS$SPECIFIC:[MCC]/OWNER_UIC=PARENT -
/PROT=(S:RWE,O:RWE,G:RE,W:R)
%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.MCC].
%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MCC].
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. A few examples are:
Eastern Standard Time is -5:00 hours from UTC.
Eastern Daylight Time is -4:00 hours from UTC.
Great Britain, Iceland, Portugal, Upper Volta are
at UTC or 0:0.
Great Britain, Summer Time +1:00 hour from UTC.
Japan is +9:00 hours from UTC.
* Time Differential Factor [-4:00]: +10:00
DECmcc requires the use of a Name Service for the storage
and retrieval of entity information. It is recommended that
DECdns be used for this purpose. DECdns is used to make
information available network-wide and can be accessed
throughout the network by software such as DECmcc.
Some installation sites may not need or want network-wide
availability for this network entity information. An
example might be a network which has little network entity
information or security relavent information. Also, a
DECdns Server has to be installed on the network otherwise
DECmcc cannot use DECdns as a Name Service.
In such cases, DECmcc provides the capability of making the
Namespace local to the system on which DECmcc is installed.
This option does NOT use the DECdns software for accessing
network-wide Namespace information.
The user may choose only one Name Service. Changing from
one Name Service to another at a later time may require
manual procedures for re-entering entity data.
* Use DECdns as the DECmcc Name Service [YES]? NO
Using DECmcc Local MIR as the DECmcc Name Service
* Is this correct [YES]? YES
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 1650 blocks.
* Do you want to install the DECmcc Reports Package [No]? NO
Product: DECMCC-BMS
Producer: DEC
Version: 1.2
Release Date: 22-FEB-1992
* Does this product have an authorization key registered and loaded? yes.
VMSINSTAL asks no additional questions.
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VMSINSTAL-I-RESTORE, Restoring product save set D ...
Applying Patch to VMS V5.4 VAXCRTL Run Time Library
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file CMGOP1$DKB0:[SYS0.SYSUPD.MCCBMST012]VAXCRTL.EXE;1
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.
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 T1.2.4 is now running.
%DCL-W-ACTIMAGE, error activating image DNS$SHARE
-CLI-E-IMGNAME, image file CMGOP1$DKB0:[SYS0.SYSCOMMON.][SYSLIB]DNS$SHARE.EXE;1
-SYSTEM-F-PROTINSTALL, protected images must be installed
*********************************************************
Fatal DECmcc BMS T1.2.4 event occurred during installation
*********************************************************
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
Installation of MCCBMST V1.2 completed at 16:21
VMSINSTAL procedure done at 16:22
$
$ lo
SYSTEM logged out at 18-DEC-1991 10:26:28.15
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1961.1 | See note 1912 | TOOK::MINTZ | Erik Mintz | Wed Dec 18 1991 13:37 | 2 |
| See note 1912 for a discussion of this same problem.
|
| 1961.2 | Have over come the DNS problem. BUT! | MEO78B::BARNHOORN | here on Cactus Island | Wed Dec 18 1991 17:34 | 15 |
|
Erik,
As I said earlier I was able to fix the DNS problem by installing the
DNS$SHARE.EXE file.
But I still have the
&MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
error.
regards
Mark
|
| 1961.3 | It looks like the management modules are not yet enrolled. | TOOK::KOHLS | Ruth Kohls | Thu Dec 19 1991 13:59 | 7 |
|
Look in sys$startup: for mcc_startup_bms.com and be sure that
it is the new version. Then, do
$ @sys$startup:mcc_startup_bms.com ENROLL
When this is done, try the IVP again and let us know what happens.
Ruth K.
|
| 1961.4 | used DNS instead | MEO78B::BARNHOORN | here on Cactus Island | Tue Dec 31 1991 00:02 | 13 |
|
Ruth,
I reinstalled the software, but this time with DNS installed amd using
it instead of local MIR.
The reason for the my initial troubles is that I printed and used the
release notes from the kit, which are T1.2.3 not the seperate release
notes.
thanks
Mark
|
| 1961.5 | Release notes are okay -- T1.2.3 is a typo.... | TOOK::CAREY | | Sat Jan 04 1992 14:39 | 26 |
|
That the release notes say T1.2.3 is probably my fault. Not bad
release notes, just a bad editor :-( (me).
I think that they're the right release notes though.
The DNS problem is probably the root of everything you saw go wrong.
I suspect that Ruth is exactly right that your management modules were
not installed correctly, probably because DECmcc couldn't startup
during the enrollment phase of the MCC startup procedure late in the
installation.
Re-installing with DNS installed solved your problem because it got the
modules installed. I believe that you won't have any trouble switching
instance repositories if you choose to.
I don't know of any significant problems related to the local
implementation of the instance repository on VMS aside from our linking
against the DNS$SHARE library.
If you have other problems, please let us know soonest.
Thanks,
-Jim
|