For SVRCONN channels on z/OS using the TCP protocol, this is the minimum time in seconds for which the SVRCONN instance remains active without any communication from its partner client. A value of zero disables this disconnect processing. The SVRCONN inactivity interval only applies between MQ API calls from a client, so no client is disconnected during an extended MQGET with wait call. This attribute is ignored for SVRCONN channels using protocols other than TCP.
This is very valuable. Why did IBM only roll it out to z/OS when 6.0 came out. Doesn't seem like it would rely on M/F specific technology to work. Hope it shows up in MQ 6.1 or 7.0. _________________ Peter Potkay
Keep Calm and MQ On
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum