Gerhard:
I honestly don't remember ever having the issue with IBM module(s). I
memory goes back to early MVS 2.0 and if we did have an issue it was
because TMS or some other vendor code hit the same module (open). In
the case of TMS it wasn't their fault so much as IBM didn't give
exits at the right points . I am not defending TMS but they just
happened to need the hooks in a "popular" spot.
Although I do not like how CA (ie TMS) and other products now put
zaps in on the fly (so to speak). I have been burned once or twice
with on the fly zaps as IBM quickly found the "finger prints" and
tossed me off the boat and I had to got to CA support begging because
IBM washed their hands of the issue once or twice. CA (this does go
back a few years) wanted to toss me back to IBM. I had to supply a
bunch of trace and dumps before CA would listen to me again but even
then I felt CA was trying to avoid the problem rather than working
with IBM & the customer to resolve the problem. The problem did get
resolved but it took days (or was it a week?) to get the problem
resolved. The biggest PITA was ACF2 (never a fan) and the way they
handled problems with TSO & Allocation. Of course the ACF2 person on
our side was well lets say less than average. I had to get involved
before the issue was resolved and I had to pound some manager at ACF2
to get them to listen. We got rid of ACF2 and never had an issue with
security after that.
Ed
On Jan 7, 2012, at 4:15 PM, Gerhard Postpischil wrote:
On 1/7/2012 2:31 PM, Ed Gould wrote:
constant zap issue. I can't remember of ever having the issue
with IBM as they send out module replacement (thanks!)
I feel its important to maintain the IDR to find out what level
the module is at. With the vendor I spoke of it was somewhat of
an issue at times.
That is why I am a strong supporter of module replacement and
zaps are for emergency fixes only.
I've had the issue with IBM modules a long, long time ago. Assuming
ZAPs are sequential, I prefer putting an identifier, APAR or
whatever, into the eyeball text at the beginning of the module.
That way I can see in a dump how it's been updated, rather than
having to run a report.
Module replacements take more effort and disk space, so ZAPs are
closer to being green <g>
Gerhard Postpischil
Bradford, VT
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
