| 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 | 
    At the TRM PM I am using a time specification, which is defined as
    BINRELTIM in the MSL.  I give the following command:
    
    SET TIMER xxx EXPIRATION 0-0:0:1	or
    SET TIMER xxx EXPIRATION "0-0:0:1.0"
    
    The TRM module gives me always
    %LIB-F-ABMDATTIM, ambiguous date-time.
    
    I tought this is the correct representation.
    Is this a BUG or my misconception ?
    
    Note:
    In the SRM, the description of MCC$TIME_MULT has a wrong format
    
    MCC$TIME_MULT	result,time1,time2	should be replaced by
    MCC$TIME_MULT	result,time,scalar
                                                            
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 22.1 | INFO -- bug | TOOK::CHANLIZARDO | Tue Oct 17 1989 11:06 | 10 | |
|     The TRM PM calls the MCC$TIME routines to convert time from a string
    to its internal representation.  There is currently a bug for delta
    times, such that when the Day portion is specified, it does not work.
    In your example, if you just want a delta time of 1 second, specifying
    00:00:01 will work.
    
    This bug will be QARed.
    
    Christine
    
 | |||||
| 22.2 | PROBLEM - Still AMBDATTIM or INV_DESCR. | KETJE::MCC | Tue Oct 17 1989 11:25 | 4 | |
|     If I use a relative time 00:00:01, or 00:00:01.00 I get
    %MCC-E-INV_DESCR, invalid string descriptor encountered.
    
    Diminique.
 | |||||
| 22.3 | INFO -- available in x0.08.1 | TOOK::CHANLIZARDO | Tue Oct 17 1989 18:04 | 9 | |
|     Sorry about that.  I'm always running the most recent TRM since I
    work on TRM, so I forget about bug fixes that aren't available until
    the next build.  The "invalid string descriptor" message was due
    to a bug in the Console datatype conversion routines.  I had found
    the problem sometime after the x0.08.0 build and fixed it.  It will
    be available in x0.08.1.
    
    Christine
    
 | |||||