DSXchange

Are you using QS (QualityStage) in this job?

To expand on what sud has mentioned : read the manual, try what it suggests and then, if you have problems, report what you tried and what went wrong. You will get a quick and hopefully correct answer in that case. DSXChange isn't a substitute for documentation or training, it is used as a supplement.

RekhaMallam1 wrote:can multiple users use same db connection??

Yes.

RekhaMallam1 wrote:Can i expect the answer with an example....

Expect: Yes, Receive: no

Try running the job and not using view data, does it work then? I think you need a local queue in order to get view data to work in the connector.

I am afraid that you haven't quite answered the question I wanted to ask, sorry. In DataStage run the job and view the output file in UNIX with a binary editor. I am fairly certain that there are no "lag problems" (a term that I haven't heard before) in that file. This conversion is almost certainly...

Just4geeks - I did read your first post and replied. At version 8 the locking mechanism is no longer exclusively controlled within the DataStage server engine as it was in the past, there are now other components involved on the IBM Information Server side. Open up and connect to "http://{servername...

Exactly when are you getting this error - when you open the Director log view? When you double-click to open a particulare log entry? Also, check your stages to see if you have a user-supplied BBB stage, as that is not a standard DataStage one.

You mean in the Options list the "Open Command" and "Close Command"?

According to your metadata that will not be the output format. Can you view your file with a binary editor on UNIX to see what the contents actually are?

I'm not at a DS client to check this, but the indexing in transform starts at position 1 (for Server compatibility) while everywhere else strings start at position 0, so the correct form might be FieldName[0,1] = '7'

This is Version 8, so you need to do this from the Websphere Information Server side as well.

"DS.REINDEX ALL" would work better.

DataSets cannot be updated as can database tables. You can append to a DataSet but you cannot update records.
It does not make sense to use hashed files in parallel jobs; much better to redesign jobs so that you have no need for hashed file type constructs.

No, there is absolutely no way to retrieve a deleted job in DataStage unless you have a backup.

Could this be a BuildOp written on another machine and where the library was not copied over.