> The fact that this thread split off from the PARM= thread and then > wrapped back demonstrates something else: JCL itself is an anacronism.
Allelujah! You betcha. > <snip> SHARE suggested that <snip> there be some new unified > command language for all environments. I suggest that command > language is REXX. Perhaps. I certainly would not mind Rexx as one of the menu of choices, but I can see good cause for others as well... Java, Perl, C or something like it, or even (blush) VB. IMO anything would be a huge improvement over JCL. As an ISV I still have the unrivalled joy of having to coerce JCL into doing things it was never really intended for and which are essentially trivial on every other platform. > I have written a number of > production batch jobs with basically no JCL and the heavy lifting in > REXX simply because it was completely impossible to do what I needed > via JCL and often trivial to do it in REXX. (In fact, pre-REXX I had > done a few of these in CLIST. Bleah.) No question about that. Any scripting language will run circles around JCL as a "language" for getting things done. JCL is a piece of arcana that should be consigned to the dustbin of history. > Of course, some of these jobs butted up against the 100 char > JCL parm limit... ...which would not exist in any alternative reality not based on JCL. JCL delenda est. CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
