nv-l

Re: nvcorrd.alog not y2k ready

2000-01-11 07:26:12
Subject: Re: nvcorrd.alog not y2k ready
From: James Shanks <James_Shanks AT TIVOLI DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Tue, 11 Jan 2000 07:26:12 -0500

Steve  is correct.  I don't recall when this was fixed but it reads "2000" in
5.1.2.  You create your own problems by not being current on maintenance.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Steve Thornhill <steve_thornhill AT UK.IBM DOT COM> on 01/11/2000 04:21:26 AM

Please respond to 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:    (bcc: James Shanks/Tivoli Systems)
Subject:  Re: nvcorrd.alog not y2k ready






Which version of Netview are you using?

Steve Thornhill - IBM ETC
Int       - 255104
Ext      - 01705 565104
Mob   - 0378 289770
Email - steve_thornhill AT uk.ibm DOT com


Juan Echevarria <echevarria AT ES.IBM DOT COM> on 11/01/2000 09:18:46

Please respond to 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:    (bcc: Steve Thornhill/UK/IBM)
Subject:  nvcorrd.alog not y2k ready







Hi all,

     I know that it's not impacting on Netview functioning but a curiosity:
nvcorrd.alog isn't y2k ready and this year's entries appear as if it was year
2100.

A nvcorrd.alog example:

100/05/01 09:56:33   nl_NVcollDnode.C[100] :    NVCollCmpDnode::Resolve NVCollCm
pDnode(Attr: Origin contained in NetViews) Failed, no objid for attr Origin, obj
 id = 2887486038
100/05/01 09:56:33   nl_NVcollDnode.C[103] :    Object not found
100/05/01 09:56:40   nl_NVcollDnode.C[100] :    NVCollCmpDnode::Resolve NVCollCm
pDnode(Attr: Origin contained in NetViews) Failed, no objid for attr Origin, obj
 id = 2371864582
100/05/01 09:56:40   nl_NVcollDnode.C[103] :    Object not found

Regards,
Juan.

Juan Echevarr
ía López
AT&T Global Network Services




<Prev in Thread] Current Thread [Next in Thread>