DSXchange

Diego, it will work if done properly. You build the string with the values embedded in it. At this point we'd need to see exactly what you are doing to be able to help.

To me it seems like DataStage should always try to use the FTP protocol independent of what port it needs to communicate over. Sorry but this isn't a DataStage issue, just a lack of understanding of the role the port number plays in the process. You can't just change it willy-nilly as they are part...

You have to build the string and substitute in the values yourself:

Command = "dsjob -run -param Parm1=" : [Col1_Of_table] : " -param Parm2 = " : [Col2_Of_table] : " etc etc etc".

Good that you've got this working. I honestly don't think you really need UserVariable stages here but don't have any way to play around and confirm/deny.

Ok... from what I recall there is a 'metadata validation' check step where it goes back to the source table and verifies the metadata you're using. The message implies it is going back and seeing COL1 as CHAR(38) in the source table. If that's not true, meaning the actual column is a CHAR(20) then y...

"Previous column of the table" - sorry but what the heck does that mean?

If it is "really 20" but your metadata shows 38, fix the metadata. If something else, please clarify.

No, just pointing out that an exact search for 'Oracle instant client' found 4 posts here where it was being used and discussed.

No, not misunderstood at all... just giving you a work-around. Everything is not "all right" as you could lose data as noted in the warning - 8.1 was broken because it did not warn you about the truncation, they fixed that in the 8.7 release. And I thought we were talking about one column ...

The "Win" part of that name should tell you it's not happening "on the server itself". :wink: What I'm asking is are other processes consuming the file and having issues? I just want make sure we're solving a real problem here and not a perceived one. I'm also curious about the '...

Well, you could always lie.

Alter the source metadata for that field to show a size of 20 and (optionally) substring the field in the SQL.

So are you having an actual problem with the file on the server or just after you move it over to your PC to look at it?

State your output requirements in words. How do you pick the survivor? Right now just looks like Aggregation to me but I want to hear the rules.

OK. Is this truly a Server job? From what I recall that rules out using a message handler to demote it.

Do you still get the warning if you substring while moving the data from one to the other?

I don't see a need for the UserVariable stage here. Typical use would be to establish values once at the beginning of a Sequence and then downstream activities would have access to them. Prime example would be a looping sequence job. I'm not quite sure I follow your ultimate design here. Triggers ca...