LIST 2.3

The LIST utility is used to maintain names with usernames as well as phone
numbers and work group.  Users are able to modify their own information
without being able to modify anyone else's information.


************************************************************************

Modifications since 2.2:

1)  (new)  Provide Disuser status when using the /FULL qualifier
    (suggested by Sheila Franklin - Naval Surface Warfare Center DD)

2)  (mod)  Make /FULL output easier to read.

3)  (mod)  Make error messages referencing insufficient privileges
    boring and mundane because some users lack any sense of humor and
    have the inability to have any fun.
    (suggested by my supervisor (who has a sense of humor), after a 
    high school only educated librarian from a backwards county (not
    country) was confused and didn't like the error messaging).

4)  (new)  Add /BORING qualifier to allow system managers that use
    this utility the ability to choose my error messaging or the
    boring "lets not perk up your day and you are not allowed to
    even smile" type of messages.  (It is my only form of rebelling
    against modification number 3).

5)  ** modified to work for axp systems.

6)  (new)  Add /ACCOUNT_FIELD qualifier to allow system manager to choose
    which field to use from SYSUAF.DAT as the group.  The default is the
    OWNER field, this qualifier will use ACCOUNT field.

7)  (new)  Add a plan capability like UN*X finger.  :-(  (the frown is
    for that nasty four letter word that starts with U.)

8)  (new)  Add routine that prevents control characters in plan display
    except horizontal tab and null characters.

9)  (fix)  Problem with output overflow resolved.

10) (fix)  Consider empty plan files.


************************************************************************

Testing:

    Tested to VMS VAX 6.0, VMS AXP 1.5  and FORTRAN 6.1


************************************************************************

Related files:

The LIST UTILITY is comprised of the following files:

     AAAREADME.1ST   --  This document
     BUILD_LIST.COM  --  Compile and link executables
     LIST.BOOK       --  Example phone listing (indexed file)
     LIST.CLD        --  LIST command deffinition file
     LIST.EXE        --  LIST executable
     LIST.EXE_ALPHA  --  AXP ready executable
     LIST.FDL        --  File Definition Language file for
                         upgrading LISTING files from pre 2.2
                         LIST
     LIST.FOR        --  LIST source
     LIST.HLP        --  LIST help file
     LIST.OBJ        --  LIST object
     LIST.OBJ_ALPHA  --  AXP ready object
     LIST.OPT        --  LIST options file

************************************************************************

To use:

1)  Install LIST with SYSPRV.  READALL if you are using the plan capability.
    Or you may have users provide access for their plan files through the
    SYSTEM protection field and Access Control Lists (ACLs).  This second
    method can be very messy for ACLs and is not recommended.  You may choose 
    other install options at your own discretion.

2)  Modify LIST.CLD and set up image path as well as choose a default
    file for the /LISTING qaulifier (phone.book is an example file).
    If the file does not exist, it will be created if you have SYSPRV
    turned on.  Also choose if /BORING is to be a default qualifier
    for the mundane error messages referencing insufficient privileges.
    /BORING is not generally a default qualifier.

3)  Choose whether OWNER field (default) or ACCOUNT field (set the qualifier
    ACCOUNT_FIELD in LIST.CLD as default) is to be used for the group.

4)  Insert the command into DCLTABLES.EXE and replace the DCLTABLES in the 
    install database, or SET COMMAND LIST to activate.

5)  Insert the help file into the HELP library.

6)  To convert pre 2.2 LIST listing files, use the following command:

       $ CONVERT/FDL=LIST.FDL    listing.file     listing.file

    (This only needs to be done for LIST files created with LIST versions
    2.1 or earlier, but should not harm later versions.)

7)  If you do not have any previous LIST files, or would rather start 
    fresh, type:

                  $ LIST /LISTING=file.name *

    to create a new listing file.  This can also be done to create multiple
    LIST files.  You may also put the above file.name into the .CLD file
    as your default listing file.  If you do this, remember to redo steps
    2 and 4.

8)  Make sure the protection on LIST.EXE has world read execute and all 
    other files do not allow access to world (even listing files).

9)  Set the logical LIST$PLAN_LENGTH in the SYSTEM logical table.  This
    logical tells how many lines to read from a users LIST.PLAN; file.  
    If not set, a default value of 4 is used.  If a value of 0 is used, the
    plan capability is disabled.  Values from 0 thru 99 are valid.

10) If you need help or I haven't made this stuff clear for you, call and
    I'll try to explain.


************************************************************************

Problems, Questions & Suggestions
If there are any problems or you need more information, please contact:



                      Jonathan C. Baker
                      Code N86
                      Naval Surface Weapons Center
                      Dahlgren, VA    22401
                      (703)663-8705

                      jbaker@relay.nswc.navy.mil