Installing Patches on VMS731

[Joseph Drozdz]

I am installing several Patches starting with VMS731_PCSI-V0100.PCSI-dcx-axpexe on an ES40. I have the patch downloaded and renamed the file to VMS731_PCSI-V0100.PCSI;1 When I do a product install* my file does not show up. I get this error:

$ product
_Operation (INSTALL, SHOW, ...): install
_Product name (* to show list): *
%PCSIUI-I-NOMATCH, no products were found matching: *
%PCSIUI-E-NOPROD, no products were found on which to perform this operation
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

What am I doing wrong?
Thanks Joe

[Dale A. Marcy · Accepted solution]

Joe,

The file that you download is an executable that extracts the patch from itself. You need to run the filename and then install the resulting patch.

$ run vms731_pcsi-v0100.pcsi-dcx-axpexe

[Dieter Rossbach]

1. Have really "renamed" the file, you downloaded, to xxx.PCSI? They might be self extracting .exe files you have ´to "RUN" to unpack them ...

2. Check the name of the file. I had problems installing PSCIs just because the filetype was .PCSi with o lowercase i! "PRODUCT INSTALL" has problems with mixed upper/lowercase filenames.

Regards

Diet

[Martin P.J. Zinser]

Assuming you did inflate the patch by running it, the problem might be that you are on an ODS-5 disk with a mixed case filename. Either make sure the filename is all UPPERCASE or move the patch to an ODS-2 disk and you should be set.

[Joseph Drozdz]

I have run the executable but slipped up on the renaming

$ rename VMS731_PCSI-V0100^.PCSI-DCX-AXP.EXE;1
_To: VMS731_PCSI-V0100.PCSI-dcx_axpexe

and are now getting this error
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters
\^\

It will not rename with this type of error. Is there a work around this beside just deleting and strating over again?
Thanks again.

[Dale A. Marcy]

I don't have any ODS 5 disks, so I don't know if this will work, but you could try:

$ rename *.PCSI-dcx-axpexe VMS731_PCSI-V0100.PCSI-dcx-axpexe

[Martin P.J. Zinser]

Hello,

just take the original file you downloaded, the name does not matter! Then do a $run .

This will create the pcsi with the correct file name for you. Then the only thing might still be the upper vs. lowercase issue.

If you still have problems then, please post the exact sequence of commands/messages as it appears on your terminal.

Greetings, Martin

[Craig A Berry]

Joseph,

The problem with your rename is that you have a file with extended syntax in its name but you don't have extended filename parsing enabled for your process.

Try

$ set process/parse=extended

Then try your rename again.

[Antoniov.]

Hi Joe,
you are using ODS-5 disk; character ^ is escape character so ^. means dot is not interpretated as extension of file.
Type command's Craig before executing commands.
Also remember PCSI use filename to find procduct and version, so if you rename the files PCSI can't match product.

Bye
Antoniov

[Terry Yeomans]

The best course to follow is as Martin prescribed.
Download the patch.
If it is a filename.PCSI type file then
RUN filename.PCSI
PRODUCT INSTALL VMS731_PCSI /SOURCE=where the file is
If in doubt do a
PRODUCT EXTRACT RELEASE_NOTES VMS731_PCSI
Yours Terry.