Clark gave you excellent advise to check what else is running at that time. I once had a cics transaction that at 10 o'clock in the morning started slow don. The DBA and his consultant claimed the system need more memory and CPU. Omegamon told us a different story: We looked at the disk where the table was located and discovered that a batch job reads the table sequentially, so the disk heads was moving all the time, which cause the slowdown. we shifted the job the problem disappeared saved us lot of money in memory and cpu purchases ;-)
So my advise is dig! look at the CPU and elapse. may be your problem is statistical. ITschak On Thu, Aug 2, 2018 at 8:40 PM Clark Morris <[email protected]> wrote: > [Default] On 2 Aug 2018 08:43:32 -0700, in bit.listserv.ibm-main > [email protected] (Tony Thigpen) wrote: > > >To answer some of the questions: > > > >1) There is no monitor. > >2) WLM only has two profiles, DAY and NIGHT. These jobs all run during > >the NIGHT settings. > >3) Turf war prevents me from actually calling ADABAS support. Only the > >DBA is allowed that option. And, if the issues are resolved with ADABAS > >tuning, then he will look really bad as he has placed all the blame on > >'Systems'. So, he will not call them for us. > > I would compare all of the job statistics that you have access to > including CPU time and i-os to see what differs between normal and > spike nights. Also check what is running concurrently with the spike > night jobs. It may be a scheduling conflict. Also if Adabas is > cutting any SMF records that could be helpful get those and ask for > access to the tool(s) to interpret them. > > Clark Morris > > > >I need to get enough ammo to dump it back on the DBA. > > > >Tony Thigpen > > > >Tony Thigpen wrote on 08/02/2018 11:13 AM: > >> Is there anyone that would be willing to give me some guidance to solve > >> some ADABAS issues. Something is causing a performance problem and > >> nobody seems to even know where to start looking. > >> > >> We have several Natural programs that run in minutes one night, then > >> take an hour on other nights. We also have some RPG programs (using the > >> VSAM bridge) that have similar problems. > >> > >> The programmers don't think it has to do with daily work-load changes. > >> They want to point the finger at Systems. We (systems) are not making > >> changes. > >> > >> The 'DBA' belongs to the programmer group, and to be honest, I don't > >> think he has a clue concerning performance, just how to define the > >> databases. > >> > >> At this point, I just need a better idea of where the problem really is > >> so I can attempt to throw it back to the DBA. > >> > > > >---------------------------------------------------------------------- > >For IBM-MAIN subscribe / signoff / archive access instructions, > >send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
