Re: Windows scripting

In article <q4jfi05tbjpbga26igb6svo1993jsnrfqf@4ax.com>,
Robert Wagner <robert@wagner.net.yourmammaharvests> wrote:

> On Sat, 21 Aug 2004 10:01:08 -0400, "Don Leahy"
> <leahydon@nospamplease.netscape.net> wrote:
> 
>
> In the case of batch, Rexx writes the JCL and CA-7 executes it.
> Running production programs running under Rexx is not in the culture.

Rexx is useful -- but more as a replacement for CLIST that as a
replacement for JCL.

There are some nice things about JCL.  The declaritiveness of it allows
for repeatable, predictable, production runs without the iffy-ness that
can show up from using a full-featured language for your scripts.

(For example, a commonly used Rexx function might be changed to have
subtle side-effects in production jobs -- JCL provides exactly what is
request or a error.)

Finally, you can't run Rexx without JCL*, so your are still somewhat
dependant upon some of its problems and oddities.





* Yes, yes, you could run it under CICS, but the you have the oddities
of CICS and JCL to deal with.  Oh, you could run it under USS, but the
you have the oddities of USS and JCL to deal with.  Well, you could run
it from a master console -- but that would be very strange...