Programming Requirements

1. You must include the IWMYCON mapping macro in the calling program.
2. If the key specified on IWM4MCRE for the input MONTKN was a user key (8-F), then the following must be true:
   • If you specify PARENTP=YES, then:
     • Primary addressability must exist to the performance block IWM4MCRE obtained (represented by the input MONTKN). You could do this 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.
     • You cannot specify the list form of this macro. With PARENTP=YES, IWMMRELA produces an inline expansion rather than an out-of-line service, so you do not need a parameter list. Registers 0, 1, 14, and 15 are not preserved across the expansion.
   • If you specify PARENTP=FINDACTIVE, then the caller must be in non-cross-memory mode (PASN=SASN=HASN). That is, the current primary (and home) must match the primary (and home) at the time that IWM4MCRE was invoked.
3. 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 monitoring environment for the parent environment.
4. Both monitoring environments must be established on the same MVS™ image.
5. The caller must serialize to prevent any delay monitoring services from being invoked concurrently for the monitoring environment.
6. When PARENTP=YES, the caller must provide recovery.