- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: TCPIP Service ECO5
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2010 05:06 AM
тАО03-04-2010 05:06 AM
TCPIP Service ECO5
openvms_patches > i64 > layered_products > i64,
But the kit was not there.
All of the other ECO's are there (1 - 4), but ECO 5 is not there. Am I looking in the wrong place, or am I just jumping the gun ??
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2010 05:13 AM
тАО03-04-2010 05:13 AM
Re: TCPIP Service ECO5
http://www13.itrc.hp.com/service/patch/patchDetail.do?BC=main|search|patchDetail{HP-I64VMS-TCPIP-V0506-9ECO5-1,{openvms:i64:8.2,}}|&patchid=HP-I64VMS-TCPIP-V0506-9ECO5-1&sel={openvms:i64:8.2,}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2010 05:17 AM
тАО03-04-2010 05:17 AM
Re: TCPIP Service ECO5
So I was hoping that it was available somewhere on the itrc FTP server.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2010 05:35 AM
тАО03-04-2010 05:35 AM
Re: TCPIP Service ECO5
tcpip show version
> [...]{openvms:i64:8.2,}[...]
There's something called
HP-I64VMS-TCPIP-V0506-9ECO5-1.ZIPEXE /.txt
under
ftp://ftp.itrc.hp.com/openvms_patches/i64/V8.2/
too.
TCPIP versions are tied so closely to VMS
versions these days that finding it among the
OS things instead of layered_products should
not amaze, I claim. Of course, a little
consistency might be nice, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2010 01:11 AM
тАО03-05-2010 01:11 AM
Re: TCPIP Service ECO5
The patches directory for 8.2 Alpha has a file called
".DEC-AXPVMS-TCPIP-V0506-9ECO5-1.ZIPEXE" while V0506 is coupled to 8.3.
The patches directory for 8.3 Alpha has no TCPIP patch anymore (not even ECO4).
This directory also has files with datetimestamps in the future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2010 01:47 AM
тАО03-05-2010 01:47 AM
Re: TCPIP Service ECO5
It was a model of ergonomy, so HP shut it, and kept the worst site.
Have a look to
http://ftp.hp.com.au/
ECO Indexes
├В┬╗ Chronological Index
├В┬╗ Indexed by Version
├В┬╗ Indexed by Rating
├В┬╗ Alpha Indexed by Name
├В┬╗ VAX Indexed by Name
├В┬╗ On Hold List
:-(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2010 06:43 AM
тАО03-05-2010 06:43 AM
Re: TCPIP Service ECO5
In the alerts e-mail, the ECO is list as
Products: Open VMS i64 8.X patch.
and under description,
Kit Applies To: OpenVMS Integrity Server V8.2
So I am forced to ask - Is this OK for OpenVMS 8.3-1H1 bladeservers??
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2010 11:50 PM
тАО03-05-2010 11:50 PM
Re: TCPIP Service ECO5
another warning: the TCPIP V5.6 ECO 9 kits for OpenVMS Alpha and OpenVMS I64 seem to have been re-released as evidenced by the entries in the DECUServe ECO notes file:
http://eisner.decus.org/DECUServe/DECnotes/ECO/2658/SDIR.HTML
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 02:24 AM
тАО03-07-2010 02:24 AM
Re: TCPIP Service ECO5
A better/preferred URL for this is:
http://decuserve.org/anon/htnotes/dir?f1=ECO&f2=2658.*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 04:40 AM
тАО03-07-2010 04:40 AM
Re: TCPIP Service ECO5
You'll find these latest TCPIP ECO05 kits available by FTP at: ftp.itrc.hp.com/openvms_patches/alpha/V8.2
and: ftp.itrc.hp.com/openvms_patches/i64/V8.2
This breaks established conventions whereby we're previously seen them in the layered_products directory tree. I have to agree - it's another example of how the process of distributing patches has become too sloppy.
Over the past 2 years or so we've seen far too many patch kits being re-issued to fix things or update things - without the necessary rigour being applied to file naming, file locations, version numbering and documentation.
Can we please stick with established conventions, unless there's a really good reason to make changes.
Bear in mind that many of us work in environments where reliability and stability are the things that matter, so we have appropriate (and sometimes over-the-top) processes and procedures to follow before we put new versions and patches into service on production systems. For example, you can't just toss a patch into service on a major finance data system, or a national healthcare system, or an air traffic control systems.
Careless errors in patch kits and changes to the way that patches are published cause us a lot of unnecessary work and annoyance, which in turn leads to the businesses that run these systems becoming annoyed by it as well - which is bad for all of us.
Cheers, Colin (http://www.xdelta.co.uk).