I would just like to echo Elbert E Silbaugh's comments about the LISTF,access
proposal.
 
1)  An intrinsic could provide the means to get what ever data is desired,
    in a format most suitable for the application.  This neither denies the
    benefit provided by third parties like VESOFT, nor demands an
    unsatisfactory parsing excercise.  The HP3000 should not need to become
    AWK-ward! :)
 
2)  If a CI command is still desirable, then provide two -
    a basic one line/accessor abbreviated version and a full, whole
    kit'n'caboodle, verbose version.
 
    In considering the former, I can recall only two situations that occur
    where I need this information:  a) I'm trying to *eliminate* all accessors
    to a file; or b) I'm trying to get another program to concurrently access
    a file used by others.
 
    For the first situation I need information to uniquely identify the user -
    a session number, pin number, and possibly the connection device.  After
    all, I would prefer to ask them to exit the program than simply abort
    them, so anything that can identify the physical user becomes helpful.
 
    In the second situation, I need to know the flags for access - SHR/EAR,
    LOCK, etc.
 
    In the case of the verbose version, having a wealth of information can
    be useful, but an overflowing gutful is just too much.  So for the
    verbose version I believe it would be desirable if this information could
    be limited not in its content but its quantity.  So I reckon you would
    need the ability limit this to a specific user, session, or pin.
 
But while we're on the subject, how about a way to do a LISTF on files in
the NEW domain?  :)
----
Jim "seMPEr" Wowchuk           Internet:    [log in to unmask]
Vanguard Computer Services     Compu$erve:  100036,106
 _--_|\                        Post:        PO Box 18, North Ryde, NSW 2113
/      \                       Phone:       +61 (2) 888-9688
\.--.__/ <---Sydney NSW        Fax:         +61 (2) 888-3056
      v      Australia