DSNB762I DUPLEXING STATISTICS FOR secondary-gbpname WRITES CHANGED PAGES = changed-pages FAILED DUE TO LACK OF STORAGE = writes-full CHANGED PAGES SNAPSHOT VALUE = changed-pages-snapshot

Explanation

This message is a section of output from the DISPLAY GROUPBUFFERPOOL command, which is part of message DSNB750I.

DSNB762I: Secondary group buffer pool details

If the DISPLAY GROUPBUFFERPOOL command included the GDETAIL option, and the group buffer pool is duplexed, the output includes the following information about the secondary group buffer pool:

  • Statistics on writes to the secondary group buffer pool
  • The total number of changed pages for the secondary group buffer pool. 
DSNB762I - DUPLEXING STATISTICS FOR secondary-gbpname 
              WRITES 
                CHANGED PAGES = changed-pages
                FAILED DUE TO LACK OF STORAGE = writes-full 
                CHANGED PAGES SNAPSHOT VALUE       = changed-pages-snapshot
secondary-gbpname
The secondary group buffer pool name. This name is the primary group buffer pool name (such as GBP0) suffixed with -SEC.
changed-pages
The number of times that a coupling facility write request for a changed page completed successfully.

If the group buffer pool was duplexed for the entire reporting interval, this number should be roughly equal to the "changed page write hit" counter in message DSNB786I. However, these counts might not be the same because of timing windows in gathering these values or if previous transaction failures occurred.

writes-full
The number of times that a write request from the coupling facility was not completed because of a lack of storage in the secondary group buffer pool.
changed-pages-snapshot
The total changed counter and snapshot value of the current number of changed pages in the secondary group buffer pool. This value is not affected by whether the DISPLAY GROUPBUFFERPOOL output is incremental or cumulative.

If the group buffer pool is duplexed, this number should be roughly equal to the "total changed"counter in message DSNB786I. However, these counts might not be the same because of timing windows in gathering these values or if previous transaction failures occurred.

Related information