Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!agate!violet.berkeley.edu!jerry
From: jerry@violet.berkeley.edu ( Jerry Berkman )
Newsgroups: comp.lang.fortran
Subject: Re: F8X response (long)
Message-ID: <7211@agate.BERKELEY.EDU>
Date: 26 Feb 88 19:47:15 GMT
References: <705@elxsi.UUCP> <44400017@hcx2> <2337@s.cc.purdue.edu>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: jerry@violet.berkeley.edu.UUCP ( Jerry Berkman )
Organization: University of California, Berkeley
Lines: 33

In article <2337@s.cc.purdue.edu> ags@s.cc.purdue.edu.UUCP (Dave Seaman) writes:
>... consider IBM's VM/CMS
>and their current FORTVS2 compiler.  In that environment you cannot open
>files by name at all, in any way that I know of.  You can open files only
>by "ddname", which means that you must remember to issue a "filedef" to
>tell the system what ddname to assign to the file before you execute the
>program.  It is not possible to issue filedefs from within an executing
>program in any way that I know of, and even if there is a way, this only
>means that VM is no worse than VSOS when it comes to opening files.
>
>Dave Seaman
>-- 
>Dave Seaman	  					
>ags@j.cc.purdue.edu

You can open files by name from within a program using the UOPEN
subroutine in IBM's VM Fortran Utility Library (Program Number:
5798-DFH).  This is non-standard, and a hassle, but it is possible.

I believe I saw a notice that this problem will be alleviated in
in VS FORTRAN Level 2.2.1 which is to be released soon.  I hope this
is the case and means CMS file identifiers will be allowed in
Fortran OPEN statements; but I do not know.

The comparison to CDCs VSOS is not valid.  CMS users run in their own
permanent files, but the Fortran OPEN can not refer to a general CMS name.
In the CDC case, from what I read, the OPEN can reference all attached files,
but jobs are not run in an environment with permanent user files defined.

Jerry Berkman
U.C. Berkeley, Central Computing Services
jerry@violet.berkeley.edu (Internet)
jerry at ucbviole  (Bitnet)
(415)642-4804