Line C in Figure 46 shows BSDS accesses. Just like the active log accesses, these accesses are mainly writes.

The block of lines starting with D shows volume of records created in the active log and offloaded by the archiving process.

The block of lines starting with E shows archive volume mounting information.

LOG ACTIVITY

QUANTITY

/MINUTE

/THREAD

/COMMIT

---------------------------

--------

-------

-------

-------

READS SATISFIED-OUTPUT BUFF

A

0.00

0.00

N/C

0.00

READS SATISFIED-OUTP.BUF(%)

 

N/C

 

 

 

READS SATISFIED-ACTIVE LOG

 

0.00

0.00

N/C

0.00

READS SATISFIED-ACTV.LOG(%)

 

N/C

 

 

 

READS SATISFIED-ARCHIVE LOG

 

0.00

0.00

N/C

0.00

READS SATISFIED-ARCH.LOG(%)

 

N/C

 

 

 

TAPE VOLUME CONTENTION WAIT

 

0.00

0.00

N/C

0.00

WRITE-NOWAIT

B

0.00

0.00

N/C

0.00

WRITE OUTPUT LOG BUFFERS

 

509.00

15.00

N/C

254.50

BSDS ACCESS REQUESTS

C

0.00

0.00

N/C

0.00

UNAVAILABLE OUTPUT LOG BUFF

 

0.00

0.00

N/C

0.00

CONTR.INTERV.CREATED-ACTIVE

D

5.00

0.15

N/C

2.50

ARCHIVE LOG READ ALLOCATION

 

0.00

0.00

N/C

0.00

ARCHIVE LOG WRITE ALLOCAT.

 

0.00

0.00

N/C

0.00

CONTR.INTERV.OFFLOADED-ARCH

 

0.00

0.00

N/C

0.00

READ DELAYED-UNAVAIL.RESOUR

E

0.00

0.00

N/C

0.00

LOOK-AHEAD MOUNT ATTEMPTED

 

0.00

0.00

N/C

0.00

LOOK-AHEAD MOUNT SUCCESSFUL

 

0.00

0.00

N/C

0.00

Figure 46. DB2 PM Statistics, Log Activity Section

11.1.3 Performance I/O Information and I/O Activity

DB2 PM can create several I/O activity reports for different types of data sets. The buffer pool report shows the activity of one identifier (for example: plan, user, buffer pool id) against the data sets in one virtual buffer pool.

Before the report can be generated, the appropriate trace must be started. It is recommended to limit the trace to reduce the impact on system performance. This can be done by specifying class and instrumentation facility componenent identifiers (IFCIDs) in the START TRACE command. Asynchronous I/O activity is not collected when user (AUTHID) or application identifiers (PLAN) are specified in the START TRACE command unless the user identifier of the DBM1 address space is also listed. Table 26 on page 124 shows the requirements to generate the trace information for the different I/O activity reports. Figure 47 on page 124 shows an extract from a summary I/O activity report. A detail report allows an analysis at the identifier level. For example, it can be used for a detailed analysis of the accesses of one application to one table space.

I/O Performance and Monitoring Tools

123

Page 145
Image 145
IBM 5695-DF1 manual Performance I/O Information and I/O Activity, 123, Minute Thread, WRITE-NOWAIT Write Output LOG Buffers

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.