Restrictions

1. 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.
2. 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.
3. When FUNCTION(CONTINUE|RETURN) are used, the caller is responsible for error recovery
4. 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 IWMMXFER or IWMMSWCH) to another (or other) dependent monitoring environment(s).
5. Both monitoring environments must be established on the same MVS™ image.
6. The caller must serialize to prevent any delay monitoring services from being invoked concurrently for the dependent monitoring environment.
7. The caller and/or the owner of the parent environment must ensure that parent environment is not deleted while between the time that IWMMXFER FUNCTION(CONTINUE) is used and the time that either IWMMXFER FUNCTION(RETURN) is used against the dependent monitoring environment OR IWMMSWCH FUNCTION(RETURN) is used against the parent monitoring environment.
8. Only limited validity checking is done on the input monitoring tokens.
9. This macro supports multiple versions. Some keywords are only supported by certain versions. Refer to the PLISTVER parameter description for further information.