Statistics and accounting traces are collected in most installations. A performance trace is collected when a specific problem has to be investigated. Activating the performance trace has a significant impact on DB2 subsystem performance. The user can cause more or less information to be collected by these traces, by specifying trace classes to be activated.

An accounting trace provides information at an identifier level. Examples of identifiers are plans, packages, users, or connection types. Accounting information can be a summary of multiple executions (Accounting Report), or it can be a detail of every execution (Accounting Trace).

A statistics trace provides information at DB2 subsystem level. It can be a summary of multiple statistic intervals (Statistics Report) or it can be a listing of each interval (Statistics Trace).

The performance trace can generate detailed information on all DB2 subsystem activity. When this trace has been started with the appropiate classes, DB2 PM can generate an I/O activity report.

DSNTIPN

UPDATE DB2 - TRACING AND CHECKPOINT PARAMETERS

 

===>

 

 

 

 

 

Enter data below:

 

 

 

 

1

AUDIT TRACE

===> NO

Audit classes to start. NO,YES,list

2

TRACE AUTO START

===> NO

Global classes to start. YES, NO, list

3

TRACE SIZE

===> 64K

Trace table size in bytes.

4K-396K

4

SMF ACCOUNTING

===> 1

Accounting classes to start. NO,YES,list

5

SMF STATISTICS

===> YES

Statistics classes to start. NO,YES,list

6

STATISTICS TIME

===> 30

Time interval in minutes.

1-1440

7

DATASET STATS TIME

===> 5

Time interval in minutes.

1-1440

8

MONITOR TRACE

===> NO

Monitor classes to start. NO, YES, list

9

MONITOR SIZE

===> 8K

Default monitor buffer size. 8K-1M

10

CHECKPOINT FREQ

===> 50000

Number of log records per checkpoint

11

UR CHECK FREQ

===> 0

Checkpoints to enable UR check. 0-255

12

LIMIT BACKOUT

===> AUTO

Limit backout processing. AUTO,YES,NO

13

BACKOUT DURATION

===> 5

Checkpoints processed during backout if

 

 

 

 

LIMIT BACKOUT = AUTO or YES. 0-255.

14

RO SWITCH CHKPTS

===> 5

Checkpoints to read-only switch. 1-32767

15

RO SWITCH TIME

===> 10

Minutes to read-only switch. 0-32767

16

LEVELID UPDATE FREQ ===> 5

Checkpoints between updates. 0-32767

F1=HELP

F2=SPLIT

F3=END

F4=RETURN

F5=RFIND

F6=RCHANGE

F7=UP

F8=DOWN

F9=SWAP

F10=LEFT

F11=RIGHT

F12=RETRIEVE

Figure 43. Installation Panel DSNTIPN

11.1.1Accounting I/O Information

11.1.1.1I/O Operations

The data I/O operations initiated by DB2 on behalf of an application are detailed in the buffer pool sections of the DB2 PM accounting report. Each bufferpool is shown independently. For an example, see Figure 44 on page 121. Every read access is reported as a getpage. Every write is reported as a buffer update. The getpages and buffer updates may initiate an I/O. These I/Os are either synchronous or asynchronous. The asynchronous reads are reported in the three prefetch fields (SEQ, LIST, DYN).

120Storage Management with DB2 for OS/390

Page 142
Image 142
IBM 5655-DB2, 5695-DF1 manual Accounting I/O Information, 11.1.1.1 I/O Operations

5695-DF1, 5655-DB2 specifications

IBM 5655-DB2 and 5695-DF1 are significant components within the IBM software ecosystem, predominantly focusing on data management and integration solutions. These offerings cater primarily to enterprise environments that require robust database management systems and associated frameworks to maintain and manipulate data efficiently.

IBM 5655-DB2 is a well-known relational database management system (RDBMS) that excels in managing large volumes of structured data. Its architecture is designed to support high availability, scalability, and performance, crucial for businesses operating in today’s data-driven world. Some of its main features include advanced indexing capabilities, support for complex queries, and dynamic workload management. Additionally, it provides strong concurrency controls, which enable multiple users to access and manipulate data simultaneously without compromising data integrity.

One of the key characteristics of DB2 is its support for various data types, including JSON and XML, making it versatile for modern applications that generate data in diverse formats. It also features robust security mechanisms to protect sensitive data, aligning with compliance standards across industries. Integration with analytics tools further allows businesses to derive insights from their data, enhancing decision-making processes.

On the other hand, IBM 5695-DF1, also known as the InfoSphere DataStage, is a powerful data integration tool that facilitates the extraction, transformation, and loading (ETL) of data from various sources to target systems. It empowers organizations to streamline their data flows, ensuring that clean, consistent information is available for analysis and operational use. Key features of 5695-DF1 include a user-friendly graphical interface that enhances developer productivity and a rich set of connectors for numerous data sources, enabling seamless data integration.

DataStage also supports real-time data integration, allowing businesses to keep their data synchronized across multiple platforms. Its parallel processing capabilities dedicatedly optimize performance, enabling organizations to handle vast datasets efficiently. It incorporates data quality tools that help in validating and cleansing data before it is used for decision-making processes.

Both IBM 5655-DB2 and 5695-DF1 are part of a broader strategy to accommodate the evolving landscape of data management. Businesses leverage these technologies to enhance their data architectures, fostering agility and competitive advantage in their respective markets. Their integration capabilities, along with a focus on security and scalability, position them as vital assets in modern enterprise environments. Whether managing critical data within a database or ensuring seamless data flow across systems, these IBM offerings provide a comprehensive approach to handling complex data challenges.