HP3000-L Archives

March 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Zoltak <[log in to unmask]>
Reply To:
John Zoltak <[log in to unmask]>
Date:
Wed, 25 Mar 1998 09:34:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Another reason for the AAMMDD format is that HP and now exegesys in
their Materials Management 3000 (MM3000) product has chosen that format
for Y2K resolution. So some of us (like me) are stuck with it. Not that
I'm complaining. I can adapt.

John Zoltak
North American Mfg Co

> -----Original Message-----
> From: Therm-O-Link [SMTP:[log in to unmask]]
> Sent: Wednesday, March 25, 1998 7:47 AM
> To:   [log in to unmask]
> Subject:      [HP3000-L] maestro and year 2000
>
> On Tue, 24 Mar 1998 16:41:51 -0800,
> [log in to unmask]
> writes:
>
> >We are using Maestro to do our date calculations in JCLs.
> >As part of year 2000 project we would like to change the date format
> from
> YYMMDD
> >to AAMMDD where AA represents (A0 = 2000 , A1=2001 ,...).
>
> This thing just won't die, will it?  As pointed out by others who are
> far more respected (and respectable) than me, the idea of using AAMMDD
>
> as a solution to the Year 2000 problem is an excrutiatingly bad one.
> Actually, if the average business hasn't started Year 2000 remediation
>
> by now, it's already too late.
>
> So, why don't you tell us *your* reasons for using this arcane AAMMDD
> date format?
>
> Jim Phillips                            Manager of Information Systems
> E-Mail: [log in to unmask]      Therm-O-Link, Inc.
> Phone: (330) 527-2124                   P. O. Box 285
>   Fax: (330) 527-2123                   Garrettsville, Ohio  44231

ATOM RSS1 RSS2