Re: PDQ on 7.12

>} >We are running 712UC2, on a dual proc. HP model K w/512MB RAM. What a >nightmare. PDQ is useless, and OPTCOMPIND is turned off. If we edit a >table structure while someone is in the table, we crash the database, How can you do this when someone is in the table, it should be locked and deny you access >and afterwards, about 50% of the time, it will set everyones PDQ to 100. > Needless to say this doesn't last very long, before half our users get >locked out. The only way we found to fix this is to set the MAXPDQ to >0. Which is now where we leave it. Setting the PDQ even when it >'works', causes the resources to be dedicated to the one job running >with PDQ (no matter what it is set at). I certainly can't say whether >your PDQ will work, but be prepared. We have had nothing but good luck with PDQ. Typically we set it a 2 in the onconfig file with MAXPDQPRIORITY=100. We also set it as high as 100 for certain batch jobs run when the system is unavailable to the user population. What is MULTIPROCESSOR set at in your onconfig file? Also have you tried lower PDQ settings like 5 and below? Typically, How many users are logged in at a time? Are you using the system for decision support or OLTP? National Linen Service 1420 Peachtree Street MS #230 Atlanta, GA 30309 e-mail: barryleb@mindspring.com