[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

2904.0. "Using NOW as a time specification" by NSCRUE::KEANE (U.S. NIS Service Engineering and Delivery) Thu Apr 30 1992 21:29

    
    VMS V5.5
    BMS T1.2.7
    ELM T1.2.7
    TS  T1.0.7
    TCPIP DA T1.2.0
    
    I am trying to use the "at" qualifier with a start modifier in an alarm 
    rule. I am trying to use the keyword NOW as the start time. I get the 
    following error:
    
    Illegal scheduling time specification.
    
    This worked and was used in V1.1 to cause the rule to fire once and
    then disable. I've gotten around it in 1.2 by using "at start = +0".
    
    The director use manual shows "now" as a valid qualifier and I didn't
    see anything in the 1.2.4 or 1.2.7 release notes about a problem with
    it.
    
    Two questions:
    
    1) Is there a better way to get a rule to fire only once?
    
    2) Is NOW still supposed to be a valid time specification?
    
    Thanks,
    Scott

T.R	Title	User	Personal Name	Date	Lines
2904.1	QAR'd as 2900 in MCC_INTERNAL	DADA::DITMARS	Pete	`Wed May 06 1992 19:25`	0