DSXchange

Exactly the same answers as you already got in your other post.

kumar_s wrote:By doing so, eventually lost a day.

Um... what is that supposed to mean?

Your IConv mask needs to match the input format of the date in question. There are ways to make it fairly flexible, but if you are going to spell it out, at least make sure they match! And it's square brackets, not parens. Since your one sample date shows as "2006-04-20" try this: Iconv(LK_EBCDI...

Exactly - one way or anther you need to get them both into the same 'format' before the lookup can be performed. Looks like the shortest approach would be to take the CFF date and use IConv to get it into 'internal' format... as long as those two formats matched for the same calendar date.

How did you guys manage this? Now we're all stuck inside Krazykoolrohit's world... help!

The issue now is when i say that job2 should run after job1 unconditionally and job1 fails, i want the control to pass to job2. ofcourse i need the exceptional handler to work too for job1? If I'm understanding your need, you are out of luck - you can't have it both ways. Either you are handling jo...

The first time when it corrupted, I did manually correct the problem. Since it happened again, I want to know how it happened. Let us know what you find. You'd have to be more specific about the nature of the problem. Note that it is not 'corrupted' per se but 'out of sync' to me - and you'd need t...

Hashed files would not be in any 'export dsx', you'd need a filesystem level backup. Or you'll need to identify which records are incorrect and update them with their correct values.

The syntax to do so has been posted here multiple times, a search for SDKSequences should turn it up...

No pound/hash signs... and you need to qualify the counter with the name of the stage it comes from:

You are manually scheduling jobs into cron? Don't. Use Director which will build a proper crontab entry for you automagically.

Apologies Michael, perhaps a bad choice of word. I wasn't sure how to qualify your frustration in the post and that was the word that came to mind. Hope everyone realizes what I meant.

Perhaps a small edit is in order...

Only if you've made them 'Multi-Instance' jobs and built them with that in mind.

It really depends on what the OP needs. If the fields can be strung together willy-nilly, each piece picking up where the previous piece ends, then all this 'concatenation' advice is fine. If the fields need to be of a certain consistant size, starting and ending in consistant positions with no deli...

A non delimited one field file, yes. A fixed width file, i am not too sure about that. If thats what the OP wants then he has to make sure that if a field is defined as length 10 and an incoming value has only 8 bytes, he needs to cat 2 extra spaces to it to make it a truely fixed width file. A lit...

Then put spaces where you want spaces and colons where you want colons. How hard is this to figure out?