I guess some more testing is required. At least i'm not the only one to
be supprised. Indeed, a pmr sounds about right at this point.
I guess a test would be pretty easy, restart (logoff/logon) one of the
TCPIP stacks and see if it produces one record. Next fiddle with NETSTAT
OBEY and see if the second record appears. Your remark on DIAG 0xDC does
point in this direction. I also discussed with a collegue and he
confirmed the NETSTAT OBEY at least once after the last IPL.
Thank you all for the help.
Regards, Berry.
Op 14-06-11 02:49, Alan Altmark schreef:
On Monday, 06/13/2011 at 07:46 EDT, Berry van Sleeuwen
<berry.vansleeu...@xs4all.nl> wrote:
I think so but I'm not quite sure. We use the NETSTAT OBEY sometimes,
usually for stop or start of a link. For instance NETSTAT OBEY START
DEVHW1.
The only way I could think of to get the same record more than once is to
declare it more than once to CP. (DIAG 0xDC doesn't appear to have a
"this buffer has been previously declared" return code.)
It would be interesting to know if the number of extra LCB (0x05) monitor
records is in any way related to the number of times you START the device
or re-define any of the LINK attributes.
I agree with Bill; you need a PMR to poke at it further.
Alan Altmark
z/VM and Linux on System z Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott
