DSXchange

Take your job that is not compiling and start removing columns until it does compile. Either there is a specific column that causing the compile to fail or it is the amount. You will need to narrow down the exact cause more before useful help can be given. If the error is because the transform stage...

Koolnitz, the message doesn't state that you had a deadlock, just that you might have. The locks available in DB/2 are not limited to record-level locking, you can also have block level and table level locks; plus you might also have other processes accessing and locking entries on your tables. The ...

Other people have posted the same type of Designer issues in the past which you could find with the search facility. I haven't had this problem, but it seems that there is a patch available from Ascential/IBM to resolve the issue.

antojj, when you import jobs you do so using a client but nothing gets placed on the client Windows PC. So if you created a project called "dstage" then that project will be visible from any other client connecting to the server. This is the way that client/server technology works. You state that yo...

It is always better to read the input files with the correct metadata, only in certain cases where you need to do processing across actual columns would you wish to read the file as one long virtual column. The column import can be used to split a long string into columns - but it is much more effic...

Actually the compilation time can be greatly reduced by using RCP if that fits the design of that job; but even a small job with a transform or two can take ages on an overloaded system; I've had jobs take over 10 minutes to compile in the past where the computer didn't seem overly busy.

lol, Ray. The real reason is none of my jobs actually make it to production

Bryceson,

Using the forum's search facility it would seem that there are 138 threads where people have discussed of this type problem.

Often you can get additional information by resetting the aborted job and then looking at the detailed messages in the "from previous run" log entry.

This is an example of the powerful string handling functions available in Server. This solves your question: FIELD(In.URL,'/',1,DCOUNT(In.URL,'/')-1) The DCOUNT() function returns the number of fields delimited by '/' and the FIELD(string,delimiter,from[,to]) function gives you all f...

You really should have known better than to put "urgent" in the title, otherwise you would already have gotten an answer.

The DataStage internal date is an integer denoting the number of days since Dec 31st, 1967. So Day 1 is January 1, 1970. There are (60*60*24*1000) Milliseconds in a day. The mathematical conversion between your millisecond representation and the DataStage internal representation is known, and the co...

Sure, just bear in mind that being 99.9% compatible doesn't guarantee thatit will work correctly in both Windows and UNIX environments. DataStage doesn't notice a difference when doing external calls - apart from choosing your external call type (DOS/UNIX), but you can use a call to system(91) to de...

the runtime parameter values replace the #parametername# and then the result is sent, unmodified, to the command line. There is no special character used to replace the space.

Perhaps you could explain the problem you are getting.

Normally files like this have quoted strings, so if the delimiter does occur inside a string it can still be differentiated. But this shifts the parsing problem to the quote character, which is also just one character (unless you have NLS enabled) - if all 256 characters are part of the data then yo...

I think that DataStage might not be the most efficient tool to do this, but if I were to do it in DS I would create a job that reads the file and writes it to /dev/null or something of the like. I'd call the job from a sequence with the filename to check and then use the job's completion status as t...