PowerHouse Licensing DECnet ECO required for SMP machines prior t o 7.1 OpenVMS Alpha

Fri, 18 Jul 2003 12:55:55 -0400

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C34D4D.742AAC00
Content-Type: text/plain;
	charset="iso-8859-1"

We have recently discovered that there is a known problem with SMP
(multi-CPU) Alpha machines running 6.1, 6.2 and 7.0 versions of OpenVMS if
running DECnet Phase IV.  There is an ECO that needs to be installed (or
upgrade to 7.1) in order to run the FlexLM license daemon successfully in
this environment.  The description of the problem from HP is as follows
(taken from a document from their support database):

"SYMPTOM:
An application hangs in LEF waiting for an I/O to complete on NETdevice.
The DECnet links on the multiprocessor Alpha system hang in states like CI
receiving, DI receiving, CI sending, DI sending. Other DECnetlinks have
00000000 owner PIDs, or show remote link numbers that nolonger exist on this
system."

We have observed exactly this scenario on a customer site when running
permanent license keys. Applying the ECO has allowed them to run with
permanent keys and doing SHOW KNOWN LINKS commands no longer shows evidence
of the broken links. Before the ECO was applied, doing a SHOW KNOWN LINKS
command in NCP showed links with 0 as the remote link, or a PID of 000000.
The license daemon was in LEF state and would not respond to license
requests (connection timeout).

For OpenVMS 6.1 and 6.2 versions you need to install ECO DECNET4AECO362 on
your machine in order to successfully run DECnet and license PowerHouse with
permanent keys.  The following URL will point to the ECO on HP's website, or
you can query the HP support database using the ECO number.   If the URL no
longer functions, contact HP for assistance, or search their website.
http://ftp.support.compaq.com/patches/public/Readmes/vms/decnet4aeco362.READ
ME

For OpenVMS 7.0, you will need to contact HP support to obtain the ECO kit
(not on the Web site) DECNET4AECO170.A or upgrade to 7.1. 
The problem is resolved in 7.1 of OpenVMS.  If you have upgraded to 7.1 and
are using temporary license keys, you should retry running PowerHouse with
your permanent keys. There is a strong likelihood that in this configuration
the daemon will now function correctly.  
Many thanks to the customer who patiently worked with us to identify the
problem and to the HP people who remembered the original issue and headed us
in the right direction, and to all of you who have had to live with
temporary key renewals until we managed to get the right combination of
people and circumstances together to resolve it.
We now have the ability to debug and therefore better resolve OpenVMS
Licensing issues, so I hope that we will  be able to address such concerns
in a more timely fashion in the future.

Allison Hamilton
ADT Development
Senior Software Engineer
Cognos Inc.

Join us at Cognos' biggest event of the year Enterprise 2003, The Cognos
Business Forum.  Taking place in over 25 cities around the world, it's an
opportunity for Business and IT leaders to learn about strategies for
driving performance. Visit http://www.cognos.com/enterprise03 for more
details. 

This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you.

------_=_NextPart_001_01C34D4D.742AAC00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>PowerHouse Licensing DECnet ECO required for SMP machines prior =
to 7.1 OpenVMS Alpha</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">We have recently discovered that there =
is a known problem with SMP (multi-CPU) Alpha machines running 6.1, 6.2 =
and 7.0 versions of OpenVMS if running DECnet Phase IV.&nbsp; There is =
an ECO that needs to be installed (or upgrade to 7.1) in order to run =
the FlexLM license daemon successfully in this environment.&nbsp; The =
description of the problem from HP is as follows (taken from a document =
from their support database):</FONT></P>

&quot;SYMPTOM:
 An application hangs in LEF waiting =
for an I/O to complete on NETdevice.
 The DECnet links on the =
multiprocessor Alpha system hang in states like CI receiving, DI =
receiving, CI sending, DI sending. Other DECnetlinks have 00000000 =
owner PIDs, or show remote link numbers that nolonger exist on this =
system.&quot;

We have observed exactly this scenario =
on a customer site when running permanent license keys. Applying the =
ECO has allowed them to run with permanent keys and doing SHOW KNOWN =
LINKS commands no longer shows evidence of the broken links. Before the =
ECO was applied, doing a SHOW KNOWN LINKS command in NCP showed links =
with 0 as the remote link, or a PID of 000000.&nbsp; The license daemon =
was in LEF state and would not respond to license requests (connection =
timeout).

<P><FONT SIZE=3D2 FACE=3D"Arial">For OpenVMS 6.1 and 6.2 versions you =
need to install ECO DECNET4AECO362 on your machine in order to =
successfully run DECnet and license PowerHouse with permanent =
keys.&nbsp; The following URL will point to the ECO on HP's website, or =
you can query the HP support database using the ECO number.&nbsp;&nbsp; =
If the URL no longer functions, contact HP for assistance, or search =
their website.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://ftp.support.compaq.com/patches/public/Readmes/vms/decnet4=
aeco362.README" =
TARGET=3D"_blank">http://ftp.support.compaq.com/patches/public/Readmes/v=
ms/decnet4aeco362.README</A></FONT>
</P>

For OpenVMS 7.0, you will need to =
contact HP support to obtain the ECO kit (not on the Web site) =
DECNET4AECO170.A or upgrade to 7.1.

The problem is resolved in 7.1 of =
OpenVMS.&nbsp; If you have upgraded to 7.1 and are using temporary =
license keys, you should retry running PowerHouse with your permanent =
keys. There is a strong likelihood that in this configuration the =
daemon will now function correctly.&nbsp;

<P><FONT SIZE=3D2 FACE=3D"Arial">Many thanks to the customer who =
patiently worked with us to identify the problem and to the HP people =
who remembered the original issue and headed us in the right direction, =
and to all of you who have had to live with temporary key renewals =
until we managed to get the right combination of people and =
circumstances together to resolve it.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We now have the ability to debug and =
therefore better resolve OpenVMS Licensing issues, so I hope that we =
will&nbsp; be able to address such concerns in a more timely fashion in =
the future.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Allison Hamilton</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ADT Development</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Senior Software Engineer</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Cognos Inc.</FONT>
</P>
<BR>
<BR>

Join us at Cognos' biggest event of =
the year Enterprise 2003, The Cognos Business Forum.&nbsp; =
Taking place in over 25 cities around the world, it's an opportunity =
for Business and IT leaders to learn about strategies for driving =
performance. Visit <A HREF=3D"http://www.cognos.com/enterprise03" =
TARGET=3D"_blank">http://www.cognos.com/enterprise03</A> for more =
details.

<P><FONT SIZE=3D2 FACE=3D"Arial">This message may contain privileged =
and/or confidential information.&nbsp; If you have received this e-mail =
in error or are not the intended recipient, you may not use, copy, =
disseminate or distribute it; do not open any attachments, delete it =
immediately from your system and notify the sender promptly by e-mail =
that you have done so.&nbsp; Thank you.</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C34D4D.742AAC00--