Restrictions
- If the key specified on IWM4MCRE for the dependent monitoring
environment was a user key (8-F), then primary addressability must
exist to the performance block IWM4MCRE obtained. This condition
is satisfied by ensuring that current primary matches primary at the
time that IWM4MCRE was invoked. If this service is invoked in a subspace,
the condition may be satisfied by ensuring that the performance block
is shared with the base space.
- If the key specified on IWM4MCRE for the parent environment was
a user key (8-F), then either primary OR secondary addressability
must exist to the performance block for the parent environment.
- When FUNCTION(CONTINUE|RETURN) are used, the caller is responsible
for error recovery
- When FUNCTION(CONTINUE) is used, the caller is responsible to
ensure that the parent monitoring environment does not already have
a continuation (via a previous IWM4MXFR or IWM4MSWC) to another (or
other) dependent monitoring environment(s).
- Both monitoring environments must be established on the same MVS
image.
- The caller must serialize to prevent any delay monitoring services
from being invoked concurrently for the dependent monitoring environment.
- The caller and/or the owner of the parent environment must ensure
that parent environment is not deleted while between the time that
IWM4MXFR FUNCTION(CONTINUE) is used and the time that either IWM4MXFR
FUNCTION(RETURN) is used against the dependent monitoring environment
OR IWM4MSWC FUNCTION(RETURN) is used against the parent monitoring
environment.
- Only limited validity checking is done on the input monitoring
tokens.
- This macro may only be used on z/OS V2R1 or higher.
|