The BATCH MARKERS purpose is to update SPIKE CV-DESC files at the end of the work day
to account for changes in proposals made during the work day.  The markers process
is actually a group of processes which are farmed out to a number of different
OPS machines in order to reduce processing time.  Processing time is also saved 
in that this update does not occur during the BATCH LRP.

The batch markers is run as a crontab from a single machine (currently ringworld), and it
starts up the individual markers subprocesses on separate machines.




The schedulability call to batch markers may be found in:

	/data/software/code/operational/spike/hst/scheduler/utilities/marker-processing.lisp

And relevant sections of it appear as follows:



(defun RUN-ACF-MARKERS  (&key name (trap-errors t) (redo-errors t) (delete-result-file nil)
                             (interactive-mode t)
                             (populate-status t)
                             (markerdir nil)
                             (verify-window-type "spike_cw")
                             (update-vcw-within-hours 24))





              (unless (sys:getenv "PCTOOLS_CODE_DIR")
                (print "ERROR in marker-processing.lisp: PCTOOLS_CODE_DIR environment variable not defined.")
                (excl:exit))
              (excl::run-shell-command 
               (format nil "~a/schedulability -noreplan -verify_windows=~a ~a" (sys:getenv "PCTOOLS_CODE_DIR") verify-window-type id)))
            (unwind-protect  ;;; so if user manually aborts session, marker file is deleted



So, the invocation seems to be:


	${PCTOOLS_CODE_DIR}/schedulability -noreplan -verify_windows=spike_cw <prop_id>