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

Conference clarid::dasc

Title:DASC Tool, Problems & Suggestions
Notice: Latest kit: see note 85.0
Moderator:CLARID::KREYER
Created:Mon Mar 26 1990
Last Modified:Fri May 23 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:208
Total number of notes:848

208.0. "Run-time error" by NEWVAX::TROMBETTA () Fri May 23 1997 00:30

    I have installed DASC V4.1 on a VAX cluster with 3 VAX nodes and 1
    Alpha node.  Following is a sample run and the error I am getting.
    
    Can anyone tell me why this is happening?
    
    ZIGLAR_$ @dasc
            -- DASC V4.1-1 --               22-MAY-1997 14:15:27.44
    
    
                    CONFIDENTIAL SOFTWARE
            PROPERTY OF DIGITAL EQUIPMENT CORPORATION
      Use authorized only pursuant to a valid Right-To-Use License
      Copyright (c) 1991, 1992 by Digital Equipment Corporation
    
    
            Do you want to enter details to appear in the report headers?
            Enter your choice <NO> : 
    
            Enter a VAXmail address to receive the report(s)
            <CR> will mail to SYSTEM, NONE implies no mail
            Enter your choice <SYSTEM> : trombetta
    
            Select the type of configuration information to be collected
            H(ardware)  S(oftware)  L(icense)  N(etwork)
             ** Network data collection may consume significant amounts
             ** of CPU resources on the node doing the collection. This
             ** may impact system performance and user response time.
            Enter a single option (N) or a list of options (HSL)
            Enter your choice  <A>ll : A
    
            Select the type of optional report(s) to be produced
            C(LUE Config)  D(UP)  I(nventory summary)  P(ostscript for
    LIFE)
            L(IFE)  H(istory for LAN collections)
             ** If you request Postscript printer information, you
             ** will see no printer output generated in most cases.
             ** However any Postscript printer attached to a print
             ** queue having job flag and/or trailer page enabled
             ** will output a job flag and/or trailer page.
            Enter a single option (I) or a list of options (ILP)
            Enter your choice  <none> : 
    
            You may generate a LAN configuration file listing ETHERNET
    devices.
            Entering 0 at next prompt will disable this function.
            Enter the number of minutes (0 to 59) <30> : 
    
            -- Collect ETHERNET config. --  22-MAY-1997 14:15:43.99
    %DCL-S-SPAWNED, process DASC$LAN spawned
    
            Enter list of nodes you want to collect on
            (comma separated list of nodes being part of this cluster)
            Enter nodes <whole cluster> : 
    
            -- Collect system info --
    %SYSMAN-I-TIMEVAL, timeout value is     0 00:06:00.00
    %SYSMAN-I-ENV, current command environment:
            Clusterwide on local cluster
            Username TROMBETTA    will be used on nonlocal nodes
     
    %SYSMAN-I-OUTPUT, command execution on node ZIGLAR
    %DASC-I-Collect     :  14:16:13.61
    %DASC-I-License     :  14:16:15.32
    %DASC-I-LIFE_start  :  14:18:47.31
    %DASC-I-Clus_start  :  14:18:57.40
    %DASC-I-Soft_start  :  14:18:58.57
    %DASC-I-Hard_start  :  14:19:18.40
    %DASC-I-End         :  14:19:25.63
    %SYSMAN-I-OUTPUT, command execution on node EISVAX
    %DASC-I-Collect     :  14:19:15.49
    %DASC-I-License     :  14:19:16.62
    %DASC-I-LIFE_start  :  14:19:26.28
    %DASC-I-Clus_start  :  14:19:33.59
    %DASC-I-Soft_start  :  14:19:34.13
    %DASC-I-Hard_start  :  14:19:39.06
    %DASC-I-End         :  14:19:44.66
    %SYSMAN-I-OUTPUT, command execution on node TAMVM6
    %DASC-I-Collect     :  14:20:45.13
    %DASC-I-License     :  14:20:48.36
    %DASC-I-LIFE_start  :  14:21:21.72
    %DASC-I-Clus_start  :  14:21:24.68
    %DASC-I-Soft_start  :  14:21:25.53
    %DASC-I-Hard_start  :  14:21:45.40
    %DASC-I-End         :  14:22:09.85
    %SYSMAN-I-OUTPUT, command execution on node SLEWPY
    %DASC-I-Collect     :  14:22:10.11
    %DASC-I-License     :  14:22:15.76
    %DASC-I-LIFE_start  :  14:22:26.48
    %DASC-I-Clus_start  :  14:22:27.03
    %DASC-I-Soft_start  :  14:22:27.49
    %DASC-I-Hard_start  :  14:22:32.39
    %DASC-I-End         :  14:22:34.16
            -- Produce final report --
    %DASC-I-Report_start:  14:21:58.58
     
    %DASC-E-Msg     DASC$MAIN Condition Handler Message
    COMPILE_REPORTS: DUP devices                                               
    HSD000   - Shelf 3 fixed
     
    %PAS-F-SUBSTRSEL, SUBSTR selection error
    %TRACE-F-TRACEBACK, symbolic stack dump follows
    module name     routine name                     line       rel PC   
    abs PC
    
    DASC$MAIN       SAVE_STORAGEWORKS_DATA           3133      00000A1C 
    000144B0
    DASC$MAIN       HSXXX_DETAILS                    3213      0000018B 
    00015DAB
    DASC$MAIN       COMPILE_REPORTS                  3808      000017ED 
    000178E1
    DASC$MAIN       DASC$MAIN                        5249      000005EE 
    0001CFBE
    
    
T.RTitleUserPersonal
Name
DateLines
208.1Found my own answerNEWVAX::TROMBETTAFri May 23 1997 00:594
    I added the following line to the DASC$CREF.SITE file and re-ran DASC. 
    The error did not re-occur.
    
    NODUP: HSD000
208.2Known problem...CLARID::KREYERAndre KREYER, Sophia Antipolis (FR)Fri May 23 1997 14:0313
>    %DASC-E-Msg     DASC$MAIN Condition Handler Message
>    COMPILE_REPORTS: DUP devices                                               
>    HSD000   - Shelf 3 fixed
	This error footprint has already been mentioned a couple of times,
	most recently in note 204.0... Please refer to 204.1 for solution.
	
	As far as your proposed fix (note 208.1) is concerned, it did mask
	the problem by avoiding to collect/report data on HSD000. The new
	code that can be made available would require you to remove this
	modification in order to again collect/report from HSD000...

								.Andre.