DCOLLECT runs once per day. The time frame for this error is anytime between 11pm and 3am. No specific time, just around Midnight.
I have a file from last night that ran during the event. That is why I was thinking of running it a little more often. To try and get closer to the actual event. I am also running SMF 30, 14 15 17 18 60-69 Records to see if I can get to the problem that way as well. Lizette > >How often are you running DCOLLECT now? I would think you could run it >just before the time period where the problem occurs and then just >before the time period ends and compare the before and after, or is it >difficult to determine the actual start and end times. >> I am working on an issue where sometime between 11pm and 3am one of my >SMS >> Pools goes from 80% used upto 97% used. I added in 4 more volumes and >it >> is still doing it. >> >> I am working with DCOLLECT and MXG to see if I can isolate out the >> offending files. However, the process is not working the way I had >hoped. >> >> Any suggestions on which way is the best to identify consumers in an >SMS >> Pool? >> >> I have been using the DCOLDSET data set in MXG and the Report >Generation >> Process in Naviquest. I am thinking I need to run DCOLLECT more often >> during my window, perhaps every 10 mins. >> >> Any other ideas will be welcomed. >> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
