PK65667: HIGH CPU USE WITH COIR IF MANY (THOUSANDS) OF TASKS QUEUED FOR MXT OR TCLASS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• COIR CPU utilization may be high if definitions against
  task-related tables are installed and a large number of tasks
  are queued due to MXT or TCLASS.
  
  Additional Symptom(s) Search Keyword(s): MAXTASK TRANCLASS
  KIXREVRJL
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex/SM V3R1M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: API and WUI requests for data from the  *
  *                      TASK, TASKRMI, TASKFILE, TASKTSQ, and   *
  *                      TASKESTG tables for a MAS may take a    *
  *                      long time to complete if the MAS has a  *
  *                      large number of tasks queued for        *
  *                      MAXTASKS or TRANCLASS MAXACTIVE.        *
  ****************************************************************
  * RECOMMENDATION: If the CPSM environment contains CMASes and  *
  *                 MASes at both the CPSM V3R1M0 and V3R2M0     *
  *                 levels, then before applying the PTF that    *
  *                 resolves this APAR and restarting V3R1M0     *
  *                 CMASes and MASes, the PTF that resolves APAR *
  *                 PK65553 must be applied to the V3R2M0 CMASes *
  *                 and MASes.                                   *
  *                                                              *
  *                 After applying the PTF that resolves this    *
  *                 APAR, all CMASes, MASes and WUI servers must *
  *                 be restarted with the updated code.          *
  *                                                              *
  *                 The restarts need not be performed at the    *
  *                 same time, however if systems are not        *
  *                 restarted at the same time, the following    *
  *                 rules apply:                                 *
  *                                                              *
  *                 - Maintenance point CMASes must be restarted *
  *                   before non Maintenance point CMASes, MASes *
  *                   and WUI Servers.                           *
  *                                                              *
  *                   If you have more than one Maintenance      *
  *                   point CMAS and those Maintenance point     *
  *                   CMASes are connected directly or           *
  *                   indirectly, then those maintenance point   *
  *                   CMASes must be restarted at the same time. *
  *                                                              *
  *                 - Before a MAS or WUI server is restarted,   *
  *                   the CMAS to which the MAS or WUI server    *
  *                   connects must be restarted.                *
  *                                                              *
  *                 Once a WUI server has been restarted, then   *
  *                 users of the CICSPlex SM supplied starter    *
  *                 set viewsets and menus must re-import the    *
  *                 starter set viewset and menu definitions     *
  *                 into each Web User Interface (WUI) server's  *
  *                 repository in order to pick up the changes.  *
  *                                                              *
  *                 The starter set viewsets and menus can be    *
  *                 re-imported either via the AUTOIMPORTTDQ WUI *
  *                 server initialization parameter or the       *
  *                 IMPORT function of the COVC WUI transaction. *
  *                 If COVC is used to re-import the starter     *
  *                 set, ensure that the OVERWRITE import option *
  *                 is specified if the WUI server's repository  *
  *                 previously contained that starter set        *
  *                 viewsets and menus.                          *
  *                                                              *
  *                 Users who have copied the IBM supplied       *
  *                 starter set viewsets and menus to another    *
  *                 name will have to manually apply the changes *
  *                 made by the PTF that resolves this APAR to   *
  *                 those copies.                                *
  *                                                              *
  *                 For details on the AUTOIMPORTTDQ parameter   *
  *                 and the COVC IMPORT function see 'Specify    *
  *                 the Web User Interface server initialization *
  *                 parameters' and 'The CICSPlex SM Web User    *
  *                 Interface transaction (COVC)' in the "CICS   *
  *                 Transaction Server for z/OS CICSPlex SM Web  *
  *                 User Interface Guide Version 3 Release 1"    *
  *                 SM Web User Interface Guide" (SC34-6461).    *
  ****************************************************************
  When an API or WUI request for data for the TASK, TASKRMI,
  TASKFILE, TASKTSQ and TASKESTG tables is issued, all running,
  dispatchable and suspended tasks are interrogated to determine
  if they should be part of the result set.  If a great number of
  tasks are queued for MXT and/or TCLASS, the request may take a
  long time to complete.
  
  For the TASKFILE, TASKTSQ and TASKESTG tables, data is never
  displayed for tasks that are queued for MXT and/or TCLASS.
  Therefore there is no reason to interrogate queued tasks when
  processing a request for these tables.
  
  For the TASK and TASKRMI tables, data is displayed for tasks
  queued for MXT and/or TCLASS.  However, users do not have the
  ability to bypass queued tasks to improve the performance of the
  request.
  

Problem conclusion

• Changes have been made to allow requests for data from the TASK,
  TASKRMI, TASKFILE, TASKTSQ and TASKESTG tables to avoid
  processing queued tasks.
  
  For the TASK and TASKRMI tables a new user specifiable parameter
  called INCL_QUEUED has been added so that the user can indicate
  whether queued tasks should be processed.  Taking the default,
  or specifying INCL_QUEUED(YES), will cause the queued tasks to
  be processed.  Specifying INCL_QUEUED(NO) will cause queued
  tasks to be bypassed.
  
  For the TASKFILE, TASKTSQ and TASKESTG tables, all queued tasks
  will automatically be bypassed, as they will never result in
  data being added to the result set.
  
  To effect this change, the following updates have been made:
  
  -  the TASK and TASKRMI resource tables have been updated to
     include the new INCL_QUEUED parameter.
  
  -  the parameter lists for methods EYU0NQTK (NQTK) and EYU0NQGR
     (NQGR) have been updated to include the new INCL_QUEUED
     parameter.
  
  -  NQTK, which is called when a TASK request is issued, has been
     updated to determine if the INCL_QUEUED parameter has been
     specified, and if so, to propagate it to the NQGR parameter
     list when calling NQGR as part of the TASK request.
  
  -  method EYU0NQK3 (NQK3), which is called by NQGR to build a
     list of tasks to process for requests for the TASK, TASKRMI,
     TASKFILE and TASKTSQ tables, has been updated as follows:
  
     -  for the TASK and TASKRMI tables, NQK3 will use the setting
        of the INCL_QUEUED parameter in the NQGR parameter list
        passed to it to determine whether to include queued tasks
        in the list of tasks to process.
  
     -  for the TASKFILE, TASKTSQ and IPFACIL tables, NQK3 will
        not include queued tasks in the list of tasks to process.
  
  -  method EYU0NCL4 (NCL4), which is called to process the
     TASKESTG table, has been updated to not process queued tasks.
  
  -  the distributed starter set viewset for the TASK table has
     been updated to include the new INCL_QUEUED parameter as a
     filter in the tabular view.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

• API and WUI requests for data from the
  TASK, TASKRMI, TASKFILE, TASKTSQ, and
  TASKESTG tables for a MAS may take a
  long time to complete if the MAS has a
  large number of tasks queued for
  MAXTASKS or TRANCLASS MAXACTIVE.
  
  
  When an API, WUI or RTA request for data for the TASK, TASKRMI,
  TASKFILE, TASKTSQ and TASKESTG tables is issued, all running,
  dispatchable and suspended tasks are interrogated to determine
  if they should be part of the result set.  If a great number of
  tasks are queued for MXT and/or TCLASS, the request may take a
  long time to complete.
  
  For the TASKFILE, TASKTSQ and TASKESTG tables, data is never
  displayed for tasks that are queued for MXT and/or TCLASS.
  Therefore there is no reason to interrogate queued tasks when
  processing a request for these tables.
  
  For the TASK and TASKRMI tables, data is displayed for tasks
  queued for MXT and/or TCLASS.  However, users do not have the
  ability to bypass queued tasks to improve the performance of the
  request.
  
  
  Changes have been made to allow requests for data from the TASK,
  TASKRMI, TASKFILE, TASKTSQ and TASKESTG tables to avoid
  processing queued tasks.
  
  For the TASK and TASKRMI tables a new user specifiable parameter
  called INCL_QUEUED has been added so that the user can indicate
  whether queued tasks should be processed.  Taking the default,
  or specifying INCL_QUEUED(YES), will cause the queued tasks to
  be processed.  Specifying INCL_QUEUED(NO) will cause queued
  tasks to be bypassed.
  
  For the TASKFILE, TASKTSQ and TASKESTG tables, all queued tasks
  will automatically be bypassed, as they will never result in
  data being added to the result set.
  
  To effect this change, the following updates have been made:
  
  -  the TASK and TASKRMI resource tables have been updated to
     include the new INCL_QUEUED parameter.
  
  -  the parameter lists for methods EYU0NQTK (NQTK) and EYU0NQGR
     (NQGR) have been updated to include the new INCL_QUEUED
     parameter.
  
  -  NQTK, which is called when a TASK request is issued, has been
     updated to determine if the INCL_QUEUED parameter has been
     specified, and if so, to propagate it to the NQGR parameter
     list when calling NQGR as part of the TASK request.
  
  -  method EYU0NQK3 (NQK3), which is called by NQGR to build a
     list of tasks to process for requests for the TASK, TASKRMI,
     TASKFILE and TASKTSQ tables, has been updated as follows:
  
     -  for the TASK and TASKRMI tables, NQK3 will use the setting
        of the INCL_QUEUED parameter in the NQGR parameter list
        passed to it to determine whether to include queued tasks
        in the list of tasks to process.
  
     -  for the TASKFILE, TASKTSQ and IPFACIL tables, NQK3 will
        not include queued tasks in the list of tasks to process.
  
  -  method EYU0NCL4 (NCL4), which is called to process the
     TASKESTG table, has been updated to not process queued tasks.
  
  -  the distributed starter set viewsets for the TASK table has
     been updated to include the new INCL_QUEUED parameter as a
     filter in the tabular view.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK65553

• APAR is sysrouted TO one or more of the following:

  UK40190

Modules/Macros

•    DYU0MOM2 EYU#NQGR EYU#NQTK EYUA0020 EYUA0145
  EYUCNQGR EYUCNQTK EYUC0020 EYUC0145 EYUEVX01 EYUE0020 EYUE0145
  EYUKVX01 EYUK0020 EYUK0145 EYUL0020 EYUL0145 EYUNNQGR EYUNNQTK
  EYUN0020 EYUN0145 EYUP0020 EYUP0145 EYUQNQGR EYUQNQTK EYURNQGR
  EYURNQTK EYUR0020 EYUR0145 EYUSVX01 EYUS0020 EYUS0145 EYUTRMAS
  EYUT0020 EYUT0145 EYUYNQGR EYUYNQTK EYUY0020 EYUY0145 EYUZNQGR
  EYUZNQTK EYU0MOM2 EYU0NCL4 EYU0NQGR EYU0NQK3 EYU0NQTK EYU0PAEC
  EYU9NAPU EYU9NAP3 EYU9NAP4 EYU9NAP5 TASK     TASKRMI
  

Fix information

• Fixed component name

  CPSM CICS 3.1

• Fixed component ID

  5655M1501

Applicable component levels

• R100 PSY UK40190

     UP08/09/30 P F809

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.