In HP3000 most Batch Job used to be process construct with
COBOL/IMAGE/FLAT File that schedule by JOB, In Unix world, most data
processing, they use Oracle with PL/SQL or SQL, the main PROC, it can
be schedule by CRON job when trigger file was touched by UNIX prompt
or outside FTP from other machines, in this PROC can be stream base on
JOB scheduler Table different Proc base on Switch set up in JOB
scheduler Table, then every PROC execute and logging how many records,
when it start and when it finished to Batch Logging Table, base on
failure, each proc have some sort of recovery function too.

(trying to simulate good old HP3000).

Cheers

www.exmlsoft.com

Tim Cummings <[log in to unmask]> wrote in message news:<[log in to unmask]>...
> It is amazing that things we took for granted on the HP3000 (temporary
> files, Batch jobs, Job queues, spooler, input priority, output priority,
> jobfence, outfence, jobq limits ...) are absent in UNIX world.  There seems
> to be no serious context for batch processing.
>
> Tim
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *