| get_lun returns LUN already in use [message #29405] |
Fri, 15 February 2002 09:15 |
george.mccabe
Messages: 10
Registered: October 2001
|
Junior Member |
|
|
hello,
i would like to apologize for submitting my post before researching
theis problem more thoroughly. i see that there has already been much
discussion on the subject of get_lun. also, where a LUN is allocated
is inconsequential to
a get_lun procedure dumb to file units allocated by another method.
thank you for your patience,
george
|
|
|
|
| Re: get_lun returns LUN already in use [message #29408 is a reply to message #29405] |
Fri, 15 February 2002 08:35  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
George McCabe (george.mccabe@gsfc.nasa.gov) writes:
> a unexpected thing happens when a logical file unit is allocated in
> the setup batch procedure execeuted when idl session is started. the
> first use of get_lun at the IDL prompt returns the unit already in
> use.
>
>
> ; LUN 100 is in use...
>
> IDL> help,/files
> Unit Attributes Name
> 100 Read, Write, New /tmp/idl-8391185
>
> ; but get_lun returns unit 100?
>
> IDL> get_lun,fu
> IDL> print,fu
> 100
>
>
> this is not 'right'.
Seems to be working correct on IDL 5.5 and Windows:
IDL Version 5.5, Microsoft Windows (Win32 x86).
IDL> help, /files
Unit Attributes Name
100 Read, Write, New, Reserved c:\temp\junk.dat
IDL> get_lun, fu & print, fu
101
I do notice that mine says "Reserved" and yours doesn't.
I don't know what that means. I opened the file for writing
(OPENW). What did you do?
Cheers,
David
--
David W. Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
