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 » security exit

Post new topic  Reply to topic
 security exit « View previous topic :: View next topic » 
Author Message
jim
PostPosted: Sat Mar 29, 2014 1:26 am    Post subject: security exit Reply with quote

Voyager

Joined: 26 Nov 2013
Posts: 94

If the SVRCONN is running and we need to update the security exit file.

The above task have any chance to impact channel process.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Sat Mar 29, 2014 3:13 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Yes.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
jim
PostPosted: Sat Mar 29, 2014 4:33 am    Post subject: Reply with quote

Voyager

Joined: 26 Nov 2013
Posts: 94

PeterPotkay wrote:
Yes.



I such case we need to stop the channel and then proceed ?
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Sat Mar 29, 2014 4:56 am    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

You can not change any channel exits dynamically - ie a running channel will not somehow magically pick up a new channel exit and start running with it. Generally speaking chaos would ensure if it did.

To pick up a new exit the channel must be stopped and restarted.

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
jim
PostPosted: Sun Mar 30, 2014 7:07 am    Post subject: Reply with quote

Voyager

Joined: 26 Nov 2013
Posts: 94

PaulClarke wrote:
You can not change any channel exits dynamically - ie a running channel will not somehow magically pick up a new channel exit and start running with it. Generally speaking chaos would ensure if it did.

To pick up a new exit the channel must be stopped and restarted.

Cheers,
Paul.


Hi Paul

Can we alter the sycdata attibute on the channel without changing the config files

It will also impact.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Mar 30, 2014 7:19 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.

jim wrote:
Can we alter the sycdata attibute on the channel without changing the config files

It will also impact.

You can change channel attributes at any time, but changes will not take effect until the channel is stopped/started.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Mar 31, 2014 1:19 pm    Post subject: Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

Stopped, or goes INACTIVE....
_________________
Glenn
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Mar 31, 2014 1:38 pm    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

Neither

The channel has to be not running which is not necessarily either of those.

Of course if a channel is INACTIVE (ie not reported by DIS CHS(*)) then the channel is not running. However, a channel can well be running even though it is in STOPPED status. You can always query the value of MCASTAT to see whether the channel is running.

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
gbaddeley
PostPosted: Wed Apr 02, 2014 1:25 pm    Post subject: Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

The exit is loaded into the MCA thread for a new channel instance at initialization, and stays with the channel instance until it terminates ???
_________________
Glenn
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Wed Apr 02, 2014 1:31 pm    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

Yes, pretty much. The channel loads the channel shared library and resolves the entry point address. The library isn't generally unloaded until the channel ends. You can see when this all happens by looking at an MQ channel trace.

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
tczielke
PostPosted: Thu Apr 03, 2014 4:54 am    Post subject: Reply with quote

Guardian

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

On Unix/Linux the lsof command (or its equivalent) could also be helpful for tracking the exit.

For example, let's say we have the logip exit in /var/mqm/exits64 and it currently has an inode of 131122.

mqm$ pwd
/var/mqm/exits64

mqm$ ls -i logip
131122 logip


You can run the following lsof command to see what processes currently have the exit loaded. Note to that the inode being reported is 13112.

mqm$ lsof -u mqm | grep logip
amqrmppa 29210 mqm mem REG 253,7 8550 131122 /var/mqm/exits64/logip


After shutting down your channels, you can run another lsof to confirm that no mqm processes have the logip exit loaded.

mqm$ lsof -u mqm | grep logip
mqm$


Make your update now to your logip exit, and note if the inode did change. In this case, it changed to 131125.

mqm$ pwd
/var/mqm/exits64

mqm$ ls -i logip
131125 logip


Now start your channels again, and your lsof command should show that the new logip (with the new inode) is being executed.
NOTE: It is possible to not get a different inode number when you change the exit file.

mqm$ lsof -u mqm | grep logip
amqrmppa 29210 mqm mem REG 253,7 8550 131125 /var/mqm/exits64/logip


If your environment is Windows, the freeware Sysinternals Process Explorer tool would be very helpful for this type of check, as well.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » security exit
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.