ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » last api timestamp connection parameter

Post new topic  Reply to topic Goto page Previous  1, 2
 last api timestamp connection parameter « View previous topic :: View next topic » 
Author Message
jcv
PostPosted: Fri Jul 10, 2015 6:41 am    Post subject: Reply with quote

Chevalier

Joined: 07 May 2007
Posts: 411
Location: Zagreb

Cool, I missed that! Thank you.

By the way, I was impressed by your RFE 45694 back then when I voted for it, and unfortunately forgot later it was yours. If I remembered that, I would probably not mention the point of these RFEs the way I did. No hard feelings I hope?

And I probably agree with you, that PID and TID should be presented in PID and TID columns in chstatus table.
Back to top
View user's profile Send private message Visit poster's website
tczielke
PostPosted: Fri Jul 10, 2015 6:59 am    Post subject: Reply with quote

Guardian

Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA

jcv wrote:
By the way, I was impressed by your RFE 45694 back then when I voted for it, and unfortunately forgot later it was yours. If I remembered that, I would probably not mention the point of these RFEs the way I did. No hard feelings I hope?


I am not sure what you are talking about with "No hard feelings", but I did not take any offense to anything you have posted regarding RFEs.

For RFE 45694 - Internal Trace Table for MQ Distributed Tracing, thanks for the compliment, but I can't take much credit there. I am just copying what CICS and MQ already do on z/OS, probably since at least the 90s!.
_________________
Working with MQ since 2010.
Back to top
View user's profile Send private message
jcv
PostPosted: Fri Jul 10, 2015 8:08 am    Post subject: Reply with quote

Chevalier

Joined: 07 May 2007
Posts: 411
Location: Zagreb

Well copied then. If I was able to add kudos to your account on this forum, I certainly would. Unfortunately, the need to copy features from z/OS version of MQ to unix is a common thing.

Cheers.
Back to top
View user's profile Send private message Visit poster's website
tczielke
PostPosted: Fri Jul 10, 2015 8:10 am    Post subject: Reply with quote

Guardian

Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA

Thanks, again for the kind words. I appreciate it!
_________________
Working with MQ since 2010.
Back to top
View user's profile Send private message
jcv
PostPosted: Fri Jul 10, 2015 8:44 am    Post subject: Reply with quote

Chevalier

Joined: 07 May 2007
Posts: 411
Location: Zagreb

jcv wrote:

... PID and TID should be presented in PID and TID columns in chstatus table.


... as decimal values in their own separate columns, I meant.
Back to top
View user's profile Send private message Visit poster's website
jcv
PostPosted: Wed Jul 29, 2015 2:30 am    Post subject: Reply with quote

Chevalier

Joined: 07 May 2007
Posts: 411
Location: Zagreb

Hello, to conclude this thread, I would add that I could have written there more concisely:
Code:

$ echo "dis chs(SVRCONN_NAME) CURSHCNV" | runmqsc QM_NAME | grep CURSHCNV | awk -F '[)(]' '{print $2}'| awk '{ total += $1 }; END { print total }'
324
$

as one way to sum CURSHCNV values. And although it's obviously not that impossible to identify client connections of interest, as it appeared to me at first, DISCINT and ClientIdle let people set up automatic disconnect and avoid all that manual investigation and handling. So, that's why it is good they introduced it. Obviously, if applications used pooled connection factories, or behaved properly enforced by any other mechanism, even that would be unnecessary.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » last api timestamp connection parameter
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.