Given that you observed the very large file in a Query PRocess
inspection, you then have a timeframe for it, which would facilitate
bracketing contributing ingredients. In particular, from the Activity
Log you know what volumes were active at the time... If collocation is
active (usual case), the
I am aware of the potential problem you raise below which is why I
scheduled it to start running at 6 am on Saturday morning as activity on
the TSM server during the day on Saturday is minimal.
I discovered this large file from the output of the "q pr" command. The
file was either being moved as p
cc
Manager"
[ADSM-L] Details of large file
backed up via TSM
You achieved TSM redirection by virtue of having a space before and
after the '>' in
FILE_SIZE > 100
If you remove the space before the '>', it will do what you want.
This is described in ADSM QuickFacts, under entry ">".
The greater issue: Performing a Select against the Contents tabl
I can see that TSM has backed up a file that is 140 Gb in size. However
I have been unable to work out which server this file came from.
I want to query the TSM database to find out some information about that
file (its name, what server it was on, etc)
After some research it appears that the fol
