Lockshot refers to making a virtual processor temporarily class 0 if it is holding a critical z/VM Control Program resource, typically a system lock. Since most system locks of that nature are held for very short periods of time, it isn't very common.
Hotshot refers to making a virtual processor temporarily class 0 due to certain interactions (issuing CP command). It's very short lived and doesn't really allow the virtual machine a long term advantage. I seem to recall, that when going back to eligible list after a hotshot, there is a small penalty, but not positive. Some of this shows up in monitor data. Or in the INDICATE QUEUES EXP command. Normally, I'd look something like the following from the command: BITNER Q1 R00 00002531/00002510 .I.. -.1308 A00 The first character of the cryptic 4 characters after the estimated working set size is the key. It will be an 'L' for LOCKSHOT and 'H' for 'HOTSHOT': BITNER Q0 R00 00002531/00002510 LI.. -.1308 A00 BITNER Q0 R00 00002531/00002510 HI.. -.1308 A00 I also remembered there is a fourth case that the virtual machine is treated as Class 0. When the virtual machine is in process of logging off, it is treated like class 0 as there is no reason to delay it freeing up resources. Bill Bitner - z/VM Customer Focus and Care - IBM Endicott - 607-429-3286
