DSXchange

I've learned something today. There is a limit.

Ctrl-J is Char(10), the LineFeed character. Given that this is a server job, scroll to the right in the Columns grid in the Sequential File stage and set the "contains line terminators" property to Yes for the field in which it occurs.

A word of warning - it's not "brief". There are major differences. If you don't have the manuals yet full information can also be had from IBM Information Center

Why "in UNIX"? The DataStage Designer client is the correct tool for doing this. Categories do not exist in UNIX - they exist in databases. More than that, they would need to be created both in the local project repository and in the common metadata repository. It's quite likely that these...

Welcome aboard. The short answer is that NO-ONE has access to the metadata repository or services tier. Everything is done through the services exposed by the WebSphere Application Server. The only time these "upper levels" are accessed is during installation. Information Server is impleme...

Can you identify the job number? Execute this command in Administrator client command window. SELECT JOBNO FROM DS_JOBS WHERE NAME = '<<Job name>>'; Use that number (nnn) to see whether there are any entries in the log. SELECT COUNT(*) FROM RT_LOGnnn; This will determine whether the problem is in th...

Has anything changed "out there" in Kerberos?

Set your Match Cutoff above 23.68. Clearly that's not enough weight to be a match given your blocking fields and match rules.

Start by dreaming up meaningful subjects for your posts!

Technically every stage in version 7 server edition is an API stage, because every single stage is written to comply with the DataStage plug-in API. Documentation exists for this API, which means it's perfectly possible to create your own stage types including metadata management capability and view...

I have no idea what you mean by that term, which is why I asked you to explain it. You have not done so.

And a guaranteed way to annoy me intensely is to use "u" instead of "you" and "r" instead of "are"!

What precisely is the "issue" that you seek help to fix?

Are you reading from a Data Set that was written when a different configuration file was in force?

How do you know it's for logs? What is it that is filling your logs? Do you have a log auto-purge policy in place? Or are you writing jobs that generate zillions of warnings, and not running small samples of data while in development? We're happy to help, but you need to help us to help you, initial...

What precisely do you mean by "non-api stage"?