Queueing a Batch

Look at the files in your directory.  The date of the .com file and the date of the .log would normally be the same.

$ dir/date

CALCULATE.COM;2       9-AUG-2005 15:03:31.57
CALCULATE.LOG;35     10-AUG-2005 09:34:00.78
INIT.COM;1           14-JUL-2005 14:50:46.75
INIT.LOG;13          11-AUG-2005 08:50:46.65
MONREP.COM;1          9-AUG-2005 08:52:38.94
MONREP.LOG;2          9-AUG-2005 08:49:49.99
POST.COM;1           15-JUN-2005 10:14:04.35
POST.LOG;11          10-AUG-2005 09:40:30.36  (the running of POST on this date would have executed using the latest version of .com in your directory, i.e., the one dated 15-JUN.)
PREPAY.COM;1          9-AUG-2005 13:16:30.04
PREPAY.LOG;26        10-AUG-2005 09:32:55.37

Normal order of creation, execution of batch files.

  1. The batch file (.bcf) is written in order  to group multiple commands so that we don’t have to execute the individual commands to perform the entire scope of work needed.  Anybody can write a batch file (see DMS Ref Manual, Vol. 1).   .bcf files normally reside in the [.exe] directory, or the [exe.site] directory.  
    To see all of the ones created for PAY, $dir users2:[pay.exe]*.bcf or $dir users2:[pay.exe.site]*.bcf.
  2. The batch file is placed on the menu so that we can “que it up,” which means place it in line for execution on a particular batch que processor.  Each user has a default que for batches and a default que for printing, but all users are authorized to que to any device on the system. 
    If you want to see all queues:  $sho que/full/all.  
    If you only want to filter the view:  $show que/full/all pay$batch, or $show que/full/all pay* (extensive use of * for wildcard is available throughout).
  3. The menu option is selected to run a batch.  The system uses the .bcf file to create a .com for execution.  If you want to take advantage of any changes made to the .bcf since the last running, you need to tell the system to create a new version of the .com file.

Here are the usual system prompts when calling up a batch to run:

Output Batch Filename <SYS$SYSDEVICE:[ADM_FLOY]ADMHISCHOOL>?  (the system names the .com file after the batch filename)

File SYS$SYSDEVICE:[ADM_FLOY]ADMHISCHOOL.COM; exists.  (it alerts you that a file already exists with that filename)

Create a new version <NO>? y   (99.99% of the time, you will respond YES)

Save SYS$SYSDEVICE:[ADM_FLOY]ADMHISCHOOL.COM; after execution <NO>? (most of the time you’ll respond NO, but if you are expecting the batch to recur at a specific time interval, say once a week or once a day, you would want the .com file to be saved)

Allow batch log to be queued <NO>?  (99.99% of the time you do not want the .log file to be queued to a print device)

 

You can get more information on various system functions in DMS Reference Manual, Vols I and II,

To POISE Home Page