Farley, Peter x23353 wrote:
Picking up on something Paul G. said in another thread, I realized I have
never known *why* the system issues JOB scope ENQ's on DSN's.
I do realize that it is most probably to avoid an ENQ "deadly embrace"
somewhere along the line, but for the life of me (well, and maybe because
it's Friday) I can't think why a DSN ENQ would be JOB scope instead of STEP
scope. At least not by default, anyway.
I've never heard of an ENQ with job scope. A quick look at the ISGENQ
service shows the following scope values:
<Doc from ISGENQ macro prolog>
SCOPE=STEP
indicates that the resource is
serialized only within an
address space. If STEP is
specified, a request for the
same Qname and Rname from a
program in another address
space denotes a different
resource.
SCOPE=SYSTEM
indicates that the resource is
serialized across all address
spaces in a system.
SCOPE=SYSTEMS
indicates that the resource is
serialized across all systems
in a GRS Star or GRS Ring
complex.
SCOPE=SYSPLEX
indicates that the resource is
serialized across all systems
in a GRS Star sysplex or GRS
ring. (Same as scope SYSTEMS.)
</Doc from ISGENQ macro prolog>
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
