DSXchange

No, a checksum is not really any kind of 'encoding'. They're used as a method of ensuring that data hasn't been lost in transmission.

No, not directly. A script would mean your user has the grants to drop/create partitions, nor really a typical thing. More typical would be a proc that does the work for you and that you have execute privs on. All of the 'dynamic' logic would be there.

A function is not 'executed', it is included in a select statement which is not something you can do before/after sql. Now, if this was a procedure you could.

There's no transformation that will allow you to put 'this whole information', meaning all 80 characters into a 40 character field. Are you allowed to truncate it? Or do you need to reject if it doesn't fit?

The documentation can say. There's an entire chapter on the stage in the Connectivity Guide for Oracle Databases pdf.

The documentation only mentions UniData 5.2 or 6 with the stages, I would check with IBM / your official support vendor for 7.2.3 support and/or issues.

Welcome. Not really a metadata related question, though, is it? This really should have gone into the General forum. You'll need to make use of a Sequencer stage to create an 'insertion' point into your job stream and then a Nested Condition stage to start things off. There you can check the job par...

We know what the problem is and no, you don't need to drop it. Did you look into the index options mentioned?

You might want to look into the 'sql file' option instead of passing in the query as a parameter.

Why not start by posting the job failure?

Pass it as a string in whatever format the proc is expecting.

For some reason I was thinking 'XML' when answering you, so what I meant was the XML Input stage... however, the FTP stage should be the correct answer here though personally I've never tried sourcing from a URL with it. Give it a shot, let us know.

Yes... add an "index option" as noted in the message.

Suggest... patience.

Why in the world would you think you need to do that?