On Mon, 31 Aug 2015 18:14:10 -0400, Joseph W Gentile wrote:
>I think the description of RNAME= in the ISGENQ macro doc is more clear. I
>could potentially use the wording in the last sentence "The RNAME must be
>from 1 to 255 bytes long, and can contain any hexadecimal character from
>X'00' to X'FF'" to update the ENQ rname_addr doc. What do you think? Also,
>I encourage you to check out the newer ISGENQ macro, in case it has
>features you might find useful.
>
Much better. Thanks. In:
z/OS 2.1.0>z/OS MVS>z/OS MVS Planning: Global Resource Serialization>Global
Resource Serialization>Introduction>ISGENQ macro
I also see:
...
ISGENQ includes parameter checking to ensure that authorized callers use
authorized qnames.
...
I'd prefer:
"ISGENQ includes parameter checking to ensure that *only* authorized
callers use authorized
qnames." As it stands, it seems to imply that authorized callers are
restricted to using authorized
qnames (I suppose that may be true) and non-authorized callers are not so
restricted.
...
REQUEST=CHANGE Change the status of an ISGENQ request from shared to
exclusive.
...
Doesn't z/OS 2.1 also support changing from exclusive to shared?
Want an RCF (or two)?
Thanks again,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
