Knutson, Sam wrote:
Fixes exist for CA-NETSPY
http://bama.ua.edu/cgi-bin/wa?A2=ind0501&L=ibm-main&P=R58816&I=1
An option to configure DATASPACE instead of ECSA use by CA-DATACOM is
available
http://bama.ua.edu/cgi-bin/wa?A2=ind0412&L=ibm-main&P=R54425&I=1
As for CA-OPERA, IBM OMEGAMON for CICS, and LRS DRS why don't you open an
incidents with the respective vendors and join the windmill "tilting" club?
The purpose of the exercise is to improve availability long term by getting
vendors to comply with IBM Integrity guidelines. If you explain it properly
to them and document findings of cooperation and lack of to your peers you
will help everyone over time.
If you want help with language or references let me know.
As for a little bit compared to a lot consider that you cannot be a "little
bit pregnant". Only if you have no products which violate this guideline
can you exploit TRAPS to prevent the abuse.
I wish that CA and BMC would both tackle this across zSeries internally but
for the current time the only way to do it seems to be product by product
making the reports as an external customer.
Thanks, I had missed the fix for NETSPY. As for DATACOM, we only started
running it
recently, and I hadn't realized it was doing this untill I issued the
command to send to the list.
I had forgotten OMEGAMON was now IBM's, so it is IBM's to fix even if
inherited.
Sometime I will have to track down who is causing this in CICS.
I do try to get these fixed when I have a chance, but some are not my
products and I don't
have contact info. But I will try to get others to open problems as well.
Richard
----------------------------------------------------------------------
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
