DSXchange

Enable 'checkpointing' and then ensure if any job aborts, the Sequence aborts as well.

I don't have any thoughts except the one that says it is always a good idea to create your own post when you have a problem. If it is similar to another post, put a link to it in your version of the issue.

You can also use Convert() to replace that space between the date and time with yet another dash.

Which is what I meant when I mentioned the "PAD character".

Another possibility - a Wait For File stage with the wait time set to zero does an existence check. Two triggers from the stage: success trigger runs the rest of the Sequence activities while a 'failure' trigger can do whatever you like when the file is not found (send an email?) including do nothin...

OK, very nice - found your corrected post where you linked to the original topic rather than hijacking it... but it was after I'd already moved this one over. I've deleted that one but it showed that you are running a Windows server so I updated the original post here.

Let's get this out of the way first: Beacuse of this as expected value generated will not be continuous. ]So no issue here but there is gap in sequence generated. Why is this in any kind of concern? Having "gaps" in surrogate key sequences is normal, expected and nothing to lose any sleep ...

I split your question out into its own post so you have full control of its fate. But to do so, I had to guess at your particulars. First question - is your DataStage server on Windows or UNIX? After that, which part of the linked answer was unclear? What additional information are you looking for? ...

I haven't seen or heard of anyone making the leap to Enterprise SSDs yet for DataStage but I imagine the only challenge would be to cut through all of the vendor hype and find out how well the various models actually perform. From what I've seen (looking for and implementing a personal SSD boot driv...

I understand but you need to pick a maximum and work with that. Profile the data you are receiving and see what the max occurance is and then use something higher to be safe. That or upgrade to 8.5 where all those shenanigans become unnecessary.

It's not until you get to 8.5 that you can create multiple output records from one input record, which is the 'looping' that I mentioned. Before that, what you need to do is turn your one big delimited column into separate columns and you can use the Field() function for that or the Column Import st...

Are you certain you can't use CHAR for this? Have you actually tried it? It's a delimited file so it seems to me that it should read it based on the delimiters rather than the field size and if one is 'short' it will use the PAD character defined to expand it to full size, so make sure that is set t...

Please show us what you tried and what isn't working about it. Also let us know if you have 8.5 or higher as that means there is a 'looping' solution for this.

Moved to the TX forum.

So, in other words...

vskr72 wrote:Any other way than hardcoding it?

No.