| Author |
Message
|
| sleepyjamie |
 Posted: Mon Aug 24, 2015 7:22 am Post subject: mqsicreatebar deployAsSource |
 |
|
Centurion
Joined: 29 Apr 2015
Posts: 135
|
| I'm wondering what the advantage/disadvantage of the deployAsSource parameter within the mqsicreatebar command? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Aug 24, 2015 8:13 am Post subject: Re: mqsicreatebar deployAsSource |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sleepyjamie wrote: |
| I'm wondering what the advantage/disadvantage of the deployAsSource parameter within the mqsicreatebar command? |
Well according to the manual, there are some things that have to be deployed as source... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sleepyjamie |
| Posted: Mon Aug 24, 2015 8:26 am Post subject: Re: mqsicreatebar deployAsSource |
|
|
Centurion
Joined: 29 Apr 2015
Posts: 135
|
Here is the documentation on the mqsicreatebar command from IBM
(Optional) Include this parameter to deploy applicable resource files without compiling them. This parameter has similar function to the compile and in-line resources option in the IBM® Integration Toolkit.
When using the mqsicreatebar command, resources such as .esql files are compiled into message flow .cmf files, and are not added to the BAR file as individual source files. If this parameter is included, it creates inline ESQL instead of the default deployable ESQL.
When the -deployAsSource parameter is used, any applicable resources are added to the BAR file as source files, and are not compiled into message flow .cmf files.
You cannot include both the compiled (.cmf) and source (.msgflow) versions of a message flow in a BAR file.
I don't see anything here that states that some resources must be left as source. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 24, 2015 8:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What have you read about the different new options on the MAPS V8 and above??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sleepyjamie |
| Posted: Mon Aug 24, 2015 8:56 am Post subject: |
|
|
Centurion
Joined: 29 Apr 2015
Posts: 135
|
| fjb_saper wrote: |
| What have you read about the different new options on the MAPS V8 and above?? |
I am only using v9.0, I don't have any previous experience with V8 or below.
Some of our bar files do contain .rules and .map files. I would guess these don't need to be compiled.
I guess that is where I am trying to understand is what is the advantage of compiling (e.g. esql file) versus leaving it as source, before it is deployed to the broker? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Aug 24, 2015 8:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The difference is what you will see in the EG after deployment.
In one case, you will only see msgflow files.
In the other case, you will *also* see .esql files.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
