DSXchange

To be more helpful, we would need to see the exact syntax of your call to DSExecute, along with prior statements that assign values to any variables used within the call, and subsequent statements that access values returned by subroutine arguments.

The "DSU" prefix indicates that ForceFail is a user-written routine of some kind. The error "not cataloged" usually indicates that the routine has not successfully been compiled. If you imported from an export file in which the executable code had not been exported, this is an equivalent situation. ...

The "DSU" prefix indicates that ForceFail is a user-written routine of some kind. The error "not cataloged" usually indicates that the routine has not successfully been compiled. The process of compiling a server Routine also causes an entry to be placed in the "catalog" (actually the VOC file) cont...

The only two choices are
the import via Manager of ODBC table definitions (you only need to get as far as populating the drop-down list of DSNs) , or
manual edit of the uvodbc.config file in the project directory on the DataStage server

You can create a DataStage job to do it! Not too many days ago I posted the column names from the DataStage log table. (Metadata from the DataStage repository tables is deliberately hidden during import of table definitions for UniVerse tables from localuv.) The only tricky bit is mapping the job na...

Dennis and the site team are currenly resolving some issues that Ascential's legal folks have about publication of their trademarks and copyright material.
Negotiations have been in progress for about five months thus far.

Your problem really is that the form "June 30 1999" is not actually a date, but a character string. So you're not comparing apples with apples. In string terminology, you're trying to compare, for example: "1999-08-31 15:03:40.024" > "June 30 1999" Ask yourself, what is the result of this string com...

I am trying to use before/after routines to set the UserStatus depending on the JobStatus of a job (am using UserStatus as requested by our support people so they can check jobs within our scheduling software). From reading the manuals I get the impression that I could set the UserStaus at the star...

There really isn't enough information for diagnosis here, Tobbi. What does your job do? What are your sources, what are your targets? Does the Transformer stage have constraint expressions? Are the hashed files loaded in the same job that refers to them? I suspect that you've tried something like th...

This job would be improved by ensuring that you aren't trying to insert rows that already exist. This would mean that the "duplicate key value" error messages would not be generated. It's probably a surfeit of error information attached to the ODBC connection or statement handle (when you're sending...

This won't help. DataStage sends a COMMIT. There is no transaction isolation level that bypasses this. Therefore an Informix database created without logging will still generate the error message when it receives the COMMIT.

Could you consider using a (perhaps multi-instance) server job, using the XML Reader stage?

Another way to detect whether the lookup failed is to interrogate the link variable NOTFOUND for the reference input link. Thus, for example, the constraint expression on the output link that handles those rows for which the reference lookup (on input link RefInput) would be simply RefInput.NOTFOUND...

You could create a DataStage job to do it!
Column names in the log are found by executing LIST DICT RT_LOG at the command level. Your job will need to determine the job number, to form the name of the actual log table (RT_LOGnn).

The Administrator's primary role is installation and setting project-wide defaults, basically the tasks on the Administrator client's tabs. After that, the DataStage engine is designed to look after itself reasonably well, though there are a few minor housekeeping tasks, such as deleting old files f...