- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: PCSI removing identifiers??
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
тАО02-13-2008 12:56 AM
тАО02-13-2008 12:56 AM
PROD INSTALL A_1.0 /DEST=disk:[A_10].
PROD INSTALL A_2.0 /DEST=disk:[A_20]
PROD REMOVE A_xxx.
The installation script for both versions are equal where it concerns creating an identifier:
$ MCR AUTHORIZE ADD/ID A_ID
The first PROD INSTALL will create the identifier, the second will try as well but it fails because it already exists - as expected.
The de-installation script does not contain a command to remove the identifier, so it is expected that PROD REMOVE A_xxx - regardless the version - will keep this identifier defined.
However, we found that, no matter which version is removed, the created identifier is removed as well.
Is this information on what identifiers are created (and which files) kept somewhere 'hidden'? If so, how can we get around the problem?
The de-installation script does NOT hold a line to remove identifier A_ID, but after PROD REMOVE A - no matter which version -
OpenVMS Developer & System Manager
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 01:34 AM
тАО02-13-2008 01:34 AM
Re: PCSI removing identifiers??
PCSI can manage rights identifiers as 'managed objects' with the rights identifier statement in the PDL file. Do you use this feature ?
PCSI would remove the identifier automatically, when you remove the product.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 09:52 AM
тАО02-13-2008 09:52 AM
Re: PCSI removing identifiers??
and that's just the annoying thing...
I don't know whether the feature is used or not. I'll check tomorrow. AFAIK, the DCL procedure that is used to install the product, does all the work, just like KITINSTAL.COM would do using VMSINSTAL.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 07:37 PM
тАО02-13-2008 07:37 PM
SolutionIn general, a PRODUCT V2.0 package is intended to entirely replace PRODUCT V1.0. You're assuming that PRODUCT V1.0 and V2.0 are distinct, and (in practice) they're really not.
There's a dependency here if you do want to follow this approach, and I'd assume that the PCSI two kits here are not set up for what you're doing. To get where you appear to want here, you might want to look at the platform kit; at a platform suite.
And for this case, see the PCSI developer's manual, and specifically the "Managed Object Conflict" section of the manual. You've got a collision within the database and within the expectations of PCSI itself.
If you're looking to implement a multi-version kit (as it appears), then you'll want to work this out within the images and tools within the kit itself, rather than with the destination mechanism.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 10:48 PM
тАО02-13-2008 10:48 PM
Re: PCSI removing identifiers??
There's nothing creative here.
In this particular case, there is a conflict in the expectations of the software supplier and the requirement to locate software versions in their own directory, like described. There is good reason for that: in this high-availability environment, it allows fast rollback if something is severely wrong with the new version.
This is a very valid situation.
WG
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2008 01:13 AM
тАО08-15-2008 01:13 AM
Re: PCSI removing identifiers??
OpenVMS Developer & System Manager