DSXchange

Learn patience. If you truly need answers within an hour, particularly when it's midnight in DSXchange-land, sign up with your official support provider for priority service. Learn just how much "urgent" is worth. DSXchange is an all-volunteer site, whose members post as and when they can...

Are you logging locally or to the common metadata repository? What are the values of ORLogging and RTLogging in the DSParams file in your analyzer project?

Please try to maintain a professional standard of written English on DSXchange. It helps those whose first language is not English. Have you looked in the manuals and on the IBM website? There is more than one possible architecture for Information Server or, to put that another way, there's no sing...

You've been here long enough to know about Search function.

Why did you specify Quote=double when clearly this is not true? Why not specify Quote=none (000)?

A Search of DSXchange may have saved you waiting for an answer. The usual approach to this kind of problem is to convert the junk characters to "". A more generic approach is nested Convert() functions, the inner to convert all the "good" characters to "" and the outer ...

You can do either lookup. But there's only one format for the {table_definition} that you include in the function. Review the manual carefully - it is properly explained there.

The actual lookup operation is performed by LUT_ProcessOp. If that's running in parallel then the lookups are being performed on all nodes, all referring to the single copy in shared memory used to implement the Entire partitioning algorithm.

There should be a file somewhere on your system called something like err.h where the common UNIX error codes may be documented.

I'm not sure whether or not you've run the Cross Domain analyses on virtual columns but, assuming that you have, then your requirement would seem to me to be one for Foreign Key analysis.

What's different between dev region and other region? "Nothing" is not the correct answer.

From which stage was this error message generated? Check nullability of the column on the input link to this stage.

You would need two jobs to achieve this or, perhaps, user-defined SQL to call a stored procedure.

The LUT_CreateOp operator (one of two operators in the composite operator generated from a Lookup stage performing "=" lookups) is running on a single node in this score. There are at least three possible reasons for this: the stage is configured for Sequential operation (check the number ...

1. Feasible. 2. Analyze the logic of the mainframe jobs (they're usually very simple) and reproduce in server/parallel jobs. 3. Impossible for me to determine. Will you, for example, be relinquishing the mainframe DataStage license? Will you continue to need to access data on the mainframe and, if s...

Show us what "combine" actually means. Also, since there's no such thing as a "subrecord stage", please confirm the actual stage type that you're using.