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


Services for Work Managers that Distribute Work Requests

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

Services for Work Managers that Distribute Work Requests

Some work managers distribute work across systems in a sysplex. Distributed work may originate from one subsystem work manager, and be processed by another. For example, a work manager may send work to a data base manager for processing. Other work managers may split up complex work into smaller pieces and distribute the pieces to other systems in the sysplex for processing.

Whether the work is distributed, or split and distributed, you may still want to keep the work classified according to the subsystem originating the work request. Not all classification information may be available to the receiving subsystem. For example, suppose JES has distributed a batch job to a data base system. The data base system issues IWM4CLSY when it receives the batch job. Because it is not the same subsystem environment, the batch job is now classified into a service class representing the data base work, and not to a service class representing batch jobs.

A work manager can use the IWMWMCON macro when it receives work and wants it to be classified using the originator's subsystem environment, and not its own. The IWMWMCON macro lets a caller modify the subsystem type and subsystem name previously provided on the IWM4CON macro.

Once the receiving subsystem has issued the IWMWMCON macro, the subsystem can issue the IWM4CLSY macro. The work is then classified according to the modified environment. Note that any other macro that requires subsystem name, subsystem type, or service class name is affected by the change. Those macros are:

For details on the IWMWMCON macro, see IWMWMCON macro — WLM Modify Connect service.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014