 
| Subject: | |
| From: | |
| Reply To: | Genute, Thomas |
| Date: | Tue, 4 May 1999 07:23:01 -0400 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
It appears that HP has pulled patch VPLJXG3B while waiting for a replacement
to resolve the intermittent 'uninitialized memory' or other problems with
the patch. We had installed 6.0 on our Y2k test system in January along
with VPLJXG3B. It passed our testing. Then we started rolling out 6.0 to
other locations, but VPLJXG3B was not shipped with the 'latest' patches for
MPE/IX 6.0.
Therefore all new MPE/IX 6.0 installations are running VPLUS version
B.06.06. Bottom line is that MPE/IX 6.0 is not Y2k compliant and here we
are in May 1999 and HP is shipping a non Y2k compliant operating system. I
think this is a very sad and serious state of affairs for HP.
Tom Genute
----------
From:
[log in to unmask][SMTP:[log in to unmask]
.COM] <mailto:[SMTP:[log in to unmask]]>
Sent: Thursday, February 25, 1999 1:46PM
To: [log in to unmask]
<mailto:[log in to unmask]>
Subject: Vplus Y2K intermittent bug
Subject: Vplus Y2K intermittent bug
Author: ERIK VISTICA at HP-USA/o2=om51
If you support MPE please read on, otherwise, delete.
There is a Known Problem with Vplus KP 5003443929 that
affects new Y2K features
for 5.5 ppt 2 and later (including 6.0). Do NOT upgrade
customers to any 5.5
power patch nor 6.0 without understanding the potential
impact to their
business.
The problem on 5.5 has existed since ppt 2 (VPLJXG3A). It is
intermittent. Some
customers have run fine for over a year and not encountered
the problem. This is
common for problems, like this one, where the root cause is
uninitialized
memory. This patch added the Y2K features to Vplus. These
new features are
enabled via:
:SETJCW VSETNEXTCENTURY 1 (or 2 or 3)
If your customer does not use this JCW, and has no plans to
do so (highly
unlikely), then the problem does not affect them and you can
stop reading now.
The symptom is that Vplus acts as though the JCW was never
set.
The date 02/29/00 is interpreted as Feb 29, 1900 (which is
an invalid date)
instead of Feb 29, 2000 (which is valid).
Vplus will return an error such as:
The field must be a valid date, in MDY order.
Another symptom is that 2 digit years are still returned
instead of 4 digit
years. This can cause user DATA CORRUPTION in a production
database.
The problem seems to have a greater probability of
manifesting itself on
5.5 ppt 5 or ppt 6 than on ppt 4. Also, simply making a
change to an existing
formfile and recompiling it can trigger the problem. The
problem can even come
and go for individual fields on a form. This is because the
JCW is searched for
on each Date type field. Depending on what was left in
memory, we may or may not
match the JCW name.
THERE IS NO WORKAROUND!
If a customer's production application is using these
features and they make a
change that triggers the problem, they must back-out
whatever change they made
and hope that the uninitialized memory returns to its prior,
benign state.
Given this, I recommend that customers do NOT install any
patches unless
absolutely neccessary until they have a GR version of the
patch VPLKXL6 in their
hands.
The first beta customer will receive VPLKXLG6 C on Fri
2/5/1999.
VPLKXLG6 A for 5.5 beta bad
VPLKXLG6 B for 6.0 beta bad
VPLKXLG6 C for 5.5 beta test
VPLKXLG6 D for 6.0 beta test
In addition, the Vplus version on 5.5 ppt 2 and later is
B.06.07. On 6.0 an
older version B.06.06 was shipped by mistake. This means
that any customer that
upgrades to 6.0 will lose the Y2K features entirely. The
patch VPLJXG3 B will at
least get the B.06.07 version on 6.0 (including the
intermittent bug).
The patch VPLKXLG6 is version B.06.08.
OS/patch Vplus version Comments
--------- -------------
-----------------------------------------------
VPLJXG3 B.06.07 Has Y2K features with
intermittent problem.
5.5 ppt 2 B.06.07 ppt 2 contains VPLJXG3
6.0 B.06.06 ! Earlier non-Y2K version. VPLJXG3
B available to
get customers to at least the
intermittent version.
VPLKXL6 B.06.08 Fixed Y2K version. In beta test
for 5.5 and 6.0.
You can check the current version with:
:RUN HP32209S.PUB.SYS
VPLUS INTRINSICS VERSION: HP32209B.06.07
------- --------------
SEGMENT VERSION
------- --------------
01 B'06'07'S01'00
02 B'06'07'S02'00
03 B'06'07'S03'00
04 B'06'07'S04'00
05 B'06'07'S05'00
06 B'06'07'S06'00
07 B'06'07'S07'00
08 B'06'07'S08'00
09 B'06'07'S09'00
10 B'06'07'S10'00
11 B'06'07'S11'00
12 B'06'07'S12'00
13 B'06'07'S13'00
14 B'06'07'S14'00
16 A.00.06.S16.00 <---- Ignore this one.
17 B'06'07'S17'00
18 B'06'07'S18'00
19 B'06'07'S19'00
20 B'06'07'S20'00
21 B'06'07'S21'00
22 B'06'07'S22'00
------- --------------
VPLUS NATIVE MODE INTRINSICS VERSION: HP32209B.06.07
OVERLAY VERSION: B.06.07.00
FOR THIS USER:
VPLUS NATIVE MODE IS ENABLED;
VPLUS SWITCH TO COMPATIBILITY MODE IS DISABLED;
WILL DEFAULT COMPATIBILITY MODE SL SEARCH TO
SYSTEM SL
DHCF A4004000
VPLUS/Windows VERSION: HP36393A.00.06
VPLUS/Windows Native Mode VERSION: HP36393A.00.06
OVERLAY VERSION: A.00.06.00
Regards,
ERIK VISTICA
[log in to unmask] <mailto:[log in to unmask]>
|
|
|
