DSXchange

It has no impact on the Sequence run.

I would imagine that is your solution, a manual rename.

Doesn't seem like it requires looping. Generate the rows and then Funnel them back together... won't it always be just two?

Did you try any other values, or just 1?

mac4rfree85 wrote:Our project guideline is not to use OCONV & ICONV.

Good Lord... why?

Are your records always coming in YYYYDDMM format or is it mixed with the other format? For the former, you just need a different Oracle TO_DATE() mask. Or substring it back around the other way.

How were these hashed files created? If they are pathed, then you can simply use O/S commands as you noted.

Why convert anything? That format will allow you to compare the char values directly.

No idea and you are the first to post it, it would seem. How about some details - source or target, database type, first attempt or used to work before, that kind of stuff.

Look at the source code for the DSSendMailTester routine, you'll need to copy and tweak it to fit your purposes. Depending on how you populated it, the data in the flat file could be retrieved using 'cat' at the O/S level or a job could read it. You'll need to combine that with whatever other text y...

That means all you exported was the 'executable'... go back and make sure you get the source as well, then re-import.

Interesting that the case doesn't seem to matter in sqlplus, they both should be acting the same. When a table name is supplied quoted the db engine should be resolving it in a case sensistive manner. And your first post shows it all upper-case.

Ah well, glad you got it sorted out.

How are you getting out of the loop when they all succeed?

Odd. Perhaps try putting the double-quotes in the sql itself and not the parameter value?

SELECT CLAIM FROM SAPSLP."#Job_Parameter#"

But when call this procedure within the STP stage in Datastage it is considered as just another ordinary output column. That's because it is 'just another ordinary output column'. Can you not just check the value after the SP stage and then 'manually' abort the job? There is also an Error Codes tab...