On Mar 6, 2006, at 8:54 PM, Laura Prill wrote:
Thanks for all the comments so far. This third-party product has
its own
segregated CSIs, which is a good thing. But the product includes APF-
authorized libraries and SVCs, which is a bad thing. I suppose we
could
implement some convoluted scheme whereby Systems has to install
anything
that touches those modules, but in my mind it seems to be more
trouble than
it's worth. I really just wondered if anyone out there was
allowing SMP/E
use outside of Systems, period!
Thanks, Laura
Laura,
Yes that is an issue and there is no easy work around, AFAIK.
Several years ago I had heard rumors that some company had started to
maintain their source (read cobol) with SMP/e. I can not confirm this
but it was a rumor.
As we all know don't look to CA as a place that gets along with
SMPe. There are other companies that do a reasonable job (fewer than
you might wish though). Personally the number is probably in the 1 or
lower two digits that do a reasonable job with SMP/e.
Given that I would strongly suggest that the system group do the
installs for *ALL* products or at least the ones that need *ANY*
access to any system library. (I think I would include the linklist &
LPALIST in this) .
It really comes down to how good your company is with politics and
finger pointing as that what will happen, believe me. It will get
nasty, take my word for it.
Don't go with the "name of the group" would know better.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
