|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Inconsistency in command syntax scanning between platforms |
« View previous topic :: View next topic » |
Author |
Message
|
mqjeff |
Posted: Mon Feb 08, 2010 2:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I guess I see what you're getting at, FJ. But the question is, if on zOS, the secondary parameter doesn't have to be second, what positions are forbidden to it? The only one clearly disallowed is first. And if no position other than the first is forbidden, then clearly it can appear anywhere else.
Unless you were trying to argue that the object name is not a corresponding value to the secondary parameter? I.e. that you could specify "DEF REPLACE QL LIKE(Q2) (Q1)", or "DEF REPLACE (Q1) LIKE(Q2) QL" instead of having to couple "QL" with "(Q1)"? I'm sure that both would fail.
I believe the intent of the language is to say that on zOS, the secondary parameter and it's value can appear at any location following the primary one. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Feb 09, 2010 10:02 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20763 Location: LI,NY
|
I was getting to a metasyntax that would only allow significant changers and not simple parameters.
Like
Simple = def ql(x) ...
easy = def replace ql(x) ...
complex2 = def replace like (y) ql(x) ...
complex1 = def like(y) ql(x) [replace] ...
So only a select few things would be allowed to precede the ql(x) ...
def defpersist(yes) ql(x) would not be authorized as defpersist is a parm and not a significant changer...
So yes the ql(x) does not HAVE to be in 2nd position but it is not allowed at random anywhere in the definition either... and certainly not after the parameters...
But then I am maybe going ahead of doctrine there...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Feb 09, 2010 11:36 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9475 Location: US: west coast, almost. Otherwise, enroute.
|
I parse; therefore, I am. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Feb 10, 2010 3:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
fjb_saper wrote: |
I was getting to a metasyntax that would only allow significant changers and not simple parameters.
Like
Simple = def ql(x) ...
easy = def replace ql(x) ...
complex2 = def replace like (y) ql(x) ...
complex1 = def like(y) ql(x) [replace] ...
So only a select few things would be allowed to precede the ql(x) ...
def defpersist(yes) ql(x) would not be authorized as defpersist is a parm and not a significant changer...
So yes the ql(x) does not HAVE to be in 2nd position but it is not allowed at random anywhere in the definition either... and certainly not after the parameters...
But then I am maybe going ahead of doctrine there...  |
It's a great idea. It's not apparently how it's documented, nor how it's implemented. |
|
Back to top |
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|