| DESCRIPTION | This option invokes an instrument specific routine to take a load listand prepare it for sending (downloading) to the instrument.The option first asks what instrument to work on, Then tells what loadlist will be used. There is a question asking if the job should be queued to the background. Then each cup of each tray that has beenbuilt into the load list is worked on by the instrument specificroutine to prepare it for sending. The data from this pass is savedin the load list file in node 2 of the cup entry. This means thatonly one instrument can use the load list at a time. The lab techsMUST be carefull in management of the load list for the instrument.At this time all cups that are on the load list will be sent, socare must be taken to see that only accessions that should be sentare built and that after sending the load list is unloaded andthese accessions are not built to the load list when setting up theload list for the next run. Tech notes: This is done in a two pass operation.1. This pass gets the accession and tests from the load list andbuilds records for the instrument that are stored in node 2 of thecup entry (see DD listing).2. In this pass the data from pass 1 is put together in the formthat is needed for the protocol. For the Ektachem700, LAEKT7Dbuilds the records that need to be sent, and LAKERM2 addsthe kermit file headers, record head and checksum, and file trailer.This is all controled by LADOWN along with the AUTO INSTRUMENT file.The entry points into LAKERM2 or other protocol routines havefixed names: START^LAxxx is called once before the first data call.NEXT^LAxxx is called once for each tray before the cup data is started. (with the ektachem each tray is a file.)DATA^LAxxx (both parts from the file) is called for each recordfound in the load list.END^LAxxx is called once at the end to close out the file. |