DSXchange

Perhaps it is a limitation of your version/platform regarding parameters. If you keep the dummy argument and change your routine to accept a parameter, does the job work?

While I'm just guessing, what happens if you call the routine with - does the compiler error change?

It would be easier to answer if you could illustrate your problem with an example, for instance the multiple dates - are they in a single column with a separator, or in distinct columns?

I think one could use , too.

Ok, then your source is Oracle. The two characters you've listed cannot be stored in 7bit ASCII, internally your Oracle is using another character set. You've specified that Oracle converts from the internal character set to 7 bit ASCII and it is there that you are losing these character values. Fin...

The DSGetStageInfo() using DSJ.LINKTYPES will get you that information.

Hello Shilp,

did you perform the link step illustrated in the example? Also, could you post how you call up your routine in the transform stage?

No such tool is available. Some of us, myself included, have coded small applications to do such checking, but since each site has different standards that they wish enforced, such code is generally not re-usable.

Have you looked into using the Complex Flat File stage in server jobs, which were created expressely for this type of data.

I would add a second output from a transform stage and output just the @OUTROWNUM value, then to an aggregator that takes the MAXimum value of that column, then to a transform stage to create your header record contents, this going to a funnel stage to the main data stream. The join would use the si...

Are all the jobs involved actually marked and compiled as multi-instance jobs?

Could you explain the error you are getting with the direct lookup at 8.1; there is no reason I can think of why that shouldn't work.

I know of no method of getting this from the command line interface.

Eitehr you have gone from a non-NLS to a NLS installation, or you have changed your default NLS locale during the conversion. Use the administrator client, select your project and click on the "NLS" tab to see what your current settings are.

The first thing is never to use kill from UNIX, particularly 'kill -9', unless there are no other options. In your case I'm still very confused as to what the situation and/or problem is. Are you, or are you not, using RESET in the job call? Somehow your job must be getting from state 'finished' to ...