DSXchange

You forgot the 'cd'. And the command separator.

If you make the changes properly, the warnings will not be generated. Have you made them? Are you still getting them?

It would also help if you posted this in the dedicated RTI forum. Also, try searching for "No handlers are available to process this request" in the forums.

From what I understand, yes. I'm sure someone will be along with a clarification or correction shortly.

Depending on what exactly is generating the warnings, there are several ways. Typically one would set the warning limit when the job runs to a (very) low value. You can also create a reject link set to 'Abort after X rows', set X to 1 and send bad things down that link. One bad thing and the job abo...

All fields in a "fixed-width" file are a fixed width, even when 'null'. So your null value for that CHAR(11) field will need to be 11 spaces or 11 somethings but it needs to be specified as a full 11 characters.

For a fixed-width file, you need to specify a null value that is the full size of the field it is associated with. Is that what you tried?

I'm out of ideas at the moment. Seems to me there really should be something different about this job than all of those "other places" where what you are doing the same thing and it's working.

Have you asked your official support provider yet?

Sorry, I was under the impression you had two UserVariable stages for some reason, which is why I said you could use one from another. You could also concatenate them together when you use them rather than in the stage itself.

How long had this been working before it stopped? I ask because the ODBC drivers only work for 30 days outside of the ODBC stage and then they want you to buy a license for them.

You can, but now I'm confused. Where exactly are you trying to concatenate these two UserVariables stage values together?

pps. That 'code' cannot be changed Yes , the change has to be done in the transformer stage, but he needs to check the derivation, rejectedcode is of type INT: 0 if row was not rejected, non zero if row was rejected. You misunderstand. That is generated code for reject row handling and has nothing ...

Ah... saw the line numbers of 185 and 207 in rameshrr3's post and thought it was yours with a little dyslexia. ps. All stage variables should always have an Initial Value as a 'best practice' and to stave off issues of this nature. pps. That 'code' cannot be changed, it is part of what DataStage gen...

Then you need to find out what the stage/field name really is. The 'Insert Parameter' helper widget should allow you to pick it from the GUI rather than you hand typing it.

Yup, that easy. It's not 'global' in the sense that it will change it for everyone, it will just be for your installation of the Director but it will be set for all jobs.