VMS732_PCSI-V0100

[Paul Murray_4]

Firstly - total VMS newbie, so I apologise if this is a dumb question, but .....

Just finished installing OpenVMS732 on a DS15 and am now trying to install the VMS732_PCSI-V0100 patch.

The install instructions state to use the command :

$ product install VMS732_PCSI /SAVE_RECOVERY_DATA /SOURCE=DKA0:[TMP]

but I get the following errors :

%PCSIUI-I-NOMATCH, no products were found matching: VMS732_PCSI
%PCSIUI-E-NOPROD, no products were found on which to perform this operation
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition


Can someone give me a clue as to what I've forgotten, or what I'm doing wrong ...

MANY thanks !!!

Paul.

[Paul Murray_4]

If it helps, product shows the following installations :



$ product show product *
----------------------------------- ----------- ------------
PRODUCT KIT TYPE STATE
----------------------------------- ----------- ------------
CPQ AXPVMS CDSA V2.0-109 Full LP Installed
DEC AXPVMS DECNET_OSI V7.3-2 Full LP Installed
DEC AXPVMS OPENVMS V7.3-2 Platform Installed
DEC AXPVMS TCPIP V5.4-15 Full LP Installed
DEC AXPVMS VMS V7.3-2 Oper System Installed
HP AXPVMS KERBEROS V2.0-6 Full LP Installed
----------------------------------- ----------- ------------

6 items found

[Joseph Huber_1]

Did You really type what the installation note told , i.e.
/source=dka0:[tmp] ?

The /source qualifier specifies the REAL location of the .PCSI patch file, substitute it for dka0:[tmp] !

[Volker Halle]

Paul,

does the file DEC-AXPVMS-VMS732_PCSI-V0100--4.PCSI exist in DKA0:[TMP] on your system ?

Volker.

[Jan van den Ende]

Paul,

Welcome to VMS!

How did you get your /SOURCE specification?

Obviously there is no PCSI kit in DKA0:[TMP]

So:
- transfer the kit there and try again, or
- specify the current location of the kit with the /SOURCE=.. qualifier.

.. and do not hesitate to ask any more questions.

Proost.

Have one on me.

jpe

[Paul Murray_4]

Many thanks for jumping into help so quickly !!

(The dka0:[tmp] is the directory where the downloaded patch files were saved - the install instructions state to use the /SOURCE= switch to specify the location - sorry, if I confused matters on that point !!).

The downloaded files are :

$ dir /date

Directory DKA0:[TMP]

VMS732_PCSI-V0100.PCSI-DCX_AXPEXE;1
19-JUL-2005 11:35:47.56
VMS732_UPDATE-V0400.;1
19-JUL-2005 11:36:09.87

Total of 2 files.


I notice that these do not end in the suffix you suggest, but there's no mention of renaming the files or pre-processing them.

Is there something I need to do in order to prepare the files ??

(Thanks),
Paul.

[Joseph Huber_1 · Accepted solution]

There is one step more to do before product install:
The file is a compressed,selfextracting file. Do a
$ RUN ...axpexe
the result is the .PCSI file for PRODUCT INSTALL.

[Paul Murray_4]

Joseph,

That did the trick !!!

By running the AXPEXE it created the PCSI and the install seems to be doing it's thing now !!!

THANK YOU !!!!!


Regards,
Paul.

[Jan van den Ende]

and Paul,

so I apologise if this is a dumb question, but .....


the only REAL dumb question is the un-asked question!

Proost.

Have one on me.

jpe

[Volker Halle]

Paul,

the OpenVMS patches are generally provided as self-expanding .PCSI-DCX_AXPEXE files, you just need to RUN them (on the OpenVMS Alpha system) after downloading.

Note that some browsers may not correctly preserve the file extension and you need to rename the file with the proper extension.

Volker.

[Lawrence Czlapinski]

Paul: VAX PCSI patches would be RUN on a VAX.

[Willem Grooters]

Found it not needed. IE stores the name without extension, so moved to VMS using binary FTP stored without extention. Run the image ($ REN .) will do and create the file.

I know most system managers would not want to do this and discourage anyone to do this, but it CAN save time:
If you start PRODUCT when the kit is on the current directory, /SOURCE is not needed. You can also use wildcard ($ PROD INSTALL *) and it will show you what is installable, and you can coose to install one, several or all in one go.