DSXchange

They do exist, and are called Intelligent Assistants. Essentially a wizard that asks questions about source and target, and builds a simple (or a slightly more complex) job design.

Some of us don't work every weekend, and are busy when we are at work. The output from uv -admin -info suggests no problems, so you should be able to see things from the Cleanup Resources utility. You do not need to be dsadm; indeed, just to look you can be any user. There are two Show All option bu...

Are you looking for a mainframe command line utility, or a server command line utility? The latter does not exist. I suspect there's not going to be one on the mainframe either, as there really isn't the same concept of a command line, but generating the COBOL FD or DCLGen is definitely possible. Bu...

You need to calculate the date 40 days ago then use this in a WHERE constraint on LAST_UPD_DTTM. In a job sequence you can use this expression to provide a job parameter with the requisite value, for example Oconv(@DATE-40, "D-YMD[4,2,2]") and use a reference to that parameter as t...

In that case precision is 0.
"-2837213623238928331187." contains 24 characters.

I don't see any TRIM_ID in your source.

Stop regarding it as a problem. DataStage is not allowing two columns with the same name to be output.

What data type, what precision?
For example, NUMBER(22,2) needs one place for the decimal place and one for the sign. Total 24.

ICE wrote:I cannot see your full msg as I am not the Chatter member

For a very small amount of money you can be entitled to read premium posts, and help to keep this site alive.

dsdlockd will not help with database deadlocks at all. dsdlockd is only for deadlocks in the DataStage Repository itself, and these are extremely rare. We mainly use dsdlockd's secondary purpose, cleaning up after defunct processes. Deadlocks in the database are either the result of faulty design (s...

uvdlockd.exe (which is called dsdlockd.exe in versions 6.0 and later) should be left running. Its purpose is to check for deadlocks periodically. As a side effect, it can clean up resources held by defunct processes, such as disconnected clients. It is NOT a deadlock. Whether it starts automatically...

The difference is that, into a new project, the changes are inserts, whereas into an existing project, they are updates. In fact, the difference is more stark than that, but will suffice for the purpose of example. Inserts are always far more efficient than updates, since they can simply move entire...

Could it be a Business Objects universe?

The point made by narasimha is that data values are case sensitive. This is true in all databases. This is why "DEFN" did not return any rows; the correct partial value is "Defn". Beware also that OBJIDNO is not a numeric data type, so sorting by it will give "numbers" sorted alphabetically 1, 10, 1...

The LIST.ITEM command was to ensure that your VOC entry describing the DS_JOBOBJECTS table is intact. It is. You now need to check that D_DS_JOBOBJECTS exists in the file system, and that you can read it. Please execute this command and report the result. SH -c "ls -l D_DS_JOBOBJECTS"