1748274 Members
4344 Online
108760 Solutions
New Discussion юеВ

Question PROD on 8.2

 
SOLVED
Go to solution
Willem Grooters
Honored Contributor

Question PROD on 8.2

Installing patches on 8.2 (Alpha) puzzles me...
I have installed patches before, from DAK0 (the system disk, labeled IO_SYS82 and mounted using that logical), and a product on DKA100 (labled as IO_DATA and mounted as such). I remember it complained about a destination disk being not mounted or not having an associeated volume name.
Now I try to install new patches, whatever I do I get the message:

%PCSI-E-OPENOUT, error opening IO_DATA: as output
-PCSI-E-INVSPIDST1, destination device is not mounted or does not have an associ
ated logical volume name
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
$

even when I specify "/dest=io_sys82

What do I do wrong?

(The system is cluster member, but with it's own system disk)
Willem Grooters
OpenVMS Developer & System Manager
18 REPLIES 18
Willem Grooters
Honored Contributor

Re: Question PROD on 8.2

Additional:
After I dismounted all disks form the other clusternode, dismounted IO_DATA from the system itself and remounted it locally, I could start PROD and it gave me the list I expected. However, there is no ALL option (no problem) and the TCPIP patch - that came as an PCSI$COMPRESSED type, could not be processed:

%PCSI-E-READERR, error reading DKA0:[SYSMGR.][install]DEC-AXPVMS-TCPIP-V0505-11E
CO1-1.PCSI$COMPRESSED;1
-RMS-W-RTB, 813 byte record too large for user's buffer
%PCSI-E-OPENIN, error opening DKA0:[SYSMGR.][install]DEC-AXPVMS-TCPIP-V0505-11EC
O1-1.PCSI$COMPRESSED;1 as input
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
$

Did I miss something?
Willem Grooters
OpenVMS Developer & System Manager
Willem Grooters
Honored Contributor

Re: Question PROD on 8.2

Addition 2:

the TCPIP kit will not install:

$ prod install */kit_attributes=(format=compressed)
%PCSI-E-READERR, error reading DKA0:[SYSMGR.][install]DEC-AXPVMS-TCPIP-V0505-11E
CO1-1.PCSI$COMPRESSED;1
-RMS-W-RTB, 813 byte record too large for user's buffer
%PCSI-E-OPENIN, error opening DKA0:[SYSMGR.][install]DEC-AXPVMS-TCPIP-V0505-11EC
O1-1.PCSI$COMPRESSED;1 as input
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

Willem Grooters
OpenVMS Developer & System Manager
Alex  Daniels
Frequent Advisor

Re: Question PROD on 8.2

You don't need to manually specify the kit_attributes=(format=compressed)

Just install it like it was a .pcsi

If you still have problems, post the output from including you prod command, but use /trace as well.

Does a 'prod list' of the kit work?

Also checksum the kit and compare that to the release notes.

Steven Schweda
Honored Contributor

Re: Question PROD on 8.2

> -RMS-W-RTB, 813 byte record too large for user's buffer

I think that I needed to reset the file
attributes on the last compressed PCSI kit I
sucked down. I think that it was for V8.2,
too, but I've lost track. DIRE /FULL. If you
used a Web browser and got Stream_LF, you may
need to set it to fixed-512 (or something).
Volker Halle
Honored Contributor
Solution

Re: Question PROD on 8.2

Willem,

a .PCSI$COMPRESSED kit file needs to be:

Record format: Fixed length 512 byte records
Record attributes: None

Volker.
Kris Clippeleyr
Honored Contributor

Re: Question PROD on 8.2

Willem,
About the error INVSPIDST1. It means that one of the disks referenced in the PCSI database is not mounted on the system, at least not with the correct LOGVOLNAM. Somehow I think that this is a "feature" of PRODUCT that is not entirely correct. IMHO, PRODUCT should not complain about a disk not being mounted, if that disk does not play part in the operation. If it can access both the source disk (where the .PCSI kit is) and the destination disk (where you want the kit to be installed), it should simply do its job. I stumbled over the same error when trying to extract release notes. I opened a call for it with HP. Let you know what they have to say.
Greetz,
Kris (aka Qkcl)
I'm gonna hit the highway like a battering ram on a silver-black phantom bike...
Willem Grooters
Honored Contributor

Re: Question PROD on 8.2

Alex:
Makes no difference. I didn't check the checksum yet, will check just to see.
Steven, Volker:
Will try that on the first occasion (may be some days), but it shouldn't have come as such in the first place.

All needed patchkits (when will there come a search-by-DATE....) have been downloaded using the one-zip possibility; the zip has been extracted on VMS, and the regular files (AXPEXE) ran flawlessly and produced usable files (all FIXED 8192, have been installed), just this one was STREAM-LF and caused problems.
I've done this before without problems.

Kris:
The issue might be that the disks were mounted /CLUSTER in this system itself (IO) - both IO_SYS82 (the system disk) and IO_DATA. For IO_SYS82, that one is obviously mounted /SYSTEM originally, probably "promoted" to /CLUSTER; but PROD complained about IO_DATA only.And that as mounted /CLUSTER from the start. On the other cluster node, theer has not been an explicit MOUNT command; it might be that one that caused problems. But dismounting it there only did not help. It was after I dismounted that disk on IO, and mounted it privately, that PROD could get to work.
We'll see what HP has to comment.
Willem Grooters
OpenVMS Developer & System Manager
Karl Rohwedder
Honored Contributor

Re: Question PROD on 8.2

Has the disk IO_DATA been copied from one physical disk to another, e.g. DA200->DA100?

Such changes should be registered in PCSI using PROD REGISTER VOLUME.

regards Kalle
Volker Halle
Honored Contributor

Re: Question PROD on 8.2

Willem,

or did you ever change the volume label on DKA100: AFTER you've installed products on that disk ?

HELP PROD REGISTER VOLUME is worth reading.

Volker.