DSXchange

Not any more there isn't. We decided that the project is corrupted, deleted the project and recreated it from production. Best practice is to build and test incrementally. There's no point adding a second activity if the first doesn't work. Use a dummy activity (maybe a routine) to test triggers.

Fix the first problem (Input "ACCOUNT" is not a value field.) first.

The numbers showing in your Data Set are indexes to vector elements. Each element is of data type string[max=37] (which is how osh refers to VarChar(37)). Each vector element is probably empty or null, because of the first error.

From memory there's an environment variable called something like APT_PAD_CHARACTER (maybe APT_STRING_PAD_CHARACTER). You can set this up as a job parameter so that you can override it just in one job. As with Arnd, I am not using DataStage this week, so that answer's from memory.

as m new to this tool can you tell me how to caputre the error return by querry or use link var, or routine that inspects the log....... Is anyway it is possible to include / import log generated by DS Director to a text file so that I can attach that in mail.Though I am including job status in mai...

Have your DBA monitor what locks are taken by DataStage processes and by MQT processes. It may be that MQT is innocent in this. Does your job design, for example, select from and update the same table? That can cause a deadlock/timeout situation all by itself.

The table is called DS_AUDIT. It is not explicitly exposed in client tools, but can be queried using the Administrator client Command window. To get a list of column names in this table either search the forum or execute the following command: LIST.DICT DS_AUDIT (anything with type "D" or type "I" i...

The problem is reported as an inability to open a file called \Projects\FP1\Data\RESIGLOB (I must assume here that \Projects is your Master Project Directory). Is this disk full? Do you have appropriate permissions to the parent folder (\Projects\FP1\Data)? Does the RESIGLOB file need to have been e...

That's just how it works. There is only one log table for the job, whether it is multi-instance or not. It is up to you to filter them once you've obtained them. Director includes appropriate filtering, but dsjob does not. Submit an enhancement request if you think it's a useful feature.

It will always yield a total of 10 characters. That's what the 10 in "10'0'L" means. It's all in the manual (DataStage BASIC) and in the on-line help for FMT.

Can you tell us how your match criteria were defined? Were your blocking fields tight enough? Indeed, did you use an Investigation job to determine the domains and cardinality of candidate blocking fields? And, then, there are the match fields? Were you cautious with these, or try to match on all po...

Could be someone has tightened the permissions on /.dshome too much, could be that an itag installation has been done, so you need the DSHOME environment variable instead. And, as Ken suggests, you may not be on the actual server.

"Unemployment" is not working.

I can only suggest that, theoretically, there's no reason why not. Examine the other files in RT_SCnnn to learn about the interface between the operating system and osh.

Not so sure about how you'd include custom routines - need to read some more in the Orchestrate Operators manual for that!

There is an example routine that shows how DSSendMail should be used. It is in the Routines branch, possibly under Examples (I don't have access to DataStage at the moment). Examine this code. DSSendMail() requires, as its single argument, a delimited string containing all of the values that will re...

Are the done files' names parameterized? If so you would need to extract the parameter reference (see below) then determine the parameter value that was used by inspection of the "job started" event in the job log (DSGetLog... functions). Otherwise you should be able to extract the command used and ...

No. Manager is one-way traffic. It can import table definitions, but can not export them (other than in a DataStage export format).