Ditto...I was out with the flu last Thursday & Friday. My full backups worked fine, but
the partials we run on the weekend bombed due to this problem. Stan's information
helped me fix it ASAP!!  Many thanks.

Cynthia Bridges-Fowler
MIS Operation Analyst
IMC Global, Inc. / IMC Salt, Inc.
[log in to unmask]

>>> "Pattison, Eva M." <[log in to unmask]> 01/10/00 10:21AM >>>
Thanks for sharing that information.  My partial backups were not working
either.  They will now thanks to the info you shared.

Eva

        -----Original Message-----
        From:   Stan Sieler [SMTP:[log in to unmask]] 
        Sent:   Thursday, January 06, 2000 2:29 PM
        To:     [log in to unmask] 
        Subject:        Y2K and STORE problem

        Hi,

        I just helped diagnose a problem where a site's
        partial backups weren't running since the start of the year.

        Turns out they were essentially doing:

           STORE / ; ; date>=1/2/0

        where the date was composed from: !HPMONTH/!HPDATE/!HPYEAR

        Unfortunately, STORE requires at least *TWO* digits for the year.

        Yes, you can argue that the STORE syntax says:

           DATE>=mm/dd/[yy]yy

        but...it allows m instead of mm, and d instead of dd ... so ...
        I classify it as a STORE bug.

        Here's what you get:

           :STORE / ; ; DATE >= 1/2/0

           YEAR PORTION OF DATE IS INVALID.  IT MUST BE GREATER
           THAN 1970 (70) AND LESS THAN 2027 (27).
           DATE SYNTAX 'mm/dd/yy[yy]'  (S/R 597)

        If you change it to:

           :STORE / ; ; DATE >= 1/2/00

        it works.

        So...check your backup scripts/jobs...I saw several postings on
HP3000-L
        over the last few years where the date is composed using HPYEAR!

        (Remember, HPYEAR is an integer variable...so it can't "return 00".)

        SS

        Stan Sieler
[log in to unmask] 
        www.allegro.com/sieler/wanted/index.html 
www.allegro.com/sieler