BA) Details concerning the DESL
hold command.At any time during a DESL session the session can be suspended via execution of the "hold" command. "hold" should at least be followed by a file name. At the time of a "hold" execution all pertinent information necessary to continue the current session at some later time is saved onto this named file. The ability to overstore a file by the same name which already exists is governed by the system "overstore" flag. If the "hold" file is actually created, the session ends via the "stopn" command. Since all SIF files which may have been created by the session being held are going to be pointed to again if the session is continued, it should be remembered that alterations to a file which will be needed by the session, if it is continued, could affect results in that continued session. If "hold" is followed by a file name AND either of the words "os" or "overstore" then the hold file WILL be created REGARDLESS of the whether it existed previously or not.
The use of the "hold" command to save an intermediate state of a DESL session should not be considered long term storage. If the DESL system changes (ie, a new version of DESL is downloaded) then the structure of the "hold" file may also change, possibly rendering any files produced by "hold" during the execution of a previous DESL version invalid.
DESL Manager at ViGYAN, Inc.
30 Research Drive
Hampton, VA 23666
Voice: (757) 865-1400
Toll Free: (800) 288-3998
FAX: (757) 865-8177
