Jie--I'm not an AIX person but on VM (I am a VM person) the format of the
date can be controlled at the system level as well at the level of the
individual userid so what you are seeing may just be a difference in a
setting at the operating system level.  Check with your AIX support people
especially since the machine with the y2k patches is the one with the 2
digit year.

Also a 2 digit year is no guarantee that the date will be handled
incorrectly.  A lot of software uses a windowing technique that will
recognize a year from 00 to 70 or so as 20yy and years from 71 to 99 as
19yy.

Jim Bohnsack
Raytheon Systems Co.

> ----------
> From:         Wu, Jie[SMTP:JWu AT NCTR.FDA DOT GOV]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Thursday, September 16, 1999 12:12 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      dsmsched.log and AIX&client version
>
> ---------------------- Information from the mail header
> -----------------------
> Sender:       "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> Poster:       "Wu, Jie" <JWu AT NCTR.FDA DOT GOV>
> Subject:      dsmsched.log and AIX&client version
> --------------------------------------------------------------------------
> -----
>
> hi all,
>         on one of my machines running AIX4.1.4, adsm client 3.1.0.7, the
> date field of an entry in dsmsched.log file is in the format of
> mm/dd/yyyy,
> such as 09/14/1999.
>         while on another machine running AIX4.3.1, adsm client 3.1.0.7, it
> is mm/dd/yy, such as 09/14/99.
>         certainly the later will have Y2K problem. I am confused because
> both clients are at the same level. In addition, the later is Y2k
> compliant
> while the former doesnot have all the Y2K patches.
>         please check your machines. Advise me if you know what is going
> on.
>
> Jie
> _____________________________
> System and Storage Administrator
> ROW Sciences Inc @NCTR FDA
> phone: 870-543-7163
> fax: 870-543-7382
>