Restrictions

1. If the key specified on IWM4CON was a user key (8-F), then the following must ALL be true:
   • caller must be in non-cross-memory mode (P=S=H). This implies that the current primary must match the primary at the time that IWM4CON was invoked. Running in a subspace is not supported.
   • must be in TCB mode (not SRB)
   • current TCB must match the TCB at the time that IWM4CON was invoked.
2. It is the caller's responsibility to serialize use of this service with use of IWMCLSFY and other services using the connect token. Failure to do so may result in classification to a service and/or report class which is other than the intended one.
3. This service should not be invoked while in a RTM termination routine (resource manager) for the TCB owning the connect token since MVS will have its own resource cleanup routine and unpredictable results would occur. It is legitimate to use this service while in a recovery routine, however, or in mainline processing.