According to Steve Cole: > > Dave, > > I've performed extensive tests on the Workload Manager and found > it to work as documented. It provides the ability to set up additional > queues, restrict CPU access for some processes while guaranting > CPU to others. I would not recommend it on small to medium > systems but it will work well on large MP systems. > Steve, what (these days) *is* a "large" HP3000 system? I used to think that anything larger that a 949 was a "large" system (more than 100 users), then it seems like it was a system with a "6" or larger as the middle digit. Today, a case could be made that the only large systems are multi-cpu systems or those with two cabinets (and I'm not talking about DTC cabinets). What did you mean my "large" and is a 967 "large"? In fact, why would you not recommend it for smaller systems? I recall a program that used to hog the cpu whenever it would run (interactive queue) and I wished for an easy way to limit this effect without rearranging all of the queues and other processes - wouldn't the workload manager assist with a problem like that even on a small system? -- -- - - - Speaking for myself and not necessarily anybody else - - - - - - Richard Gambrell | Internet: [log in to unmask] Mgr. Tech. Services | POT: 504-483-7454 FAX: 504-482-1561 Xavier University of LA | Smail: 7325 Palmetto, New Orleans, LA 70125