0587adbc-8477-431f-8c68-9226adea11ed
Blog
About this blog

Welcome to the Application Performance Management Blog, where you can read the perspectives from APM experts. This Blog provides insights into the Application Performance Management solution, as well as technical details about specific IBM products.
Related posts
Updated
Likes 2
Comments 0
Updated
Likes 4
Comments 0
Updated
Likes 2
Comments 0
Updated
Likes 1
Comments 0
Updated
Likes 1
Comments 0
ITM Tivoli Monitoring - KDEB_INTERFACELIST processing
With the introduction of changes for APARs OA37960 and IV12368 in 6.2.2-TIV-ITM-FP0008 and 6.2.3-TIV-ITM-FP0001, setting KDEB_INTERFACELIST causes ITM basic services to use an interface-specific bind rather than an anonymous bind. This change affects the situation where this level of code runs in parallel with older levels of code. Due to newer code using an interface-specific bind and older code using an anonymous bind, there is a contention between the two because TCPIP allows the two instances to each bind to the same port. The external symptoms of this is that the two instances continually go online and offline.
The circumvention is to either remove the KDEB_INTERFACELIST specification from the instances, or to configure the older instances such that an interface-specific bind is to be used. This is accomplished by prefixing the KDEB_INTERFACELIST value with the exclamation point character, for example: KDEB_INTERFACELIST=!SYSA
Tags: 
interface
bind
itm
|
Login to access this feature