Re: [ADSM-L] Occupancy discrepancy between 220.127.116.11 and 18.104.22.168 server
occupancy numbers were made incorrect by various bugs in early 6.1 code,
see apar ic73005. There is a special utility to fix the numbers, "repair
It was supposed to be in 22.214.171.124 but isn't, you need an e-fix for 126.96.36.199.
Of course, you can ignore the errors unless you are using the unified
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Wednesday, March 07, 2012 8:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Occupancy discrepency between 188.8.131.52 and 184.108.40.206 server
Doing some reorganization, we recently moved (server-to-server export)
some nodes from a 220.127.116.11 server to a 18.104.22.168 server. Now, the occupancy
numbers on the 6.2 (71mb) server are lower than the 6.1.5 (83mb) server,
eventhough the file/object counts are identical (static file system)?
All of the apars I found (so far) that address occupancy information are
at (supposedly) patch levels below these levels.
Anyone else see this kind of discrepancy?
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details