home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 11 Util
/
11-Util.zip
/
apshe103.zip
/
ApSched.Doc
< prev
next >
Wrap
Text File
|
1998-01-17
|
5KB
|
151 lines
ApSched 1.03
(c) Copyright 1997-1998 by Alberto Pasquale
F R E E W A R E
LICENSE
You may copy, distribute and use this program freely, provided
you do not modify the original archive and Copyrights.
DISCLAIMER
You are entitled to use this freeware program "as is". No
guarantee can be given on the performance of the program. The
author will not be liable for any damage or loss related to the
use of this program.
Overview
ApSched is a simple Scheduler that allows to execute commands
and batch files at will.
It is currently very poor in the interface, and it will probably
remain this way, but it is reliable and easy to use.
I wrote ApSched because I have 6 mailer tasks in my BBS, but I
did not want to link external "global" events to any specific
mailer task.
This is useful in many situations, for example when the mailer
task that should execute an external batch event is busy with a
long session.
Configuration
ApSched requires a configuration file that describes all the
events: let us name it ApSched.Evt.
Before the Events definitions, two statements are accepted:
LogFile <LogFile>
Specifies a Binkley style log file.
BatchFile <BatchFile>
Specifies a batch file to be used for events.
The event definitions follow, one per line, with the following
format:
================================================================
"<description>" <Day>[,<nth>][-<month>] <time> <Cmd> [<flags>]
"<description>" is a short (truncated to 39 chars) description
of the event
<Day> can be:
All
Sun|Mon|Tue|Wed|Thu|Fri|Sat
Week (Mon->Fri)
WeekEnd (Sat|Sun)
1..31
Multiple items separated by |
<nth> is the nth <day> in the month
Multiple items separated by |
5 means last (becomes 4 if the 5ft does not exist)
<month> can be:
All
Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec
Multiple items separated by |
<time> is 24h time in hour and minutes, range 00:00 -> 23:59
E.g. 14:00
<Cmd> If no V flag: is the parameter passed to <BatchFile>
If V flag: is a full command (possibly quoted)
Max 79 chars.
<flags> is a set of flags, | separated:
V Use <Cmd> as verbatim command, not parameter to
<BatchFile>
================================================================
ApSched is designed to remain running 24h/24h, so it does not
need forced events: it starts examining events at the time it is
launched and will execute all the configured events, even if the
time has already elapsed waiting for the termination of a
previous command.
Usually, <Cmd> specifies a string that will be passed to
<BatchFile> on its command line (will be used as %1).
So you should change your old habit of using meaningless
errorlevels to the new style of "labels".
When useful, you can also specify the V flag and use <Cmd> to
specify a normal command (possibly the name of a batch file with
parameters): this way ApSched will not invoke <BatchFile> with
<Cmd> parameter; instead it will directly execute <Cmd>.
================================================================
Here the magnificent TUI commands are listed.
For people not updated to the latest technological advances, TUI
stands for Teletype User Interface, which includes the results
of the latest research in ergonomics.
ALT-X: Exit
ALT-R: Reload event file
ALT-S: Show Events
ALT-E: Enter Event number to execute immediately
ALT-H: Help
The program is launched by specifying the name of the event file
on the command line:
ApSched <EventFile>
================================================================
Errorlevel:
0 Help given
1 ALT-X exit
2 Configuration file not found
4 ApSched is already running
================================================================
For comments and suggestions:
Alberto Pasquale of 2:332/504@fidonet
alberto@apworks.com