| Author |
Patch error |
molotovmouse
Member
Posts: 15
Joined: 23.02.07 |
| Posted on February 14 2010 18:07 |
|
|
I downloaded some layered product updates (binary) from the ITRC ftp site but keep running into problems extracting them.
When the DCX_AXPEXE file is run directly I get, regardless of the directory to expand it into -- generally its just left blank for current directory.
Decompress into (file specification):
Opening and checking compressed file...
%FTSV-W-COMP_INPUTERR, error manipulating input file
-RMS-F-SYN, file specification syntax error
Unzip has worked for some files in the passed, but not this time.
Any ideas would be helpful. Thank you. |
|
|
| Author |
RE: Patch error |
martinv2
Member
Posts: 107
Location: Goslar, Germany
Joined: 02.10.07 |
| Posted on February 14 2010 23:55 |
|
|
|
I downloaded some layered product updates (binary) from the ITRC ftp site but keep running into problems extracting them.
When the DCX_AXPEXE file is run directly I get, regardless of the directory to expand it into -- generally its just left blank for current directory.
Decompress into (file specification):
Opening and checking compressed file...
%FTSV-W-COMP_INPUTERR, error manipulating input file
-RMS-F-SYN, file specification syntax error
It would certainly help to know exactly which layered product patch you're talking about here.
Unzip has worked for some files in the passed, but not this time.
DCX is a different compression algorithm from ZIP, so UNZIP will not be useful in this case. DCX is built into VMS, but (apart from an API) not visible from the outside (i.e. via DCL or a utility).
cu,
Martin
http://de.openvms.org/martinv/ |
 |
| Author |
RE: Patch error |
molotovmouse
Member
Posts: 15
Joined: 23.02.07 |
| Posted on February 15 2010 07:19 |
|
|
First the system is vms8.3 with all current(ish) OS ECOs installed.
I ftp'd FORMSAVME0422.A-DCX_AXPEXE in binary form into both an ODS-5 & 2 disk, and when prompted I just hit return so the file will be extract into the current directory I get the same error. I've done this on both ODS5 & 2, it doesn't matter. This seems to only effect the DCX_AXPEXE files, as the ZIPEXE are fine -or- at least I can unzip them so at least I know they've transferred correctly. This is my first time encountering this problem.
BRUNO::JAMIE >>> run FORMSAVME0422.A-DCX_AXPEXE
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...
%FTSV-W-COMP_INPUTERR, error manipulating input file
-RMS-F-SYN, file specification syntax error
BRUNO::JAMIE >>> |
|
|
| Author |
RE: Patch error |
molotovmouse
Member
Posts: 15
Joined: 23.02.07 |
| Posted on February 15 2010 07:56 |
|
|
I copied the file both via the command line FTP (ucx) and COPY/FTP/BIN/ANON to an ODS2 directory, but it still returns the same response as earlier.
Edited by molotovmouse on February 15 2010 10:17 |
|
|
| Author |
RE: Patch error |
molotovmouse
Member
Posts: 15
Joined: 23.02.07 |
| Posted on February 15 2010 12:03 |
|
|
I fired up PersonalAlpha, alas, I was able to extract the files. Obviously its an environmental/process issue.
Thank you, thank you so much for your assistance. |
|
|
| Author |
RE: Patch error |
Bruce Claremont
Member
Posts: 623
Joined: 07.01.10 |
| Posted on September 26 2011 04:04 |
|
|
|
We have been unable to reproduce this problem. FORMSAVME0422.A-DCX_AXPEXE runs without issue on our test systems. |
|
|
| Author |
RE: Patch error |
abrsvc
Member
Posts: 108
Joined: 12.03.10 |
| Posted on September 27 2011 05:58 |
|
|
Try using a new account without any symbol definitions or logical names. I suspect that there is a lurking logical that matches a "file spec" being used by the decompression code. Try using a file spec with the extention rather than defaulting to only the name.
Dan |
|
|
