Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.atnf.csiro.au/computing/software/gipsy/tsk/nhermes.dc1 Дата изменения: Tue Apr 30 08:14:44 2002 Дата индексирования: Fri Jan 16 18:16:13 2009 Кодировка: Поисковые слова: eclipse

Document: nhermes

Purpose: GIPSY master control program for a non interactive environment

Category: USER-INTERFACE

File: hermes.src

Author: M.A.M. Ruiter

Use: nhermes [ -l ] [ -t ] { }

You should give one or more user commands to nhermes.
The -l and -t flags are optional.

can be a cola script or a name of a servant task
with their parameters.
The name of the servant task or the cola script with their
parameters should be suitable quoted or escaped to keep it
together (e.g. between double quotes).
A cola script file should have the extention .col as specified
in the documentation of the application program COLA.
You may give the name of the cola script with or without the
extention .col to nhermes.

The options may appear in any order and may be intermixed with
the user commands:

-l With this option you can give the name of the
log file as output of NHermes. The log file
will always have the extention .LOG. If you
don't give the extention in uppercase or not
at all, it will be added to .
The default log file name is GIPSY.LOG.

-t This is the timer option. After
minute(s) a time out will occure.
The time out provides termination of the user
command when it is stucked in an endless loop

Description: The non interactive Hermes, NHermes, is based on the interactive
Hermes, Thermes.
The user command will be considered as if it was a user type-in
in the User Command Area of the THermes. Default values for
unspecified keywords will be taken if available. If there is no
default available, an error message will be generated in the log
file and NHermes will stop with the current user command.
When a user command is done, NHermes will start the next user
command if given by the user.
If the time out is set, a time out will occure after
minute(s) and NHermes will stop with the user command it is
dealing with.
The time out works seperately for each user command.
All output will be kept in a log file.

Consult the manuals of Hermes and the GIPSY servant tasks for
detailed information about how to build a cola script and how to
use servant tasks.


LOGFILE


NHermes maintains a log file like THermes. This log file
contains a history of all operations done and also information
generated by servant processes. The information in the log file
which is generated by servant processes depends on the settings
of those processes.


ENVIRONMENT


NHermes should run in a GIPSY environment. Consult the
GIPSY user manual for the installation of this environment.

See also: hermes.dc1, thermes.dc1, xhermes.dc1, GIPSY.doc.

Warnings: SETTINGS OF SERVANT TASKS
At this moment you can not change any settings (e.g. output
level) of servant tasks (See XHermes and THermes for settings).

USER COMMAND IN ARGUMENT LIST
If the given servant task or cola script with their parametes
are not suitable quoted or escaped to keep it together, NHermes
shall handle them as if they were seperate user commands.

Updates: Fri Jan 31, 1992: MAMR, document created
...
Tue Nov 16, 1999: JPT, show current parameters for "macro"
Tue Nov 23, 1999: JPT, keyword file write bug fixed
Tue Apr 2, 2002: JPT, incorrect task count fixed