That will tell you if a particular variable contains a file pointer, which may be useful if you always use the same name for a file everywhere that it is used, but it doesn't help if you use different names. For example, if you had a program that took two file names as command line arguments and did some sort of processing from one to the other. The variables in your program that you open the files into have no name-relationship to the files being used, but you might want to take advantage of an existing file pointer in COMMON.
I don't have any idea at this point how much overhead is involved in opening a file in universe and unidata. I mentioned before that universe used to have a technical bulletin about it, because file opens were very time consuming, but that was back around release #6. It might not be worth the trouble to reuse file variables anymore. Or instead of speed being the issue, you might be trying to pool to get around limitations on the number of open files per process--but I think that is handled internally by the database. On Mar 5, 2012, at 3:40 PM, David Jordan wrote: > I set up a function to open files. Instead of using the open file command > in a program, I call the function. The function first calls the fileinfo > command to see if the file is open and then returns otherwise it opens the > file and returns. > > David Jordan > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
