- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Question PROD on 8.2
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 08:10 AM
тАО10-30-2005 08:10 AM
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)
OpenVMS Developer & System Manager
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 08:20 AM
тАО10-30-2005 08:20 AM
Re: Question PROD on 8.2
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?
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 08:34 AM
тАО10-30-2005 08:34 AM
Re: Question PROD on 8.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
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 11:17 AM
тАО10-30-2005 11:17 AM
Re: Question PROD on 8.2
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 03:52 PM
тАО10-30-2005 03:52 PM
Re: Question PROD on 8.2
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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 06:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 07:03 PM
тАО10-30-2005 07:03 PM
Re: Question PROD on 8.2
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 08:23 PM
тАО10-30-2005 08:23 PM
Re: Question PROD on 8.2
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.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 09:53 PM
тАО10-30-2005 09:53 PM
Re: Question PROD on 8.2
Such changes should be registered in PCSI using PROD REGISTER VOLUME.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2005 11:13 PM
тАО10-30-2005 11:13 PM
Re: Question PROD on 8.2
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.