- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Header files for definitions for utility routines ...
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-24-2006 04:30 AM
тАО02-24-2006 04:30 AM
Apparently the C header files do not contain this condition value. I searched the reference directory where the list of H files included in the .TLB is provided, and none of the header files contain this.
I am building this on 8.2 in preparation for our itanium port. Originally, this code was using several assembler modules to extract the defintions from $LBRDEF, $QUIDEF and $PRVDEF macros and the compiled module was linking against these.
Could someone tell me where to find these missing definitions from header files?
Thanks,
Malleka
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 05:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 05:27 AM
тАО02-24-2006 05:27 AM
Re: Header files for definitions for utility routines and system services
here is an old TIMA article (from OpenVMS V4.x days) describing this:
http://h18000.www1.hp.com/support/asktima/appl_tools/009181EA-5633A280-1C01E7.html
And what's wrong with using MACRO-32 assembler modules on OpenVMS Alpha V8.2 or even OpenVMS Itanium ???
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 05:34 AM
тАО02-24-2006 05:34 AM
Re: Header files for definitions for utility routines and system services
yes, it has been defined as global.
I just went thru most of the *.MLB, and *.TLB, unbale to find LBR$_KEYNOTFND macro.
As Mr.Volker said it should be global variable, that is why it has been declared as
EXTERNAL LBR$_KEYNOTFND in the programs
You can declare this as a
external LBR$_KEYNOTFND.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 05:41 AM
тАО02-24-2006 05:41 AM
Re: Header files for definitions for utility routines and system services
See VMS help under condition_values_returned for this LBR$ routine...
$help lbr$ lbr$lookup_key
Note:
Malleka, Nice to know you do this kind of work, because I am also in the process of migrating my MACRO application to Itanium.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 05:43 AM
тАО02-24-2006 05:43 AM
Re: Header files for definitions for utility routines and system services
Good info from your link.
Thanks
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 05:55 AM
тАО02-24-2006 05:55 AM
Re: Header files for definitions for utility routines and system services
$ help lbr$ lbr$lookup_key
This should be:
$ HELP LBR LBR$LOOKUP_KEY
The help topic is called: LBR_ROUTINES
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 06:20 AM
тАО02-24-2006 06:20 AM
Re: Header files for definitions for utility routines and system services
Any special reason why LBR$_ routine's return codes categorized as global symbol, are they being used frequently to keep it in Main mem?.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 06:28 AM
тАО02-24-2006 06:28 AM
Re: Header files for definitions for utility routines and system services
Volker, I don' think there is anything wrong with using MACRO modules. It just happens to be a multi-platform application and the code may have to be maintained by someone who has not worked with OpenVMS.
It will be much easier if they had only C modules to look at.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2006 06:36 PM
тАО02-24-2006 06:36 PM
Re: Header files for definitions for utility routines and system services
in OpenVMS, data structure and constant definitions for public system APIs (system services, RTL routines etc.) are generally defined in either header (or include) files or - in case of constant declarations - as global symbols inside the shareable image files.
Structure definitions are typically defined with SDL (Structured Definition Language - see OpenVMS Freeware V5) and include or header files are generated by SDL for the various languages and put into .TLBs (e.g. FORSYSDEF.TLB, SYS$LIB_C.TLB etc.).
Constant definitions (e.g. for service return status codes) may also be defined as global constants within the shareable images files. These files will be put into IMAGELIB.OLB and the linker will resolve those definitions at link time.
The following command will list the names of all the global symbols from the global symbol table of LBRSHR.EXE (by convention, names for a facility generally start with the facility name, e.g. LBR):
$ pipe libr/lis sys$library:imagelib/names | sea sys$pipe lbr
Volker.