Re: y2k problem - APAR IY07219 nvColToSQL

Yes, an APAR was opened on this yesterday. I recall some discussions last
year that indicated that development thought the two digit year would not
be
a problem since it was unambiguous. However, if the rdbms treats a 00 in a
date datatype as 1900, then it is a real problem. Ask support for the
status of
APAR  IY07219.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager


---------------------- Forwarded by Leslie Clark/Southfield/IBM on
01/06/2000 03:51 PM ---------------------------

scardona AT visiontech.com DOT [email protected]> on 01/06/2000 11:03:56 AM

Please respond to scardona AT visiontech.com DOT co

Sent by:  Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>


To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:
Subject:  y2k problem



Hi All:
I Have FrameWork 3.6.1 patched up to 0056, NetView
5.1.2 AIX 4.3.2, Oracle 7.3.4.

I am using the RIM to move the trapd.log and the
snmpCollect data to an Oracle database, the date in the
trap_create_time in the trapdlog table is right but the
date in the collectime in the coldata table is wrong it
has 1900 date !!!! it look like :
COLLECTTIME
----------------
05/01/1900 16:56
05/01/1900 16:56
05/01/1900 16:58
05/01/1900 16:59

moreover if I graph the snmpCollect data via NetView it
looks good.

 I wonder if Anybody has had this problem ?

Anybody has any idea ?


Thanks in advance,

Sergio Cardona.


-----------------------------------------------------
This mail sent through IMP: http://web.horde.org/imp/