We have several TSM 4.2 servers running on both z/OS and AIX and have
concerns about the TSM DB size as it impacts our ability to run maintenance
operations like DB Audits, Reorgs, and SQL Queries also seem to take much
longer than they should on some systems.
I am curious what DB Sizes others ha
Mark,
I am unaware of any formula to figure this out, but in my experience this is
very odd. In some recent testing of Windows 2000 nodes restored from TSM on
MVS I was able to restore 1.9 Million files (45GB) in 18 Hours over 100 Mb
Ethernet. Usually when I have seen restore times like you are r
We went through a similar process recently. This required us to schedule 24
hours of down time to do a DB reorg. Unfortunately this is not an online
process. We saw the numbers change from 100GB DB that was 33% used to a
100GB DB that is 22% used. Our goal was to set the maximum size to 50GB. We
w
I ran into this same problem a while back. If you are using the command with
a script, you need to use '%%string%%'. If you type them into the admin
interface you should be able to use '%string%'.
I run several scripts from a W2K batch file similar to this:
DSMADMC.exe -tcpserveraddress=tsmserve
