- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Seeking basic015.release_notes and basic014.releas...
Operating System - OpenVMS
1753865
Members
7551
Online
108809
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО06-15-2009 05:25 PM
тАО06-15-2009 05:25 PM
Seeking basic015.release_notes and basic014.release_notes
I'm trying to find out if an obscure problem (%OTS-F-FATINTERR, fatal internal error in Run-Time Library) we're seeing in our Basic 1.3 environment was addressed in one of these two releases. I have the 016 release notes. No mention in there.
The problem seems to be the result of the Basic program closing a file/channel with a LIB$FREE_LUN(channel_l) .
Thanks in advance,
Art
The problem seems to be the result of the Basic program closing a file/channel with a LIB$FREE_LUN(channel_l) .
Thanks in advance,
Art
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2009 06:02 PM
тАО06-15-2009 06:02 PM
Re: Seeking basic015.release_notes and basic014.release_notes
Art,
LIB$FREE_LUN doesn't close a file or channel. All it does is free a LUN allocated with LIB$GET_LUN. You need to close the file in BASIC before freeing the LUN.
From dim and distant memories, this pair of routines is very, very simple. GET_LUN is basically just a FFS instruction to find a free LUN in a static bitmask, followed by BICL to mark it allocated. FREE_LUN is a BISL to mark it free again. (I may have the sense of the free/allocated bits around the wrong way).
There are a handful of other instructions for sanity checks. There's not a lot that can go wrong!
I can't see how a problem in LIBRTL could be fixed by a Basic compiler update. Remember that all RTLs belong to OpenVMS, NOT the compiler, so compiler kits don't change RTLs.
If you think it's the LIB$*_LUN routines causing trouble, try reimplementing them yourself so you can debug them. All you need to do is allocate and deallocate numbers in the range 100-119 or 100-299 if it's Alpha or I64.
That said, my usual advice with compilers is to always use the latest version. Compilers only ever get better, and the first step in diagnosing any compiler issue is to try the latest version. It's also trivially easy to retain old versions of compilers and switch between them any time you like (Pascal does this for you automatically, I'm not sure about Basic).
Since compilers are really just user mode text processors, any user can break open a compiler kit, copy the compiler image to their local directory, define a logical name, and use a different compiler version without having to install it.
If none of that helps, please post the stack dump for the FATINTERR.
LIB$FREE_LUN doesn't close a file or channel. All it does is free a LUN allocated with LIB$GET_LUN. You need to close the file in BASIC before freeing the LUN.
From dim and distant memories, this pair of routines is very, very simple. GET_LUN is basically just a FFS instruction to find a free LUN in a static bitmask, followed by BICL to mark it allocated. FREE_LUN is a BISL to mark it free again. (I may have the sense of the free/allocated bits around the wrong way).
There are a handful of other instructions for sanity checks. There's not a lot that can go wrong!
I can't see how a problem in LIBRTL could be fixed by a Basic compiler update. Remember that all RTLs belong to OpenVMS, NOT the compiler, so compiler kits don't change RTLs.
If you think it's the LIB$*_LUN routines causing trouble, try reimplementing them yourself so you can debug them. All you need to do is allocate and deallocate numbers in the range 100-119 or 100-299 if it's Alpha or I64.
That said, my usual advice with compilers is to always use the latest version. Compilers only ever get better, and the first step in diagnosing any compiler issue is to try the latest version. It's also trivially easy to retain old versions of compilers and switch between them any time you like (Pascal does this for you automatically, I'm not sure about Basic).
Since compilers are really just user mode text processors, any user can break open a compiler kit, copy the compiler image to their local directory, define a logical name, and use a different compiler version without having to install it.
If none of that helps, please post the stack dump for the FATINTERR.
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2009 06:57 PM
тАО06-15-2009 06:57 PM
Re: Seeking basic015.release_notes and basic014.release_notes
Have a read of...
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=936094
as that thread looks similar...
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=936094
as that thread looks similar...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2009 01:44 AM
тАО06-16-2009 01:44 AM
Re: Seeking basic015.release_notes and basic014.release_notes
Art,
running the reproducer from John Gillings response in the previous posting, I can see that the fix seems to have appeared in a newer version of DEC$BASRTL.EXE.
Under VMS V7.3-2 this version of BASRTL generates the OTS-F-FATINTERR messages:
image name: "DEC$BASRTL"
image file identification: "V01-026"
image file build identification: "X9ZK-0060100000"
link date/time: 1-OCT-2003 21:18:27.41
linker identification: "A11-50"
Under VMS V7.3-2 with a BASIC V1.7 compiler the BASRTL is reported as
image name: "DEC$BASRTL"
image file identification: "V01-034"
image file build identification: "XBPL-BL1-000000"
link date/time: 30-AUG-2007 11:19:08.54
linker identification: "A13-03"
and the reproducer runs without errors.
I do not have the 015 or 016 kits available to check out their version of DEC$BASRTL.
Duncan
running the reproducer from John Gillings response in the previous posting, I can see that the fix seems to have appeared in a newer version of DEC$BASRTL.EXE.
Under VMS V7.3-2 this version of BASRTL generates the OTS-F-FATINTERR messages:
image name: "DEC$BASRTL"
image file identification: "V01-026"
image file build identification: "X9ZK-0060100000"
link date/time: 1-OCT-2003 21:18:27.41
linker identification: "A11-50"
Under VMS V7.3-2 with a BASIC V1.7 compiler the BASRTL is reported as
image name: "DEC$BASRTL"
image file identification: "V01-034"
image file build identification: "XBPL-BL1-000000"
link date/time: 30-AUG-2007 11:19:08.54
linker identification: "A13-03"
and the reproducer runs without errors.
I do not have the 015 or 016 kits available to check out their version of DEC$BASRTL.
Duncan
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