DSXchange

Possibly a bad (corrupted) libmawt.sl file?

Data Set with VarChar DOES work. I have lots of them.

VarChars are not padded. Only Chars are padded.

VarChars can be trimmed prior to comparison. You can use Modify stages for trimming if speed is important.

Set the quote character to 000 in the Format tab of the Sequential File stage that creates the file in the server job. And/or write Decimal data types (which will not be quoted) rather than VarChar in that stage.

Transformer functions are intolerant of nulls. You must handle them separately. NULL is valid for any data type (provided the receiving field is nullable). Therefore you require something like If IsNull(InLink.TheColumn) Then 1 Else IsValid("Integer", InLink.TheColumn)

Set them up as environment variables and obtain them from those.

Welcome aboard. :D

There is an IsValid() function that allows you to check, in a Transformer stage, whether an input string is valid as some other data type.

From the DB2 API stage?!!

It's my understanding that you need DB2 Connect to be installed on the DataStage server machine.

If you are fluent as a server job developer, you could enrol on the Server to Parallel Transition Lab offered by the owners of this site. They run sporadically and are announced here.

Version Control also increments the version number, and it's possible that developers do also. You can query the Repository using a "UV" command in DSExecute. SELECT NAME, EVAL "@RECORD<8>" AS VERSION FROM DS_JOBOBJECTS WHERE OBJTYPE = 'J' AND OBJNAME = 'ROOT' AND OBJIDNO = (SELECT JOB...

DSguru2B wrote:I am getting this error for compilation RT_CONFIG89. Cannot figure out the reason to this.

There is NO WAY that is the complete error message. Therefore your statement that "I posted the exact error message" can not be true.

Edit dsdlockd.config file to set Start=1, then the deadlock daemon (dsdlockd) will start next time DataStage is started.

The job design in the first post on this thread had you writing to a hashed file. Was that problem solved? If so, please close this thread as Resolved, and open a new thread for a new problem. We will not enter into wandering discourses about various, changing problems. It makes life too difficult f...

You're working for someone who expects you to process mainframe volumes on a Windows server?!! Have they purchased the mainframe edition of DataStage, so at least you have have DataStage generate code that can run on the mainframe? (Didn't think so.) There is no mechanism whatsoever that means serve...

Page faults are indicative of insufficient memory. When a memory page is required for processing but memory is full, one or more of the least recently used pages are moved out to disk ("paged") to make room. This operation is called a "page fault". In an ideal world, there would be no page faults. I...