z/OS MVS Programming: Workload Management Services
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Restrictions

z/OS MVS Programming: Workload Management Services
SC34-2663-00

Restrictions

  1. The Connect token from the input classify parameter list must be owned by the current home address space and must be associated with a system key (0-7), as specified on IWMCONN. The Classify parameter list and hence the Connect token is only relevant for TYPE=INDEPENDENT enclaves.
  2. Since this service may only be used by system-like code, some validity checking on the parameter list is not performed. These checks would only be needed if the macro were not used to invoke the service routine.
  3. The variable length fields associated with the classify parameter list (the classify parameter list is only relevant for certain options) given by the CLSFY keyword have the following limitations in addition to those documented in IWMCLSFY:
    • SUBSYSPM is limited to 255 bytes
    • COLLECTION is limited to 18 bytes
    • CORRELATION is limited to 12 bytes
  4. When TYPE(MONENV) is specified the following apply:
    • If the key specified on IWMMCREA was a user key (8-F), then primary or home addressability must exist to the performance block IWMMCREA obtained. This condition is satisfied by ensuring that the current primary or home address space matches primary (=home) at the time that IWMMCREA was invoked.
    • The caller must serialize to prevent any delay monitoring services from being invoked concurrently for the environment represented by the monitoring token.
    • Only limited checking is done against the input monitoring token.
    • TYPE=MONENV enclaves cannot be created for report-only monitoring environments.
  5. This macro may only be used on z/OS® R2 or higher levels for EXSTARTDEFER keyword.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014