Z13

Brett Sinclair

Z13
Good Morning –
We have noticed more DB2 CPU consumption ever since we moved to a Z13; especially DB2 batch jobs.
Has anyone else noticed similar issues?
Has anyone had the issues, and found a solution?

Thank you, Brett Sinclair


Ce message est confidentiel; Son contenu ne represente en aucun cas
un engagement de la part de AXA Technology Services (AXA Tech) sous
reserve de tout accord conclu par ecrit entre vous et AXA Technology
Services (AXA Tech).Toute publication, utilisation ou diffusion,meme
partielle, doit etre autorisee prealablement. Si vous n'etes pas
destinataire de ce message, merci d'en avertir immediatement l'expe-
diteur.

This message is confidential; its contents do not constitute a
commitment by AXA Technology Services (AXA Tech) except where provi-
ded for in a written agreement between you and AXA Technology
Services (AXA Tech). Any unauthorised disclosure, use or dissemina-
tion, either whole or partial, is prohibited. If you are not the
intended recipient of the message, please notify the sender imme-
diately.

James Campbell

Z13
(in response to Brett Sinclair)
There have been reports that, under some circumstances, after a task (as in TCB task)
interrupt a z13 can restart the task on a CP that does not share memory cache with the CP
that was previously processing the task. So the memory cache needs to be refreshed and
performance suffers.

Raise a PMR. I have seen the terms "Absolute Group Capping" and "Alternate Central
Processor Assignment" used in change records.

James Campbell

On 16 Dec 2016 at 14:03, SINCLAIR Brett wrote:

>
> Good Morning -
>                 We have noticed more DB2 CPU consumption ever since we moved to a Z13; especially DB2 batch
> jobs.
> Has anyone else noticed similar issues?
> Has anyone had the issues, and found a solution?
>  
> Thank you, Brett Sinclair