Originally posted by: SystemAdmin

I've always thought a "Burst Count" command would be useful, but alas we don't have one yet.

Has anyone worked out a way to count the Burst that is currently being processed in a map?

E.g. simple input file containing 4000 defined records. Burst mode with Fetch of 1000. Therefore we know there will be 4 bursts in total. In my output card I want to PUT ("FILE", "C:\RecordSet_" + Index(Burst) ) to end up with 4 files named RecordSet_1, RecordSet_2 etc.

Using a group (0:s) in your output card, and INDEX($) or even a functional map will not work as you will always only have 1 occurence of that output according to the map.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Tarun
Would a GETandSET work here or another outside variable read per burst.
Tim
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hi Tim,

I was just trying GETANDSET one this morning (using a second input file with only an integer in it) but not having much luck as it only updates the number once at the end of the map run (I tried various commit options).

I can get it to work if I use a second input file containing a fixed number of incrementing values such as
1
2
3
4
5
etc
and then read this in as my 2nd input card in Burst mode with FetchUnit=1.

However as you might imagine this creates a dependency on this fixed file.

Could really do with that IndexBurst command!

Thanks,

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

Originally posted by: SystemAdmin

This worked nifty for me. I tried GetAndSet on an input card that was a single number field. I use a source of Echo and the value of 0 (zero). Then in my first output card I did a GetAndSet:
code:1:a0073b7d17
InputCard : SeqNo
Type Tree : Single Number Field
Source : Echo
Value : 0

OutputCard: Burst_Instance
Type Tree : Single Number Field
Source : Sink
Rule : =GetAndSet(SeqNo,SeqNo + 1, 2)

[/code:1:a0073b7d17]

Now the secret to using the correct value is to reference b:a0073b7d17Burst_Instance[/b:a0073b7d17] and not b:a0073b7d17SeqNo[/b:a0073b7d17]. The reason is b:a0073b7d17SeqNo[/b:a0073b7d17] doesn't exactly keep up for some reason. I think it might have to do with the min/max settings on the number field type tree.

Hope this helps,
John M Gibby
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange