Advanced Topics › Global Data Set Integrity Facility › MIMQNAME/GDIEXMPT Processing Flowcharts › Notes on the Flowcharts

Notes on the Flowcharts

The following notes further explain items in the flow charts:

#1

Use the following table to determine if the SCOPE value you specify on the QNAME statement (row) matches the scope of the ENQ or RESERVE request (column):

#2

If a reserve request was issued and a LOCAL statement (including the DEFAULT statement) applies to this request (if it is not overridden with a GLOBAL statement), the action taken depends on GDIF EXEMPTRESERVES.

With EXEMPTRESERVES=NO, the LOCAL statement does not apply. Thus the enqueue is propagated and the reserve is either kept or converted, depending on the keyword RESERVES. See #3.

With EXEMPTRESERVES=YES, the LOCAL statement does apply, and the hardware reserve is not converted. If the request is not a reserve and a LOCAL statement applies (if it is not overridden with a GLOBAL statement), then the enqueue is not propagated.

#3

The enqueue is propagated to external systems. If this was a reserve request, then the hardware reserve is either kept or converted, depending on the keyword RESERVES.

RESERVES can be specified on the GDIINIT, QNAME, and GLOBAL statements. If specified on the QNAME statement, then this overrides anything specified on the GDIINIT statement. If specified on the GLOBAL statement, then this overrides anything specified on either the GDIINIT or QNAME statement.

#4

The default settings for a dynamically-added QNAME are:

ECMF=NO,EXEMPT=YES,GDIF=YES,REPORTAFTER=0,REPORTCYCLE=60,
SCOPE=SYSTEMS,TRACE=NONE

#5

To determine how the exempt list is searched, see How GDIF Reorders the Exempt List at Startup Time and How GDIF Matches Requests with Exempt List Statements in this chapter.