Note:      The following was distributed to the MDI team and the SPWG mailing list.
Correction: Also, large files will still need to be submitted outside of DSN contact.
            (Can also read as -- large command files can be submitted during DSN
             contact IF and ONLY if NOBODY is commanding!)

To:	  MDI Team
From:	  Laura Allen, SoHO SOC
Date:	  April 11, 1997
Subject:  Background Queue Commanding 

Just to let you know, both Command Management Systems (CMS) are running a new
version of software (Release 5) which contains the changes to the
background queue command processing requested by the instrument teams and SOCs.

The software will enable an instrument team to submit a background queue
file that contains a large number of commands (up to 8000 commands) which
will be validated, and then broken down into smaller sub-files (containing
a maximum of 8 commands each) for uplink.

In operational testing, a large file containing 8000 full OBDH block commands
was sent from the CMS to the ECS.  It took roughly ~ 20 minutes to 
validate the large file and receive a single validation report at the ECS.
Subsequently, it takes a little less than 1 hour to break the large file
down into smaller files containing 8 commands each for uplink.
Large files will still need to be submitted outside of DSN contact.

For reference, the new naming conventions for background queue files (as 
detailed in Eliane Larduinat's memo in 1996) is appended for reference.

---------
To:      Instrument Teams
From:    Eliane Larduinat
Date:    September 04, 1996
Subject: Modification to the File Naming Convention for the 
          Background_Queue Commands.


The CMS maintenance team has brought to my attention that we
need to make a minor modification to the current file naming
convention for the background-queue files.

Currently, the instrument teams use the following convention:
   iiixxxxxxxxx.BCK where 
     iii (3 characters) represents the instrument and 
     xxxxxxxxx (9 characters maximum) uniquely identifies the file.  

With the new CMS implementation, where a single file will
be uplinked in small chunks generated by CMS, the file naming
convention needs to be:
   iiixxxxx.BCK where 
     iii (3 characters) represents the instrument and 
     xxxxx (5 characters maximum) uniquely identifies the file.  
This will allow CMS to use the 4 remaining characters to uniquely
identify each chunk being uplinked.


EXAMPLE:

GOL0001_0000.BCK  to GOL0001_0999 containg 8 OBDH blocks each
 
could be replaced by

GOL0001.BCK containg 8000 OBDH Blocks.