Re: SQ20226 - The maximum number of stacked diagnostics areas has been exceeded.

[rob@xxxxxxxxx]

Finally got a fix from IBM.  PTF # SI17194.  It's still in test mode.

Turned out, that the part generating this was doing no imbedded SQL.  Just 
a CLRLIB.  Took some TRCJOB's of the loop before, and after, the error 
started occurring to pin it down.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





rob@xxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/09/2004 10:12 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
SQ20226 - The maximum number of stacked diagnostics areas has been 
exceeded.






I seem to be getting these in a job log on a program that sits in a never 
ending loop until a data area tells it to stop.  After x number of seconds 

it checks the data area, then checks for some other stuff, and it neither 
then waits again.  Job gets restarted by the backup.  Starts around 3am 
and starts generating this message around 10am.  As far as we can tell, 
everything is working ok.  IBM said that there was an apar on it very 
early on in V5R3 but it dealt mainly with stored procedures and the genre, 

and was fixed in new base code.  Here, were just using simple imbedded 
SQL.  Can't get the developer in charge of that project to delve into it 
since 'it seems to be working - just noticed this in the joblog'.  Anyone 
else came across this and what ramifications there were - if any?  Job 
log's from/to programs never seem to point to our programs - only system 
type programs.  Even in message above and below it.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.