On Sat, 5 Aug 2006 00:35:12 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote:
>... >You're wrong! >It is a big deal! >ISPF will run CAPS off if there is one character in lower case in the member. > >As a vendor, it may seem fine to you. >But, you should aim for the lowest common denominator. >... Ok. Ed doesn't get to vote. I'm a customer (but not of Ed's products) so I get to vote, and I vote for mixed case JCL. I find mixed case comments much easier to read. I don't turn caps on (and don't like it when ISPF does it for me. Yes, I sometimes end up with lower case JCL causing JCL errors, but find that ISPF's bulk line command UUC and/or UCC fix that well. I would rather run the risk of the JCL errors than run the risk of having path definitions converted to upper case when I copy mixed case JCL into a CAPS ON member I'm editting. Pat O'Keefe ---------------------------------------------------------------------- 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
