Db2 12 for z/OS Omegamon Accounting Package Information

Daniel Luksetich

Db2 12 for z/OS Omegamon Accounting Package Information
Folks,

I'm looking at an accounting long report for a Db2 subsystem, and am
confused by some counts for packages related to routines. I'm looking at
three fields:



OCCURRENCES

NBR OF ALLOCATIONS

NBR RLUP THREADS



I get the impression if a routine is invoked then OCCURENCES represents the
number of times it was invoked. If the routine is invoked by another routine
then NBR RLUP THREADS represents the number of times it was invoked.
Actually, NBR RLUP THREADS appears to always reflect the number of times the
routine was invoked and is equal to OCCURENCES if a routine is invoked, and
NBR OF ALLOCATIONS if the routine is invoked by another routine.



Does that sound correct? This is on a system that is not accumulating
accounting records.



Thanks,

Dan



Daniel L Luksetich

DanL Database Consulting



IBM GOLD Consultant

IBM Champion for Analytics

IDUG Content Committee Past-Chairman

IDUG DB2-L Administrator

IBM Certified Database Adminstrator - DB2 11 DBA for z/OS

IBM Certified System Administrator - DB2 11 for z/OS

IBM Certified Application Developer - DB2 11 for z/OS

IBM Certified Advanced Database Administrator - DB2 10.1 for Linux UNIX and
Windows



Norbert Jenninger

RE: Db2 12 for z/OS Omegamon Accounting Package Information
(in response to Daniel Luksetich)

The values of field "OCCURRENCE" and "NBR RLUP THREADS" are counters based on the 

... the total number of accounting trace sections for a package or
DBRM regardless of enabled or disabled DB2 trace classes 7 and 8 at the
time of writing the trace record. In case of Distributed Data Facility
(DDF) or Recoverable Resource Manager Services Attach Facility
(RRSAF) threads, it is the number of accounting intervals rolled up in a
record.
=> Means the report program is counting the number of package data section within the DB2 trace records.

 

The value of "NBR OF ALLOCATIONS" is based on and derived from the Db2 trace field QPACSWITCH

...NUMBER OF TIMES THAT A PACKAGE WAS INVOKED FROM A  
DIFFERENT PACKAGE. FOR THE FIRST PACKAGE THAT IS   
RUN BY AN APPLICATION, THE INITIAL CALL COUNTS AS A
PACKAGE SWITCH. IF THIS PACKAGE CALLS A NESTED     
PACKAGE (TRIGGER, USER-DEFINED FUNCTION, OR STORED
PROCEDURE), RETURN FROM THE NESTED PACKAGE DOES NOT
COUNT AS A SWITCH.                    

Please consider and read in addition the Report Reference manual for specific Accounting Reports 

      REPORT ORDER (ACTNAME)

 

Regards, Norbert Jenninger

Daniel Luksetich

Db2 12 for z/OS Omegamon Accounting Package Information
(in response to Norbert Jenninger)
Norbert,

I have read the manual many times, and looked at various presentations. Everything repeats what the manual says.



So, I’ll just ask the question…



Does NBR RLUP THREADS count the number of times a package was invoked? My guess is yes.



Thanks,

Dan



Daniel L Luksetich

DanL Database Consulting



IBM GOLD Consultant

IBM Champion for Analytics

IDUG Content Committee Past-Chairman

IDUG DB2-L Administrator

IBM Certified Database Adminstrator – DB2 11 DBA for z/OS

IBM Certified System Administrator – DB2 11 for z/OS

IBM Certified Application Developer – DB2 11 for z/OS

IBM Certified Advanced Database Administrator – DB2 10.1 for Linux UNIX and Windows



From: Norbert Jenninger <[login to unmask email]>
Sent: Thursday, May 9, 2019 4:10 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: Db2 12 for z/OS Omegamon Accounting Package Information



The values of field "OCCURRENCE" and "NBR RLUP THREADS" are counters based on the

... the total number of accounting trace sections for a package or
DBRM regardless of enabled or disabled DB2 trace classes 7 and 8 at the
time of writing the trace record. In case of Distributed Data Facility
(DDF) or Recoverable Resource Manager Services Attach Facility
(RRSAF) threads, it is the number of accounting intervals rolled up in a
record.
=> Means the report program is counting the number of package data section within the DB2 trace records.



The value of "NBR OF ALLOCATIONS" is based on and derived from the Db2 trace field QPACSWITCH

...NUMBER OF TIMES THAT A PACKAGE WAS INVOKED FROM A
DIFFERENT PACKAGE. FOR THE FIRST PACKAGE THAT IS
RUN BY AN APPLICATION, THE INITIAL CALL COUNTS AS A
PACKAGE SWITCH. IF THIS PACKAGE CALLS A NESTED
PACKAGE (TRIGGER, USER-DEFINED FUNCTION, OR STORED
PROCEDURE), RETURN FROM THE NESTED PACKAGE DOES NOT
COUNT AS A SWITCH.

Please consider and read in addition the Report Reference manual for specific Accounting Reports

REPORT ORDER (ACTNAME)



Regards, Norbert Jenninger



-----End Original Message-----

Norbert Jenninger

RE: Db2 12 for z/OS Omegamon Accounting Package Information
(in response to Norbert Jenninger)

Your question:

Does NBR RLUP THREADS count the number of times a package was invoked initially? My guess is yes.

=> YES, to be more precise, I want to add "initially".

 

Again, the value of "NBR OF ALLOCATIONS" is based on and derived from the Db2 trace field QPACSWITCH

DB2 describes QPACSWITCH as follow:
...NUMBER OF TIMES THAT A PACKAGE WAS INVOKED FROM A
DIFFERENT PACKAGE. FOR THE FIRST PACKAGE THAT IS
RUN BY AN APPLICATION, THE INITIAL CALL COUNTS AS A
PACKAGE SWITCH. IF THIS PACKAGE CALLS A NESTED
PACKAGE (TRIGGER, USER-DEFINED FUNCTION, OR STORED
PROCEDURE), RETURN FROM THE NESTED PACKAGE DOES NOT
COUNT AS A SWITCH.

I think, the sentence "THE INITIAL CALL COUNTS AS A PACKAGE SWITCH." is clear.

In addition, "RETURN FROM THE NESTED PACKAGE DOES NOT COUNT AS A SWITCH".

That is that is the way, how Db2 reports the value within QPACSWITCH.

Means not every repeating call to the same package within the same thread execution is counted by DB2. That was confirmed in an earlier discussion with Db2.

Regards, Norbert Jenninger