| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Finding out if a channel is still used or not? |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Wed Oct 27, 2021 11:47 am Post subject: Finding out if a channel is still used or not? |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Assuming we have various ancient channels (especially svrconn) that are probably no longer used - how do we prove 100% that is true (short of disabling the channel)?
Channel events are one option (but we don't want to keep too many of these event messages).
Is there anything recorded in SMF for MQ on z/OS for channel names?
CHIN syslog is another option but tedious to deal with.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
 |
| elkinsc |
| Posted: Wed Oct 27, 2021 12:13 pm Post subject: |
|
|
Centurion
Joined: 29 Dec 2004
Posts: 138
Location: Indy
|
Greetings,
Yes channel names are in the task accounting data (Accounting class 3 - the WTID record) and of course in the Channel Accounting data (Accounting class 4).
One thing to remember is that the client channel connect and disconnect messages can be (and often are) suppressed so do not show up in the CHIN JES log. If the clients are particularly poorly behaved suppressing those messages can save a lot of CPU.
So the data is available, but it is from a tedious location no matter which way you look at it. 
Thanks
Lyn |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Oct 27, 2021 10:43 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Thanks
It would be handy if MQ kept the channel's last start date in the MQ object itself (rather like the last modification date).
Just the date would only need one update per day so low overhead.
I guess I will have to try out whatever has replaced the RFE system....
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Oct 28, 2021 12:19 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon Nov 01, 2021 11:01 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
<vendor_plug>
If you want a simple but effective solution, you could use Capitalware's MQ Channel Connection Inspector for z/OS (z/MQCCI). z/MQCCI allows a company to track and/or audit what information a client application or remote queue manager is exchanging with the local queue manager when a connection is made.
z/MQCCI is designed to provide the MQAdmin with any or all of the fields of the MQCD and MQCXP structures from a client connection to a queue manager in a "human readable" format.
Example MQCCI output written to a CSV file:
| Code: |
| 2021/09/24 18:49:43.675307, CONN, Tag=2HSQpOrnmilh8nwF, CD_QMgrName=MQWT1, CD_ChannelName=TEST.EXIT.CHL, CD_ConnectionName=10.10.10.10, CD_ShortConnectionName=10.10.10.10, CD_MaxMsgLength=4194304, CD_PutAuthority=MQPA_DEFAULT, CD_MCAUserIdentifier=roger, CD_RemoteUserIdentifier=roger, CD_RemotePassword_Length=0, CD_SSLCipherSpec=, CD_SSLClientAuth=MQSCA_REQUIRED, CD_CertificateLabel=, CXP_PartnerName=roger, CXP_SSLCertUserid=, CXP_SecurityParms_AuthenticationType=MQCSP_AUTH_USER_ID_AND_PWD, CXP_SecurityParms_UserId=roger, CXP_SecurityParms_Password_Length=8, CXP_SharingConversations=TRUE, CXP_MCAUserSource=MQUSRC_MAP, CXP_RemoteProduct=MQJB, CXP_RemoteVersion=09010000, |
| Code: |
| 2021/09/24 18:49:46.044185, DISC, Tag=2HSQpOrnmilh8nwF, CD_QMgrName=MQWT1, CD_ChannelName=TEST.EXIT.CHL, CD_ConnectionName=10.10.10.10, |
Note: The above example is 2 very long lines.
Or the user can select "Pure CSV" then the output will look like:
| Code: |
| "Date Time", "Connection Type", "Tag", "CD_QMgrName", "CD_ChannelName", "CD_ConnectionName", "CD_ShortConnectionName", "CD_MaxMsgLength", "CD_PutAuthority", "CD_MCAUserIdentifier", "CD_RemoteUserIdentifier", "CD_RemotePassword_Length", "CD_SSLCipherSpec", "CD_SSLClientAuth", "CD_CertificateLabel", "CXP_PartnerName", "CXP_SSLCertUserid", "CXP_SecurityParms_AuthenticationType", "CXP_SecurityParms_UserId", "CXP_SecurityParms_Password_Length", "CXP_SharingConversations", "CXP_MCAUserSource", "CXP_RemoteProduct", "CXP_RemoteVersion", |
| Code: |
| 2021/09/24 18:50:10.705293, "CONN", "nk6KlZ3jgc6MUsCP", "MQWT1", "TEST.EXIT.CHL", "10.10.10.10", "10.10.10.10", 4194304, "MQPA_DEFAULT", "roger", "roger", 0, "", "MQSCA_REQUIRED", "", "roger", "", "MQCSP_AUTH_USER_ID_AND_PWD", "roger", 8, "TRUE", "MQUSRC_MAP", "MQJB", "09010000", |
| Code: |
| 2021/09/24 18:50:10.725120, "DISC", "nk6KlZ3jgc6MUsCP", "MQWT1", "TEST.EXIT.CHL", "10.10.10.10", |
Note: This example is 3 very long lines.
</vendor_plug>
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
