- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: How come VMS Perl requires user written extens...
Operating System - OpenVMS
1754277
Members
3228
Online
108813
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
11-07-2007 06:54 PM
11-07-2007 06:54 PM
Re: How come VMS Perl requires user written extensions to be installed?
Tim,
On how to say "thanks" in these forums, please review
http://forums1.itrc.hp.com/service/forums/helptips.do?#33
Proost.
Have one on me.
jpe
On how to say "thanks" in these forums, please review
http://forums1.itrc.hp.com/service/forums/helptips.do?#33
Proost.
Have one on me.
jpe
Don't rust yours pelled jacker to fine doll missed aches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2007 09:49 AM
11-08-2007 09:49 AM
Re: How come VMS Perl requires user written extensions to be installed?
Tim,
>I don't think there is a way out of this.
There's ALWAYS a way out! You just have to understand your objectives, and what's really going on :-)
> They also link with a bunch of shareable
>images, some of them are installed with
>privs.
>
This concerns me. SHAREABLE images should not be installed with privilege. It doesn't do anything useful, but can cause image activation problems (like yours). See:
$ HELP INSTALL ADD/PRIV - in particular the bit that says:
o The /PRIVILEGED qualifier applies only to executable images.
Just to make sure we're prefectly clear on this, if you RUN the image you can give it privileges, if you LINK against an image, you CANNOT give that image privileges, and should not INSTALL the image with /PRIVILEGE.
Try removing the privileges from ALL shareable images you link against and try again. This should not break anything. Ask anyone who objects to explain exactly what /PRIVILEGE is buying them other than problems. As I said in my first response:
Standard reminder... there is NO SUCH THING as a "privileged shareable image".
(OK, there's ONE potential use for a shareable image installed with privilege, that's when it also contains a transfer address - kind of a hybrid executable image and shareable image - it is possible, but rarely done in practice, and not recommended. In that case if you INSTALL the image with privilege, you'll get the privileges if you RUN the image, but not if it's activated as a shareable image. IF you have one of these beasts, it's a simple matter of splitting up the main program part and shareable routines part, then linking them separately. As far as I know, this, and fanatical adherance to upwards compatibility, are the only reasons the /PRIVILEGE qualifier hasn't been blocked for shareable images in INSTALL)
>I don't think there is a way out of this.
There's ALWAYS a way out! You just have to understand your objectives, and what's really going on :-)
> They also link with a bunch of shareable
>images, some of them are installed with
>privs.
>
This concerns me. SHAREABLE images should not be installed with privilege. It doesn't do anything useful, but can cause image activation problems (like yours). See:
$ HELP INSTALL ADD/PRIV - in particular the bit that says:
o The /PRIVILEGED qualifier applies only to executable images.
Just to make sure we're prefectly clear on this, if you RUN the image you can give it privileges, if you LINK against an image, you CANNOT give that image privileges, and should not INSTALL the image with /PRIVILEGE.
Try removing the privileges from ALL shareable images you link against and try again. This should not break anything. Ask anyone who objects to explain exactly what /PRIVILEGE is buying them other than problems. As I said in my first response:
Standard reminder... there is NO SUCH THING as a "privileged shareable image".
(OK, there's ONE potential use for a shareable image installed with privilege, that's when it also contains a transfer address - kind of a hybrid executable image and shareable image - it is possible, but rarely done in practice, and not recommended. In that case if you INSTALL the image with privilege, you'll get the privileges if you RUN the image, but not if it's activated as a shareable image. IF you have one of these beasts, it's a simple matter of splitting up the main program part and shareable routines part, then linking them separately. As far as I know, this, and fanatical adherance to upwards compatibility, are the only reasons the /PRIVILEGE qualifier hasn't been blocked for shareable images in INSTALL)
A crucible of informative mistakes
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP