DSXchange

This is a simple and relatively straightforward operation in DataStage. To keep things simple, define your columns as VarChar in the sequential file stage. Now you need to perform two actions, the first is to convert this string representation of a timestamp into a timestamp: StringToTimeStamp(In.Co...

Posting your actual compilation error would be quite helpful.

In addition, you need to allocate your "JobHandle" variable with a call to DSAttachJob(), and the first parameter to cour DSGetLinkInfo() call needs to be the JobHandle.

No two user variables are needed. Just one outside the loop to hold the string containing the loop elements, then the loop counter itself will hold each value for each iteration.

Very strange, I cannot see how 7Gb can be used in a lookup stage. I wonder if the 7Gb might be the full table size but that the lookup only uses keys and a select subset of the data columns? Also, the "APT_LUTCREATE_MMAP = 1" setting applies to using lookup filesets but you stated that the...

You can use Job Parameters in the Before/After SQL but the allocation and parsing of the ORCHESTRATE.{column} cannot be done there since the SQL in the before/after is executed once per stage while the ORCHESTRATE.{column} are parsed per row.

sorry, as corrected above, the loops are available as of 8.5. Since you have 8.1 and loops within a transform stage are not an option you have a simple, but limited option if the maximum number of iterations is known; i.e. if you know you won't have more than 25 in column1 then you could make a tran...

This looks like the perfect application of transform stage loops available in Version 8.7 and above of DataStage. Do you have this version?

I'm not quite sure if I understand (i), but for (ii) the answer depends upon your system configuration. A dataset consists of a descriptor file (usually with a .ds suffix) which in turn points to the file(s) containing the actual data. If your paths as defined in your APT_CONFIG file are identical y...

If you have a multi-instance job "abc", then if "abc" is running you won't be able to start "abc.instance1", but if "abc.instancex" is running you can start "abc" but won't be able to start new instances of "abc" until the master has comple...

There are some warning messages which cannot be programmed around in a job and thus there are (very few) cases for demoting warning messages to information. I believe that there should be no case for demoting an informational message to "suppress", though.

It does depend upon what sort of a lock you have. The most common cause is a terminated designer session and for this I activate the DataStage lock daemon in the background and that ensures that these types of locks are cleared at most every 15 minutes; instead of playing around with locks and poten...

One way is to mark the message in the director log, then right-mouse click and choose the option "add rule to mesage handler" to get the screen which allows you to deprecate messages.

Did you make a copy of the job with a hardcoded SQL, and did that also show the same problems?

Have you actually checked how much data is being used for the lookup reference set on the machine that is working?

I would start narrowing down the error first. Create a job copy and use the SQL hardcoded instead of as a parameter. If that still reproduces the error, Turn on all the reporting options you can find and see if those log entries give you additional information.