Batch on other systems:
(can Darren or someone please report to L-SOFT problems
replying via the web interface to plies such as Rex's
that have:
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"
They can be read clearly. When replying, quoted text
appears as unrendered base64.
I'd do it myself, but IIRC, L-Soft requires customer ID.
Thanks.)
On Aug 27, 2012, at 07:18, Pommier, Rex R. wrote:
>
> ... Unless you specifically "background" a task, when you run a script it
> ties up your terminal session, whether it be for a transaction or a task that
> updates millions of rows in a database. ...
>
But the *NIXen let the programmer "background" a process
with a single keystroke and later to wait for its completion
and sense its exit status; something extraordinarily (PoV)
difficult in TSO.
command-name & # "&" indicates background
PID=$! # Save process-ID; repeat if desired
... # do whatever you want in meantime
wait $PID # Wait for completion
echo "command-name completed with status $?"
What would be necessary to do this with CLIST or Rexx
with e.g. IEFBR14 as command-name? Please enumerate any
additional files (JCL) or nonstandard (ISV, CBBTAPE)
commands that would be needed.
And the command language for *NIX batch is identical to
the foreground scripting language; newcomers may devote
that part of their learning resouce to more productive
areas.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
