DSXchange

Welcome aboard! :D

This error is failure of an internal GRANT CONNECT TO username; SQL statement. That it occurs is a bug. You can work around it by logging in as the user who installed DataStage, and executing the GRANT statement explicitly.

DS_JOBS contains all the job names and job numbers. RT_LOGnnn contains the log for job number nnn. Use DSGetNewestLogId() to find the closest event number to the timestamp in question. Then cycle backwards till you find "job started" or "job finished" event. From this you will be able to determine t...

View it with a hex editor and a companion who understands the rules for storage of decimal data types. You will find that it's not "garbage". So string_from_decimal (in a Modify stage) or DecimaltoString (in a Transformer stage) should do the job for you. Make sure that the string has sufficient cha...

Sometimes the line termination character is converted to a field mark (@FM, or Char(254)) as part of being captured.

Who told you to use DSStopJob? This is singularly bad advice. Simply detect that the lookup has failed (use the Reject link of the Lookup stage for example). Only pass the row to the table if the lookup has succeeded. You can do whatever you like with the stream of rows for which the lookup failed, ...

Search is your friend, it's been described on a number of occasions. You need an upstream job which captures the result you want and stores it somewhere (maybe that job's user status area), which is then available downstream in the controlling job sequence for loading into parameters.

Do you have RCP enabled, and there's a string EFF_DT in a source schema?

Beware that most of the metadata for DS_METADATA are not in the public domain.
You can get some sense of what's possible by looking at Kim Duke's tools and their associated SQL; some of which has been posted on this forum (Search is your friend).

That is a very complex query, Arun, since the start and end times are stored in a different table for every job. Further, I believe your site uses multiple job instances, which roughly doubles the complexity. You would be better off creating DataStage componentry to extract this information; a set o...

Duplicate post. Please delete the other.

A batch is created in Director, a job sequence (note, no trailing "r") is created in Designer.

Welcome aboard! :D

The most common cause for this error is that one of the jobs referred to in the Job Activity has not been compiled. Or is not currently in a knowable (or runnable) state for some other reason.

OK, I think you're at a point where you need to get the DBA involved, if only to trace what requests DB2 is getting when you're trying to import the column definitions.

Can anyone else at the site successfully import them? If the DBA logs in and uses Manager, does that work?

There is a limit to how much data at a time can be retrieved from UniData - from memory I believe it's 8KB. Based on this your rows per chunk figure should (can?) be no higher than 8KB/physical row size.

Typically a command output has leading and trailing line terminator characters that you need to strip off.
Try using Trim() or Convert() function to remove all Char(10) characters.

Check the schema associated with EVERY link. Somewhere there's a string data type. Otherwise you wouldn't have seen that particular error.