Re: CRTPFRDTA job

Another thought. Are any of the performance files required for a full recovery? Answer no. Therefore the only reason you would back up the performance files is to keep them for posterity's sake.

I routinely omit libraries QPFRDATA and QMPGDATA from the back ups. If I want them for some reason then I'll stop the performance monitor, back them up and then start it again, usually on a Sunday or another day were usage is very light, but not during the normal user data back up routines where they can cause mischief as you are finding out now.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 11/22/2011 10:21 AM, rob@xxxxxxxxx wrote:

IBM's instructions are to end them *IMMED
http://www-03.ibm.com/systems/power/support/perfmgmt/faq_datacolli.html


Rob Berendt
-- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Cyndi Bradberry <CyndiB@xxxxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>, Date: 11/22/2011 09:57 AM Subject: CRTPFRDTA job Sent by: midrange-l-bounces@xxxxxxxxxxxx We use a home grown version of the go SAVE 22 command to back up our data every night. This Performance Data job has a lock on a number of files and the system has to wait thru each one before moving on with the backup. I would like to be able to end this job forever, or if I need to have it running, be able to end it before my nightly processing, and turn it back on after. Changing a totally quiescent system at this time is not possible. I am obviously not looking in the right areas for the END command. If anyone could point me in the right direction, I would appreciate it. Cyndi B. Boise, ID
--