On Thu, 9 Apr 2020 07:02:26 -0500, John McKown wrote:
>
>So, I kind of wish that the JCL converter or interpreter would accept JCL
>in lower case. In particular, upper casing the JCL statements which are not
>inclosed in ticks. It would just make my life easier. I.E JCL should ignore
>case when not in ticks.
>
Ditto TSO commands typed on the ISPF primary panel. It's absurd that
tso allocate path('/dev/null')
results in:
PATH /DEV/NULL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED.
(BTW, was there really a catalog search attempted?)
But I'd gp to a different extreme: keywords should be case-insensitive;
this can be done in the table search routine. *Everything* else should
be taken as typed.
And symbol substitution should be performed everywhere, not merely
in the handful of cases enumerated in the JCL Ref.
I have always commented my JCL in mixed case. That practice
infuriates some colleagues who drop into ISPF Edit and find CAPS OFF.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
