AD) Details concerning the DESL
cleanup command.During a typical DESL session, as the result of execution of one or more functions, numerous data files files can be created. All of these files will be marked, either explicitly or implicitly at their creation, as files "to be RETAINED" or files "to PURGE" at the next "cleanup" execution. Execution of "cleanup" can eliminate the files whose fate is "to PURGE at cleanup". This function provides the capability to control the number of created data files which might otherwise be "left over" at the end of a DESL session. Also, the use of the "xfiles" option and argument list will eliminate ANY type file from the current directory.
Any names enclosed in brackets are required or are in a set of options, one of which must be specified. Any non-blinking names enclosed in brackets are optional or are in a set of options, only one of which can be specified.
In cases where the option name is one of a set each different set number is indicated by a red numeric set number superscript trailing the respectiveright bracket :
ADfiles)
(Command :cleanup) Details for the files option.This list of files can be implicitly extended via use of the "<list" argument which can appear among the specified file names. If one or more of the "<list"-type arguments are specified, where "list" is a currently defined file name list, the file names contained in the indicated file name list(s) will be included, at their respective point(s) of encounter, in the current file list. The referenced list(s) must have been produced by the "newfiles" and/or "newfilex" argument lists associated with one or more previously executed DESL commands. Each "list" name can be up to 15 characters long. Up to 200 files can be explicitly or implicitly specified. File names can also include the {...} construct. This type specification within a file name implies that the list name given between the curly brackets ( {} ), is to be used to have each of its elements substituted in turn for the { ... }, inclusively, such that an implicit lengthening of the file list is accomplished, up to the maximum number of files allowed. Any time such a {...} usage occurs, all lists mentioned must exist; i.e., must have been previously defined in the current DESL session. Only one {...} construct can be included in a file name. Including more than one such construct will result in unpredictable results.
An example of this type of file name specification is the following :
t43r{runs}.sif
Here, the list "runs" will have its elements used, in turn, in place of the {runs} substring.
| . |
(Begin modifications on 052102)
Each file name, whether it includes the {...} or not,
can be a maximum of 256 characters long.
However, strings longer than 16 characters must be
enclosed in the DESL-standard question mark delimiters.
(End modifications on 052102) |
Example : ... files gen1 thru gen8 <flist6 ...
ADxfiles)
(Command :cleanup) Details for the xfiles option.The asterisk wildcard character can be used in the "xfiles" file names to remove the appropriate files from the current directory.
This list of files can be implicitly extended via use of the "<list" argument which can appear among the specified file names. If one or more of the "<list"-type arguments are specified, where "list" is a currently defined file name list, the file names contained in the indicated file name list(s) will be included, at their respective point(s) of encounter, in the current file list. The referenced list(s) must have been produced by the "newfiles" and/or "newfilex" argument lists associated with one or more previously executed DESL commands. Each "list" name can be up to 15 characters long. File names can also include the {...} construct. This type specification within a file name implies that the list name given between the curly brackets ( {} ), is to be used to have each of its elements substituted in turn for the { ... }, inclusively, such that an implicit lengthening of the file list is accomplished, up to the maximum number of files allowed. Any time such a {...} usage occurs, all lists mentioned must exist; i.e., must have been previously defined in the current DESL session. Only one {...} construct can be included in a file name. Including more than one such construct will result in unpredictable results.
An example of this type of file name specification is the following :
t43r{runs}.sif
Here, the list "runs" will have its elements used, in turn, in place of the {runs} substring.
| . |
(Begin modifications on 052102)
Each file name, whether it includes the {...} or not,
can be a maximum of 256 characters long.
However, strings longer than 16 characters must be
enclosed in the DESL-standard question mark delimiters.
(End modifications on 052102) |
Up to 200 files can be explicitly or implicitly specified.
Example : ... xfiles gen1 thru gen6 r10 <xflis r29 ...
DESL Manager at ViGYAN, Inc.
30 Research Drive
Hampton, VA 23666
Voice: (757) 865-1400
Toll Free: (800) 288-3998
FAX: (757) 865-8177
