[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

1320.0. "DON'T CHANGE THE DATE FORMAT. DECMCC FAIL!" by MLNEDU::GIAMMARINI (Remember...you must die!!) Wed Aug 07 1991 09:12

    I tried to activate the historian, the exporter and performance
    analyzer over my VAXstation 3100 with DECmcc BMS V1.1, but I didn't
    manage to do it. I tried to create and activate alarm rules, but I
    didn't manage to do it.
    In the first case, every time I started the exporter, the historian or
    the performance analyzer, the message I gained was:
    
    %MCC-E-INVALIDTIME, Invalid time specification
    
    In the second case the command procedures for alarms notification
    looped infinitely and no alarm were shown on the diplay.
    At last I found the problem that caused all these things:
    
    DON'T CHANGE THE DATE FORMAT ON YOUR SYSTEM!!!
    DON'T USE THE LIB$DT_STARTUP AND ALL THE LOGICAL NAMES CONNECTED TO
    CHANGE DATE FORMAT.
    
    Of course I used the italian format and DECmcc failed. It wants the
    american date format, nothing else...I don't know why, but that's.
    
    Bye, Domenico
T.RTitleUserPersonal
Name
DateLines
1320.1Yup, it's an ALARMS bug...TOOK::ORENSTEINWed Aug 07 1991 13:0613
    
    Domenico,
    
    Yes, ALARMS assumes a certain time format on the VMS V1.1 product.
    The truth is that I didn't know of any time format other than the
    VMS "American" time.
    
    I will file a QAR against ALARMS.
    
    Thanks for letting me know about this.
    
    	AUD...
    
1320.2Not just an alarms problemTOOK::GUERTINI do this for a living -- reallyThu Aug 08 1991 12:5915
    Well, actually _all_ of MCC wants "American" time.  It's extremely
    unfortunate.  The lower level time routines do the "right thing" and
    call the right LIB$ date/time routines to support user-defined
    (international) time formats.  But since the SRM documents that only
    the English format is allowed (and only the VMS style), the PMs and
    most FMs must validate it.  So I wrote a higher layer routines which
    "expands" and validates the English format.  This resulted in MCC only
    supporting the English format.  But things are getting more confusing
    because, even the English format is not right.  The ISO format is more
    confusing (in my humble opinion), and is the "correct" long term
    international standard.  Sorry for the problems this has caused (and
    will be causing).  I believe this restriction is documented in the
    release notes.
    
    -Matt.