VMS 8.3 Alpha PCSI Problem

[Dieter Rossbach]

When I do ...

DIETER>product install *

1 - DEC AXPVMS VMS83A_ACRTL V4.0 Patch (remedial update)
2 - DEC AXPVMS VMS83A_BASRTL V1.0 Patch (remedial update)
3 - DEC AXPVMS VMS83A_MOUNT96 V4.0 Patch (remedial update)
4 - DEC AXPVMS VMS83A_SYS V6.0 Patch (remedial update)
5 - DEC AXPVMS VMS83A_UPDATE V5.0 Patch (remedial update)
6 - DEC AXPVMS VMS83A_VERIFY V1.0 Patch (remedial update)
? - Help
E - Exit

Choose one or more items from the menu: 5

I get ...

Performing product kit validation ...

%PCSI-E-VALFAILED, validation of DSA0:[DIETER.][000000]DEC-AXPVMS-VMS83A_UPDATE-
V0500--4.PCSI$COMPRESSED;2 failed
-PCSI-E-CDSA_TEXT, CSSMERR_SD_NO_TARGETFILE: User-input target file doesn't exis
t or is empty
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition


on am Alpha System with the following patch level:

VMS 8.3

VMS83A_ACMELDAP-V0100.RELEASE_NOTES;1 25 1-FEB-2007 12:36:56.31
VMS83A_ACRTL-V0100.RELEASE_NOTES;1 43 15-FEB-2007 14:10:42.89
VMS83A_ADDENDUM-V0100.RELEASE_NOTES;1 61 25-SEP-2006 15:22:41.33
VMS83A_ADDENDUM-V0200.RELEASE_NOTES;1 34 3-OCT-2006 13:17:21.50
VMS83A_BACKUP-V0200.RELEASE_NOTES;1 21 15-FEB-2007 12:32:56.39
VMS83A_ERRFMT-V0100.RELEASE_NOTES;1 22 31-JAN-2007 08:30:26.97
VMS83A_RMS-V0100.RELEASE_NOTES;1 25 4-OCT-2006 13:33:05.80
VMS83A_SECSRV-V0100.RELEASE_NOTES;1 18 3-OCT-2006 10:49:03.09
VMS83A_TZ-V0100.RELEASE_NOTES;1 27 5-FEB-2007 08:29:19.44
VMS83A_UPDATE-V0100.RELEASE_NOTES;1 32 14-NOV-2006 12:14:55.50
VMS83A_UPDATE-V0200.RELEASE_NOTES;1 43 7-FEB-2007 13:13:22.59
VMS83A_UPDATE-V0200.RELEASE_NOTES;1 43 7-FEB-2007 13:13:22.59

I downloaded the files via PC/FTP-Transfer and with Mozilla direct to the Alpha system in various forms with the same results.

What's wrong?

regards

Dieter

[Bart Zorn_1]

Hello Dieter,

What files are in the directory PCIS$SOURCE ?

Bart Zorn

[Dieter Rossbach]

Nothing ...

DIETER>sh log pcsi$source
%SHOW-S-NOTRAN, no translation for logical name PCSI$SOURCE

Dieter

[Kris Clippeleyr]

Dieter,

This could be a glitch in PRODUCT INSTALL.
The newer releases of PRODUCT INSTALL check for the existence of e.g. DEC-AXPVMS-VMS83A_UPDATE-V0500--4.PCSI$COMPRESSED_ESW, when trying to install DEC-AXPVMS-VMS83A_UPDATE-V0500--4.PCSI$COMPRESSED.
Normally, it should continue in case this file (the *.*_ESW) does not exist. Apparently, in your case, it does not.
As a workaround, please download the _ESW files, and try again. And if possible, raise a call with HP.
Regards,
Kris (aka Qkcl)

[Bart Zorn_1]

Dieter,

The patch files are indeed supposed to be in your current directory, unless you either specify /SOURCE= on the PROD command line, or you have PCSI$SOURCE defined.

What files *.PCSI* do you have in your directory?

Bart

[Dieter Rossbach]

DIETER>dir dec*

Directory disk$user:[DIETER]

DEC-AXPVMS-TCPIP-V0506-9ECO2-1.PCSI$COMPRESSED;1
97404 2-AUG-2007 17:25:15.25
DEC-AXPVMS-TCPIP-V0506-9ECO2-1.PCSI$COMPRESSED_ESW;1
18 2-AUG-2007 17:25:35.54
dec-axpvms-vms83a_acrtl-v0400--4.pcsi$compressed;1
7913 12-DEC-2007 11:31:37.31
DEC-AXPVMS-VMS83A_ACRTL-V0400--4.PCSI$COMPRESSED_ESW;2
18 12-DEC-2007 11:31:52.79
DEC-AXPVMS-VMS83A_BASRTL-V0100--4.PCSI$COMPRESSED;2
995 13-DEC-2007 10:02:00.69
DEC-AXPVMS-VMS83A_BASRTL-V0100--4.PCSI$COMPRESSED_ESW;2
18 13-DEC-2007 10:02:12.94
DEC-AXPVMS-VMS83A_MOUNT96-V0400--4.PCSI$COMPRESSED;2
669 4-DEC-2007 17:31:04.61
DEC-AXPVMS-VMS83A_MOUNT96-V0400--4.PCSI$COMPRESSED_ESW;2
18 4-DEC-2007 17:31:16.78
DEC-AXPVMS-VMS83A_SYS-V0600--4.PCSI$COMPRESSED;2
8906 3-DEC-2007 14:56:51.83
DEC-AXPVMS-VMS83A_SYS-V0600--4.PCSI$COMPRESSED_ESW;2
18 3-DEC-2007 14:57:05.96
DEC-AXPVMS-VMS83A_UPDATE-V0500--4.PCSI$COMPRESSED;3
76646 4-DEC-2007 10:06:44.22
DEC-AXPVMS-VMS83A_UPDATE-V0500--4.PCSI$COMPRESSED_ESW;3
18 4-DEC-2007 10:07:11.16
DEC-AXPVMS-VMS83A_VERIFY-V0100--4.PCSI$COMPRESSED;2
523 3-DEC-2007 12:43:54.55
DEC-AXPVMS-VMS83A_VERIFY-V0100--4.PCSI$COMPRESSED_ESW;2
18 3-DEC-2007 12:44:14.66

As you can see: _ESW-Files are there,too.
It's the same behaviour with all these files. When testing older compressed pcsi-files, everything is fine.

Dieter

[Bart Zorn_1]

Hmm...

I have installed all of those patches without problems.

I guess you should follow Kris's advise and see what happens.

Bart

[Volker Halle]

Dieter,

I would have guessed:

$ SET PROC/CASE=BLIND

but most of your .PCSI file names seem to be uppercase anyway.

How about version numbers > 1 and different version numbers ?

You can validate these file manually using CDSA$VALIDATE.EXE:

$ VALIDATE :== $SYS$SYSTEM:CDSA$VALIDATE.EXE
$ validate filename.PCSI$COMPRESSED

Volker.

[Kris Clippeleyr]

Indeed strange.
You seem to have the correct *UPD*.* files (sizes seem to be correct).
Just concentrating on the UPDATE-V0500 files...
The kit itself should be "fixed 512-byte", the ESW should be "stream-lf".
See the attachment for a DIREC/FULL on the files we have (and installed without problems).

Regards,
Kris (aka Qkcl)

[Dieter Rossbach]

The version numbers have no effect, die file attributes are the same as in your attached document.

validate says:

DIETER>validate dec-axpvms-vms83a_update-v0500--4.pcsi$compressed
Validation of dec-axpvms-vms83a_update-v0500--4.pcsi$compressed FAILED.
Error: CSSM_ERRCODE_MODULE_MANIFEST_VERIFY_FAILED
Modules manifest verification failed

Dieter

[Volker Halle]

Dieter,

I also tried the validate command on an existing VMS83A_UPDATE-V0400 .PCSI file, that I had recently installed successfully and I'm getting the same error from validate.

Volker.

[Volker Halle]

Dieter,

after the manual validate operation failed, I tried a PROD INSTAL VMS83A_UPDATE-V0400 in the same process and this operation succeeded to verify the file.

Puzzled,

Volker.

[The Brit]

Dieter,
Just a "shot in the dark". When you FTP'd the files, did you set type to BINARY?

Dave.

[Volker Halle]

Dieter,

CDSA$VALIDATE.EXE seems to implicitly require UNIX file name semantics:

$ validate /$9$dka0/kits/dec-axpvms-vms83a_update-v0400--4.pcsi$compressed

works fine, whereas

$ validate dec-axpvms-vms83a_update-v0400--4.pcsi$compressed

fails, although I set the default directory correctly.

Volker.

[The Brit]

Dieter,
Just a "shot in the dark". When you FTP'd the files, did you set type to BINARY?

I installed UPDATE V5.0 a couple of weeks ago without any issues (although I had previously installed V4.0, if that is relevent). I was just wondering if it was a problem going from Version 2.0 to 5.0, although I wouldn't have thought so.

Dave.

[Volker Halle]

Dieter,

the CSSMERR_SD_NO_TARGETFILE error message seems to indicate, that the 'input' file (i.e. the VMS83A_UPDATE-V0500--4.PCSI$COMPRESSED) does not exist. You can provoke this error message, if you provide a non-existing filename to CDSA$VALIDATE.

A SET WATCH FILE/CLASS=ALL preceeding the PRODUCT INSTALL VMS83A_UPDATE should show, which file access might fail...

Volker.

[Dieter Rossbach]

Volker,

DIETER>validate ./dec-axpvms-vms83a_update-v0500--4.pcsi$compressed
Validation of ./dec-axpvms-vms83a_update-v0500--4.pcsi$compressed SUCCEEDED.


OK, and what's next?

Dave,
1. FTP of the ZIPEXE-Files to a PC and than via FTP/binary to the VMS
2. FTP directly to the VMS-System (binary-mode)
3. creation of a Zip-File (ITRC-Service), download and expanding to get the ZIPEXE

in any of these cases the ZIPEXE-files run without problems and generated the PCSI$COMPRESSED and *_ESW files.

and in any of these cases, I cannot install them.

Strange

There might be a problem going from V0200 to V0500, but older updates are not on the ITRC-Servers.


Dieter

[Volker Halle · Accepted solution]

Dieter,

as a workaround, try to delete/rename to .PCSI$COMPRESSED_ESW file and install the patches without verification.

Or try PROD INSTAL/OPT=NOVALIDATE_KIT.

Nevertheless, I would still be interested in finding out what's wrong.

Volker.

[Volker Halle]

Dieter,

I've just downloaded VMS83A_SYS-V0600.ZIPEXE from the ftp.itrc.hp.com server and manually validated the file and tried a PRODUCT INSTALL - all verifications worked without a problem.

$ prod sho util
POLYCENTER Software Installation utility version: V8.3-054

Volker.

[Dieter Rossbach]

Volker,

I can install everything with /opt=noval.

(and did it)

It a solution, but not an answer ...

I'll continue searching


Dieter

[Willem Grooters]

Dieter,

I return to the question: how did you download the files? If you used the ITRC function to create a zip file, that might have been the cause. I have encountered similar problems (corrupted files after expanding the zip file).

Willem

[Volker Halle]

Dieter,


When testing older compressed pcsi-files, everything is fine.


Were these 'older' PCSI files signed as well (i.e. were there _ESW files for them) ?

Volker.

[Volker Halle]

Dieter,

what did your default directory look like ?

The following filespec looks suspicious:

DSA0:[DIETER.][000000]DEC-AXPVMS-VMS83A_UPDATE-V0500--4.PCSI$COMPRESSED;2 failed

I remembered this thread, when a new PRODUCT INSTALL problem was raised today:

http://forums12.itrc.hp.com/service/forums/postanswer.do?threadid=1205502

Volker.