Yes, this appears to be true. This is what I was trying to say in my note below
when I wrote,

"While existing schedules did not show up as running on 02/29/2000, they do
show up as running on 02/29/2004. So it looks like this problem is specific to
the year 2000."

Try creating a schedule like this:

DEF SCH STANDARD LEAPYEAR STARTDATE=02/29/2000
DEF ASSOC STANDARD LEAPYEAR ANDY
Q EV STANDARD LEAPYEAR ENDD=03/07/2000

You should see events in the range 02/29/2000 through 03/07/2000. However, I
noted that there is no event of 03/01/2000. I have also mentioned this to the
server developers.

I've taken a brief look at our date/time handling routines, and I can assure
you that they are set up to handle 2000 as a leap year, and 02/29/2000 as a
leap day.

Since I do not work on the ADSM server, I can not be absolutely certain, but I
suspect that correcting this should not take very long (probably a minor logic
bug outside of the date/time routines). I have already notifed the server
developers about the issues raised in this thread.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 06/17/98 08:08:47 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Y2K...!


Andy,

We runs clients V3.1.0.3, server MVS 3.1.1.2

q event * * begind=02/29/1999 or 2001 gives Invalid date:     OK
q event * * begind=02/29/2004 gives the list of events as Future:     OK

But

q event * * begind=02/29/2000 accepts the date but brings: ANR2034E no match
found:  NOT OK! It should give the list of event like for 2004.

Regards,

René Lambelet - *3543 - *A581
Nestec SA - 55, Av. Nestlé - CH-1800 Vevey
Tel: ++41/21/924'35'43 / Fax: ++41/21/924'45'89
E-Mail: rene.lambelet AT nestle DOT com




> -----Original Message-----
> From: Andrew Raibeck [SMTP:storman AT US.IBM DOT COM]
> Sent: Wednesday, June 17, 1998 4:30 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Y2K...!
>
> The rules for a leap year are:
>
> 1) If the year is divisible by 4 then it is a leap year.
>
> 2) The exception to this is years that are divisible by 100, unless the
> year is
> also divisible by 400. For example, 1900 is not a leap year because it is
> divisible by 100. But 2000 is a leap year because it is divisible by 400.
>
> ADSM should treat the year 2000 as a leap year. I briefly checked our
> date/time
> routines and it does look like we attempt to handle leap years according
> to the
> rules I mentioned above. While existing schedules did not show up as
> running on
> 02/29/2000, they do show up as running on 02/29/2004. So it looks like
> this
> problem is specific to the year 2000. Also, I was able to create a
> schedule
> with a start date of 02/29/2000, and a QUERY EVENT showed that it would
> run on
> that date.
>
> The ADSM server developers may already be aware of this issue, but I will
> mention it to them anyway.
>
> Thank you,
>
> Andy
>
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 06/17/98 06:24:33 AM
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Re: Y2K...!
>
>
> Hi,
>
> %If make a query on 01/03/2000   like for example :
> %
> %q event * * begindate=02/29/2000
> "02/29/2000" doesn't exist!!!
>
> Try "01/03/2000" or "02/28/2000"
> %Herwig Evenepoel
> %CARC
> %KBC Bank Belgium
>
> Ciao
>         A. Kossack
>
>
>