DSXchange

My automatic export strategy is a BAT file that executes dscmdexport (after renaming yesterday's export after deleting the previous renamed export file). If you don't mind embedding a clear password (and relying therefore on Windows security to prevent others from seeing it), you can schedule the BA...

Q. Can I create a sequential file on the fly? A. You could make the sequential file name (or pathname) a job parameter, and use that parameter in the Sequential File stage. You can also, as diamondabhi noted, use the date only as the job parameter. The file name need not be entirely a job parameter...

It's not an error - it's a warning of the fact that DataStage is going to perform some partitioning that you did not specify or that you specified in a way that won't work. Because DataStage is not executing the actual design, it issues a warning. This actual message and its meaning has been posted ...

That's just an informational message (you can tell because of the ##I at the start). The first error (##E) message indicates "Access denied." The OP (original poster) needs to resolve that first.

MetaStage_Loc_Info is not a table. It's a collection of data that is a property of a design-time object, most particularly a table definition. Project-wide MetaStage proxy mode can be enabled/disabled in Administrator or by editing the DSParams file. This setting can be overridden by checking the "R...

Welcome aboard. :D Very few of the other tables are used for administrative purposes; the main ones being UV.ACCOUNT and UV_* (which count as system tables) and SYS.MESSAGE. Directories with names beginning and ending in "&" are also similar to system tables. Tables whose names begin with DS_ ar...

Found this site and thought some here may find it interesting, while others may find it amusing.

No. Nothing in uvconfig will help this problem, which has to do with the current status of the job. Note that the status reported in Director's status view is the last recorded status - it may not be the actual current status. Clearing the status file for the job and recompiling is guaranteed to ret...

Are you running version 7.5x2 or a different version? Do you change any other properties in the Column Generator stage when this occurs? Export your job prior to running and export it again after runnning. Copy the generated OSH before running and again after running. Examine both pairs of files to ...

A simple matter of reading all the information supplied in the error message.

You are using a user ID from which some privilege - possibly CONNECT - has been revoked - maybe for too many failed login attempts. This is not a DataStage error. Contact your DB2 DBA for a resolution.

Previous post didn't really deserve premium status, so I've removed same. There's nothing technical in it.

The job that populated the Lookup File Set stage used a different number of nodes, or a different set of nodes, than the job that is attempting to use the Lookup File Set stage to perform lookups.

At a quick guess, it's incorrect (insufficient) permission on C:/Ascential/DataStage/PXEngine/etc/standalone.sh or one of the processes that it needs to fork.

Or it may be that the system has run out of available processes. This is quite rare, but not impossible, on Windows systems.

Along similar lines, if the lookup succeeds, just perform the substitutions in the Transformer stage output column derivations.