Andi,
IBM suggested it might be ACF2 based on their review of the data we sent
them. We had the IBM and Broadcom developers meet about this issue and the
result is the
issue we are having with TCPIP is back in IBMs hands and is no longer
considered a possible ACF2 issue. The issue is we are getting different abends
in TCPIP such as
878-0C
653
4C5
To recover TCPIP we have to issue command
V TCPIP,,SYSPLEX,JOINGROUP
When we back out z/OS 2.5 the problem goes away. Looks like IBM changed
something in TCPIP that can not handle the volume of TCPIP traffic we receive
and the way we receive it. IBM is still trying to figure out our issue. Were
you able to resolve your situation with TCPIP on Z/OS 2.5? If so how? Do you
have an IBM case number that you could share?
Michael Brennan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
