DSXchange

Let's see if I've got this right, FEMS sends OIM XML via MQ to WWPRT RDBMS with BRL for CBS and you want to know if you can use RTI. Even if I did have half an hour to spare and an acronym database I still don't know whether I could answer the question. Try Ascential sales. RTI or the MQ plugin or ...

Vincent,

cool - I'd never thought of looking there! Thanks for (rE)pointing us to the FAQ.

Looks like a timing issue, with the first write to the hashed file happening during the delete and causing your error message. Can you redesign the job so that your reference link comes from the same hashed file stage object as you are writing to? That will ensure that you don't get timing issues.

The only way I know of is to use the graphical interface, just like you did with your development project.

So the difference lies in the time required to set up the query? I don't know what the difference could be. It must be something else that hasn't been identified yet - could there be anything else? Different userids on UNIX or in connecting to the DB?

Have you recompiled the sequence? Normally no shell script is generated by the program, there is just the default mail script.

The message handlers aren't part of the .dsx export and import, you will need to add them explicitly in each instance.

Incremental Loading is more of a general approach and methodology than a DataStage specific question. The general term for what you are looking to do is "Change Data Detection" and a search on the web and in this forum will give you a number of hints. I also think that the product documentation goes...

Are you 100% certain that the job gets started the same way (i.e. same parameters, no reset-if-required switch) between the 5-second and the 2-hour run? Check you 2-hour log - is there a large startup or finish time or do the rows process much slow? DataStage jobs are started as background processes...

You have embedded spaces in your paths. Either use the 8.3 notation or enclose the files in double-quotes.

I missed that in your original post.

You can fully qualify your column names in the metadata or when you run the import app in the manager. Alternatively, you can click on the user-defined-SQL tab and it will default to the current SQL; then you can manually add in the identifier to make the column names unique.

Vijay,

did you read my first post - just use absolute instead of relative pathnames for the files.[/b]

It sounds like your DataStage installation itself might be corrupted. Have you tried stopping & re-starting DataStage to see if the problems go away?

The DS.TOOLS command is documented; if you look at the entry in the VOC file you will see that it is a MENU, which in turn can be looked at and which shows the actual TCL commands issued. The real reason is that some of us have been working with UniVerse and it's compatible products for more years t...