Initiators have a historic tendency for storage problems, especially the
longer they run. Fixing your WTO problem by restarting the initiator is a
classic workaround for such problems.
It's possible that you're taking abends you're not seeing because of DAE
dump suppression. As a first pass, look in IPCS at the DAE utility (3.5)
for getmain failures. If nothing shows up, when the problem occurs again,
set a nonspecific PER SLIP trap for a job name that is known or likely to
fail.
Unfortunately, finding a getmain failure does not solve the problem, which
is probably a result of storage fragmentation over time. We had a similar
problem once, and our simple minded plan was to stop and restart initiators
at intervals frequent enough to reduce the effects of fragmentation.
Diagnosis of the root cause will not be simple.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
Shane
<[EMAIL PROTECTED]
.AU> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Re: IEFACTRT exit
01/18/2008 02:50
PM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
On Fri, 2008-01-18 at 16:19 -0500, O'Connor, Ruth wrote:
> Any ideas about what could have happened to the initiator to affect an
> smf exit's WTOs?
Have a look at the subpool for any getmains.
Shane ...
----------------------------------------------------------------------
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
