DSXchange

I'll toss out another option since no one has mentioned it yet (there are always options): IsValid("decimal[4,0]", "35E1") This will return 0 since the string literal 35E1 is not a valid decimal(4,0). IsValid("decimal[4,0]", 35E1) This will return 1 since the numeric li...

I think the dsadmin command had the ability to protect or unprotect a project from the command line. However, I don't recall if it could report the current setting without initiating a change.

Mike

1) Yes, but be aware that as soon as the job sequence stops running, it will no longer record any checkpoints. So if you have any activities that were started by the job sequence, they will still be running and will not record a checkpoint when they finish. 2) Compiling a job sequence will also remo...

My questions weren't specific to your particular issue... rather they are questions that I ask any time that a job terminates abnormally. Regarding your specific issue with the restart causing more than one run, I would carefully read through each job runs' log to trace what was executed, what was s...

My opinion is that your project requirement is dangerous. Jobs are not expected to abort/stop/crash. I want to know what unexpected event triggered the abnormal termination. Was it preventable? If it is due to a development or design defect, then get that fixed so that it doesn't repeat. Is there a ...

Personally, I would never attempt to automate the restart of a STOPPED or CRASHED job. These are unexpected ways for a job to end.

I would require human intervention to perform analysis and take corrective action based on the analysis.

Mike

Start a sufficiently long running job sequence and have your admin stop the DataStage engine. After the DataStage engine is brought back up again you should have a CRASHED job sequence.

Jobs end up CRASHED when there is an unexpected stoppage of the engine.

Mike

I doubt that you'd see any noticeable performance difference between a pipeline of 7 lookup stages and a single lookup stage with 7 reference links. The important thing is you will get 7 of 7 correct results instead of 1 of 7. It would be an interesting exercise to compare the job score between the ...

One lookup stage can only designate 1 reference link for multiple rows so you can only do range lookups on whatever reference link is designated. You can do two range lookups against 1 reference link. Since you want to do range lookups on 2 different reference links, you will have to use 2 lookup st...

TonyInFrance wrote:If I don't use the multiple rows option, I get a warning that duplicate rows exist which is also something I don't want.

I've never seen a warning like this in a case where there wasn't actually a duplicate row based on the defined lookup key(s).

Mike

Bug? No. That is just the nature of server jobs. There is no strong typing like you get in parallel jobs. Everything in a server job is essentially a string. Conversion to and from a number is pretty fluid, and lengths don't really matter. Add a number to a string: "1" + 0 Concatenate a nu...

I haven't been down this path before, but just wanted to point out that the error line(s) in these types of problems are usually the ones to be concerned about. They will be the ones with ##E at the start of the line. See if the IBM articles in this Google search are of any help: https://www.google....

After doing as Craig suggests... If the issue persists, the next step would be to compare the OS and applications on your machine against that of your colleagues. There may be an application or update on your machine that is triggering the issue. If you reach that point, you should definitely be in ...

COMP-3 is packed decimal, which you don't have there. Try it with COMP.

Mike

First thing to do is isolate the issue. I doubt that reading from the sequential file is a problem.

Create a copy of your job that looks like this:
I would suspect the ODBC driver or the ODBC DSN set up before I would suspect the sequential file read.

Mike