You can determine the resulting scope of your ISGENQ request and
what caused any scope change to take place by using one or both of
the ISGQUERY and ISGENQ REQUEST=TEST services. Use these services
to insure that the resulting scope is correct for the current configuration
of your product. For RNL=YES requests, the scope can change by the
RNL or installation exit.
Note that alternate serialization products use installation exits
to control the scope that global resource serialization uses. For
example, an alternate serialization product can extend the scope such
that it would indicate to global resource serialization that the scope
should be local so it could extend it to its global scope. This scope
might be larger than the global resource serialization complex. You
can check the following ISGQUERY output fields related to an ISGQUERY
of the interested resource to determine if its scope is global:
- Is ISGYQUAARqxAltSerExtended on? This indicates that it is globally
managed by an alternate serialization product.
- Is ISGYQUAARSSCOPE=ISGYQUAA_kSYSTEMS or ISGYQUAA_kSYSPLEX on?
This indicates that it is globally managed by global resource serialization.
You can use various fields within the ISGYQUAA mapping to determine
what caused the scope to be altered.
You can test what the potential resulting scope of an ISGENQ REQUEST=TEST
request for resource would be by checking the following ISGYENQ fields:
- Is ISGYENQAAALTSEREXTENDED on? This indicates it would be globally
managed by an alternate serialization product.
- Is ISGYENQAAFinalScope=ISGENQ_SYSTEMS on? This indicates that
it would be globally managed by global resource serialization.
You can use various fields within the ISGYENQ mapping to determine
what caused the scope to be altered.