On Fri, 18 Jul 2025 12:02:45 +0000, Seymour J Metz <[email protected]> wrote:
>"that tells you it's a non-repeatable choice which is very different from
>mutually exclusive."
> is total BS.
Again, comments without any supporting facts. It's only been a couple weeks
since your last non-sense wasted my time.
Mutually exclusive would issue an error message. I asked Gemini AI "what
happens to conflicting parms in tso commands?" which came back with the correct
answer.
In TSO (Time Sharing Option) commands on IBM mainframes, when you specify
conflicting parameters, the general rule is that the last specified parameter
for a given attribute takes precedence. This means the system will use the
value provided by the parameter that appears latest in the command string,
overriding any earlier, contradictory specifications for the same attribute.
For example, if a command allows you to specify a file's disposition as either
NEW or OLD, and you type:
ALLOCATE DSN('MY.FILE') NEW OLD
The OLD parameter would typically override NEW because it's the last one
encountered.
> There is no path from the opening double arrow to the closing double arrow
> that goes through both.
Gemini also responded with: This is a common design pattern in command-line
interfaces.
Those arrows indicate conflicting parms but nothing about how conflicting parms
are handled.
> Eunix is a red herring.
Unix is relevant because it too has commands but is inconsistent on how
conflicting parms are handled. TSO command parser consistently handles parms.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
