View previous topic :: View next topic
|
Author |
Message |
Patricia Magne
New User
Joined: 25 May 2006 Posts: 10
|
|
|
|
Hi, I would like to know why if I put CPU Critical Flag in YES in a Service Class, after the activation in SDSF I see the column CPUCrit in YES and then change to NO and stay with this value.
Code: |
Service Class CICSCICC - SERV. CLASS PARA CAJEROS
Base goal:
CPU Critical flag: YES
# Duration Imp Goal description
- --------- - ----------------------------------------
1 1 Execution velocity of 95
SDSF DA VZL1 VZL1 PAG 0 CPU/L 60/ 59 LINE 1-1 (1)
COMMAND INPUT ===> SCROLL ===> CSR
NP JOBNAME SrvClass SP ResGroup Server Quiesce ECPU-Time ECPU% CPUCrit
CICC CICSCICC 1 YES 4348.68 0.09 NO |
Code'd
Why this happen? |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Not very sure what your question is? May be, and just mab be, "status of falg has something to do" with your curent session. Once you're "out of the session", default value is displayed. It's just a guess, however, have you verified that? |
|
Back to top |
|
|
Patricia Magne
New User
Joined: 25 May 2006 Posts: 10
|
|
|
|
The problem is: I put in WLM the flag for critical cpu for a CICS called CICC and active policy, immediately to changes observed in SDSF CPUCrit column to YES, but only lasts a few seconds then switch back to NO. We also observed the same in RMF, the C R field does not indicate all th time that CPU address spaces is Critical.
CPU= 43/ 43 UIC= 65K PR= 0 System= VZL1 Total
12:30:41 DEV FF FF PRIV LSQA X C SRM TCB CPU EXCP SWAP LPA CSA NVI V&H
JOBNAME CONN 16M 2G FF CSF M R ABS TIME TIME RATE RATE RT RT RT RT
CICC 1176 0 132 105 928 X 0.0 1899 2038 94.0 0.00 0.0 0.0 0.0 0.0 |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Only suggestion I can give at this point of time is, please get in contact with your site-support group. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
|
|
|
|
My only guess is that your WLM policy is not following all the requirements for CPU Critical (there are several). WLM detects this and turns off CPU Critical after the first evaluation period. That is, however, only a guess as I haven't used CPU Critical on our workloads. |
|
Back to top |
|
|
|