- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Alpha to I64 migration
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
05-10-2016 01:23 PM
05-10-2016 01:23 PM
Alpha to I64 migration
We are moving from an Alpha platform to I64. Whenever we try linking our FORTRAN programs, we are seeing this error,
> LINK PL_ERROR_PRT, T_OBJLIB/LIB
%ILINK-E-INVOVRINI, incompatible multiple initializations for overlaid section
section: RDB$DBHANDLE
module: RDB$PL_INIT_INW_CNTL
file: DM$SWCTL:[BPRF.DM_TEST]OBJ_CODE.OLB;1
module: RDB$PL_FETCH_INW_CONV
file: DM$SWCTL:[BPRF.DM_TEST]OBJ_CODE.OLB;1
%ILINK-W-NUDFSYMS, 95 undefined symbols:
%ILINK-I-UDFSYM, SQL$PRC10_9U69EKJV74C10VT20480
%ILINK-I-UDFSYM, SQL$PRC11_AU69EKJV74C10VT20480
%ILINK-I-UDFSYM, SQL$PRC12_BU69EKJV74C10VT20480
[And the list continues on for 95 entries]
Any ideas what this means and how to fix it? Everything worked fine on the Alpha, and we were hoping to just migrate straight over to the I64 architecture.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2016 02:11 PM
05-10-2016 02:11 PM
Re: Alpha to I64 migration
Search for the word incompatible in the following for resources for information the triggers for and resolutions for this error, which usually involves sorting out your psect declarations. The following includes documentation on this error, as well as some other issues and information around porting OpenVMS apps and OpenVMS Rdb-using applications to OpenVMS I64:
http://de.openvms.org/TUD2012/customer_success_stories.pdf
http://download.oracle.com/otndocs/products/rdb/pdf/forums_2006/rdbtf06rs_14_rdb721.pdf
http://h71000.www7.hp.com/doc/83final/4548/4548pro_010.html
http://www.oracle.com/technetwork/documentation/rdb7200-rn-134690.pdf
The forum software dropped the previous reply to this question, and then the password change blew up, which dropped everything on the floor with the usual cascade of failures... This is the reply, re-entered. What blows up this time?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2016 05:08 PM
05-10-2016 05:08 PM
Re: Alpha to I64 migration
I ran into similar types of error messages with another Fortran based application. In my case, COMMON definitions were not consistant in their naming and size which created all kinds of problems. Also, default alignment issues can cause similar errors.
Look at the module for COMMON definitions and verify that they are actually constructed properly. Earlier versions of the compiler (Pre F90) worked in spite of "problems".
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2016 10:56 PM
05-10-2016 10:56 PM
Re: Alpha to I64 migration
> [...] COMMON definitions were not consistant in their naming and size
> which created all kinds of problems. [...]
It's been at least twenty years since I did much with Fortran, but
isn't that what the INCLUDE statement is for?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2016 03:34 AM
05-11-2016 03:34 AM
Re: Alpha to I64 migration
Perhaps, but much code exists that doesn't utilize that option (include statements).
Also, I neglected to mention that the issue is with NAMED common sections along with BLOCK DATA modules.
Dan