home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: SysTools
/
SysTools.zip
/
cronct12.zip
/
CronCT.DOC
< prev
next >
Wrap
Text File
|
1994-10-06
|
29KB
|
664 lines
CronCT/2 v1.20g & CUtil/2 v1.20g
Timed Based Execution
USER MANUAL
Software and Documentation written by Billy F. Glover
(C) Copyright 1993-1994 CyberTech Software
ALL RIGHTS RESERVED!
──────────────────────────────────────────────────────────────────────────────
Table of Contents:
1 Introduction
1.1 What is CronCT/2 ?
1.2 Features & The Future
1.3 Contents of Archive
1.4 Registering & Authors Address
1.5 Copyright & License Information -- PLEASE READ
2 CronCT/2
2.1 Installation & Command Line Options
2.2 CronCT.DAT File
2.2.1 Options & Overrides
2.2.2 Examples
2.3 Status Window
2.4 Log Window
2.4.1 ERRORS & NOTES During System IPL
2.4.2 ERRORS & NOTES Processing CronCT.DAT
2.4.3 ERRORS & NOTES Processing CronCT.AT
2.5 Queue Window
2.6 Menu Commands
2.6.1 INS-CREATE
2.6.2 DEL-KILL
2.6.3 Execute
2.6.4 Goto
2.6.5 Modify
2.6.6 Skip
2.6.7 Terminate
2.6.8 View
2.6.9 Colors
2.6.10 Log
2.6.11 PM
2.6.12 ALT-P Pause
2.6.13 F1-HELP
2.6.14 ESC-EXIT
2.7 Exiting - ErrorLevels & DropFiles
3 CUtil/2
3.1 General Options
3.2 LOG Trimmer
3.3 AT Command
3.3.1 Examples
3.4 ErrorLevels Returned
4 Credits
──────────────────────────────────────────────────────────────────────────────
CHAPTER 1 - Introduction
──────────────────────────────────────────────────────────────────────────────
1.1 What is CronCT/2
──────────────────────────────────────────────────────────────────────────────
Thank you for trying out CronCT/2! CronCT/2 can schedule events with
great precision. You can schedule an event based upon minutes, hours, days,
months, and/or day of week, using any combination thereof.
LAN Servers can be scheduled to be backed up after hours, as can critical
files such as CONFIG.SYS, AUTOEXEC.BAT, and OS/2 .INIs just to name a few.
BBS SysOps can schedule events so there BBS can stay on-line, when the BBS
is open for callers, and when that voice line is used for a second node!
There are several things that are inconvenient to have to do, and if your
like me, sometimes I'll forget something that needed to be done. We all
know Murphy's law, the second you need that backup, you'll have forgot to
do it! With CronCT/2 running you won't have to worry about that anymore.
CronCT/2 is the result of many months worth of work. I started working
on it around NOV 15, 1993. It was started for my boss, who ended up going
bankrupt. So I decided to finish it and see if there was any interest in
it. There sure was! I'm really surprised by amount of people that have
called in about it. I didn't know that it would go over as well as it did!
──────────────────────────────────────────────────────────────────────────────
1.2 Features & The Future
──────────────────────────────────────────────────────────────────────────────
Features:
Works under OS/2 v2.0 GASP, v2.1 GA, v2.1 GASP, & OS/2 for Windows.
Command Line Utility for interfacing with CronCT/2.
Very low system memory requirements.
Supports HPFS Long Filenames.
Auto-detection of Application type.
Future Plans:
PM version.
HyperText Help Engine.
DAEMON version.
──────────────────────────────────────────────────────────────────────────────
1.3 Contents of Archive
──────────────────────────────────────────────────────────────────────────────
CronCT .EXE - The main executable file.
CUtil .EXE - Command Line Util for interfacing with CronCT/2.
CCTSM .DLL - CronCT/2 Support Module.
CronCT .DAT - Sample CronCT.DAT file.
CronCT .DOC - CronCT/2 & CUtil/2 Documentation. ( This File! )
CronCT .REV - Complete program History. ( Well almost anyway )
File_ID.DIZ - Short description of program for BBSs
──────────────────────────────────────────────────────────────────────────────
1.4 Registering & Authors Address
──────────────────────────────────────────────────────────────────────────────
Starting with version 1.20 I will accept all contributions offered. As
a lot of my time is now spent answering the phone, mail, and faxes about it.
Please send what you feel the program is worth. If sending cash, please
send it by registered mail only for your protection. If you send a check,
I'll wait for it to clear. If you have a FidoNet node number or access to
a FAX machine, please include it, and I'll send your registration code to
you. I'm already working on v1.30 now. Please include the version you have
if you call/fax/mail me. Thanks.
All new versions & bugfixes of CronCT/2 are uploaded to OS/2 ShareWare
BBS. I may be reached there as User: Billy Glover. Please get a hold of me
if you have a suggestion, bug report, or just what to chat! The InterNet
account below belongs to a friend of mine and e-mail sent to it will take a
while to get to me, but I will get it and reply. Enjoy the program.
CyberTech Software Voice : (817) 684-1434
C/O Billy Glover FAX : (817) 552-6288
P.O. Box 333 INTERNET : JHOBBS@ABACUS.MWSU.EDU
Crowell, TX 79227 OS/2 Shareware BBS - (703) 385-4325
──────────────────────────────────────────────────────────────────────────────
1.5 (C) Copyright & License Information -- PLEASE READ
──────────────────────────────────────────────────────────────────────────────
CronCT/2 Executables & Documentation are Copyright (C) CyberTech Software,
Billy Glover. All Rights Reserved. You may use CronCT/2 in any environment
for any purpose. You may NOT sell CronCT/2, nor charge a fee for CronCT/2
except where a nominal price would be applicable for recovering costs.
You have accepted this program with the understanding that CyberTech
Software makes no representations or warranties as to the suitability of
this program for your particular purpose, and to the extent you use or
implement this program in your own setting, you do so at your own risk.
In no event will CyberTech Software be liable for any damages, whether
consequential, incidental, or special, arising out of the use or inability
to use the program provided herewith. This program has restrictive terms
and conditions associated with its use and reproduction to which you must
agree. DO NOT POST MODIFIED VERSIONS OF THIS PROGRAM FOR PUBLIC ACCESS.
CronCT/2 & CUtil/2 are trademarks of CyberTech Software, Billy Glover.
All other product names and services identified in this manual are
trademarks or registered trademarks of there respective companies.
──────────────────────────────────────────────────────────────────────────────
CHAPTER 2 - CronCT/2
──────────────────────────────────────────────────────────────────────────────
2.1 Installation & Command Line Options
──────────────────────────────────────────────────────────────────────────────
Create a base directory and UnZip the distribution archive ( SECTION 1.3)
in it. This directory should to be placed in your CONFIG.SYS path statement
for convenience. The next thing you need to do is create your own CronCT.DAT
file using the one given as a guideline ( SECTION 2.2 ).
CronCT/2 Command line: CronCT.EXE [/L] [/P-]
/C- Will deactivate the PIPE Thread. This is the thread that CUtil/2 uses.
/L Will activate logging to CronCT.LOG
/M Mono Colors
/P Activate CronCTPM/2
CronCT/2 can be auto-started each time you boot by:
1. Creating an Icon for CronCT.EXE and placing it in your startup folder.
2. Starting it from your STARTUP.CMD file.
This is the interactive version of CronCT/2, so don't 'DETACH' or 'RUN' it.
──────────────────────────────────────────────────────────────────────────────
2.2 The CronCT.DAT File - Structure, Options & Overrides, Examples
──────────────────────────────────────────────────────────────────────────────
CronCT.DAT, the heart of CronCT/2, may be created with any text editor.
An example copy of CronCT.DAT is given with the distribution archive. On
the top of each minute, CronCT/2 will check CronCT.DAT for changes and will
be reprocessed if needed. While processing CronCT.DAT, LOG messages may
appear in the LOG window. They are described in SECTION 2.4.2
General Structure of CronCT.DAT:
Comments are denoted by a '#' sign in the 1st column
Comments denoted by '#$' are logged each time the processes
after them are executed
Each Queue Record will have the following:
[!]Minutes, [!]Hours, [!]Days, [!]Months, [!]Day of Week
[/PM | /OS2 | /VDM] [/M:filename] [/FG | /BG] [/NJ] [/NU[:#]]
[/WIND[-]] | /FULL[-]] are Options & Overrides. See SECTION 2.2.1
[PATH]+FileName & Options
Minutes, Hours, Days, Months, and Days of Week can have multiple entries
by separating them with commas. Make sure there aren't any spaces after
each comma ( 1,2,3 ). Hours are in 24 hour format, this may change later.
By placing a [!] before a number entry, the number is treated as a time
to Terminate that Queue entry. ( 0,!30 1,!1,2 ) would start at 1:00a 2:00a
and stop at 1:30a but not 2:30a.
The [-] is the range operator. ( 0,!30 1-4,!1-3 ) would start at 1:00a
2:00a 3:00a 4:00a and stop at 1:30a 2:30a 3:30a but not 4:30a.
──2.2.1 ─ Options & Overrides─────────────────────────────────────────────────
Commands Options & Overrides may appear after the Day of Week entry and
before the [PATH] Program entry. They can be in any order.
In most cases, CronCT/2 will auto-detect the process type, but defaults
to type OS2. You may override this with /PM | /OS2 | /VDM.
/FULL[-] & /WIND[-] Fullscreen or Windowed. '-' Minimized to Icon.
/M:filename will direct CronCT/2 to execute this file before running this
Queue Record. If the Macro returns an errorlevel of 1 then the Queue Record
is executed, anything else and the try is logged and the Queue Record isn't
executed.
/SIZE:X,Y & /POS:X,Y will override the default settings for window Size
& Position. Value is in PELs.
/FG | /BG override: /FG for ForeGround, /BG for BackGround. CronCT/2
defaults to type /BG background.
/NJ will cause CronCT/2 to remove this Queue Records Session information
from the PM 'Window List'. In effect, you can't jump to or see it from the
PM 'Window List'. You can still terminate or switch to it from CronCT/2.
This is good for making sure that a Queue Record isn't stopped on accident.
/NU[:#] is the Notify User command. This will notify the user after each
time the Queue Record has ended. CronCT/2 will 'PopUp' in any Fullscreen
non-pm window that's in the Foreground to inform the user. The 'PopUp' will
last 5 seconds or until a key is pressed. If you specify a number ( /NU:# )
CronCT/2 will only 'PopUp' if the errorlevel returned is different from the
number.
──2.2.2 ─ Examples────────────────────────────────────────────────────────────
Some Examples:
0 1 2 3 * /FULL- D:\os2\apps\misc\backup.exe -now
On March 2, 01:00 am Launch <backup.exe -now> as Fullscreen MIN process.
0,!0 1,!3 * * * /WIND- Mailer.EXE /com2
At 1:00am Launch <Mailer.EXE /com2> as PM-Window MIN process. Kill at 3:00a
0 1 * * * /NJ /OS2 /NU:0 JOB
At 1:00am Launch [JOB] as OVERRIDE apptype to OS2, NoJump, & notify user of
exit if errorlevel isn't 0.
──────────────────────────────────────────────────────────────────────────────
2.3 Status Window
──────────────────────────────────────────────────────────────────────────────
╔═════════════════════════════╗
║ Monday, August 22, 1994 ║ PM - Total PM processes Queued/Running.
║ 19:32 ║ OS2 - Total OS2 processes Queued/Running.
║ ║ VDM - Total VDM processes Queued/Running.
║ ║
║ PM : 000/000 AT : 000 ║ AT - Total # of AT Processes Queued.
║ OS2 : 000/000 GEN : 000 ║ GEN - Total # of GEN Processes Queued.
║ VDM : 000/000 TOT : 000 ║ TOT - Total # of Processes in memory.
╚═════════════════════════════╝
CronCT/2 displays GEN Queue Records in the QUEUE below. AT Queue Records
aren't displayed. For more information about the QUEUE, SEE SECTION 2.5
──────────────────────────────────────────────────────────────────────────────
2.4 Log Window - System IPL, CronCT.DAT, CronCT.AT, PIPE
──────────────────────────────────────────────────────────────────────────────
If CronCT.LOG is busy ( in use by another process ) CronCT/2 will place
the LOG entry on the pending write stack ( FIFO Queue ). Once CronCT.LOG is
ready, it will write out all pending writes in the order they were received.
If CronCT/2 is terminated & CronCT.LOG is still busy, CronCT/2 will write
out all pending writes to PLogW.CCT. The contents of this file are then
added to CronCT.LOG during the next System IPL.
──2.4.1 ─ ERRORS & NOTES During System IPL────────────────────────────────────
During System IPL, CronCT/2 may log any of the following:
NOTE: Pipe Handler Disabled! - Started with Option /P-
NOTE: Processing Pending Log Writes - Found 'PLogW.CCT'
NOTE: Processing Pending AT Adds - Found 'PATAdd.CCT'
NOTE: Processing Pending AT Kills - Found 'PATKill.CCT'
──2.4.2 ─ ERRORS & NOTES Processing CronCT.DAT────────────────────────────────
During processing of CronCT.DAT, CronCT/2 may log any of the following:
NOTE: BAD MIN [ # ] LN: # - Range 1-59
NOTE: BAD HOUR [ # ] LN: # - Range 0-23
NOTE: BAD DAY [ # ] LN: # - Range 1-31
NOTE: BAD MONTH [ # ] LN: # - Range 1-12
NOTE: BAD DOW [ # ] LN: # - Range 1-07
NOTE: BAD Option or Override LN: # - Recheck line, SEE SECTION 2.2.1
──2.4.3 ─ ERRORS & NOTES Processing CronCT.AT─────────────────────────────────
During processing of CronCT.AT, CronCT/2 may log any of the following:
NOTE: BAD Option or Override! LN: # - Recheck line, SEE SECTION 2.2.1
ERROR: AT QUEUE DATE/TIME INVALID! - Line Removed.
──2.4.3 ─ ERRORS & NOTES from PIPE────────────────────────────────────────────
During PIPE ( CUtil/2 ) operation, CronCT/2 may log any of the following:
ERROR: DosCreateNPipe() RC: # - CronCT/2 may already be running.
ERROR: DosConnectNPipe() RC: #
ERROR: (R#) Broken PIPE! RC: #
ERROR: (R#) MORE DATA! RC: # BR: #
ERROR: (R#) Something wrong with PIPE! RC: #
ERROR: (DDCNP) Broken PIPE! RC: #
ERROR: (DDCNP) BAD PIPE! RC: #
If you keep getting any the above 7 errors call up and I'll check into it.
The above errors are very rare, and you shouldn't ever get any of them.
Rejected AT Queue Entry from PIPE! - AT Queue rejected from CUtil/2.
ERROR: AT Queue DATE/TIME Invalid! - because of DATE/TIME information.
──────────────────────────────────────────────────────────────────────────────
2.5 Queue Window
──────────────────────────────────────────────────────────────────────────────
╔══════════════════════════════════════════════════════════════════════╗
║ QUEUE SESSION INFO PROGRAM & OPTIONS STATUS ║
╟──────────────────────────────────────────────────────────────────────╢
║ 001 PM/WIND/MIN PMP.EXE -com1 Ready ║
║ > 002 OS2/FULL/MIN OS2Scan.EXE C: D: E: Running ║
║ 003 VDM/FULL/MIN DB.EXE Running ║
║ 004 OS2/FULL/MIN Tape.EXE -now MacroCHK ║
║ 005 OS2/FULL/MIN Play.CMD FILE=CUCKOO.WAV Ready ║
║ 006 * PM/FULL/MAX *Jigsaw -scramble Ready ║
║ ║
║ ║
║ ║
║ ║
╚══════════════════════════════════════════════════════════════════════╝
QUEUE
Queue numbers, each Queue Records is given a Queue Number. The '>'
designates the current Queue Record.
SESSION INFO
Session Type, Fullscreen | Windowed, Minimized | Maximized. If the
process type has been forced it will have a '*' before it.
PROGRAM & OPTIONS
Name and any options that go with it. Path is not included. If the
program can't be located it will have an '*' before it and be launched as
an OS2 command shell type ( like a cmd file ).
STATUS
Ready - Ready to be executed.
Running - Currently running.
Failed - Queue Record failed to execute, check log for reason.
Skipped - Queue Record has be skipped.
MacroCHK - Executing MACRO.
Modify - The Queue Record is currently being modified.
──────────────────────────────────────────────────────────────────────────────
2.6 Menu Commands
──────────────────────────────────────────────────────────────────────────────
Menu Command - Action Taken
INSERT - Create Queue Record.
DELETE - Delete current Queue Record.
E - Execute current Queue Record.
G - Switch this running Queue Record to the Foreground.
M - Modify current Queue Record.
S - Toggle Skip current Queue Record.
T - Terminate ( stop running program ) current Queue Record.
V - View current Queue Record.
C - Colors.
L - Log Options.
P - CronCTPM/2 Options.
ALT-P - Pause Queue Launches.
F1 - HELP.
ESC & ALT-X - Terminate CronCT/2.
Page UP/DOWN - Move one page Up/Down in the Queue.
/ - Move up/down in CronCT's Queue.
HOME/END - Change to the top/bottem of current Queue list.
CTRL-HOME/END - Change to the START/END of Queue list.
──2.6.1 ─ INSERT──────────────────────────────────────────────────────────────
Comment - Comment to log before each launch
Program - Program to launch
Options - Program Options
Path - Path to find the program
Minutes, Hours, Days, Months, and Days of Week can have multiple entries
by separating them with commas. Make sure there aren't any spaces after
each comma ( 1,2,3 ). Hours are in 24 hour format, this may change later.
By placing a [!] before a number entry, the number is treated as a time
to Terminate that Queue entry. ( 0,!30 1,!1,2 ) would start at 1:00a 2:00a
and stop at 1:30a but not 2:30a.
The [-] is the range operator. ( 0,!30 1-4,!1-3 ) would start at 1:00a
2:00a 3:00a 4:00a and stop at 1:30a 2:30a 3:30a but not 4:30a.
The following are Options & Overrides from SECTION 2.2.1
Session Type - Defaults to AUTO-DETECT
Notify User - 'Y' to Notify all the time, or a Number to notify only
if the errorlevel doesn't match. Defaults to NO.
FULL/WIND - 'F' for Fullscreen, 'W' for Windowed. Defaults to FULL.
Jumpable - 'J' for Jumpable, 'N' for NotJumpable. Defaults to J.
FgBg - 'F' for Foreground, 'B' for Background. Defaults to BG.
Macro - Macro to execute. Defaults to NONE.
After your finished editing the Queue Record press ALT-S or F10.
──2.6.2 ─ DELETE──────────────────────────────────────────────────────────────
The DELETE command should be used with caution! Once deleted, the only
way to get the Queue Record back is to re-enter it. You will not be asked
for confirmation.
──2.6.3 ─ Execute─────────────────────────────────────────────────────────────
Executes the Queue Record if its status isn't one of the following:
Running - Already running!
Skipped - Unskip it to execute.
MacroCHK - Checking Macro, already running.
──2.6.4 ─ Goto────────────────────────────────────────────────────────────────
Switches the Queue Record into the foreground. If the Queue Records was
launched with the option of /NJ, this is the only was to switch to the
Queue Record.
──2.6.5 ─ Modify──────────────────────────────────────────────────────────────
The modify command lists all the information from SECTION 2.6.1 and lets
you change any of it. You can't change a running Queue Record. After your
finished editing the Queue Record press ALT-S or F10.
──2.6.6 ─ Skip────────────────────────────────────────────────────────────────
The SKIP command will toggle the skip status of the current Queue Record.
This command only works if the current status is READY.
──2.6.7 ─ Terminate───────────────────────────────────────────────────────────
The TERMINATE command will stop the current Queue Record from running. If
the Queue Record was started with the option of /NJ, this is the only way to
stop it, until it ends normally.
──2.6.8 ─ View────────────────────────────────────────────────────────────────
The VIEW command lets you view all the information from SECTION 2.6.1, but
not change any of it. Press any key when finished.
──2.6.9 ─ Colors──────────────────────────────────────────────────────────────
The COLOR Command lets you change ANY color ANYWHERE in CronCT/2.
──2.6.10 ─ Log─────────────────────────────────────────────────────────────────
* Log Options havn't been implemented yet.
──2.6.11 ─ PM──────────────────────────────────────────────────────────────────
* PM Support was taken out at the last minute. Its just to unstable in this
version and will be in the next version. This was my first attempt at PM
coding so I still learning!
──2.6.12 ─ ALT-P Pause─────────────────────────────────────────────────────────
The ALT-P command will suspend the background launching of Queue Records
( including AT Queue Records ). Press ALT-P again to resume.
──2.6.13 ─ F1-HELP─────────────────────────────────────────────────────────────
* F1-HELP system hasn't been implemented yet.
──2.6.14 ─ ESC-EXIT────────────────────────────────────────────────────
This command, or ALT-X, will perform CronCT/2 system shutdown. Anything
pending action ( Log/AT ) will be wrote to dropfiles and processed during
the next System IPL.
──────────────────────────────────────────────────────────────────────────────
2.7 EXITING - ErrorLevels & DropFiles
──────────────────────────────────────────────────────────────────────────────
CronCT/2 will return an errorlevel of 0 if everything went ok. Otherwise,
it will return the following:
248 - General Error Code
249 - Error with CCTSM.DLL
250 - Error in Command Line Options. Check your command line options.
251 - Memory Allocation Error. You should'nt get this error.
252 - Can't Create/Locate File. Check your files.
253 - Thread Creation Error. You should'nt get this error.
254 - CUtil/2 PipeError.
255 - EXCEPTION ERROR! Record all information and call me
( SEE SECTION 1.4 ).
Under certain situations CronCT will leave 'dropfiles' in its base
directory. These files, if they exist, will be processed during the next
System IPL.
CronCT .AT - AT Command Support File, Modify this file at your on risk.
CronCT .INI - Where CronCT/2 keeps its Colors.
PATAdd .CCT - Pending AT Adds, will be added to 'CronCT.AT'.
LOG Entry: 'NOTE: Processing Pending AT Adds'
PATKill.CCT - Pending AT Kills, will be deleted from 'CronCT.AT'.
LOG Entry: 'NOTE: Processing Pending AT Kills'
PLogW .CCT - Pending Log writes, contents will be added to 'CronCT.LOG'.
LOG Entry: 'NOTE: Processing Pending Log Writes'
──────────────────────────────────────────────────────────────────────────────
CHAPTER 3 - CUtil/2
──────────────────────────────────────────────────────────────────────────────
3.1 General Options
──────────────────────────────────────────────────────────────────────────────
Command - Action Taken
/? - CUtil.EXE Usage Information.
/I - Get CronCT's General/AT Queue Status.
/Iq - General Only
/Ia - AT Records Only
/It - AT Records Time to execute ( AM/PM format ).
/L - Trim CronCT's LOG. ( SEE SECTION 3.2 )
/Q - Terminate Running CronCT/2.
CronCT/2 Queue Commands: /COMMAND QUEUE # | FILENAME
/E Execute /S Skips /P Pauses
/T Terminate /U Unskips /R Resumes
CUtil.EXE /S EXE Would Skip all entries with EXE in there FILENAME.
CUtil.EXE /U le Would Unskip all entries will 'le' in there FILENAME.
──────────────────────────────────────────────────────────────────────────────
3.2 LOG Trimmer
──────────────────────────────────────────────────────────────────────────────
Command Format: CUtil.EXE /L [path]filename #
CUtil/2 Log Trimmer will trim your log based on date or finding a trigger
word in the log line. Trigger words are stored in the file 'CU_LOG.CCT'.
This file MUST be in the same directory as CUtil/2. If CUtil/2 can't find
this file it will still work, just not using kill words.
The file 'CU_LOG.CCT' has one entry/line, and you can have any number of
entries. Each entry can be more than one word, so that 'Log Trimmer' would
be one entry line.
Command Format: CUtil.EXE /L filename #
* CU_LOG.CCT hasn't been implemented yet.
──────────────────────────────────────────────────────────────────────────────
3.3 AT Command Options
──────────────────────────────────────────────────────────────────────────────
[DATE] [TIME] [[NEXT | INCREMENT] TIME DESIGNATION] [Opts | Overrides] JOB
CUtil.EXE /AT 01/02/94 03:00 JOB - DateTime.
CUtil.EXE /AT + 2 MONTHS JOB - Now + 2 months.
CUtil.EXE /AT NEXT DAY JOB - Now + 1 day.
CUtil.EXE /AT SAT + 2 WEEKS JOB - Next SAT + 2 Weeks.
CUtil.EXE /AT DEC 7 [1994 | 94] 00:00 JOB - DEC 7, 1994 at Midnight.
Keywords are: ( Case insensitive )
NEXT | + # [ MIN[UTEs] | HOURs | DAYs | WEEKs | MON[THs] ]
NOON = 12:00pm MIDNIGHT = 00:00am TOMORROW = +1 Day
Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.
JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC.
You can use any of the Options & Overrides listed in SECTION 2.2.1
──3.3.1 ─ Examples────────────────────────────────────────────────────────────
CUtil.EXE /AT NEXT DAY 11:00 /NU:0 /NJ /FULL- DOTHIS.EXE Opts
CUtil.EXE /AT + 5 HOURS /WIND- DOTHIS.EXE Opts
CUtil.EXE /AT 8:00 TOMORROW DOTHIS.EXE Opts
CUtil.EXE /AT DOTHISNOW.EXE Opts
──────────────────────────────────────────────────────────────────────────────
3.4 ErrorLevels Return from CUtil/2
──────────────────────────────────────────────────────────────────────────────
CUtil/2 will return an errorlevel of 0 if everything went ok. Otherwise,
it returns 1 for error.
──────────────────────────────────────────────────────────────────────────────
CHAPTER 4 - Credits
I would like to think all the registered users and Alpha/Beta/Gama Testers
for there contributions. Thank you for the time you spent testing the code,
reporting problems, and making suggestions. CronCT/2 wouldn't be half the
program it is today without you!
Alpha/Beta Sites:
Jennifer Blackwell
Mark Zembrzuski
Jason Knight
Eric Hall
I'd also like to send a very special thinks to:
Bob Hood - For answering so many questions!
Miriam Irwin - So MANY things its unreal! :)
──────────────────────────────────────────────────────────────────────────────