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


Considerations Before Using the Services

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

Considerations Before Using the Services

Before you use the subsystem work manager and the execution delay monitoring services, you should consider the following:

  • What “type” of subsystem work manager you are.
    • Transaction processing system
    • Data or resource manager
  • What benefits do you expect to reap from using the WLM services?
    • Do you want your customers to be able to specify goals for your transactions?
    • Do you plan on getting reporting information on goals defined in the MVS™ workload management service definition?
  • What kinds of address spaces does the subsystem work manager consist of?
  • What is the definition of a transaction or work request, from your customer's perspective?
  • What kind of functions do the address spaces provide?
    • Control address spaces?
    • Transaction level dispatching?
    • Other execution regions?
    • Other supporting address spaces?
  • What environments does the subsystem work manager run in?
    • Authorization, including PSW key
    • Dispatchable unit mode
    • Cross memory mode
    • AMODE
    • ASC mode
    • Interrupt status
    • Locks
  • Does the subsystem work manager use other products, such as a data manager?
  • Does the work cross MVS system (MVS image) boundaries?
  • Does the work cross MVS sysplex boundaries?

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014