Avoiding 0 byte Sequential File creation

[SachinCho]

Hi,
I have one parallel job in which is common for two processes. Depending upon process name there are two flows inside it say A and B. Now if process name is A it generates XML file and if process name is B then it generates seq file.
Requirement is if job runs for process A then only XML file should be generated while actually 0 byte seq file of process B is also getting generated.

Any idea how to restrict this in job itself. Process flow is seperated after transformer.

[ArndW]

While you cannot prevent the file creation, you could add an after-job call to UNIX which would delete those files if empty.

[gssr]

Hi,
I have one parallel job in which is common for two processes. Depending upon process name there are two flows inside it say A and B. Now if process name is A it generates XML file and if process name is B then it generates seq file.

Can you provide the Job Design and stages deployed. So that everyone get a clear idea about the creation of XML and Seq File.

[gssr]

Hi,
I have one parallel job in which is common for two processes. Depending upon process name there are two flows inside it say A and B. Now if process name is A it generates XML file and if process name is B then it generates seq file.

Can you provide the Job Design and stages deployed. So that everyone get a clear idea about the creation of XML and Seq File.

[chulett]

Doesn't really matter as (bottom line) the file creation cannot be avoided. The stage creates the file when the job starts, regardless of 'flow'. Arnd has noted the typical 'workaround' for this.