> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Bernd Oppolzer
>
> I only had similar problems once in 2008 ca., but then subtasking was
> involved and APL etc., and there
> was some sort of race condition where one subtask ran too fast and the
> POST/WAIT protocol dit not work
> ... ABEND S201, IIRC ...
> the error was in IBM code, not in ours.
>
> The problem occured only on newer hardware with many processors, only every
> 5 hours or so, and only when there was heavy load by other concurrent jobs.
> IBM maintenance was not able to reproduce the error, because our machines
> were faster than theirs.
>
> Very hard to find ...
>
> I don't think that such problems may be involved here ...
I'm inclined to think not, as well. GTF trace (we captured the last 15 seconds
or so before dump invocation) showed that each alteration of the monitored
storage was caused by the same LE module, and the only two values observed were
x'00000000' and the same non-zero value every time it was non-zero.
> another idea that comes to mind: areas of storage that are normally zero, but
> now due to opsys release
> changes etc. are non-zero, and the application (which by error doesn't
> initialize some automatic
> variables properly) now fails.
> That is: a programming error that was there all the time, but now shows up
> for the first time.
Certainly possible, but we think very unlikely. The same source code, compiled
with COBOL 4.2, runs without problem "every time". The application program
itself was first written in 1996, when we were using OS/VS COBOL and VS COBOL
II.
And we still run z/OS with VSM USEZOSV1R9RULES=YES defaulted in DIAGxx.
-jc-
**********************************************************************
Information contained in this e-mail message and in any attachments thereto is
confidential. If you are not the intended recipient, please destroy this
message, delete any copies held on your systems, notify the sender immediately,
and refrain from using or disclosing all or any part of its content to any
other person.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
