@Peter, the example I quoted came from https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieag100/m3modaxr.htm . (Hope that survives the wrap.)
I was *actually* working from the V2R1 docs (because I am a stick in the mud and prefer BookManager to the unreliable Knowledge Center). I see IBM has now improved the wording. While V2R1 only shows the syntax I quoted, the V2R4 that I cite above permits and shows both SR,STATUS and SR STATUS. (The V2R1 doc was adequate to my point: it is sufficient to show that my perception of "no blanks allowed" was incorrect.) Thanks for asking. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Relson Sent: Thursday, February 11, 2021 6:25 AM To: [email protected] Subject: Re: Datasets with - in HLQ Curtis P wrote <snip> On Feb 10, 2021, at 3:27 PM, Charles Mills <[email protected]> wrote: > > I guess blanks are legal in a MODIFY command operand. I see an example in the manual: F AXR,SYSREXX STATUS > > I did not know that. > I believe that the console address space handles modify commands by sticking everything after the comma into a buffer and passing that to the referenced job. Then it’s up to the receiving code to decide how to parse it. </snip> Curtis is correct. Many command processors treat everything after the first blank as commentary (IEASYSxx parsing, while not a "command", has that protocol). Many of the more recent command processors treat blank the same as comma. HOWEVER, the doc in the book is atypical and will be changed. The intent is that the doc for commands shows the syntax style typical for commands (e.g., comma separators, KEYWORD=value notation) while the doc for parmlib members shows the syntax style typical for parmlib members (blank separators, KEYWORD(value) notation), even if they might happen to support both styles (as the SETPROG command and the PROGxx parmlib member do). Charles, I found that here "z/OS 2.4.0 -> IBM z/OS Management Facility -> IZUP916E". Did you perhaps find another occurrence that we can also correct? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
