Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

 
stas_2
Occasional Contributor

trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

downloaded by vms 7.3-1 tcpip 5.3-184 in binary mode.
r CXXAE02062.A-DCX_AXPEXE;2

FTSV DCX auto-extractible compressed file for OpenVMS (AXP)
FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT
Copyright (c) Digital Equipment Corp. 1993

Options: [output_file_specification [input_file_specification]]

The decompressor needs to know the filename to use for the
decompressed file. If you don't specify any, it will use the
original name of the file before it was compressed, and
create it in the current directory. If you specify a
directory name, the file will be created in that directory.

Decompress into (file specification):
Opening and checking compressed file...
Decompressing (press Ctrl-T to watch the evolution)...
Creating decompressed file...
Original file specification: WORK5:[ECOKITBLD.LP.COMPLETE]CXXAE02062.A;1
Decompressed file specification: DISK$WORK:[STAS]CXXAE02062.A;1
%FTSV-W-COMP_DECOMPERR, fatal decompressor error
-DCX-W-TRUNC, data truncated
7 REPLIES
Dale A. Marcy
Trusted Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

Doing a Help/Message on V7.1 system (sorry, no V7.3 systems available) eventually provides the following:

TRUNC, data truncated

Facility: DCX, Data Compression/Expansion Facility

Explanation: The buffer is too small for the compressed data record
produced by DCX$COMPRESS_DATA or for the expanded data record
produced by DCX$EXPAND_DATA. As much data as the buffer can
hold has been returned.

User Action: Provide a larger buffer.


Dale A. Marcy
Trusted Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

I just tried downloading the kit to a VMS V7.1 Alpha system and received the same error when attempting to expand the patch. I think HP has a problem with their kit.
John Gillings
Honored Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

Please report this via the "contact hp" link in the top left hand corner of this page.

Select "ask a question about using the IT resource center" then area "General use of ITRC" and Category "Downloading: patches and software"

Make sure you give the exact steps used to obtain the file and the complete error message.

Thanks
A crucible of informative mistakes
George_145
Valued Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

I'm taking a look at this. I can't explain why but when this file was brought over from the old site the re-package and move were pretty much hosed. First of all, this kit is obsolete and shouldn't even appear on the ITRC site. It was replaced by the CCAE04062 ECO kit. This kit was also repackaged and moved and can be found by searching for CCAE04062...but don't bother. That kit expands...or it would if it also didn't fail... into a CXXAE02062 kit!! Clearly, things really got messed up.

I'm fixing this now. A new, correct, CCAE04062 kit is being moved to the ITRC. It will replace both the CCAE02062 and CXXAE02062 kits that are there now. The new kit should be available tomorrow morning EST.
George_145
Valued Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

Forget everything I just said. Well, almost everything. The CCAE04062 kit does have a problem that needs to be corrected but the CXXAE02026 kit also needs to be fixed. It seems that the old CXXAE02026 archive directory from the previous ECO site contains the CCAE04062 kit. Which is what probably caused the confusion and problems when the kits were moved over in hte first place. It will take a while to figure this out. Tomorrow we should have new CCAE and CXXAE eco kits available.

George Pagliarulo
Willem Grooters
Honored Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

george (and others @HP)

Sorry having to say so:
It's not the first time something went wrong in moving kits. The same happened before.

I bet most of the participants in this forum will agree:

"Never fix something that isn't broke"

It seems HP doesn't know this :-((

Willem
Willem Grooters
OpenVMS Developer & System Manager
Ian Miller.
Honored Contributor

Re: trouble with CXXAE02062.A-DCX_AXPEXE patch from ftp.itrc.hp.com

I think the problem with distribution of patches on itrc is due to trying to use a system inherited from hpux patch distribution with lots of historical baggage and adapting to do everything for everybody. It appears there are many steps between a fix being created in VMS Engineering, a patch kit being created and it being publicly available and much manual intervention is required. I know vms does not have the patch issue rate of windows etc (for which we are grateful :-) but patches are issued sufficently often that a simplified automated process is required.
____________________
Purely Personal Opinion