DSXchange

Define what 'and give message appropriately' means in your last paragraph. How is this 'message' sent? What happens other than this message, is the load failed or do you load it and send a message noting 'the sequence was not in sequence but I re-sequenced it for you, no need to thank me.'? What hap...

For what reasons do you advised me to restart the first machine and perform DS.REINDEX ALL in the first project? Because of this statement, I assume: For some reasons , I cannot find the old jobs. So I cannot import old jobs to another new project. I took that to mean something was wrong with your ...

I was wondering about that but forgot to ask. Disabled = what? Installed but 'turned off' or not installed?

Bounce = stop and then restart. Down and back up... like a ball. No other connections = all alone. This is vital to ensure the reindex works.

It should work fine in the 'old' project as long as no other connections exist to the project. If you are unsure, bounce DataStage first.

Did you 'copy all the files of old project to new projects' at the O/S level without using DataStage? That is *not* the way to do things if the answer is 'yes'.

Create a User Defined Environment variable in the Administrator for NLS_LANG. Set the value to $ENV so that it defaults to the current 'environment' value. Use the special button on the job's Parameter tab to add this new Environment Variable to your job and then supply the new, override value that ...

What character set is in effect in your job's environment? Double-click on the second log entry for a complete list of all environment variables in that run. If that is different than your databases, then from what I've seen, conversions will be going on 'in flight'.

There are short-cut keys to the menus themselves. Alt activates the menu and then: F ile V iew T ools H elp -- E dit D iagram De b ug W indow The only actual shortcuts to menu items I see are: Ctrl-N: New job Ctrl-O: Open job Ctrl-S: Save Ctrl-A: Save As Most else requires access to the menus, I do ...

No, the alias is a convenience for you - not a necessity for accessing dsjob.

As noted, really something outside of anything DataStage. What database, by the way? That can change the answers given as, for example, Oracle is notorious for problems when loading with bitmap indexes in place.

After some inactivity time? That would be normal unless you've set your installation to 'Do Not Timeout'.

While you certainly could write a routine to do this, why not stick with 'sed'? It would certainly be... simpler. Heck, you could even leverage that in the Filter option of the stage. Otherwise, you'll need to investigate all of the BASIC functions for handling sequential files: OPENSEQ READSEQ WRIT...

No, not a bug, you can't have multiple writers to the same sequential file in any tool. It's not called a sequential file without reason. You need to redesign your job to write to two separate files and then combine them post job. That or use the Link Collector stage to combine them into a single wr...

In the General tab of the Hashed file stage I selected the Use Account name and picked the one I want from the drop down list(this is where I created teh table definition in the Manager as well). What actual value did you pick? This locks your hashed file to always live in that account and not move...