There are several SRM/WLM options that allow you to control how work is assigned between zAAPs and standard CPs. Java-eligible work that could execute on zAAPs may also execute on standard CPs in order to achieve workload goals.
In parmlib member IEAOPTxx, there are two statements which control the workflow to zAAPs. The default values will allow both zAAPs and standard CPs to be used for receiving zAAP-eligible work, as well as dispatching both zAAP-eligible and non-zAAP-eligible work in priority order.
IFAHONORPRIORITY: If you specify IFAHONORPRIORITY=YES (the default) in IEAOPTxx, you indicate that standard CPs may execute both Java™ and non-Java work in priority order, if zAAP processors are unable to execute all zAAP-eligible work.
If you specify IFAHONORPRIORITY=NO, then zAAP-eligible work can execute on standard CPs, but at a lower priority than non-Java work.
Refer to z/OS MVS Initialization and Tuning Reference for more information on the parmlib member IEAOPTxx.