On Mon, 11 Jul 2022 09:12:45 -0700, Charles Mills wrote:
>The problem is that there just is no generic MODIFY format, and I guess there
>really is no universal console command format. Yes, yes, the next time they
>write MVS they should do a single parser shared among all commands, but
>unfortunately they did not do it for this MVS.
>
It's only half as bad as you make it sound. But there should have
been some lexical uniformity, such as: "Apostrophes always protect
speciall characters."
>For MODIFY, the command I am most familiar with, EVERYTHING after the procname
>and so forth is passed to the application. I just verified this. For a test
>app I have, I entered
>
>/F procname,how now brown cow
>
how about:
/F procname,How now, Brown Cow
(multiple spaces?)
>And verified that what the application received in the CIB was
>
>HOW NOW BROWN COW
>
Who forces upper case? What If I want:
/F procname,PATH: /dev/null
>What a given application might choose to do with that is entirely up to that
>application, of course. No MVS-generic documentation is possible. (Other than
>"your results may vary.")
>
That's proper provided that the application's documentation
specified the behavior, even as the JCL Ref. doesn't specify
every program's interpretation of PARM.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
