Leonard,
I'm sad to say that this may be another occurrence of IC20140 (or one of
its sysroutes). The only thing that doesn't match up is the first
'Address' value (10008d66); this value has pretty consistently been
'101331ce' for me.
If this error occurred during an EXPORT SERVER or EXPORT NODE, then its
still probably a pretty good hit. Unfortunately, you may not like the fix.
I reported the problem to IBM Support in July and was told I ought to
upgrade to V3 (note that IC20140 is a V3 APAR). I pointed out to them that
V2 still had over 2 months of support and I wanted to see the problem fixed
in V2. They said they'd think about coming out with a PTF 15 for NT but
did nothing, and finally told me two weeks ago that they had no plans to
fix the problem in V2.
I can't really give you a good circumvention. I haven't seen the problem
when I ran exports consecutively (1 at a time) but I can't really afford to
do that so I can't say I gave that a really good test.
I haven't seen the problem occur in V3 although I've only been running at
that level for about a week. I'll know more in a couple of weeks.
Good luck and thanks for the venting opportunity.
Dennis Schaffer
Mutual of Omaha
SNOLEN AT VM.SAS DOT COM on 10/05/98 05:22:40 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Dennis Schaffer)
Subject: adsm 2.1 wnt server failure - anyone seen pkthread.c(2550) error
Has anyone seen the following error? We saw this on a windows nt
2.1 ptf .14 adsm server last night. I did not find a match on IBMLINK.
ANR9999D pkthread.c(2550): ADSM Exception Information:
Code = c0000005, Address = 10008d66Attempt to write data
at address 44a7038
Thanks len boyle
-------------------------------------------------------------------------
Leonard Boyle, Mainframe support snolen AT vm.sas DOT com
Leonard Boyle, Mainframe support snolen AT vm.sas DOT com
SAS Institute Inc. ussas4hs@ibmmail
Room E206 (919) 677-8000 ext 6241
203 SAS Campus Drive
Cary NC 27513
|
