Originally posted by: SystemAdmin

At the moment I' upgrading some interfaces from Version 1.4.2 (yes it's still alive) to version 6.7.1.

In the old version there was on the event server settings for output cards the following options available:

• choice between "Create" - "Delete Always" - "Append"
• additonal flag "Delete if Empty" yes or no

This will give 5 useful combinations:

1. "Create" + "Delete if Empty" = yes
- this is the same as "CreateOnContent" in 6.7.1

2. "Create" + "Delete if Empty" = no
- this is the same as "Create" in 6.7.1

3. "Delete Always" + "Delete if Empty" = yes or no
- this is the same as "!Create" in 6.7.1

4. "Append" + "Delete if Empty" = yes
- this is not available in 6.7.1

5. "Append" + "Delete if Empty" = no
- this is the same as "Append" in 6.7.1

But I need the combination number 4. I have a lot of situations, where one map creates in case of problems with the data a log file. This log file is processed by the next map time and event triggered e.g. every 15 minutes. If there were within the 15 minutes more problems, then the information should be appended to the log file. But if there are no problems at all then the log file should not be created and the next map will never be triggered.

Is there a way or workaround in order to get combination number 4 back?

Hope to get a solution soon.

Joerg
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Can you not do a createoncontent on the first map and use append on subsequent maps?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I was already thinking of the same solution, but this idea means I have to add a map in between, which pick up the output file of the first map (if there is an output) and append the content to the real file, which I want to process time and event triggered. That will blow up the system with additional watches and resources.

I'm looking for a solution, which is a one to one copy of the way how Mercator 1.4.2 was working. Maybe somthing to be picked up by the developers of Datastage TX.

Kind Reagards,

Joerg
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange