
Batch operation of SPIDER on VAX/VMS
In addition to running SPIDER in the usual interactive mode
(and preferentially for long jobs), you can utilize the
VMS batch facility to submit the SPIDER session (as specified by the
SPIDER command file) to the batch queue.
This is done by running the VMS command file
SPIDERF.COM.
This command file will allow you to create or update a SPIDER
command file and to submit the job to the batch queue. If you have
followed the usual
installation procedure
, the command $SPIDER will execute SPIDERF.COM.
Starting the SPIDER system by the command "SPIDER"
Starting the SPIDER system by the command "SPIDER"
(The symbol "SPIDER" has to be defined in your LOGIN file
SPIDER:==@disk:[directory]SPIDERF.COM )
OUTPUT: YOUR INPUT: OPERATIONS PERFORMED:
SPIDER or Run the command file
SPIDER E or SPIDER.COM ; If you
SPIDER F type in SPIDER E the
EVE Editor will be used
(=EDIT/TPU), otherwise
the EDT editor is used .
If you type in SPIDER F
the command file does not
start any editing.
PROJECT/DATA CODE: xxx/yyy according A file named xxx.yyy is
to the SPIDER rules created and the project and
data extension is written into this
file. xxx.yyy will be deleted
at the end of the job.
COMMAND FILE NAME: Bdd , where dd is Bdd is written into the file
a two-digit number xxx.yyy and another file named
Bdd.xxx is opened by the
editor. (EDT or EVE editor,
depending on what you typed
in. SPIDER or SPIDER E )
EDIT: Now you can edit
the command file.
Do changes or type
in the command string
if the file did not
exist before. Exit the
Editor.
QUALIFIERS: Type in qualifiers A batch job will be generated
as described for the with the name given by /NAME.
DCL command SUBMIT. Default is SPIDERF.
e.g. /NAME=......
/QUEUE=......
/AFTER=.....
PRINT OUTPUT ? (YES OR NO):
YES The output file named ....LOG
accoding to /NAME= will be
printed on the line printer.
NO The file ....LOG will be cre-
ated in your main directory
and not printed on the line
printer.
Mail (Y/N) N Lets you specify if you want to
get a mail message when your job
is finished.
RESULTS AND DATA WILL BE WRITTEN IN DIRECTORY
default directory
The same information is written
in the ....LOG file. is the directory from
where you start SPIDER.
Job number .... entered in.....
Spider batch job started
Notes:
The questions originating from the command file do not need to be answered
line by line. For example, the shortes way to submit a batch job running
SPIDER is:
SPIDER F PRJ/DAT B01
Qualifiers: (if you want to use all the defaults
of the DCL-command "submit"
or:
SPIDER F PRJ/DAT B01
Qualifiers: /NAME=B01PRJ/NOTIFY/QUE=MYBATCHQUE/AFTER=TOMORROW etc.
The command file SPIDERF.COM creates a file named xxx.yyy, where
xxx/yyy is the project/data extension and is a number derived from the
time the job is submitted. This file normaly is deletet after a successfull
completion of the batch job. These files are delete protected. If a batch job
terminates unregularly , these files remain and can be deleted. Before
doing this, change the protection of the corresponding file to O:RWED.
Do not run SPIDER sessions with the same project extension on data in the
same directory. I.E. do not run spider interactively with the same project
extension as a batch job that is running at the same time. These processes would
try to open the same results file, log file and other supporting files which
would result in a file access conflict.
Be carefull when you run two jobs in the same directory with the same data
extension. Especially procedures may use intermediate data files with the same
name, which can result either in an access conflict of an exchange of data
between to jobs that have nothing to do with each other and produce unpre-
dictable results.
File: batch_doc.html Source updated on 05/13/96 al
©
Copyright Notice /
Enquiries: spider@wadsworth.org