Provide a mechanism to stop ADAPS batch procedures or functions cleanly
Provide a mechanism to stop ADAPS batch procedures or functions. A stop file is created in the ADAPSTABLES directory for the specified procedure or function(s). Each procedure or function will check for the existence of a specific stop file in ADAPSTABLES. When the stop file exists, the procedure will stop at the next convenient time (see User Notes).
- DRIVE(--)
- Tape drive. The tape drive that AVHRRSTACK is currently using. Only the AVHRRSTACK that has DRIVE allocated will be stopped when more than one version of AVHRRSTACK is running. The default will create a stop file for all drives that AVHRRSTACK has allocated. This is determined by looking for the AVHRRSTACK lock files in ADAPSTABLES.
- FUNCNAM(ALL)
- Function name. The ADAPS orbital stitching function(s) to stop. The default is to stop all ADAPS orbital stitching functions. A complete list of functions can be obtained by doing a 'more' on the file $ADAPSTABLES/adapstop.ppf or by running GETPARM on this file with the appropriate parameters.
- FUNCNAM(ALL)
- Function name. The ADAPS processing function(s) to stop. The default is to stop all ADAPS functions except AVHRRSTACK. Use the -STACK subcommand to stop the stacking of images to tape, or the -ALL subcommand to stop all batch processes. A complete list of functions can be obtained by doing a 'more' on the file $ADAPSTABLES/adapstop.ppf or by running GETPARM on this file with the appropriate parameters.
A stop file for the AVHRRSTACK procedure will be created in the ADAPSTABLES directory. It will signal the AVHRRSTACK procedure using the remote drive sg2@2 to stop processing at the next convenient time.
A stop file for each of the orbital stitching functions will be created in the ADAPSTABLES directory. They will signal each of the functions to stop at the next convenient time.
A stop file for the BWTRANS function will be created in the ADAPSTABLES directory. It will signal BWTRANS to stop at the next convenient time.
A stop file for each procedure and function is created in the ADAPSTABLES directory. Each stop file will signal the appropriate procedure or function to stop at the next convenient time.
A stop file is created for each of the specified functions in the ADAPSTABLES directory. The stop file name is created from the function name with an extension of ";stop". The exception to this is AVHRRSTACK which appends _DRIVE to the function name (ie avhrrstack_sg2@s;stop, bwtrans;stop, ...) The stop file is a TAE parameter file that contains the stop file name and the name of the function that is to be stopped. The parameters in the stop file are used to check the status of the function in the batch queues. After all the stop files have been created, the batch queues are checked to determine if the specified functions are running. This is done by using the stop file (TAE parameter file) as input to the queue checking function. The queue checking function will search the output from the function "qstat" (SGI only) for the name of the function to stop. The script queuestat.csh is used to access the qstat function to search all the batch queues. If the function name is not found, the function has been stopped or is not currently running so the stop file is removed. When the function name is found, the function has not been stopped yet. ADAPSTOP continues to the next stop file and checks the batch queues for it. This process continues until all specified functions are stopped and the stop files removed.
A nonfatal error was encountered during processing. The message that is displayed immediately preceding this error message is the specific error that was encountered.
The "qstat" function is used to monitor the batch queues to determine when a function has been stopped. This function is only supported on SGI systems. The specified stop files were created in the ADAPSTABLES directory. The user should manually monitor the functions and remove the stop files from ADAPSTABLES when they have completed.
This message will be displayed once after the qstat function has checked for the specified function(s) in the batch queues fifty times. After 75 times this error message will be displayed each time through the checking loop. The user may want to check the batch queues manually to determine if the specified function(s) have been stopped or if the function name matches some string from the output of qstat.
A fatal error was encountered. The message that is displayed preceding this message is the error that was encountered.