Richard,
Thank you for both answers. REPORTING_MB is the basic answer. And, thanks for
the select reminder.
Keith
tsm: TSMBL01>q occ esappj10
Node Name Type Filespace FSID Storage Number of Physical
Logical
Name Pool Name Files Space
Space
Occupied
Occupied
(MB)
(MB)
---------- ---- ---------- ---- ---------- ----------- -----------
-----------
ESAPPJ10 Bkup / 3 DEDUP 19,011 -
799.10
ESAPPJ10 Bkup /boot 2 DEDUP 64 -
244.57
ESAPPJ10 Bkup /home 4 DEDUP 10,462 -
415.37
ESAPPJ10 Bkup /opt 5 DEDUP 27,215 -
7,545.83
ESAPPJ10 Bkup /usr 6 DEDUP 86,980 -
5,377.92
ESAPPJ10 Bkup /var 1 DEDUP 10,042 -
4,102.47
tsm: TSMBL01>select filespace_name,stgpool_name,reporting_mb from occupancy
where node_name='ESAPPJ10'
FILESPACE_NAME: /boot
STGPOOL_NAME: DEDUP
REPORTING_MB: 244.57
FILESPACE_NAME: /var
STGPOOL_NAME: DEDUP
REPORTING_MB: 4102.47
FILESPACE_NAME: /home
STGPOOL_NAME: DEDUP
REPORTING_MB: 415.37
FILESPACE_NAME: /
STGPOOL_NAME: DEDUP
REPORTING_MB: 799.10
FILESPACE_NAME: /opt
STGPOOL_NAME: DEDUP
REPORTING_MB: 7545.83
FILESPACE_NAME: /usr
STGPOOL_NAME: DEDUP
REPORTING_MB: 5377.92
On 12/23/15, 15:34, "ADSM: Dist Stor Manager on behalf of Richard Cowen"
<ADSM-L AT VM.MARIST DOT EDU on behalf of rcowen AT CPPASSOCIATES DOT COM>
wrote:
>Try REPORTING_MB.
>Also
>
>Select colname from syscat.columns where tabname='OCCUPANCY" and
>tabschema='TSMDB1'
>richard
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
>Of Arbogast, Warren K
>Sent: Wednesday, December 23, 2015 3:07 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: [ADSM-L] Select from Occupancy table is blank for Directory pool
>
>Hi Stephen,
>Thank you for sharing that idea. It didn’t quite reveal the mystery of the
>Occupancy table yet. I wonder whether new tables or new attributes have been
>added for directory container pools?
>
>tsm: TSMBL01>select sum(logical_mb) from occupancy where node_name='ESAPPPJ10'
>
>
> Unnamed[1]
>----------------------------------
>
>
>
>tsm: TSMBL01>
>
>
>
>
>
>
>
>On 12/23/15, 15:01, "ADSM: Dist Stor Manager on behalf of Stefan Folkerts"
><ADSM-L AT VM.MARIST DOT EDU on behalf of stefan.folkerts AT GMAIL DOT COM>
>wrote:
>
>>Hi Keith,
>>Try this:
>>select sum(logical_mb) from occupancy where node_name='ESAPPJ10'
>>
>>On Wed, Dec 23, 2015 at 8:50 PM, Arbogast, Warren K <warbogas AT iu DOT edu>
>>wrote:
>>
>>> We are running TSM/EE 7.1.4 on RHEL6, and are actively migrating
>>> backups on other primary pools to directory container pools, which
>>> are named ‘DEDUP'.
>>>
>>> I need to count MB in the DEDUP pools by node for all pertinent nodes.
>>>
>>> When I run ‘q occupancy <nodename>’ from an Admin command line, the
>>> logical_mb in the DEDUP pool for that node is displayed, like this:
>>>
>>>
>>> tsm: TSMBL01>q occ esappj10
>>>
>>>
>>> Node Name Type Filespace FSID Storage Number of Physical
>>> Logical
>>>
>>> Name Pool Name Files Space
>>> Space
>>>
>>> Occupied
>>> Occupied
>>>
>>> (MB)
>>> (MB)
>>>
>>> ---------- ---- ---------- ---- ---------- -----------
>>> -----------
>>> -----------
>>>
>>> ESAPPJ10 Bkup / 3 DEDUP 19,011 -
>>> 799.10
>>>
>>> ESAPPJ10 Bkup /boot 2 DEDUP 64 -
>>> 244.57
>>>
>>> ESAPPJ10 Bkup /home 4 DEDUP 10,462 -
>>> 415.37
>>>
>>> ESAPPJ10 Bkup /opt 5 DEDUP 27,215 -
>>> 7,545.83
>>>
>>> ESAPPJ10 Bkup /usr 6 DEDUP 86,980 -
>>> 5,377.92
>>>
>>> ESAPPJ10 Bkup /var 1 DEDUP 10,042 -
>>> 4,102.47
>>>
>>>
>>>
>>> But, when I run a select statement on the Occupancy table for the
>>> same node, the output is blank, like this:
>>>
>>>
>>> tsm: TSMBL01>select logical_mb from occupancy where node_name='ESAPPJ10'
>>>
>>>
>>> LOGICAL_MB
>>>
>>> -----------------
>>>
>>>
>>>
>>> Surely there is a way to do this. Can someone tell me how to get that
>>> data from the Occupancy table, or another table, if I am looking in
>>> the wrong place?
>>>
>>> Thank you,
>>> Keith Arbogast
>>> Indiana University
>>>
>>>
>>>
>>>
>>>
|
