ADSM-L

Re: Strange Date in ADSM

2000-04-21 16:26:55
Subject: Re: Strange Date in ADSM
From: VoAn Nguyen <vanguyen AT CA.IBM DOT COM>
Date: Fri, 21 Apr 2000 16:26:55 -0400
Hi Bill,

This is APAR  IY07233:
WEB ADMIN SUGGESTS INCORRECT BEGINDATE WHEN SELECTING
'OBJECT VIEW' / 'SERVER' / 'ACTLOG'

It was introduced in the 3.1.2.50 level and fixed in 3.1.2.55 available
on the ftp site:
ftp://service.boulder.ibm.com/storage/adsm/fixtest/v3r1/aixsrv/3.1.2.55/

Regards,

Vo An Nguyen
Email: vanguyen AT ca.ibm DOT com



"Slaughter, Bill" <BillSlaughter AT TUPPERWARE DOT COM> on 04/21/2000 15:28:27

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Strange Date in ADSM




I am attempting to do a select statement to identify filespaces that hove
not been backed up.

I am getting strange results so I isolated the problem to the field
current_timestamp.

When I run the following:

select current_timestamp as Stamp , date(current_timestamp) as Date from
libraries     <<<<<===== Can be any table but smaller the better I only
have
2 libraries.

I am running it today 4-21-2000 and it returns 5-21-2000 even though the
server date is accurate along with actlog.

Does anybody know of a patch to cause/correct? I did apply iy05372 a couple
of days ago.

Bill Slaughter
Tupperware U.S., Inc.
14901 S. Orange Blossom Trail
Orlando, FL 32837
(407) 826-4580
(407) 826-8890 Fax
Text Pages 4079747099.5701585 AT pagenet DOT net
<Prev in Thread] Current Thread [Next in Thread>