Yes, the clients, being part of ADSM, are also Y2K ready.

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 08/29/98 04:26:30 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Year 2000


Does anyone know if the Y2K compliancy also applies to the ADSM clients?  I'm
assuming since IBM is claiming ADSM is Y2K compliant that it applies to client
code as well as server.  I have a customer needing to validate all of the
software on his pc's for audit purposes.  Thanks


ADSM-L AT VM.MARIST DOT EDU on 08/27/98 04:14:57 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Year 2000


Hi Carol,

According the to the README files, the Feb 29th, 2000 issue has been
fixed in PTF5 (3.1.0.5) of the server. We haven't had a chance to re-run
our Y2K ADSM tests yet with this version, but we will be doing so in the
next couple of weeks.


Trevor

        -----Original Message-----
        From:   Nunamaker, Carol A. [SMTP:Carol_Nunamaker AT HMIS DOT ORG]
        Sent:   Thursday, 27 August 1998 11:47 pm
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        FW: Year 2000


        We are running v3 of ADSM on MVS, RISC and NT.* I was wondering
has anyone done any testing on
        Year 2000 and leap year?* If so what were there results?** I
remember reading a few months back that
        there was a problem with the way ADSM handles the leap year in
2000.* If this is the case, does IBM
        have a date when a fix will be available?

        Thanks

        Carol
        HMIS