DSXchange

Welcom to DataStage, Abhijeet1980.

Which client program are you referring to? The Director or Manager or Designer?

The client configuration, at least the minimums, are outlined by IBM/Ascential. Sizing the server is a bit tougher. I can flow 1Tb through my notebook with no problems, except it will take quite a bit longer than on a top-end Solaris box. So part of the sizing questions must be times and not just da...

[quote="talk2shaanc"][quote="ray.wurlod"]...Secondly, we are here not to correct anybody's english but to correct Datastage understanding. If language used by somebody is abusive or insulting, then we should raise a concern...[quote] Correct, but there is no need to use SMS type ...

Lotus26 wrote:...I tried in another way:
Command Issued: SH -c "dsjob -ljobs KMC | wc -l"
Message: SH:dsjob: not found 0
...

You need to make sure that the dsjob executable is in your path. You can change the call to "$DSHOME/bin/dsjob -ljobs KMC | wc -l"

Does the project directory get created in your case? It might be that your umask settings are such that you can create but then don't have sufficient permissions to modify. The secondary index files in the project directory start with I_

Kberisha, if the Oracle message is ORA-01722: invalid number then your Oracle DDL either contains a numeric field or your SQL does a numeric operation of some sort. Can you confirm the DDL by either re-importing the metadata for the table into DataStage or by using your favorite Oracle tool and gett...

Can you do a view-data from the designer and see your data?

DSDB2 has correctly converted the date into the DataStage server internal format, which is the number of days since 12/31/1967. You can use OCONV() with one of the date formats to make this display differently. This behaviour is one of the idiosyncracies of DataStage.

Hello SPA_BI, DataStage contains a facility for binding in external objects such as c/c++ routines. This is documented for the UniVerse product in the UniVerse GCI Guide . I've done this in previous versions where DataStage and UniVerse were still the same product and it has always been a bit tricky...

Call DSLogWarn() will not abort your job, a call to DSLogFatal() will. In your job settings you might be defaulting to make the job abort after 50 warnings; once you reach that number your job will also abort. You can change this value, but it is much better to ensure that you don't generate those w...

The number "10188" has absolutely nothing to do with the row number. It is a process ID. This number will be re-assigned each run. There should be messages in the log file to go along with this error, or you can do a reset of your log and see if you get a message titled "from previous run" that migh...

These commands create files that would only be used within DataStage; so there is no potential for damage outside of DS and I can't see any potential within DS, either.

I have to disagree with you on this one, Ray. There are some great things that PX allows you to do with RCP, particularly when developing "generic" jobs with logic & inputs/outputs which can be used with different file formats. But for the majority of job development work RCP causes issues and s...

I think RCP is best defaulted to be turned OFF and only enabled when you explicitly need it. It is an incredibly useful and powerful feature with all the benefits and potential drawbacks associated with such functionality. If you explicitly work with each column in your schema then having RCP enable...