A fix is available
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 V3R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: API, WUI and RTA requests for data from * * the TASK, TASKRMI, TASKFILE, TASKTSQ, * * TASKESTG and IPFACIL 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: After applying the PTF that resolves this * * APAR, all CMASes, MASes and WUI servers must * * be restarted. 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 these 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 * * updated starter set MAS viewset into the WUI * * server's repository in order to pick up the * * changes. * * * * The MAS viewset can be re-imported either * * via the AUTOIMPORTDSN and AUTOIMPORTMEM WUI * * server initialization parameters or the * * IMPORT (from a dataset) function of the COVC * * WUI transaction. * * * * If COVC is used to re-import the viewset, * * ensure that TYPE operand is set to ALL or * * VIEWSET, and that the Import option is set * * to OVERWRITE. * * * * For details on the AUTOIMPORTDSN and * * AUTOIMPORTMEM WUI server initialization * * parameters see 'Specify the Web User * * Interface server initialization parameters' * * in the "CICS Transaction Server for z/OS * * Installation Guide Version 3 Release 2" * * (GC34-6812). * * * * For details on the COVC IMPORT function see * * '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 2" * * (SC34-6841). * * * * The updated starter set viewset names that * * need to be imported are: * * * * TASK ViewSet : EYUxA00K * * TASKRMI ViewSet : EYUxA041 * * EVALDEF ViewSet : EYUxA260 * * * * Replace x with the required language version * * to be imported: E - English, K - Japanese, S * * - Chinese. * * * * Insure that the import references the * * SEYUVIEW dataset that was updated by the PTF * * that resolves this APAR. * * * * * * Finally, all non-REXX CPSM API programs that * * include the EVALDEF resource table copybook * * must be re-compiled or re-assembled to pick * * up the changes to the EVALDEF copybook. * * Ensure that the compile or assembly JCL * * points to the copybook libraries updated by * * the PTF that resolves this APAR. * * * * REXX CPSM API programs that reference the * * EVALDEF resource table with a constant * * length value must be changed to specify the * * new length. * **************************************************************** When an API, WUI or RTA request for data for the TASK, TASKRMI, TASKFILE, TASKTSQ, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKTSQ and IPFACIL 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 and TASKRMI tables have been updated to include the new INCL_QUEUED parameter as a filter in the tabular views. - the EVALDEF resource table has been updated to include a new attribute, EVALDEF_GETPARMS, where user specified get parameters can be specified for RTA supported tables. Users can use this new attribute to specify the new INCL_QUEUED parameter for the TASK and TASKRMI tables. - method EYU0PAEC (PAEC), which is called to create and update EVALDEFs, has been updated to process the EVALDEF_GETPARMS attribute. If the data is valid for the table, the EVALDEF will be created or updated. If the data is not valid for the table, the create or update will be failed with a status of INVALID_GETPARMS. - method EYU0PECD (PECD), which is called to install EVALDEFs, has been updated to include the EVALDEF_GETPARMS in the get request for the table associated with the EVALDEF. - the distributed starter set viewset for the EVALDEF table has been updated to include the new EVALDEF_GETPARMS attribute. The attribute will be an input field in the create and update displays, and will be an output field in the browse display.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
API, WUI and RTA requests for data from the TASK, TASKRMI, TASKFILE, TASKTSQ, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKESTG and IPFACIL 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, TASKTSQ and IPFACIL 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 and TASKRMI tables have been updated to include the new INCL_QUEUED parameter as a filter in the tabular views. - the EVALDEF resource table has been updated to include a new attribute, EVALDEF_GETPARMS, where user specified get parameters can be specified for RTA supported tables. Users can use this new attribute to specify the new INCL_QUEUED parameter for the TASK and TASKRMI tables. - method EYU0PAEC (PAEC), which is called to create and update EVALDEFs, has been updated to process the EVALDEF_GETPARMS attribute. If the data is valid for the table, the EVALDEF will be created or updated. If the data is not valid for the table, the create or update will be failed with a status of INVALID_GETPARMS. - method EYU0PECD (PECD), which is called to install EVALDEFs, has been updated to include the EVALDEF_GETPARMS in the get request for the table associated with the EVALDEF. - the distributed starter set viewset for the EVALDEF table has been updated to include the new EVALDEF_GETPARMS attribute. The attribute will be an input field in the create and update displays, and will be an output field in the browse display.
APAR Information
APAR number
PK65553
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
50M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-05
Closed date
2008-09-25
Last modified date
2008-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK65667 UK40227
Modules/Macros
EVALDEF EYU#NQGR EYU#NQTK EYUA0020 EYUA0145 EYUA2808 EYUCNQGR EYUCNQTK EYUCPAEC EYUC0020 EYUC0145 EYUC2808 EYUEA00K EYUEA041 EYUEA260 EYUE0020 EYUE0145 EYUE2808 EYUKA00K EYUKA041 EYUKA260 EYUK0020 EYUK0145 EYUK2808 EYUL0020 EYUL0145 EYUL2808 EYUNNQGR EYUNNQTK EYUP0020 EYUP0145 EYUP2808 EYUQNQGR EYUQNQTK EYUQPAEC EYURNQGR EYURNQTK EYURPAEC EYUR0020 EYUR0145 EYUR2808 EYUSA00K EYUSA041 EYUSA260 EYUS0020 EYUS0145 EYUS2808 EYUTRMAS EYUTRRTA EYUT0020 EYUT0145 EYUT2808 EYUYNQGR EYUYNQTK EYUYPAEC EYUY0020 EYUY0145 EYUY2808 EYUZNQGR EYUZNQTK EYUZPAEC EYU0NCL4 EYU0NQGR EYU0NQK3 EYU0NQTK EYU0PAEC EYU0PECD EYU9NAPU EYU9NAP3 EYU9NAP4 EYU9PSPU EYU9PSP3 EYU9PSP4 EYU9XDU2 TASK TASKRMI
| SC34684201 | SC34685001 |
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R50M PSY UK40227
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 October 2008