Conference iosg::all-in-1_v30

	OA$CABFIFOS is not new; it has always existed throughout V2.x.  The
purpose of OA$CABFIFOS is to define those folder names which will store entries
in First-In/First-Out order, as opposed to the default ordering of Last-In/
First-Out (LIFO).  This is done by using the alternate fields DOCNUM and REFNUM,
which are 9's complements of each other, and putting the appropriate value into
a field called FIXER.

	The difference in V3.0 is that the names of the included folders are
now stored in a list, rather than being directly coded into the DSAB definition
in OAGBL.BLI as literals.  This list is defined by a BLISS variable called
OA$GA_FIFO_LIST.  The list, however, is now created in a .MAR file.  The reason
for this is that any modifications to OAGBL.BLI required the use of a BLISS
compiler.  The more information that can be extracted from OAGBL.BLI and put
into Macro files, the easier it is to customize on-site.

	Anyway, the new Macro file is called OAFIFO_LIST.MAR.  If you look at
it, you will find that it basically defines the table that is referenced from
OAGBL.BLI -- the list named OA$GA_FIFO_LIST.  There are enough comments within
the code, as well as diagrams, to make any modifications intuitively obvious.
(I.e., read the comments, especially at the end of the module.)

	F

    The File Cab Server also needs to need to know about any changes to the
    FIFO list and it has its own table to update. Be sure to do both
    activities in sync.
    
    Cheers
    
    Stuart

    Re .2
    
    Where are the FCS ones defined?
    
    Graham (too lazy to walk 30 yards and ask!)

    In file oa$data:system_folders.dat. The FCS team supplied a utility
    program to update it called OAFC$SYSFOLD_SEED.
    
    Cheers
    
    Stuart