Have you looked at RMF data to see what the job is doing? Do you have products like STROBE or OMEGAMON that can help you isolate the jobs run?
Is the application cycle controled by products like ENDEVOR or ChangeMan? If so, you can then verify when changes have been made to the application code. Service units going up with out any reference is not easy to identify. You need to use various tools to watch the job when it runs, or run RMF reports to assist in analysis. Do you have products like MXG or MICS? Other things to ask questions about - Has the input data increase in the application? Has there been any hardware changes? Has there been and JCL changes (a blocksize change can alter runtime)? Lizette > >We have a job that has a posting step that runs 6-7 minutes last year. We >noticed that the job more than doubled starting with the first processing day >of 2008. The application owners swear that no changes were made on there >side and the systems guys swear that no changes were made on their side >neither. The only think that I noticed by looking at the jobs sysout is that >the >SERVice Units went from 5335K to 13549K. Any ideas. \ ---------------------------------------------------------------------- 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
