Could it be APAR OA33407? **************************************************************** * PROBLEM DESCRIPTION: High CPU usage for output device PCEs, * * such as SAPI PCEs, when selecting work * * with user routing. * **************************************************************** * RECOMMENDATION: * **************************************************************** The WSROUT routine in HASPSERV is not distinguishing between a real JOE and an artificial JOE (JOA). So it incorrectly determines for a JOA that it cannot utilize the user routing information to do work selection, so significantly more devices are posted than should be. When the device attempts to do work selection it cannot find JOEs that match. This incorrect processing results in excessive CPU usage. This problem affects the following output devices when they select work with user routing: printers, punches, SYSOUT transmitters, and SYSOUT API (SAPI).
Greg Shirey Ben E. Keith Company ----- Original Message ----- From: "Cobe Xu" <cob...@gmail.com> To: IBM-MAIN@bama.ua.edu Recently, we have a problem when sending large amount spool files (about 2.5 million lines) to RJE printer, as the work caused JES2 consumes lots of CPU, therefore impacted the CICS online performance. We consider to limit JES2 address space CPU, using WLM resource group, but this will suppress other JES2 process as well. So, any idea to limit RJE work only? Thanks a lot! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
