MAX_PROCESSES and WLM considerations for Endevor Concurrent Action Processing and Workbench.

book

Article ID: 52173

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA PanAudit Plus CA Easytrieve Report Generator CA PAN/SQL CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM) CA 2E

Issue/Introduction

Description:

When using WLM to control the maximum number of spawned tasks on the LPAR may cause unpredictable behavior in CCI spawn processing. For other WLM considerations see the Implementation Guide.

Solution:

Consider the following sample CCI definition for Concurrent Action Processing:

********************************************************************
* CCI SERVICE STATEMENTS FOR ENDEVOR
********************************************************************
ENDEVOR        SERVICE SERVER_NAME=MVS_START_SERVER,
                   DEALLOCATE=TERMINATE,
                   LOST_CLIENT=DEALLOCATE,
                   MAX#_SERVICES=100,
                   MAX#_CLIENTS=1,
                   MAX#_PROCESSES=15,
                   SERVICE_UNAVAILABLE=START_SERVICE,
                   START=SPAWN_ONLY,
                   SIGNON/NOPASSCHK=SERVICE
********************************************************************
* CCI PROCESS STATEMENTS FOR ENDEVOR
********************************************************************
                   PROCESS PROCESS_TYPE=MVS_STC,
                   PROCNAME=ENDEVOR,
                   PARM='BC1PCPS0'

If SPAWNNMAX in C1DEFLTS is 3, and there are 10 users who submit jobs at the same time, meaning there can be up to 30 tasks running simultaneously, then by having MAX#_PROCESSES set to 15, then the maximum number of the tasks will be limited to 15.

It is not recommended to let WLM limit this number of spawned tasks; using WLM to control this maximum number of spawned tasks on the LPAR may cause unpredictable behavior in CCI spawn processing.

For a note regarding priority setting via WLM of the involved tasks, see the CA Software Change Manager for Mainframe Implementation Guide, Page 36.

Environment

Release:
Component: C21E

Attachments

1558535398316TEC509034.zip get_app