topic Re: Exception handler for EDT$EDIT VMS-routine in Operating System - OpenVMS

Exception handler for EDT$EDIT VMS-routine

Vladimir K. Vershinin — Fri, 30 Jul 2004 15:53:16 GMT

See C source in attachment.

Re: Exception handler for EDT$EDIT VMS-routine

Martin P.J. Zinser — Sat, 31 Jul 2004 16:14:09 GMT

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 ;-)

Re: Exception handler for EDT$EDIT VMS-routine

Vladimir K. Vershinin — Sat, 31 Jul 2004 16:40:02 GMT

Thank you for your reply, Martin!

If you run test and press Ret more then
once you see error message only once.

Greetings, Vladimir

Re: Exception handler for EDT$EDIT VMS-routine

John Gillings — Sat, 31 Jul 2004 22:39:25 GMT

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.

Re: Exception handler for EDT$EDIT VMS-routine

Vladimir K. Vershinin — Sun, 01 Aug 2004 07:18:41 GMT

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