pdreclaim VV-RR        *** DB RECLAIM ***       YYYY-MM-DD hh:mm:ss[1]
 
TABLE NAME : USERA.TBL01 [2]
[3]     [4]                                 [5]          [6]
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                 11,395            244
  2  USER02                                 11,403            252
 
14284 16:22:54 un01    KFPL00739-I Pdreclaim terminated, return code=0
 

Explanation:

1. Header for the processing results
   VV-RR: Version, revision number
   YYYY-MM-DD hh:mm:ss: pdreclaim start date and time
   
2. Name of the table that was processed
   If the processing was in units of schemas, the information beginning with this item is repeated.
   
3. Serial numbers
4. Names of the table storage RDAREAs
5. Numbers of pages released
6. Numbers of segments that can be released
   Each RDAREA's number of segments that can be released includes not only segments that can be changed to unused segments by releasing used free pages by pdreclaim, but also segments that can be changed to unused segments by the DELETE statement for a table on which the LOCK statement was executed (executing the DELETE statement in the no-log mode automatically places the segments in LOCK-executed status).
   

 
pdreclaim VV-RR        *** DB RECLAIM ***        YYYY-MM-DD hh:mm:ss[1]
 
TABLE NAME : USERA.TBL01 [2]
[3]      [4]                                [5]           [6]
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                      -            244
  2  USER02                                      -            252
 
16066 16:23:57 un01   KFPL00739-I Pdreclaim terminated, return code=0
 

Explanation:

1. Header for the processing results
   VV-RR: Version, revision number
   YYYY-MM-DD hh:mm:ss: pdreclaim start date and time
   
2. Name of the table that was processed
   If the processing was in units of schemas, the information beginning with this item is repeated.
   
3. Serial numbers
4. Names of the table storage RDAREAs
5. Always - when the -j option was specified
6. Numbers of segments released

 
pdreclaim VV-RR        *** DB RECLAIM ***        YYYY-MM-DD hh:mm:ss[1]
 
INDEX NAME : USERA.(PRIMARY0000131193) [2]
[3]      [4]                                [5]           [6]
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                     32              0
  2  USER02                                     32              0
 
INDEX NAME : USERA.IDX01
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                    815             15
  2  USER02                                    815             15
 
INDEX NAME : USERA.IDX02
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                     93              1
 
 1273 16:58:26 un01    KFPL00739-I Pdreclaim terminated, return code=0
 

Explanation:

1. Header for the processing result
   VV-RR: Version, revision number
   YYYY-MM-DD hh:mm:ss: pdreclaim start date and time
   
2. Name of the index that was processed
   If multiple indexes were processed, the information beginning with this item is repeated.
   
3. Serial numbers
4. Names of the index storage RDAREAs
5. Numbers of pages released
6. Numbers of segments that can be released
   Each RDAREA's number of segments that can be released includes not only segments that can be changed to unused segments by releasing used free pages by pdreclaim, but also segments that can be changed to unused segments by the DELETE statement for a table on which the LOCK statement was executed (executing the DELETE statement in the no-log mode automatically places the segments in LOCK-executed status).
   

 
pdreclaim VV-RR        *** DB RECLAIM ***        YYYY-MM-DD hh:mm:ss[1]
 
INDEX NAME : USERA.(PRIMARY0000131193) [2]
[3]      [4]                                [5]          [6]
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                      -              0
  2  USER02                                      -              0
 
INDEX NAME : USERA.IDX01
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                      -             15
  2  USER02                                      -             15
 
INDEX NAME : USERA.IDX02
No.  RDAREA NAME                        PAGE COUNT  SEGMENT COUNT
  1  USER01                                      -              1
 
 1381 16:59:34 un01    KFPL00739-I Pdreclaim terminated, return code=0

Explanation:

1. Header for the processing results
   VV-RR: Version, revision number
   YYYY-MM-DD hh:mm:ss: pdreclaim start date and time
   
2. Name of the index that was processed
   If multiple indexes were processed, the information beginning with this item is repeated.
   
3. Serial numbers
4. Names of the index storage RDAREAs
5. Always - when the -j option was specified
6. Numbers of segments released

The processing results are output in the order that processing of the resources was completed.

When the -j option is specified, the numbers of pages released as displayed by pdreclaim may not match the numbers of pages that can be released (Collect Prearranged Page) that is displayed as the analysis result of pddbst. Also, the numbers of segments that can be released (processing results of pdreclaim without the -j option specified) may not match the numbers of segments released (processing results of pdreclaim with the -j option specified). The reasons are explained below.

(a) When a page is expected to be releasable, but pdreclaim is unable to release it

• To allow concurrent execution of a UAP and utility update processing, pdreclaim does not release any used free page that may result in concurrent updating. Also, the utility releases used free pages in such a manner that the number of index levels is not reduced.
• If pdrorg or pdrorg with the synchronization point specification terminates abnormally, pdreclaim does not release the first segment allocated to the corresponding table even if that segment contains no data.
• If pdreclaim is executed concurrently with update processing, a used free page or segment that was determined to be releasable may be used for update processing.

(b) When a page is expected to be nonreleasable, but pdreclaim can release it

• An intermediate page of an index is released when all of its lower leaf pages are released by pdreclaim. However, if pddbst is executing, the usage of the intermediate page cannot be treated as being 0% because there are leaf pages.