DSXchange

The problem's with locks, not with sizes of anything.

Check whether RT_CONFIG2660 is already locked using list_readu command.

Restart DataStage when there is nothing happening. This will guarantee that all (memory-based) locks are cleared. Then try the job again, and let us know the outcome.

After the job aborts, you must RESET the job in Director. Tell us of any "from previous run..." message that appears in the job log.

Job parameter.

Or two - one for the directory, one for the file name.

That's the whole point, isn't it?

You must provide the error messages and any "from previous run..." messages logged after resetting the job. Otherwise we have no diagnostic information on which to base any judgment.

Can you feed a reference input link with the user-defined SQL? Of course, you will need to figure a way to represent the three arguments as key values using this approach.

Otherwise, can you create a stored procedure in Oracle, and use "stored procedure" as the access method from the ODBC stage?

You can create job control code to do what you desire. If it's really urgent you can hire a competent consultant to do it for you probably more quickly that you could achieve the same result.

(We don't usually do "urgent" here - search to find out why.)

If the job has finished, and has not been re-scheduled, the entry to schedule it will have been removed from the at queue, leaving you no means to determine the job's "schedule time". If it has been re-scheduled, at some future time, then you still can't determine its previous "schedule time".

Error code 2 2 usually means that either DataStage is not licensed, or that a licence has expired.

bit(8) is an eight-bit, or one-byte, quantity. It's a binary value - if the bits don't assemble into the representation of a viewable (printable) character then the View Data mechanism has no hope of displaying it. You could try temporarily changing the data type to uint8, which is a value from 0 th...

Every company uses the different naming conventions and terminology which give the hard time to new person like me. That's the beautiful thing about standards - there are so many from which to choose. Unfortunately, it's a fact of life - you need to adapt to the standards used by each of your custo...

I intuit that the thought process was "if I can change Job A's parameter values in Job A, then Job B can use DSGetParamInfo() to read those values" and sought to pre-empt that line of thinking.

FUNCTION ValidateHashFile(HashFile) * Ignore input argument Message = "There is no such thing as a hash file." Message<-1> = "It's a HASHED file." Call DSTransformError(Message, "ValidateHashFile") Ans = @FALSE RETURN(Ans) (It has been brought t...

I invite anyone to compare the two pieces of code. One is indented, spaced and includes comments to explain what is happening in each section. The other lacks these features. The second piece of code includes invocation of DSLogFatal(), which results in a job aborting. The first does not. The first ...

No job, once started, can alter the value of any of its own job parameters.

I disagree with kumar_s's assertion that MPP systems have more than 200 processors. DataStage EE training (in this part of the world) is done on a cluster of four single-CPU Linux machines connected by a 1GB wireless network and a 100MB copper network (through which clients connect). It's not a part...