DSXchange

-1 is SQL.ERROR therefore the code must iteratively call SQLError() to remove error information from the environment, connection or statement handles until they are clean. In the process of doing so you will learn the true reason for the error code.

If you feel you must change it, simply remove the association. Open Windows help and type the question "remove association". How it's actually done differs depending on what kind of Windows you're running, and I don't propose to cover all the possibilities here.

IBM's advice is to prefer Connectors in all circumstances.

Maybe add some IsNull() and UnAssigned() checks on the function arguments.

does not accomplish anything, as it's overwritten by

If you're using SSL everything is encrypted.

dsdlockd -p is a "probe" and should finish fairly quickly.

In my experience it is totally undesirable to dismiss any character as "junk" without consultation with the owners of the data.

When you install Information Server specify for the MQ plug-in (if you will be using this) that you want to install in client mode.

In DataStage jobs, whether using the MQ Connector or the MQ plug-in stage, specify the name of the MQ server and the queue name(s) that you need to process.

NOT(DSJS.RUNOK) is not a complete expression to use in a trigger. DSJS.RUNOK is a DataStage constant. Against what are you comparing it? Perhaps you need to lose the NOT and use a "not equals" operator.

None of which I'm aware, unless diff could do the job.

These are Japanese characters. There are no rules in QualityStage for dividing characters based on the character sets to which each belongs. That's not really what QualityStage is for, although you might be able to create a heavily customised rule set. The preferred tool would be DataStage, and you'...

For example you may want to specify how the number is to be rounded or truncated.

Of course, if your decimal number has a scale of 0, that point is moot.

Your assumption that "" is not a valid hashed file key is incorrect. Only NULL is not permitted as a key value or, depending on certain settings, key values containing item marks or field marks.

This is the RetrieVe query language (not SQL). Arnd's explanation is correct and complete, provided that you are aware that his D1 means the data field in position number 1 - navigation in hashed file data records is by field position rather than by name.