> The only difference I see is that SQL has a repeat arrow; but that should > make no difference > or if it does then shouldn't the HOW TO explain it?
The intention is to show that for the SQL stage you can specify a number of options with no specified order. Additional rules (like what happens when you use the same option more than once or specify both conflicting options) is not show in the syntax diagram, but only in the text. The other z/VM books tend to have syntax diagrams in horizontal style that specify a specific order of the options, and the explanatory text then says that the order is free. The vertical style is often more compact when viewed online. As you conclude from the picture, the default for the SQL stage is as if the COMMIT option were specified. This is indicated by putting above the main track. I believe for consistency there should also have been a straight line under the COMMIT to show the case when you don't specify any of these options. And it would probably have to show the default NOINDICATORS above the line as well. Plus the default value for PGMOWNER. I'm not a big fan of showing the default in the syntax diagram like this. In many cases the default is more subtle, and you can't avoid having to read the text to understand what to do. Feedback on the documentation has not yet encouraged us to make major documentation changes just for the sake of consistency in either direction. > CASE 2: Some diagrams include a character in the repeat arrow e.g. > <,+ > This is not explained in the HOW TO. When there is a character in the repeat arrow, it specifies the separator that you put between the repetitions. Like a list of identifiers, separated by commas. If you find places where the documentation is unclear or should be improved, I am more than happy to assist. Sir Rob the Plumber
