Shmuel wrote:
> IMHO, poor programming caused the outage, and your enterprise is far
more at risk from that than it is from changes to undocumented
interfaces. This scenario reminds me of the wailing and gnashing of
teeth when programs that were working fine[1] under OS/360 started
taking S0C4's under OS/VS1 and OS/VS2. Also, did you go to a new z/OS
release without doing regression testing?

You are right that the root cause is bad programming. The vendor has
since resolved the problem by rewriting their code. My main complaint
was that the change was undocumented (so I spent a lot of time debugging
it) not that GETMAIN changed.
By the way, this happened during an ESP so, yes, we were doing
regression testing.

As far as source code, acquisitions don't always come with compliant
programmers and source code.

Jon

Jon L. Veilleux 
veilleu...@aetna.com 
(860) 636-2683 


This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna   

----------------------------------------------------------------------
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