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


IWM4MINI macro — Monitor environment initialization

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

IWM4MINI macro — Monitor environment initialization

IWM4MINI allows the caller to supply MVS with some or all of the work request attributes needed for the monitoring environment. The attributes include userid, transaction name, transaction class, source LU, and LU 6.2 token.

There are three types of monitoring environments available, management monitoring environments, report-only monitoring environments and buffer pool management only environments. Management monitoring environments provide both performance management and performance reporting. Report-only monitoring environments can be used for performance reporting only. Buffer pool management only environments provide only buffer pool performance management for enclaves.

Use the REPORTONLY=YES parameter to specify the monitoring environment will be used for reporting purposes only.

If you are invoking IWM4MINI with the REPORTONLY=YES parameter, ASSOCIATE=ENCLAVE or ASSOCIATE=ADDRESS_SPACE must be specified to associate the monitoring environment with an enclave or an address space.

Use the BPMGMTONLY=YES parameter to specify the monitoring environment will be used for buffer pool management for enclaves only.

If you are invoking IWM4MINI with the BPMGMTONLY=YES parameter, ASSOCIATE=ENCLAVE must be specified to associate the monitoring environment with an enclave.

For management monitoring environments, where possible, you should invoke IWM4MINI immediately following IWMCLSFY, and pass the service class for the work request. Without the associated service class in the monitoring environment, delay information cannot be accumulated and reported accurately.

IWM4MINI can be issued multiple times for the same work request. The first time you invoke IWM4MINI for a work request, you must specify MODE=RESET, otherwise the previous work request's attributes are associated with this work request. Any subsequent time you invoke IWM4MINI from the same address space for the same monitoring token for the same work request, specify MODE=RETAIN. If the caller subsystem work manager consists of multiple address spaces (with multiple monitoring tokens), the first time IWM4MINI is invoked in each address space for a given work request must specify MODE=RESET. Any subsequent invocations for the same work request should specify MODE=RETAIN.

If you are invoking IWM4MINI for a management monitoring environment, multiple times for the same work request, only one of the invocations should specify EXSTARTTIME=exstarttime. It is up to you to decide at which point in the subsystem work manager's processing you consider the real execution start time.

Optionally with this macro, you can use the OWNER_TOKEN and OWNER_DATA parameters to specify a token for the user/owner of the monitoring environment for your own use.

Optionally with this macro, you can use the FROM_SUBSYSNM parameter to specify the subsystem name from where a request came in. This allows you to identify an address space as work provider or consumer.

Information

Note that this service was previously called IWMMINIT for 31-bit addressing only (see IWMMINIT – Initialize Monitoring Environment).

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014