Message from discussion
Update to TCP/IP problem with Alpha VMS 8.4
Received: by 10.68.230.68 with SMTP id sw4mr805835pbc.7.1333758483297;
Fri, 06 Apr 2012 17:28:03 -0700 (PDT)
Path: r9ni27031pbh.0!nntp.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 06 Apr 2012 19:28:02 -0500
Date: Fri, 06 Apr 2012 20:27:51 -0400
From: "Richard B. Gilbert" <rgilber...@comcast.net>
Reply-To: rgilber...@comcast.net
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
Newsgroups: comp.os.vms
Subject: Re: Update to TCP/IP problem with Alpha VMS 8.4
References: <d0e5080d-2862-41ae-8694-0ab6d4e8da7e@l4g2000vbt.googlegroups.com> <ed528bdc-3ebc-4640-9e09-d04e5abb74d0@j15g2000vbt.googlegroups.com> <jlku05$u4i$1@dont-email.me> <3d936d88-5d47-4a5a-8e6c-5de6597be84d@er9g2000vbb.googlegroups.com> <jll3bt$9lc$1@news.albasani.net> <6b8e75f3-9f02-4c5e-ad04-d865eaeb7bad@l7g2000vbw.googlegroups.com>
In-Reply-To: <6b8e75f3-9f02-4c5e-ad04-d865eaeb7bad@l7g2000vbw.googlegroups.com>
Message-ID: <PIKdnacED5KPF-LSnZ2dnUVZ_uydnZ2d@giganews.com>
Lines: 47
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-dIKs04u/d2lODHbFezRfUD09/PdhtNpaeabd1EUvrKXUUX9Jke0Gt/T+cd1FCOhYmSTa/BpREqz5OV6!bDxtLm+LV/Jw7knhr4boNr7CSR6B71y8dhZx1qIL7fF2L6BU8eAe8XJ2CYJAyuhH26rbgY6jpA==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2968
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 4/5/2012 7:20 PM, vmsmang...@earthlink.net wrote:
> On Apr 5, 2:38 pm, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>
> wrote:
>> vmsmang...@earthlink.net wrote 2012-04-05 22:21:
>>
>>> Here is the reaponse to Jan-Erik's reply:
>>
>> Hi. Sorry if I was a bit "short" earlier, but I usualy (and
>> I know others too) find hard output better then rewritten
>> descriptions of something. :-)
>>
>>> COUGAR$ tcpip show ver
>>
>>> HP TCP/IP Services for OpenVMS Alpha Version V5.7
>>> on an AlphaServer DS20 500 MHz running OpenVMS V8.4
>>
>> OK. My system says :
>>
>> $ tcpip sh ver
>>
>> HP TCP/IP Services for OpenVMS Alpha Version V5.7 - ECO 3
>> on an AlphaServer DS25 running OpenVMS V8.4
>>
>> $
>>
>> Are you able to goto ECO 3 ?
>> No idea if that "solves" anything of course, it's just
>> a thought. There is usualy no reason *not* to apply ECO's.
The conservative approach is to NOT apply ECOs, or upgrades
unless they fix a problem that YOU HAVE or add a feature that
that you NEED.
It's not always possible but you should be conservative
in applying patches and upgrades when possible; especially
if your system is working properly.
Fixes have been known to break working systems. Sometimes they
don't even fix the problem(s) that they are supposed to fix!
Upgrades may create new problems! TEST before installing upgrades,
or fixes in production!
<snip>