Dear Brian,

Thank you. 

I will give the anwser soon I get all the information you list. 

Here is out GTFPARM probably this is the default parm. If we need to add more 
option:

TRACE=SYSM,USR,TRC,DSP,PCI,SRM 

Thanks and regards,

Mohd Shahrifuddin




???:Brian Westerman
????:2010-10-12 14:13:58
???:IBM-MAIN
??:
??:Re: Batch loop in SYSplex

Okay,
This shouldn't be too difficult to determine.
first, when you notice the HIGH CPU, what other address spaces are also
showing HIGH CPU, there will probably be at least one.
second, can you check your RMF III reports and see if there are any enqueues
at the time, and who they are for I would be most intrested in contention
for SYSZIGW3 IGWSHC02 resources if they exist (if so I have your answer).
third, Have you discovered what actual programs are involved at the time, is
this a standard IDCAMS job or is it a user written program of some sort that
is performing the functions.  
I'm not sure about your expertise level, but the next step (if nothing came
out of the above questions) would be a GTF trace so that we can see what we
are doing.  Depending on the answers to the above, you should be able to
code, or I could  give you the parms necessary to perform the trace.  
If you are familiar with using the trace results then you're golden and the
cause should be relatively easy to find (a fix might be a little more
difficult).
I'm fairly certain that I have seen your problem before.  let me know what
your results are to the above.
Brian Westerman
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to