In a recent note, EA MacNEIL said: > > Revolutionary changes in an evolutionary manner. > > Let's stretch PARMS and JCL Card Images, but not in such a way that we break > some > thing. > > I believe that a new zPARM is the better approach. > What would permitting longer PARM strings break? Existing "dusty deck" JCL with short PARMs would continue to call Legacy programs with no breakage.
> 2. It's about time that JCL supported mixed case. > > //step1 exec pgm=iefbr14 > > should be just as acceptable as: > > //STEP1 EXEC PGM=IEFBR14 > > (and we can always use quotes whenever we don't want something > mapped to upper case, just as we do with PATH= > _Provided_ that quoting is permitted wherever names may appear. E.g.: //'step1' exec pgm='iefbr14' ... should execute member "iefbr14", not "IEFBR14" from the STEPLIB concatenation, and a subsequent: //STEP2 EXEC whatever,COND=(0,NE,'step1') ... should test the result code of "step1", not of "STEP1". The same conventions should apply to TSO commands if the user specifies PROFILE ASIS. However, I believe no quoting should be necessary; keywords should be case-insensitive; names case-sensitive. Again, this would break no dusty decks. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
