HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Exception handler for EDT$EDIT VMS-routine
Operating System - OpenVMS
1827707
Members
2785
Online
109967
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
Forums
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
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
07-30-2004 08:53 AM
4 REPLIES 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 09:14 AM
07-31-2004 09:14 AM
Re: Exception handler for EDT$EDIT VMS-routine
Hello Vladimir,
I do not understand your question really.
Building and running your example program, one
gets an image that invokes edt to edit a file.
As per your description I've set this file to no access to the owner. Again invoking the
program the following error message is
generated
$ run temp
Ret - edit file XXX.YYY, ^Y - exit program:
%EDT-F-OPENIN, error opening US$ROOT:[EURMPZ]XXX.YYY; as input
-RMS-E-PRV, insufficient privilege or file protection violation
Ret - edit file XXX.YYY, ^Y - exit program:
That is IMHO expected behaviour, since the file is protected against write. So, can you please explain which behaviour you do want to achieve?
Greetings, Martin
P.S. For other forum members, you do need an
un-prived process to see this ;-)
I do not understand your question really.
Building and running your example program, one
gets an image that invokes edt to edit a file.
As per your description I've set this file to no access to the owner. Again invoking the
program the following error message is
generated
$ run temp
Ret - edit file XXX.YYY, ^Y - exit program:
%EDT-F-OPENIN, error opening US$ROOT:[EURMPZ]XXX.YYY; as input
-RMS-E-PRV, insufficient privilege or file protection violation
Ret - edit file XXX.YYY, ^Y - exit program:
That is IMHO expected behaviour, since the file is protected against write. So, can you please explain which behaviour you do want to achieve?
Greetings, Martin
P.S. For other forum members, you do need an
un-prived process to see this ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 09:40 AM
07-31-2004 09:40 AM
Re: Exception handler for EDT$EDIT VMS-routine
Thank you for your reply, Martin!
If you run test and press Ret more then
once you see error message only once.
Greetings, Vladimir
If you run test and press Ret more then
once you see error message only once.
Greetings, Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 03:39 PM
07-31-2004 03:39 PM
Solution
Vladimir,
There's nothing "wrong" with your code.
Modify your program to capture the return status from EDT$EDIT and you'll see that on second and subsequent invokations, it's returning (decimal) 8749116.
This is a limitation of the EDT$EDIT routine. If the routine ever terminates with a severity E or F error, all subsequent attempts to invoke the routine will fail with status
%EDT-F-REENTRY, attempt to re-enter EDT
The EDT editor was made obselete with the release of TPU circa 1984 (20 years ago!). EDT has many restrictions and limitations, all of which are resolved by using a more modern editor.
Your specific issue was formally reported to OpenVMS engineering in 1990. The response was:
"SOLUTION:
OpenVMS engineering is no longer considering corrections to problems reported on EDT unless the problem is a regression from the release previous to the current shipping version of OpenVMS. Our current fully supported editor is TPU, which is the default editor for OpenVMS. EDT will continue to ship with OpenVMS to provide this editor, in its current working form, to those customers who prefer to use it.
WORKAROUND:
If possible, use another callable editor such as TPU or LSE.
"
Sorry!
Please modify your code to call TPU instead.
There's nothing "wrong" with your code.
Modify your program to capture the return status from EDT$EDIT and you'll see that on second and subsequent invokations, it's returning (decimal) 8749116.
This is a limitation of the EDT$EDIT routine. If the routine ever terminates with a severity E or F error, all subsequent attempts to invoke the routine will fail with status
%EDT-F-REENTRY, attempt to re-enter EDT
The EDT editor was made obselete with the release of TPU circa 1984 (20 years ago!). EDT has many restrictions and limitations, all of which are resolved by using a more modern editor.
Your specific issue was formally reported to OpenVMS engineering in 1990. The response was:
"SOLUTION:
OpenVMS engineering is no longer considering corrections to problems reported on EDT unless the problem is a regression from the release previous to the current shipping version of OpenVMS. Our current fully supported editor is TPU, which is the default editor for OpenVMS. EDT will continue to ship with OpenVMS to provide this editor, in its current working form, to those customers who prefer to use it.
WORKAROUND:
If possible, use another callable editor such as TPU or LSE.
"
Sorry!
Please modify your code to call TPU instead.
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2004 12:18 AM
08-01-2004 12:18 AM
Re: Exception handler for EDT$EDIT VMS-routine
Thank you for your reply, John!
As I wrote in a comment to XXX.C it's
only a little fragment of a more big
program which I developed in 1991. Now I
have a lot of free time and want to
redesign my program and use in it a
more simple then TPU but fully functional editor by means of only ONE CALL. Hence, in accordance to your reply, if I want to
continue using EDT$EDIT I must trace EDTSHR code "on-the-fly" (as I wrote in a comment to XXX.C)... Or develop my own editor by
means of TPU (it will be possible in the
future).
Best regards,
Vladimir
As I wrote in a comment to XXX.C it's
only a little fragment of a more big
program which I developed in 1991. Now I
have a lot of free time and want to
redesign my program and use in it a
more simple then TPU but fully functional editor by means of only ONE CALL. Hence, in accordance to your reply, if I want to
continue using EDT$EDIT I must trace EDTSHR code "on-the-fly" (as I wrote in a comment to XXX.C)... Or develop my own editor by
means of TPU (it will be possible in the
future).
Best regards,
Vladimir
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP