DSXchange

There is a CASE statement in DS Basic, it actually ends up compiling as if it were an IF-THEN-ELSE Construct (unlike most other compiled languages), but it does make code much easier to read. IF a=1 THEN Ans=1 ELSE IF a=2 THEN Ans=2 ELSE IF A=3 THEN Ans=3 ELSE Ans=0 BEGIN CASE CASE a=1 Ans = 1 CASE ...

Even stranger. I wrote a test function which displays an informational message and executes a SLEEP and added that function call to my job. The informational message is being displayed, but no SLEEP is taking place. Somehow the sleep call is being suborned/skipped/ignored. Very odd..

If I create a dummy job and put in SLEEP 30 into the job control it works like it should and pauses for 30 seconds before continuing. I have now created a job with more complex processing in the job control, it is actually used to start n-parallel runs of several hundred jobs (meaning you specify ho...

I would recommend to activate the deadlock daemon (you can use search or read the documentation to get additional information on this subject). This will wake up ever n-minutes (default is 15) and clear up all these locks automatically, so there will no longer be a danger of release locks on process...

dsxdev,

I am sure that the quotes need to be escaped when you use a parameter in the "where" column; if you type the values in directly they need not be.

-Arnd.

Try the following derivation:

FMT(In.YourColumnWithNumber,"17'0'R")

-Arnd.

This may just be the "display data" portion, if you write to a sequential file and look at the result there I think the zeroes will be maintained.

If you have a valid backup of the project you should first make sure that it is valid by creating a temp project and loading in your backup. If that works then getting completely rid of an old project that has become corrupted is done in two steps 1. Removing the link in DataStage to that project Th...

David,

I'm away from a DS installation (and documentation), but I think there is another code in the DSGetJobInfo() call for the User status vs. the job status.

Ray,

I just kept plugging away at the problem, once I tried changing the quotes between single and double ones I was on the right track.

Hello Aravind,

What exactly is not working in your job? Is it the delimiter? What is the difference between your metada and data that is not as expected?

If you pass your 13 parameters to your routine in the form MyRoutine(a:',':b:','...) (where the ... means 'and so on'), then your routine could look like: MyRoutine(InputArg) ParamCount = DCOUNT(InputArg) Ans = '' CurrentParam = 0 LOOP UNTIL(Ans OR CurrentParam=ParamCount) Cu...

This usually occurs when you do not have indices defined correctly; i.e. there is a difference between the keys used in the Db and those used in the lookup for the insert/update.

I found it, should have figured it out right away.

The quotes in the WHERE clause need to be escaped, i.e.

IDYEAR = \'2002\'

and then it worked!

I have been frustrated today with what seems to be a simple problem, but I cannot get it to work; perhaps someone here knows the solution: I am reading from DB/2 using the ODBC stage. I have specified a "table" load and it is working as I expected. Since this is a large (17 million row) daabase on t...