| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| is eSQL code stored in broker database |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqmbuser |
 Posted: Fri Jan 07, 2011 12:21 am Post subject: is eSQL code stored in broker database |
 |
|
Newbie
Joined: 07 Jan 2011
Posts: 2
|
Hi,
We have a strange problem where we have to know what version of code has been deployed onto production.
Messages flows and Message sets has been deployed onto execution group but the barfile is missing and no one knows what version has been deployed.
There is a cvs repos but there are so many versions for it.
Does any one know is eSQLcode stored on any of the broker database tables?
if so,how to retrive it?
Thanks in Advance and any reply's are very much appreciated. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Jan 07, 2011 2:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's not a strange problem.
It's a failure in your procedures.
Deploy the right version. Stop worrying about whether the wrong version is deployed.
Take steps to ensure that the version you have deployed is tagged, so you know what version is deployed.
Don't let developers deploy ANYTHING to production. Assign *one* person to do *all* deployments.
Make them take notes. |
|
| Back to top |
|
|
| mqmbuser |
| Posted: Fri Jan 07, 2011 2:55 am Post subject: |
|
|
Newbie
Joined: 07 Jan 2011
Posts: 2
|
Thanks Jeff for your reply.
All you said is absolutely right but unfortunately i'm also very new to this ORG and i was asked to look into it rather than giving suggestions to them..
Going forward,they are setting up a deployment team
I tried taking out the code from the broker database tables and added a trace node and printing it as an Environment varaible but that's giving in all HEX format and even tried with converting that to CHAR using CAST function but no luck. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Jan 07, 2011 3:32 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
There's no easy way of extracting ESQL from a running broker. If you're running V7.0.0.2 you can use my pattern to recover the message flow source, but the ESQL will not be available from this.
Some alternative suggestions:
1. Check out the deployment information on the broker; the deployment time, BAR file information, userid etc. might give you additional clues.
2. Ensure that the source in the CVS repository is tagged with some version information. Embedding a string such as $MQSI CVS Version = $id$ MQSI$ is a start.
3. Deploy likely candidate message flows on an alternative broker until you get the same behaviour as the unknown broker.
4. Instigate a lessons learned session to get your deployment procedures up to scratch! |
|
| 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
|
|
|
|
