DSXchange

pradeepleon wrote:It isn't a fixed flat file.Have you got this resolved?...If not reply....

How do you know this? Sure looks like it could be to me. Usually one would know or be told by whomever provides the file, you shouldn't have to guess.

Post your transforms on this field and the sql you are using in the target stage.

We have some critical requirement in which any new file can come in any format and we have to just plug that file with the existing transformation logic. Source file can be anything like fixed width flat file, csv file, XML, SOAP, etc. I am thinking on following approach:<snip> Wow... that's just c...

You can't directly there. Routine code can be documented, but for derivations you'll need to use either the General tab of the stage or put an annotation on the canvas.

I've found the latter works best as most peoples may never see the other.

No, not included. Yes, an additional PACK that must be purchased if you want that functionality.

Welcome! :D

We'd need more information to be able to help. Describe your complete job design and check in the Job Properties if you have anything setup to run 'After Job'.

Make sure you've got a Transformer between the two and use a constraint to stop the nulls.

Not nearly enough information to be able to help. Except to say I'd wager it's because you are not explicitly handing your date transforms but making assumptions about the formatting. You also need to verify that Date() returns the same information on both operating systems. I would think they would...

First thought would be to take these messages to your Informix DBA and see if they mean anything to them.

Actually, they do - or at least the ones I've tried have worked - hence my answer. I just don't understand why someone wouldn't try first rather than seemingly come here and ask. And if they did try and it didn't seem to work, explain what they tried and what about it "didn't work". I'm currently us...

I'm guessing that if they had that pack, they wouldn't be asking the question. To add what Nick said, you wouldn't call a web service from a Sequence job directly but rather a job or 'utility' running under that Sequence. And without the pack, that means you'll need to write something outside of Dat...

Clear Status was not the right answer. Your message means the job is still running under the covers. Find someone who can kill it for you if you can't.

Sure... what happened when you tried?

Rather than define all that metadata in the FTP Stage (which I assume is what we're discussing here) what I've found works best is to define your record as one long field, no quotes, no nothing added. This is the closest you'll get in DataStage to the functionality of the command line ftp process. T...

sshettar wrote:and later complied both the routines

I'll bet this is what fixed your problem.