DSXchange

Clearly that is not the correct answer, otherwise the job would have run successfully "today". The problem (the change) may be in your data, the problem may be in your hardware, operating system configuration, database configuration, and so on.

The answer may vary in different regions, so contact your IBM support in local business hours.

As a rule of thumb, IBM support two major releases back.

You could also use a before-stage subroutine in the Transformer stage to do the same thing and, since it's in the same process, transfer values through system variables such as @USER0 through @USER4 back into the Transformer stage. But the OP's stated requirement (and thread subject) was "before job...

Can the Doctool (*.mdb) population (refresh) be automated the way reporting assistant within Manager does? No. Aslo, is it possible to load the tables such as DSProperties, DSStages etc. in the doctool using the Universe stage? Only if you have used UniVerse as the Documentation Tool database. ".md...

paranoid wrote:I think hashed file takes up lot of space in my server which i dont have. Is there any other solution?

Get more space on your server.

If you haven't got enough space for a moderately sized hashed file you are going to run out of space somewhere, sometime in your ETL processing.

DS_JOBS contains the job names within one project which is why it does not need to show the project name. Each DataStage project is isolated from all the others. That is why the command line interface dsjob is the only mechanism that can retrieve job status information from another project with no c...

Before we go any farther, are there any other errors/warnings you have not bothered to mention?

Welcome aboard. Create one operating system group per project and one "general" DataStage group. The general group is associated with all the DataStage software, and each project's objects are protected with its own group. Users are added to project-specific groups and to the general DataStage group...

Command line interface (the dsjob command). You specify the other project name on the command line.

Nothing at all to do with Link Collector.

Read the error message.

The problem relates to the ODBC trace file - maybe you lack write permission to the directory where it is to be created.

DateToString(), substring, concatenation, StringToDate().

Date and Timestamp conversion functions, with appropriate format strings, are what you need. You may also need to accommodate different formats (for example one-digit versus two-digit month).

What changed "today"?

The dsenv script is a good location to set NLS_LANG because this script is executed by all DataStage processes. Group it with the other Oracle-specific environment variables such as ORACLE_HOME.

If you add an additional Specification to the Modify stage, containing the single word NOWARN, does the warning go away?