{   The purpose of this request is to control the subsequent flushing of
{ catalogs within the requesting job.
{
{       FSP$CHANGE_CATALOG_FLUSH_OPTION (FLUSH_CATALOGS, STATUS)
{
{ FLUSH_CATALOGS: (input)  This parameter specifies whether or not pages of a
{       modified catalog are to be written out after the catalog is updated.
{
{       If TRUE is specified, modified catalog pages are forced to mass storage
{       immediately after the catalog transaction is completed; however, the
{       task that requested the catalog update is given control back before the
{       catalog I/O completes.  If the catalog is again referenced before the
{       I/O completes, the new accessor waits for any pages that are being
{       written out, if those pages are referenced by the new accessor.
{
{       If FALSE is specified, modified catalog pages are not forced to mass
{       storage immediately after the catalog transaction is completed.
{       Catalog pages are kept in the SHARED_DEVICE_FILE queue.  The duration
{       of time that modified catalog pages will remain in memory is tunable.
{
{       It is recommended that a site select TRUE for catalog flushing.
{       However, if the site has an Uninterruptable Power Supply (UPS), catalog
{       flushing may be turned off at the site's discretion, if the performance
{       of catalog access is a problem.  If a site turns off catalog flushing,
{       the value of the MINIMUM_SIZE attribute of the SHARED_DEVICE_FILE queue
{       should be set to 0 (the default) to ensure that all modified catalog
{       pages are ultimately recorded on mass storage.
{
{       If an application makes repetitive updates to the same catalog,
{       performance may be improved by turning off catalog flushing prior to
{       beginning the sequence of updates.  Once the update sequence is
{       completed, it is strongly recommended that the catalog be flushed using
{       FSP$FLUSH_CATALOG.  If a catalog becomes inconsistent on mass storage
{       and NOS/VE's memory image is lost, an entire catalog subtree may become
{       lost or inaccessible.
{
{ Status: (output)  This parameter specifies the request status.
{
