Which WLM class should the ENF and CCI tasks, such as CCISSLGW run in?

book

Article ID: 50659

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

Currently client is running the ENF task using the SYSSTC WLM and the CCISSLGW task runs in STCMED. At shutdown ENF is getting more service than CCISSLGW, resulting in faster termination of the ENF address space.

Solution:

Ensure that both the ENF and CCISSLGW tasks run in the same WLM service class, which should be SYSSTC (or the equivalent). These are system level tasks and should be defined similar to that of JES. Failure to set these up in this workload management class can result in problems for CA products relying on these tasks to service their requests. In general, the ENF and CCI tasks should be defined in a WLM class equal to or higher then the CA applications depending on its services.

An example of what could happen can involve these two tasks themselves. If ENF is running in a higher WLM class than CCISSLGW is running, then during system shutdown, if ENF shuts down faster than CCISASLGW, S0C4 abends can occur in CCISSLGW code because the cleanup of all CCI connection related control blocks has taken place within the ENF shutdown process.

Other symptoms can be maintaining CCI connectivity with remote systems in a busy environment. If CCI cannot process the work it is trying to handle in a timely manner, remote connections may disconnect due to what is perceived as no response to internal ping request.

Environment

Release:
Component: ENF