On Tue, 30 Apr 2013 13:27:40 -0500, Elardus Engelbrecht wrote:
>
>>z/OS seems to be transitioning more towards using lower case in addition to 
>>upper case. 
>
>Where? ;-)   Please give Examples - short and sweet please... ;-)
>
Binder.  HLASM.

But I have considerable disagreement with Binder's making it an option.
The only behavior should have been MIXED.  This would have been
an entirely compatible extension of Linkage Editor behavior.

And I'm perplexed by HLASM's backward interpretation of MACROCASECOMP

>>One area in which it affects me is when the ISPF editor automagically 
>>switches to upper/lower case support and I forget to type in UPPER CASE when 
>>I do things like a CHANGE command. Yes, this is my fault due to a long 
>>standing habit. 
>
>Yeah, let that be a lesson to you... ;-D   It is a common PITA. ;-D
>
>Today I submitted a job resulting in a *** JCL error caused by a stupid lower 
>case character. PITA because I modified+submitted a job in SDSF using SJ  and 
>did some mindboggling typing without saving that job. 

>>But I am wonder why the JCL converter/interpreter could be changed ...
>
>Do you actually mean 'could NOT be changed'?
>
>>... to accept keywords such as DD and DSN= in lower case as if they were 
>>upper case. 
>
>I think there is a backward compatibility issue, but you have got a good point.
> 
I don't see such.

>It should be easy. Check for 'a-z' outside quotes in JCL and do a simple 
>translation to 'A-Z'. A few lines at most in JES2 interpreter. But still why 
>not?
>
My preference would be to see keywords case-insensitive and all names
case-sensitive, looking ahead to a day when DISABLE(DSNCHECK) might
become common practice.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to