DSXchange

Can you share your job design? it will help in getting a proper response.And as criag asked please post the the whole log entry. I had earlier been thru some of these errors but my issue had been with the aggregrator stage.

With the given information people can only guess what is happening on your machine. Do provide complete information about the error message. It might be your DS license issue....

If i remember it correctly, one of the user 'michaeld' or 'bcarlson' has written a generic 'C' function and posted here which does this.Do a search in the forum.

I suggested that b'coz once at a client site,it happened to me and the culprit had been the Administrator who had changed some groups security assuming that group does not exist anymore. Are you able to log onto any other systems or applications apart from this?

Do check with your network administrators about those login details. There might be a possibility that during last six months that userid's got expired or so.

Or In the sequential file use the filter option and sort your data beforehand then pass it to hashed file for lookup.

What are the specifications you are defining in the sort stage? And what are your expectations about the output?

You need to use six different Lookup stages. Run the reject links from each of them through a Funnel stage to accumulate the rejected rows. Be careful with the NULL values in both source and reference.Or you can create two staging temp tables and perform some joins using SQL.

In the .odbc.ini file set the TRACE parameter to '0' from '1'. Do check if someone has requested for tracing with your DS admin before making any change.

In the .odbc.ini file set the TRACE parameter to '0' from '1'. Do check if someone has requested for tracing with your DS admin before making any change.

You can do a compare between the results from both server and parallel and obtain those three records and check what is going with them. My guess will be that those records are getting dropped in the server job due to Nulls or non-printable characters in the COL_DT fields. But your job design inform...

It depends on how rigrous is the validation check and how critical is that validation. If you are much concerned about the Data Quality then i will recommend you to use QS only. If there is some simple business logic you are trying to implement for the validation then DS can do it with the help of I...

It seems you do not have the access to the trace file in the .odbc.ini directory. I would suggest for setting that tracing to "off" unless it is required.

Seach the forum on keywords 'Job lock'.

If you want to run the job from command prompt use "dsjob" command with other parameters and you can learn about this in Command Line Interface section in Server Job Developer's guide. If that is not what you are looking for then be specific and clear in you question.