the
Operational Reporting tool.
Thanks, in advance and have a happy Mardi Gras.
David Moore
State of Louisiana
linked to say's sixth edition (December
2003)
is this the latest?
David Moore wrote:
This link provides the latest performance tuning guide put out by the Boulder
Support staff. I've used it to optimize my z/OS installation. There's a
section for the Solaris servers. Hope it helps
This link provides the latest performance tuning guide put out by the Boulder
Support staff. I've used it to optimize my z/OS installation. There's a
section for the Solaris servers. Hope it helps.
http://www-1.ibm.com/support/docview.wss?uid=pub1sc32910101
Kindest regards,
Dave
, LOADFORMAT, LOADDB first? Will that lead to smoother database
maintenance?
Thanks in advance.
David Moore
State of LA / DOA / OCS
database...
David Moore wrote
Any ideas on why the TSM DB is shrinking?
This is going to be down to data expiration. Does your activity log show
that expiration is running longer and expiring more.
Did you have the opposite pattern a while back where you database grew
over a short period.
What I find
I went from 5.1.9 to 5.2.3 in late Sept. I'm sure you know you need to load
the new 5.2.0 base code, then apply the upgrade to take you to the 5.2.3
levels. When you start the server on the upgraded level, my IBM consultant
told me to run without the UPGRADEDB parameter first and the system
from the base product
installation libraries. This way, I control what levels I am at and when I
upgrade !
Again, thanks for your experiences !
David Moore [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
11/09/2004 10:02 AM
Please respond to
ADSM: Dist Stor Manager [EMAIL
Hello List -
I'm running TSM 5.2.3 on z/OS 1.2. I've observed over the past week that my
26MB TSM database has shrunk from about 83% utilization to about 67% and
counting. I've had two major events in the recent past:
1. I upgraded TSM from 5.1.9 to 5.2.3 on Sept. 26.
2. I have recently
Robert -
Both TSM Tech Support and a local consultant recommended that we run the 'cleanup
backupgroups' utility before we moved up to 5.2 (btw, mine is a z/OS shop and we
recently moved from 5.1.9 to 5.2.3). This utility cleans up orphaned database
objects, which will extend your upgradedb
Hello List -
We're running TSM 5.2.3 on z/OS 1.2. Current 9840 tape breakdown: TAPECOL = about
400, TAPENON = about 200, TAPEARCHIVE = 22.
Due to competing resources, I was told to convert TSM to use the 3592 tapes (300GB
capacity) rather than the 9840 tapes (20 GB capacity) that we have
Hello List -
I've got zero scripting experience for TSM. But, we are trying to determine the
number of processors that are on each of the nodes that we are backing up. That info
is not available in the WEBGUI drop-downs and I don't know the tables and layouts in
the database. Is this
11 matches
Mail list logo