>Thanks for doing IBM's documentation for them. <g>
I'm sure we all thank the posters for the clarifications and suggestions,
but better would be for this information to be sent in by you as a
suggestion.
It is rarely helpful just to say that a section is bad (or to complain
only in this venue), but often it is very helpful to point out just what
is bad and/or missing.
A question was raised why IARCP64 appears the same in the unauthorized and
authorized books: the general intent is that the authorized books contain
interfaces available to authorized programs (whether they are also
available to unauthorized programs or not). So for a service that has no
authorized-only components, it's quite understandable for the two books to
be the same.
That isn't to say that the books fully accomplish that intent.
Regardless, for IARCP64, the "minimum authorization" section does identify
the areas that could/should be different (i.e., that require
authorization) But the non-authorized book for whatever reason does not
omit those things (but certainly could and quite possibly should).
>,EXPAND=NO
> This parameter does not try expanding.
Of course it would have been less misleading if a more complete snippet
were shown. While no one could successfully argue that "this parameter
does not try expanding" is other than horrible (and EXPAND=YES not
surprisingly is similar), I'll bet every reader of this section would have
no difficulty in understanding the complete section for EXPAND:
,EXPAND=YES
,EXPAND=NO
When REQUEST=GET is specified, a required parameter that indicates
whether to attempt expanding the pool if there is no available cell.
,EXPAND=YES
This parameter tries expanding.
,EXPAND=NO
This parameter does not try expanding.
(and, yes, if it had said "This parameter indicates to try expanding" /
"This parameter indicates not to expand" it would certainly have been
better. Many chapters would have omitted "This parameter" but this chapter
appears to like that style, even if not implemented well)
>Apparently nada in the Services Guide. No overview. No usage. The example
>in the reference is just a rehash of the parameters.
What guidance would you want? This is quite a simple service. What would
you want it to say that is not appropriate to place directly in the
reference? If there is other information missing from the parameter
sections then please bring them up. I'm sure we have all been in the
position of being too familiar with something to be able to spot some
simple errors (especially errors of omission). Description of the extent
size is, as has been mentioned, a rather significant omission.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
