[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

2091.0. "DECmcc 1.2.4 install failure" by F18::ROBERT () Mon Jan 13 1992 18:09

    I have just now gotten around to installing DECmcc 1.2.4 - This is the
    .log file, it is the same error that I had when I tried to install
    1.2.3 -
    
    Can someone help me solve my problem?
    
    $ @sys$update:vmsinstal
    
    
            VAX/VMS Software Product Installation Procedure V5.4
    
    
    It is 13-JAN-1992 at 14:31.
    
    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]? yes
    * Are you satisfied with the backup of your system disk [YES]?
    * Where will the distribution volumes be mounted:
    NETMON$DKB100:[000000.DECMCC]
    
    Enter the products to be processed from the first distribution volume
    set.
    * Products: mccbmst012
    * Enter installation options you wish to use (none):
    
    The following products will be processed:
    
      MCCBMST V1.2
    
            Beginning installation of MCCBMST V1.2 at 14:32
    
    %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]]:
    
    
    * 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. 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.
    
       Using the DECdns TDF as the default TDF
    
    * Time Differential Factor  [-6: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]?
    
       Using DECdns as the DECmcc Name Service
    
    * 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").
    
    * 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]? yes
    
    * Target directory for DECmcc Reports files
    [SYS$COMMON:[MCC.MCC_REPORTS_FILES]]
    :
    %VMSINSTAL-I-SYSDIR, This product creates system disk directory 
    SYS$COMMON:[MCC
    .MCC_REPORTS_FILES].
    
    
            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-ECOSET, eco level 3 already set in
    VMI$ROOT:[SYSLIB]VAXCRTL.EXE;2
    %VMSINSTAL-W-NOFILE, New file VAXCRTL.EXE  does not exist.
    
       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 T1.2.4 is now running.
    
    DECmcc (T1.2.4)
    
    
    MCC 0 ALARMS RULE __dummy_test
    AT 13-JAN-1992 14:50:13
    
    Entity created successfully.
    
    MCC 0 ALARMS RULE __dummy_test
    AT 13-JAN-1992 14:50:15
    
    Entity deleted successfully.
    
    The MCC_STARTUP_BMS startup procedure for DECmcc T1.2.4 is now ending.
    
    
       Completing DECmcc BMS Postinstallation Procedure ...
    
    
       Beginning DECmcc BMS Installation Verification Procedure ...
    
    
    
       The IVP for DECmcc BMS will now be run.
    
    DECmcc (T1.2.4)
    
    
    MCC 0
    AT 13-JAN-1992 14:50:27
    
    Test Successful
    DECmcc (T1.2.4)
    
    
    MCC 0 FCL
    AT 13-JAN-1992 14:50:35
    
    Test Successful
    DECmcc (T1.2.4)
    
    
    MCC 0 REGISTRATION_FM
    AT 13-JAN-1992 14:50:44
    
    Test Successful
    DECmcc (T1.2.4)
    
    
    MCC 0 DNA4_AM
    AT 13-JAN-1992 14:50:52
    
    Test Successful
    DECmcc (T1.2.4)
    
    
    MCC 0 DNA5_AM
    AT 13-JAN-1992 14:51:01
    
    Test Successful.
    DECmcc (T1.2.4)
    
    
    MCC 0 ICONICMAP
    AT 13-JAN-1992 14:51:09
    
    Test Successful
    DECmcc (T1.2.4)
    
    %MCC-E-INV_IN_ENTITY, software error: invalid in_entity (input entity)
    parameter
    %MCC-E-INV_IN_ENTITY, software error: invalid in_entity (input entity)
    parameter
    
       The following command failed.
    
          "MANAGE/ENTERPRISE TEST MCC 0 DOMAIN_FM, TO FILE =
    MCCBMS$OUT.TXT"
    
       DECmcc BMS T1.2.4 Installation Failed
    
    
    %MCC-F-FAILED, fatal DECmcc error
    
       *********************************************************
    
       Fatal DECmcc BMS T1.2.4 event occurred during installation
    
       *********************************************************
    
    %VMSINSTAL-E-IVPFAIL, The IVP for MCCBMST V1.2 has failed.
    
    Enter the products to be processed from the next distribution volume
    set.
    * Products: exit
    
            VMSINSTAL procedure done at 14:52
    
    
    $ logo
      SYSTEM       logged out at 13-JAN-1992 14:52:10.84
    %REM-S-END, control returned to node _NETMON::
    
    
    Thanks Dave
    
T.RTitleUserPersonal
Name
DateLines
2091.1BSYBEE::EGOLFJohn C. Egolf LKG2-2/T02 x226-7874Mon Jan 13 1992 18:376
	Could you  copy  and  run the audit command file to ensure that
	your sysgen and process quotas  are set up right?

	BSYBEE:;DUA0:[PUBLIC]MCC_AUDIT.COM

2091.2F18::ROBERTMon Jan 13 1992 19:1270
    This is the output from the audit_mcc.com file that is dated 8 oct 1991
    and is 52 blocks.
    
    $ @AUDIT_MCC.COM
    AUDIT_MCC V1.2  13-JAN-1992 16:05:00.85,
              on node NETMON::, a VAXstation 3100/GPX, running VMS V5.4
     Checking Process Quotas
     - No process quotas found to be too small for user SYSTEM
     Checking Sysgen Parameters.
     - No Active Sysgen parameters found to be too small.
     Checking installed images
     Checking Disk Space
      MCC_COMMON:
      SYS$LOGIN:
      SYS$SYSDEVICE:
     Checking Memory
    %DCL-W-USGOTO, target of GOTO not found - check spelling and presence
    of label
    
    
    $ ty AUDIT_00000099.TEMP_MEM_LIST;1
                  System Memory Resources on 13-JAN-1992 16:05:06.27
    
    Physical Memory Usage (pages):     Total        Free      In Use   
    Modified
      Main Memory (32.00Mb)            65536       42584       21679       
    1273
    
    Slot Usage (slots):                Total        Free    Resident    
    Swapped
      Process Entry Slots                 90          67          23          
    0
      Balance Set Slots                   81          60          21          
    0
    
    Fixed-Size Pool Areas (packets):   Total        Free      In Use       
    Size
      Small Packet (SRP) List           4100        3659         441        
    112
      I/O Request Packet (IRP) List      750         568         182        
    176
      Large Packet (LRP) List             44          34          10       
    1648
    
    Dynamic Memory Usage (bytes):      Total        Free      In Use    
    Largest
      Nonpaged Dynamic Memory         900096      457808      442288     
    422624
      Paged Dynamic Memory           1000448      580256      420192     
    576592
    
    Paging File Usage (pages):                      Free  Reservable      
    Total
      DISK$PAGESWAP:[SYSEXE]SWAPFILE.SYS;1         13496       13496      
    13496
      DISK$PAGESWAP:[SYSEXE]PAGEFILE.SYS;1        156183      117091     
    159992
    
    Of the physical pages in use, 7971 pages are permanently allocated to
    VMS.
    
    
    Everything else is the same as I had it on DECmcc 1.1 -
    all my programs are running except decmcc. i.e. dns, and so forth.
    
    Could this be a problem that is caused by my export .rdb file that was
    created with the old DECmcc. My DTR info is the same also.
    
    Thanks Dave
    
2091.3Any old files laying around: TEMTY::L_GROSSMANWed Jan 15 1992 11:289
Could you make sure (as stated in some other replies):

1) There are no mcc files in sys$specific:[syslib], sys$specific:[sysexe]

2) There are no process logicals mcc_*

3) Make sure there are no mcc_fdictionary.* files in mcc_specific

2091.4F18::ROBERTWed Jan 15 1992 11:4550
    I looked in the places you suggested and this is what I found, are you
    saying that these should not be there???
    
    $ dir
    
    Directory SYS$SPECIFIC:[SYSLIB]
    
    DNS$LIB.EXE;1            79  24-JUN-1988 16:20:33.91 
    (RWED,RWED,RWED,RE)
    DNS$NS_DEF_FILE.DAT;1
                              1   6-MAY-1991 15:23:48.21 
    (RWED,RWED,RWED,R)
    MCC_DOMAIN_FM.EXE;1
                            134   4-NOV-1991 15:28:21.70  (RWED,RWED,RE,)
    MCC_DOMAIN_FM.JNL;1
                              7   4-NOV-1991 15:28:20.66  (RWED,RWED,RE,)
    MCC_PA_FM.EXE;1         233  16-OCT-1991 09:55:32.35  (RWED,RWED,RE,)
    
    Total of 5 files, 454 blocks.
    
    
    $ dir
    
    Directory SYS$SPECIFIC:[SYSEXE]
    
    DNS$BACK.EXE;1          131   9-JUN-1988 16:22:04.32 
    (RWED,RWED,RWED,RE)
    DNS$CONTROL.BIN;1        24  12-OCT-1988 09:35:12.90 
    (RWED,RWED,RWED,RE)
    DNS$CONTROL.EXE;1        94  10-JUN-1988 14:31:25.96 
    (RWED,RWED,RWED,RE)
    DNS$DEFAULT_FILE.DAT;1
                              1   6-MAY-1991 15:23:50.08 
    (RWED,RWED,RWED,RE)
    DNS$DISPLAY_TREE.EXE;1
                            146  13-NOV-1987 17:05:17.46 
    (RWED,RWED,RWED,RE)
    DNS$GLOBAL.GBL;1         18   6-MAY-1991 15:23:41.94  (RWED,R,R,R)
    DNS$GLOBAL_CACHE.GBL;1
                            400   6-MAY-1991 15:23:42.39  (RWED,RWED,,)
    DNS$ML.EXE;1             74   9-JUN-1988 15:45:28.97 
    (RWED,RWED,RWED,RE)
    DNS$TRANS.EXE;1          96  21-SEP-1988 08:44:57.14 
    (RWED,RWED,RWED,RE)
    
    
    I guess I am missing something, doesn't the install procedure put these
    files in these places?
    
    Thanks Dave
2091.5F18::ROBERTWed Jan 15 1992 12:068
    I also looked in mcc_specific:*.*
    
    Directory SYS$SPECIFIC:[MCC}
    
    MCC_DNC-SETUP.DEF;3     1   10-SEP-1991  16:12:29.39  (RWED,RWED,re,)
    
    Dave
    
2091.6F18::ROBERTWed Jan 15 1992 14:105
    I got rid of the mcc* files in the sys$specific: area and the DECmcc 
    install completed.
    
    Thanks Dave
    
2091.7F18::ROBERTWed Jan 15 1992 14:5711
    I try to use my old map and get the following error,
    
    map file and domain mismatch
    
    entities found in domain but not in map file
    
    do I have to run the autoconfiguration??? So that I do not have to
    rebuild my database???
    
    Thanks      Dave
    
2091.8Convert SNMP entities?TOOK::R_SPENCENets don't fail me now...Wed Jan 15 1992 19:155
    Did you have SNMP entities in the domain?
    
    If so, did you convert them as per the release notes?
    
    s/rob
2091.9F18::ROBERTWed Jan 15 1992 22:177