| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Fileoutput node Diractory and Name setting |
« View previous topic :: View next topic » |
| Author |
Message
|
| PEPERO |
 Posted: Sun May 28, 2017 9:30 pm Post subject: Fileoutput node Diractory and Name setting |
 |
|
Disciple
Joined: 30 May 2011
Posts: 177
|
Hi all;
In a message flow a huge message is splitted to smaller messages using a compute node. Since each of the propagted small message from the compute node contains an outputlocalenvironment with the following tree
| Code: |
(0x01000000:Name):Destination = (
(0x01000000:Name):File = (
(0x03000000:NameValue):Directory = '/u/broker/axs05' (CHARACTER)
(0x03000000:NameValue):Name = '1.MCOL1047' (CHARACTER)
)
)
|
This structure is maintained just before the FILEOUTPUT node as a trace node before the Fileoutput node proves this. So it is expected the output file node use the Directory and Name from the input local environment , but it doesnt.
It seems the local environment which is passed to the output file node is the one constructed when reading the first recoed cause the trace node put in the Failre path of the FILEOUTPUT node shows this.
I've to say that the file is produced in the mqsitransit directory but when it receives the Finish file event , it couldn't move the file to the desired directory. |
|
| Back to top |
|
 |
| kash3338 |
| Posted: Mon May 29, 2017 12:08 am Post subject: Re: Fileoutput node Diractory and Name setting |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| PEPERO wrote: |
| This structure is maintained just before the FILEOUTPUT node as a trace node before the Fileoutput node proves this. So it is expected the output file node use the Directory and Name from the input local environment , but it doesnt. |
What is the failure message? Did you capture the complete failure message and check for the exact error? Is it something to do with fail writing permissions?
| PEPERO wrote: |
| It seems the local environment which is passed to the output file node is the one constructed when reading the first recoed cause the trace node put in the Failre path of the FILEOUTPUT node shows this. |
This is the expected behaviour in case of failure. When a failure occurs, the Localenvironment in the failure terminal will contain the details of Input File node and not the altered local environment.
Check for the complete error message. |
|
| Back to top |
|
|
| PEPERO |
| Posted: Mon May 29, 2017 12:31 am Post subject: |
|
|
Disciple
Joined: 30 May 2011
Posts: 177
|
Since i don't want the values set for the fileoutput node at design time be used in runtime, the related attributes are left null. The failure occurs due to null values for the Directory and Name attributes.
The interesting issue is that the file is created with correct name '1.MCOL1047' in the mqsitransit directory but when it wants to put the file in the desired directory '/u/broker/axs05' on Finish event , the failure path is run. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Mon May 29, 2017 2:12 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| PEPERO wrote: |
Since i don't want the values set for the fileoutput node at design time be used in runtime, the related attributes are left null. The failure occurs due to null values for the Directory and Name attributes.
The interesting issue is that the file is created with correct name '1.MCOL1047' in the mqsitransit directory but when it wants to put the file in the desired directory '/u/broker/axs05' on Finish event , the failure path is run. |
That cannot be the issue. You can leave the File Output Node directory and File name fields blank and set them in ESQL.
Post your complete exception message. Get a user trace and check for the exact error message. |
|
| 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
|
|
|
|
