[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

5962.0. "MCC-E-WRONG_CMA, How do I install ?" by JRDV04::T_ONO (Tomonari. ACMSxp Dev @ DECpark) Tue Apr 26 1994 08:13

    Hi, I'm member of ACMSxp/Japanese group.

    In VAX/VMS V6.1 (Japanese version), MCC V1.3 makes stack dump when
    installation with messages as follows:

%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)

%RMS-E-FNF, file not found

    Image ID of CMA$LIB_SHR.EXE in SYS$LIBRARY is "CMA V2.11-129", and is
    included in original VMS kit. No other product replaces CMA*.* at all.

    It seems that installation procedure have provided all files of MCC, but
    startup procedure MCC_STARTUP_DIR.COM makes errors above.

    Off course, I have already read topic 5349.*, but I need official answer
    for my BIG customer.

    How do I install and start up MCC V1.3 on VMS V6.1 ?

Thanks from Japan,

/Tomo

Installation Log following...


$ @SYS$UPDATE:VMSINSTAL MCCDIR013 SYS$COMMON:[SYSMGR]


	OpenVMS VAX Software Product Installation Procedure V6.1


It is 26-APR-1994 at 17:54.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-ACTIVE, The following processes are still active:
	OSITPCM_SERVER
* Do you want to continue anyway [NO]? YES
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  MCCDIR V1.3


	Beginning installation of MCCDIR V1.3 at 17:54

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
                                                               
   ************************************************************
   *                                                          *
   *                  DECmcc DIRECTOR V1.3.0                  *
   *                    Integrated Package                    *
   *                                                          *
   *                  Installation Procedure                  *
   *                                                          *
   ************************************************************
                                                               
                                                               
 

                            WARNING                            
                                                               
   DECmcc V1.3.0 requires at least Motif V1.1.3  
                                                               
   All windowing interfaces to DECmcc will not function        
   normally and will not be supported.                         
                                                               
* Do you want to continue [NO]: YES

                            WARNING                            
                                                               
   The kit to be installed contains V1.3.0 of the TCP/IP SNMP
   Access Module.  After you have installed this kit, you      
   should not reinstall V1.1 of the TCP/IP SNMP Access Module. 
   V1.1 is incompatible with this kit.                         
                                                               
* Please press return to continue: 
 

   DECmcc requires a directory where the DECmcc common files   
   will be installed.  If the logical MCC_COMMON has been      
   redefined, the new definition will be used as the default.  
   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]]: 
%VMSINSTAL-I-SYSDIR, This product creates system directory [MCC].
%VMSINSTAL-I-SYSDIR, This product creates system directory [MCC.MCC_SCRIPTS].
%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]
.
                                                               
 
* Do you want to run the DECmcc DIRECTOR IVP after the installation [YES]? 
                                                               
* Do you want to purge files replaced by this installation [YES]? 
%MCCDIR-I-USE_DECDTS_TDF, DECmcc will use the DECdts TDF (9:00)
 
* Please press return to continue: 
 

                                                               
   DECmcc requires the use of a namespace service for the      
   storage and retrieval of network entity information. You    
   can select a local namespace or a distributed namespace     
   (DNS). Select the local namespace, unless you have multiple 
   DECmcc systems that need to share namespace information, or 
   you are running DECnet/OSI and are using its distributed    
   namespace.  If either of these conditions apply, select the 
   DNS; otherwise, select the local namespace.  You may choose 
   only one namespace.                                         
                                                               
   If you select the DNS, please see the DNS chapter in the    
   DECmcc Planning and Installation for VMS manual on how to   
   configure your namespace.                                   
                                                               
   If you intend to use the DECmcc Autoconfiguration           
   applications with the local namespace, please see the       
   Autoconfiguration and Autotopology Use manual on how to     
   plan your entity name structure.                            
                                                               
* Use DECmcc Local MIR as the DECmcc Name Service [YES]? NO
                                                               
   Using the distributed namespace (DNS) for DECmcc.          
 
* Is this correct  [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").                                
                                                               
%MCCDIR-I-DECNET_IDP, The default is the DECnet/OSI IDP.
                                                               
* Initial Domain Part  [49::]: 
                                                               


        Product:      DECMCC-DIRECTOR
        Producer:     DEC
        Version:      1.3
        Release Date: 9-JUN-1992


* Does this product have an authorization key registered and loaded? YES
                                                               
   VMSINSTAL asks no additional questions.                     
                                                               
                                                               
                                                               
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
   Linking mcc_mts_priv_shr...
                                                               
   Following the copying of the files, the DECmcc DIRECTOR     
   start-up command procedure(s) will be invoked.  Operational 
   tables will be created by this procedure.                   
                                                               
   To automatically set up DECmcc DIRECTOR on your system,     
   edit your local system start-up command procedure           
                                                               
             SYS$MANAGER:SYSTARTUP_V5.COM                      
                                                               
   so that it invokes the DECmcc DIRECTOR start-up command     
   procedure.  Add:                                            
                                                               
             @SYS$STARTUP:MCC_STARTUP_DIR.COM                  
                                                               
   after the statement that invokes the DECnet start-up        
   command file (STARTNET.COM).                                
                                                               
   Following the DECmcc DIRECTOR start-up the DECmcc DIRECTOR  
   IVP command procedure will be invoked.                      
                                                               
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
                                                               
   Beginning DECmcc DIRECTOR Postinstallation Procedure ...    
                                                               
   Deleting obsolete DECmcc verbs...                           
                                                               
 
 
The MCC_STARTUP_DIR startup procedure for DECmcc V1.3.0 is now running.
 
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)

%RMS-E-FNF, file not found
 
 
The MCC_STARTUP_DIR startup procedure for DECmcc V1.3.0 is now ending.
 
                                                               
   Completing DECmcc DIRECTOR Postinstallation Procedure ...   
                                                               
                                                               
   Beginning DECmcc DIR Installation Verification Procedure .. 
                                                               
 
 
   The IVP for DECmcc DIRECTOR will now be run. 
 
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)


MCC 0 
AT 26-APR-1994 18:08:01 

Test Successful
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)


MCC 0 FCL 
AT 26-APR-1994 18:08:06 

Test Successful
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)


MCC 0 DNA4_AM 
AT 26-APR-1994 18:08:12 

Test Successful
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)


MCC 0 DNA5_AM 
AT 26-APR-1994 18:08:17 

Test Successful.
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0013472B  0013472B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.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, TO FILE = MCCDIR$OUT.TXT"
 
   DECmcc DIRECTOR V1.3.0 Installation Failed
 
 
%MCC-F-FAILED, fatal DECmcc error 
                                                               
   *********************************************************   
                                                               
   Fatal DECmcc DIRECTOR V1.3.0 event occurred during installation
                                                               
   *********************************************************   
                                                               
%VMSINSTAL-E-IVPFAIL, The IVP for MCCDIR V1.3 has failed.


	VMSINSTAL procedure done at 18:08


$
$
T.RTitleUserPersonal
Name
DateLines
5962.1Kernel ECO neededBIKINI::KRAUSECSC Network Management/HubsWed Apr 27 1994 09:3511
You'll need an MCC kernel ECO (MCCKRNECO01013) to solve this problem. If 
you can't get it through TIMA, you could copy it from

	BIKINI::MCC_DISK:[BMS013.VMS.PATCH]MCCKRNECO01013.*

Please follow the *important* information in the .README file!

*Robert

P.S.: I haven't tested this ECO on VMS V6.1 yet - did anyone try it and
      care to comment? 
5962.2Inst is good, but IVP fail...JRDV04::T_ONOTomonari. ACMSxp Dev @ DECparkThu May 05 1994 03:3963
    Thank you for your reply, Robert.

    As you said in .-1, this problem is solved by installing ECO #03.
    And,

>P.S.: I haven't tested this ECO on VMS V6.1 yet - did anyone try it and
>      care to comment? 

    On VMS V6.1, installation of ECO #03 is successfully completed. But
    some errors appear when executing IVP. Log of IVP is under below,
    and if you have any idea to avoid these errors, please teach me.

Thanks,
/Tomo

$ @SYS$TEST:MCC_DIR_IVP


   The IVP for DECmcc DIRECTOR will now be run.

DECmcc (V1.3.0a)


MCC 0
AT  5-MAY-1994 15:33:26

Test Successful
DECmcc (V1.3.0a)


MCC 0 FCL
AT  5-MAY-1994 15:33:31

Test Successful
DECmcc (V1.3.0a)


MCC 0 DNA4_AM
AT  5-MAY-1994 15:33:36

Test Successful
DECmcc (V1.3.0a)


MCC 0 DNA5_AM
AT  5-MAY-1994 15:33:41

Test Successful.
DECmcc (V1.3.0a)

%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, TO FILE = MCCDIR$OUT.TXT"

   DECmcc DIRECTOR V1.3.0 Installation Failed


%MCC-F-FAILED, fatal DECmcc error

5962.3BIKINI::KRAUSECSC Network Management/HubsThu May 05 1994 08:4217
>MCC 0 DNA5_AM
>AT  5-MAY-1994 15:33:41
>
>Test Successful.
>DECmcc (V1.3.0a)
>
>%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, TO FILE = MCCDIR$OUT.TXT"

This test should be 'ICONICMAP'. Do you have a symbol or logical
'ICONICMAP' defined?

*Robert
5962.4still "Current version of CMA is incompatible with DECmcc"BIS54::PUTMANSHakuna MatataWed May 10 1995 14:43188
Hi,

i installed this patch but i still get the error
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc

-----------------   log file of installation   --------------

PPCMGR> set def sys$update:
PPCMGR> @vmsinstal


        OpenVMS VAX Software Product Installation Procedure V6.1


It is 10-MAY-1995 at 11:48.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-ACTIVE, The following processes are still active:
        ACMS397SP004003
        SQLSRV$SERVER
	.
	.
        SS_GENERIC_0136
        ACMS39BSP014012
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?
* Where will the distribution volumes be mounted: DISK$PPC2:[PUTMANS]

Enter the products to be processed from the first distribution volume set.
* Products: MCCKRNECO01013
* Enter installation options you wish to use (none):

The following products will be processed:

  MCCKRNECO01 V1.3


        Beginning installation of MCCKRNECO01 V1.3 at 11:49

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

****************************************************************************
**
MCCKRNECO01013 For MCC_KERNEL_SHR.EXE and MCC_MTS_PRIV_SHR.EXE

This ECO will replace the image MCC_KERNEL_SHR.EXE and MCC_MTS_PRIV_SHR.EXE
under SYS$COMMON:[SYSLIB].
Users are strongly urged to make a backup copy of their system disk.
This procedure requires 2 to 5 minutes to execute, depending on your
system configuration.

****************************************************************************
**

* Do you wish to continue [N]? y
%MCCKRNECO01-I-IMAGE_FOUND, Image file found is MCC_KERNEL_SHR.EXE
%MCCKRNECO01-I-IMAGE_MOVE,  Now moving image MCC_KERNEL_SHR.EXE to
SYS$COMMON:[S
YSLIB]
%MCCKRNECO01-I-IMAGE_FOUND, Image file found is MCC_MTS_PRIV_SHR.EXE
%MCCKRNECO01-I-IMAGE_MOVE,  Now moving image MCC_MTS_PRIV_SHR.EXE to
SYS$COMMON:
[SYSLIB]
Now Rerun sys$common:[sys$startup]mcc_startup_bms.com


The MCC_STARTUP_BMS startup procedure for DECmcc V1.3.0 is now running.

%PURGE-W-SEARCHFAIL, error searching for
DSA0:[SYS0.SYSUPD.MCCKRNECO01013]MCC_DN
A4_EVL.LOG;*
-RMS-E-FNF, file not found
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000D9B2B  000D9B2B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)


Node4 PPCMGR Local Sink Monitor
AT 10-MAY-1995 11:50:22

Node is not registered.

Node4 PPCMGR Local Sink Monitor
AT 10-MAY-1995 11:50:22

Node is not registered.

Node4 PPCMGR Local Sink Monitor
AT 10-MAY-1995 11:50:22

Node is not registered.

Node4 PPCMGR Local Sink Monitor
AT 10-MAY-1995 11:50:22 Characteristics

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 PPCMGR Outbound Stream PPCMGR Remote Sink Monitor
AT 10-MAY-1995 11:50:23

Node is not registered.

Node4 0 Local Sink Monitor
AT 10-MAY-1995 11:50:23

Connection to PhaseV system rejected. Use NODE directive.
%PURGE-W-SEARCHFAIL, error searching for
DSA0:[SYS0.SYSUPD.MCCKRNECO01013]MCC_EV
C_SINK.LOG;*
-RMS-E-FNF, file not found
%MCC-E-WRONG_CMA, Current version of CMA is incompatible with DECmcc
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000D9B2B  000D9B2B
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             152      00000011  0000598D
                                                           0000594A  0000594A
DECmcc (V1.3.0)


MCC 0 COLLECTION_AM SINK DECnet
AT 10-MAY-1995 11:50:36

Disable completed successfully.

MCC 0 COLLECTION_AM SINK DECnet
AT 10-MAY-1995 11:51:30

Collector AM internal error


The MCC_STARTUP_BMS startup procedure for DECmcc V1.3.0 is now ending.

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
directories...

        Installation of MCCKRNECO01 V1.3 completed at 11:51

Enter the products to be processed from the next distribution volume set.
* Products:

        VMSINSTAL procedure done at 11:51


PPCMGR>
5962.5On VMS 6.1 the good choice is DECmcc V1.4AZUR::DURIFThu May 11 1995 17:597
Hi,

On VMS 6.1 the best is to install DECmcc V1.4.

It was fully tested and is supported.

Benoit