What is the second factor used to calculate this exception.Type: CPU percentage for a DB2 address space V1: CPU used by DIST address space QWSAEJST V2: N/A

Document ID:  TEC1372215
Last Modified Date:  07/11/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA SYSVIEW Performance Monitor for DB2 for z/OS

Components

  • CA Insight Database Performance Monitor for DB for z/OS:IDB2
  • Common Insight Services:CIDB
Issue:

What is the second factor used to calculate this exception:

Type: CPU percentage for a DB2 address space                          

V1: CPU used by DIST address space                           QWSAEJST 

V2: N/A  ?

                                        

Resolution:

The second  factor doesn't apply for this exception but here is the breakdown of this exception:

>>> 

The JS-TIMER and SRB-TIMER 

Those values come from the STATS1 record, IFCID 1, from the DSNDQWSA section which is the dsect for this section. 

There are normally at least 4 repeating sections in the record, one for MSTR, one for DBM1, one for IRLM and one for DIST DB2 address spaces. 

The JS-TIMER is the same as the dsect field QWSAEJST, which is the jobstep timer value for the address space. 

SRB-TIMER is the same as field QWSASRBT in this data section and contains the SRB timer value for the address space. 

 

 

CPU used by MSTR address space QWSAEJST MSTR-JS-TIMER 

CPU used by DBM1 address space QWSAEJST DBM1-JS-TIMER 

CPU used by DIST address space QWSAEJST DIST-JS-TIMER 

CPU used by IRLM address space QWSAEJST IRLM-JS-TIMER 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >

Chat with CA

Just give us some brief information and we'll connect you to the right CA ExpertCA sales representative.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing