R
Rob Fitzpatrick
Guest
I'd also run this batch client with -yx. At the end of the batch run, look at proc.mon to see which procedures register the most execution time. If there is an outlying value that could lead you to a code-related issue like the one Paul described with the repeated chmods. Also, double-check the other client startup parameters and see if something obvious is missing. Where does the batch client run? Is it self-service or shared-memory? Where does the code reside relative to the client? Is it r-code or procedure libraries? Or compile on-the-fly? Is the client using -q? Where do the client's temp files reside (-T), and what is their size and I/O during execution? How many databases does the client connect to? It would be helpful to know all of the client and broker startup parameters, including those in parameter files.
Continue reading...
Continue reading...