DSXchange

Check out ArndW's reply in the following post
http://www.dsxchange.com/viewtopic.php?t=97052

If you have the exception handler stage then no need to connect all of them to a sequencer with mode 'Any' and then to the notification activity. Just drop an exception handler connected to a notification activity. When any job fails, the control will be passed on to the exception handler which in t...

Look into the Loop start and loop end activity stages in the sequence jobs.
If your control is at the unix level, you can code to run that particular job x number of times.

You need to break the process down. Think about major categories like Design, Error handling, restartability etc. Then break each one of them down according to the specs and make decisions such as use of staging tables or use of staging files, what table will hold what type of dimensions, what type ...

Try checking with your unix admin.
Try running this command at the unix level, just copy past my code and see if the file gets created.

True. But its not DataStage .odbc.ini file. Its the system dsn itself as the OP is not able to get it working via MSQUERY

You dont $. Thats to reference it inside the script. And note date is surrounded by ` and not '(quote). Just copy paste my code in the execsh.

I did. I tested it out.
It creates the file "output20060713_201435.txt"

Upgrade. Simple as that.
Try the after job subroutine.

Can you vi it or cat it.
And the problem is not even due to AIX. Over here i tested it both on Sun and AIX. No problems. Also i checked on wikepedia, the colon is not a forbidden character. So its definately something else.

If nothing works out, then just simply create the file output.txt and run an After Job Subroutine and do this

I need to identify among all the records which two records have same key, how do I do that here... A couple of ways, sort on key, and chech for identical keys by using stage variables and then depending upon the deciding column (maybe a date column) flag the inactive one. Pass it through aggreagato...

True. Very true.
Its just my personal rule of thumb, a space in a file name, a big no no.
Because once this file is built. If it needs to be accessed again in some other job, the sequential file wont read it then due to that pesky space. Or it can, am i missing something here ???

Krazykoolrohit wrote:check your DSN. is the server name correct there.

The last test was tried outside datastage which proved that there is something wrong with the odbc connection. No server name, just the odbc configuration that needs to be fixed.

You never needed it in the first place. I guess the client gave you a break.