| Re: Active FIDs? [message #66306] |
Sun, 03 May 2009 19:42 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Jonathan Greenberg writes:
> I'm getting the following error in some code I've written: CLOSE: File
> unit is not within allowed range: 133. I'm guessing I'm forgetting a
> FREE_LUN someplace, but is there a programmatic way to check to see
> what FIDs (acquired initially via openr,..,/GET_LUN) are currently
> "open"?
If you are opening the file with GET_LUN, either as
a keyword or as the procedure, there is no need to use
CLOSE. FREE_LUN will both close the logical unit number
and free it up to be used over again.
Help, /FILES will tell you which files you currently have
open and attached to a logical unit number.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Active FIDs? [message #66308 is a reply to message #66306] |
Sun, 03 May 2009 17:30  |
mankoff
Messages: 131
Registered: March 2004
|
Senior Member |
|
|
On May 3, 7:34 pm, Jonathan Greenberg <jgrn...@gmail.com> wrote:
> I'm getting the following error in some code I've written: CLOSE: File
> unit is not within allowed range: 133. I'm guessing I'm forgetting a
> FREE_LUN someplace, but is there a programmatic way to check to see
> what FIDs (acquired initially via openr,..,/GET_LUN) are currently
> "open"?
help, /files
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
