Author |
Message
|
saddankula |
Posted: Tue Jun 07, 2016 9:37 am Post subject: How to extract esql code from the deployable message flows |
|
|
Acolyte
Joined: 27 Jun 2013 Posts: 51
|
Hi Team,
In MQ 7 I have used
mqsibrowse MB7BROKER -t brokerresources > C:\Broker.txt to extract esql code from the deployable message flows.
But in MBV8 &IIB how can i extract esql code from the deployable message flows which are deployed in Broker |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jun 07, 2016 9:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It depends on if the ESQL code is included or not, and if subflows are inlined or not and and and and...
Also, you should never need to read runtime resources to figure out what they are doing.
You should know what was deployed, based on a source control system.
If you need to figure out what a flow is doing during runtime, you can enable a usertrace. Among other things, that will show you the steps that the ESQL code takes. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
saddankula |
Posted: Wed Jun 08, 2016 4:16 am Post subject: |
|
|
Acolyte
Joined: 27 Jun 2013 Posts: 51
|
Can any one please suggest what is equivalent command to mqsibrowse command in MB8&IIB9,
pls provide command |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jun 08, 2016 4:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
Vitor |
Posted: Wed Jun 08, 2016 4:48 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
saddankula wrote: |
Can any one please suggest what is equivalent command to mqsibrowse command in MB8&IIB9, |
I agree with my most worthy associate:
a) this command seems to have been retired
b) you should obtain the ESQL from a source code control repository rather than the deployed flow. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
maurito |
Posted: Wed Jun 08, 2016 11:24 pm Post subject: |
|
|
Partisan
Joined: 17 Apr 2014 Posts: 358
|
This from my windows box:
Code: |
MQSI 9.0.0.5
C:\Program Files\IBM\MQSI\9.0.0.5
C:\temp>mqsibrowse
BIP8121W: Lists the contents of a components persistent store.
Syntax:
mqsibrowse componentName -t persistentStoreTable
Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse.
BIP8007E: Mandatory argument missing.
When using this command interface the user should supply the mandatory argument.
Correct and reissue the command.
|
|
|
Back to top |
|
 |
saddankula |
Posted: Thu Jun 09, 2016 3:05 am Post subject: |
|
|
Acolyte
Joined: 27 Jun 2013 Posts: 51
|
MQSI 9.0.0.5
C:\Program Files\IBM\MQSI\9.0.0.5
C:\temp>mqsibrowse
BIP8121W: Lists the contents of a components persistent store.
Syntax:
mqsibrowse componentName -t persistentStoreTable
Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse.
BIP8007E: Mandatory argument missing.
When using this command interface the user should supply the mandatory argument.
Correct and reissue the command.
-------------------
I got same description in UNIX server also.
Can any one suggest what is component Name' and persistentStoreTable in below command options. Pls suggest
Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse. |
|
Back to top |
|
 |
maurito |
Posted: Thu Jun 09, 2016 3:15 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014 Posts: 358
|
saddankula wrote: |
MQSI 9.0.0.5
C:\Program Files\IBM\MQSI\9.0.0.5
C:\temp>mqsibrowse
BIP8121W: Lists the contents of a components persistent store.
Syntax:
mqsibrowse componentName -t persistentStoreTable
Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse.
BIP8007E: Mandatory argument missing.
When using this command interface the user should supply the mandatory argument.
Correct and reissue the command.
-------------------
I got same description in UNIX server also.
Can any one suggest what is component Name' and persistentStoreTable in below command options. Pls suggest
Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse. |
You should raise a PMR asking IBM to document the command and its options |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jun 09, 2016 4:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Why are you so strongly dedicated to getting this command working in IIB v9?
Have you (or the customer/client/company you are working for) lost all of their ESQL code?
If they are moving from MB v7, then there's a very strong possibility that the business requirements have changed. So it's probably better to rebuild from scratch.
If they are trying to save money by not having to rebuild everything from scratch, then it's clear they didn't understand the risks of not using a source control system. And you should start by getting one of those set up before you do anything else.
Using the Mapping node feature in v9 should also save you a lot of time in rebuilding flows, without having to recover the ESQL.
Again, a user trace can show you everything that the ESQL code is doing, and even give you the actual code statements that are doing them.
But not necessarily in a pretty package. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jun 09, 2016 4:40 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
maurito wrote: |
You should raise a PMR asking IBM to document the command and its options |
Or to confirm that the command is undocumented in IIBv9 and therefore unsupported. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jun 09, 2016 4:41 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Why are you so strongly dedicated to getting this command working in IIB v9?
Have you (or the customer/client/company you are working for) lost all of their ESQL code?
If they are moving from MB v7, then there's a very strong possibility that the business requirements have changed. So it's probably better to rebuild from scratch.
If they are trying to save money by not having to rebuild everything from scratch, then it's clear they didn't understand the risks of not using a source control system. And you should start by getting one of those set up before you do anything else.
Using the Mapping node feature in v9 should also save you a lot of time in rebuilding flows, without having to recover the ESQL.
|
Even if this works, it's a rubbish way to store source code. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|