Problems with open-Statement

[rossow74atfsg]

Hi,

we have got a problem concerning the open-Statement.
For historical reasons we have got an "ownopen" which is called several times.
The keywords have to be set like this:
call ownopen_setstatus("old")

In the ownopen-routine we have got an open like this.
open(unit=unit, file=filename, access=access, form=form, status=status,......)
For the keywords that are not set we want to use the default.
We call an init in which we set the normal defaults but
the problem is that there are some keywordchanges that depend defaultchanges on other values.

is there any possibility to do something like this:
open(unit=unit, file=filename, access=default, form=default, status=status,....)

Please don't tell me to use the open-Statement instead of the ownopen.
We have more than 1000 ownopens.

Thank you in advance
H. Sommer

[Steven_L_Intel1]

Sorry, there is no support for such a thing. I can think of some alternatives:

- If there aren't too many comnbinations of omittable values, have a series of OPEN statements and select at run time which one to use that has the proper keywords omitted

- Add your own default value code to try to match what OPEN woild do