Importing OpenVMS system include file

[David_Hittner]

I am exploring porting some OpenVMS Fortran code, and am having a problem with the OpenVMS system include files.The code has an "import '($strdef)'" line in it, which means "extract the module named '($strdef)' from the system text library sys$library:forsysdef.tlb".

If I create a file in the include path named "($strdef)" with no extension containing the critical definitions that I need, the compiler can't find the file. What default file extension isthe Intel compilerlooking for, or what other magic is going on (string substitution), such that it can't find the namd include file?

[Steven_L_Intel1]

This was a little nugget I snuck into the compiler about ten years ago. If /vms is in effect, an INCLUDE specification of (name) turns into 'name'. The file type can be .f90, .for or, I think, .f In your case, it will look for $strdef.f90 or .for or .f.

The intent was to ease porting of VMS programs that used text libraries. At the time, there were two vendors of VMS-compatibility libraries which provided the various system-defined text modules such as $strdef. You probably don't have such a library and will need to replace use of the STR$ routines with calls to library routines provided on Windows.