DSXchange

Then backup the project, delete & re-create it and re-load your jobs. That is faster than trying to figure out what has gone wrong; particularly since fixing that might involve re-creating the project anyway.

Hmmm... OK, I see what Ray is stating; but think that we disagree in matters of semantics instead of technically. If you make changes to a job and the Rows/Second changes then you have a metric that means something. You cannot compare it to the rows/second performance of any other job; and I feel th...

No, the &PH& directory and contents aren't germane to this issue.

Did you create a new project on this machine and see if you can get jobs to run in that project?

StageName and LinkName are case sensitive. Is the job you wish to monitor a Multiinstance one? Are you calling this function from within the job itself?

When a job completes it will close all of the open JobHandles but I would always recommend explicitly doing a DSDetachJob().

Just a precautionary note with JobHandle = DSPrepareJob(JobHandle) If it needs to reset the job it will return a new JobHandle. This is normally not an issue but sometimes you need to be aware of this; I had some job control where I stored the JobHandle in an array and this changing of handl...

Rajeshekar - there is no reason to quote Ray's post. It is a "premium" post which, should you join as a premium member, you can read in it's entirety.

I recall something similar happened to me but I cannot remember what the cause was.
- Try using "dsjob -run -mode NORMAL {proj} {job}" to see if your new job will run
- Create a new project and see if you can create/compile/run jobs. If not, then a full re-install is going to be your quickest path

Your problem is not in the trim() you posted. It is somewhere else where you are performing a numeric operation on a value that is not numeric.

Can you also run the job you just created?
Can you validate the job - it should have a non-compiled status so that you can reset it.

Parsing the string into components is simple, you can use the FIELD() function. The complexity comes in trying to figure out which part of the string goes where. If you have it, you can use the QualityStage components, if you don't you need to come up with your own rules as to determining which part...

Hmmm.. Compiling and Validating are 2 very different functions. One generates executable code and the other checks to see if that code can run.

If you manually create a simple dummy job can you compile and run that in the new project? Also, are you sure the compile is working? Try "resetting" a job and then compiling it to see if the status changes to make sure.

Naveen - I am confused. You stated that you have written a script to retrieve the DB2 data; just add a redirector such as ">> textfile.txt" in order to create a sequential file from the output. Are you sure you wish to make it complicated and use a script and not do this in DataStage job with just 2...

a) put in a call to DSLogWarn() when you reset the job to make sure it is being executed.

b) put in a call to DSWaitForJob() after the reset to give it time to complete.

c) Have you looked at DSPrepareJob()?

The most efficient in your case will be the datatype which requires the least conversions. You can minimize I/O on output by choosing the smallest possible display mask - the source column type is irrelevant in this case as a conversion needs to be done either way.