- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- HP BASIC & $XABFHCDEF
Operating System - OpenVMS
1748112
Members
3342
Online
108758
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
03-13-2008 01:14 PM
03-13-2008 01:14 PM
Re: HP BASIC & $XABFHCDEF
In C, there are several predefined macros to help with coding in situations like this.
No there are not... read on.
>>> in this shop if I could in Basic distinguish between Alpha and Itanium,
No you should not.
>> I could have $XABDEFFHC included conditionally.
You should be able to include is unconditionally.
There is an XABDEFFHC on for the version of OpenVMS since 7.3-X / DECbasic 1.3 on Alpha, as well as on Itanium.
If there is not one om the particular Alpha system which is being used then is is 99.99% certain to be non-standard, out-of-date library and placed there explicitly.
You can do the exact same thing on Itanium. That would not be a bad thing to do. No worse then the Alpha situation today. There is NO platform dependencies in XAB(FHC)DEF for Alpha/Itanium. They are exactly the same, both conforming to the RMS defitions which are the same.
>> The following two-line program compiles fine on our Itanium; but fails to compile on our Alpha.
The operative word is *our*.
It will work on any other Alpha.
Best regards,
Hein van den Heuvel
No there are not... read on.
>>> in this shop if I could in Basic distinguish between Alpha and Itanium,
No you should not.
>> I could have $XABDEFFHC included conditionally.
You should be able to include is unconditionally.
There is an XABDEFFHC on for the version of OpenVMS since 7.3-X / DECbasic 1.3 on Alpha, as well as on Itanium.
If there is not one om the particular Alpha system which is being used then is is 99.99% certain to be non-standard, out-of-date library and placed there explicitly.
You can do the exact same thing on Itanium. That would not be a bad thing to do. No worse then the Alpha situation today. There is NO platform dependencies in XAB(FHC)DEF for Alpha/Itanium. They are exactly the same, both conforming to the RMS defitions which are the same.
>> The following two-line program compiles fine on our Itanium; but fails to compile on our Alpha.
The operative word is *our*.
It will work on any other Alpha.
Best regards,
Hein van den Heuvel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2008 02:40 PM
05-23-2008 02:40 PM
Re: HP BASIC & $XABFHCDEF
Just adding a bit more information in case someone runs into a similar situation. The installation kit prompts the user whether or not to create the 'system definitions'. The default is NO. Consequently, if you install the new versions of the compiler, and select the default, you get to keep the old definitions.
I'm not sure if this option is shown when installing on a VMS 8.3 machine; where BASIC$STARLET is distributed with OpenVMS.
Somewhere along the line, some coding changes needed to be made with the compiler upgrade.
I'm not sure if this option is shown when installing on a VMS 8.3 machine; where BASIC$STARLET is distributed with OpenVMS.
Somewhere along the line, some coding changes needed to be made with the compiler upgrade.
- « 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