- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DECC$FD_LOCKING - OpenVMS 8.4
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
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
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
08-06-2011 02:24 PM
08-06-2011 02:24 PM
DECC$FD_LOCKING - OpenVMS 8.4
Hi,
For some applications we had to define a C RTL logical name DECC$FD_LOCKING to have a better memory management for some multi-threaded Java applications.
$ DEFINE/PROCESS/NOLOG DECC$FD_LOCKING TRUE
This worked OK on OpenVMS 8.3-1H1.
On OpenVMS 8.4 I don't know if we still should use this logical or not?
I found out last week that Oracle 10gR2 on OpenVMS 8.4 will not work anymore when this logical is defined.
Oracle can't create any file (table space or Archive file) or do a RMAN backup.
On OpenVMS 8.3-1H1 I didn't have this behaviour.
Are there any release notes about the changes in the C Runtime library on OpenVMS 8.4 or where can I find them ?
/Toine
DECC$FD_LOCKING
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2011 06:04 PM
08-06-2011 06:04 PM
Re: DECC$FD_LOCKING - OpenVMS 8.4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2011 12:14 AM
08-08-2011 12:14 AM
Re: DECC$FD_LOCKING - OpenVMS 8.4
>>> $ DEFINE/PROCESS/NOLOG DECC$FD_LOCKING TRUE
<<<
As already said, $ DEFINE/USER is what you want to avoid conflicts. Setting any DECC feature logical process wide will get you in trouble, sooner or later.
>>> (If anyone knows a simple recipe for getting a user-supplied LIB$INITIALIZE function called in a C++
program, I'd be interested.)
<<<
Define/describe what you mean by "a simple recipe".
There is no such thing like a "user-supplied LIB$INITIALIZE function". There are user-supplied init routines, which are listed in a LIB$INITIALIZE PSECT. There is a VMS-supplied LIB$INITIALIZE routine which calls the user-supplied init routines in the order in which they appear in the LIB$INITIALIZE PSECT.
Regarding C++, this was already answered in http://h30499.www3.hp.com/t5/Languages-and-Scripting/C-v-LIB-INITIALIZE-DECC-ARGV-PARSE-STYLE/m-p/4371453: you need a shareable image with a user-supplied init routine. (I tried to explain image initialization in a VTJ article, including a C++ example. But the article was not accepted.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2011 10:59 AM
08-08-2011 10:59 AM
Re: DECC$FD_LOCKING - OpenVMS 8.4
>I tried to explain image initialization in a VTJ article, including a C++ example. But the article was not accepted.
Did you want to create a Knowledge Base article?