DSXchange

Thank you. Between the SetUserStatus and "type" of a flat file, I should be able to come to an optimum solution.

Terry Medearis

I would like to be able to set parameters for a sequence of job activities based on the results of an initial activity. For instance, I would like to read a column value within a row of an Oracle table and use that value as input to a subsequent job activity. I am failing to determine how to pass th...

Seems crazy, but changing to your suggestion worked. SUBSTRINGS function seems a little suspect. THANK YOU

Seems crazy, but changing to your suggestion worked. SUBSTRINGS function seems a little suspect. THANK YOU

Problem must be something else, as my job seems to be handling several strings that are longer that 6054.

I am trying to read a string up to 30,000 bytes from a flat file and pass it to a stored procedure. I use the SUBSTRINGS function to break the string into 30 1000 char substrings. It seems that when I get to a string longer than 6054, the SUBSTRINGS function is not working. The doc does not say what...

Ray... I do not control the purse strings, and going through all the hoops to get it done is frankly too much of a pain. If you can just answer this, I will be happy. Why does DataStage allow me to store two different routines with, ignoring case sensitivity, the same name, in two different categori...

Ray and ArndW, Thank you for your replies. Unfortunately, much of your replies are cut off, because you are premium posters. To me, this is a significant DataStage bug. If DataStage is able to store separate source code files for routines that are in different categories, then it should be able to s...

I may have misunderstood you. My point is that since I have two different routines in two different categories, and DataStage is handling their text existence, it should handle their separate executables.

I disagree. If DataStage is smart enough to know the difference between the text of the two different routines, it should be able to handle the different executables. Instead, the executable of one is covering the other. In particular, since the files are in different categories, DataStage should ha...

Well, Windows is smart enough to know that c:\A\getIata.txt is not c:\B\getIata.txt. DS should be able to do the same.

I have figured out the cause of this problem. I have one routine in folder A named getIataIdk and another routine in folder B named getIATAidk. When these two routines are compiled, it appears that the executable of one covers over the executable of the other. Basically, DataStage allows different r...

No. Unfortunately, I can not reliably produce the problem. I recompiled the DS job and all the sequences involved, and it appears everything is running correctly, now. But I did that before and the problem came back. I understand that it sounds crazy, but it has happened multiple times, now.

Thank you for your interest in my problem. I have the following routine: FUNCTION getIataIdk(iataKey, tvlagtpntreq) IF len(iataKey) > 0 THEN Ans = iataKey END ELSE if len(tvlagtpntreq) > 0 THEN Ans = tvlagtpntreq end else Ans = "" END; After running a DS sequence that calls a DS job that c...

Greetings, I have experienced multiple events where a DataStage routine produced incorrect results in a DataStage job. I then recompiled the routine, and everything ran fine. I thought I had found the solution when I started recompiling all routines and jobs before execution using the muptiple job c...