
The general idea behind these routines is to send batch processes to a
file server or PC not in use on a local area network (LAN), thus freeing
up your computer for other tasks.  Place all of the files marked with an
asterisk (*) in a subdirectory named C:\BATCH.  Also, make sure you have
COMSPEC set correctly (points to where COMMAND.COM can be found).

It will currently handle a queue of 3 tasks, but could easily be expanded
to process more.

I use this system for batch compilations and links with
Clipper and C.  It has saved me countless hours, and it's a great
panacea for the dreaded EDIT-COMPILE-LINK-EDIT cycle.  I can make some
changes to a program, send a batch compilation out, and then continue
editing the program or go do something else.  Maybe you have some other
uses for it.

A side benefit is that the compilations and links go much faster
because I send them to the file server, which is idle most of the time
due to lack of main memory.

This system was developed on a 4 user network with 2 "AT" class machines
and 2 "XT" machines running MS-DOS 3.2 under IBM's PC-LAN.  It has also
been tested using NETWORK-OS (Novell compatible - CBIS Corporation,
Atlanta, GA).  It should run on any DOS network or multitasking enviroment.


The files contained in QUEUE.ARC are as follows:

HOST.BAT
---------
This the queue handler and batch calling program.  Run it on the PC in
the network that you want to do the batch processing. If you have a
non-dedicated server, you might want to run HOST.BAT on it.


Q.BAT
------
This is the queue manager program.  Place Q.BAT in a subdirectory which
has a path set to it so that it can be run from any prompt.  The syntax
for the command is:

              Q [batch file name] / Q / D {batch no.} / ?

Q [batch file name] will place the specified batch file name on the
processing queue.  If 3 jobs are already in the queue, an error message
indicating this will be printed.

Q Q will send the host machine a flag telling it to terminate the HOST
mode after processing all pending jobs.  After entering Q Q, no further
jobs will be accepted.

Q D {batch no.} will delete a job from the processing queue.  The batch
no. is required.  If no batch no. is passed, or if the batch no. entered
is the number of the job currently running, an error message will be
printed.

Q ? will display the syntax of the Q command.

Entering Q by itself (no command line parameters) will show the names
of the files currently in the queue and indicate which one is running.


DOWN *
-----
This is an empty file which acts as a flag to the system indicating
whether a host computer is present or not.  It gets renamed to UP by
HOST.BAT when a host machine is set up.


CD *
---
This is a 3 byte text file containing the string "CD ".  The currently
logged directory of the machine requesting the batch job is combined with
this file to log the host machine to the right directory when it runs the
batch job.


READONLY.BAT *
-------------
This is not currently used by the system.  It, along with READWRITE.BAT,
are meant to protect from a SHARING error when both machines attempt to
write to the same file.


READWRITE.BAT *
--------------
See READONLY.BAT above.


QUIT.BAT *
---------
This is the exit routine for the host machine.


This system was designed using the IBM PC-LAN program.  The only code
specific to that network is the section in HOST.BAT which sends a
message out indicating when a process has completed.  This could be
removed if you are not using PC-LAN.  Take out the lines that read:

        net send jon Batch process number x finished.

If you are using PC-LAN, you might want to issue a NET LOG command
for your station so that the remote machine does not interrupt your
application with an annoying message when it finishes.


Granted, these routines are VERY primitive relative to some of the
same types on the market.  Ain't nothing free; however I hope that
someone will get some use out of them, because I put a lot of time
into them.  If you find use for my system, I'd love to hear about it.

Here's how you can reach me:

                                          ATTN: Jon Lawrence
                                          PRISM CORPORATION
                                          2954 Central Parkway
                                          Cincinnati, Ohio 45225
                                          513/221-3848


**********************************************************************
Revision 1

August 18,1987

This revision of the queueing system has added a simple batch file
named QC.BAT.  It's purpose is to facilitate the easy queueing of
COMMANDS as opposed to BATCH FILES.  The syntax is:

          QC <command 1>  <command 2> ..... <command 9>

QC.BAT will create a temporary batch file in the logged directory of
the machine issuing the command and queue that temporary batch file.

This enhancement grew from the need to queue small, often one-time,
tasks without the need for creating a batch file.  I use it most often
for archiving files or doing compilations of single source code modules.
I hope you find it useful.

Jon Lawrence
PRISM CORPORATION

(eof)

