DSXchange

Yep sure was quiet! Even with the volume up full and the headphones on I had to listen pretty hard. Looks pretty impressive - is the rightmost column (Transformation) free text, or is there some specified form that it must take. In particular, can the column names be dragged into here (rather than c...

Curious. So this is not the DSJobReport routine (in Built-In\Before/After category) that ships with DataStage (obviously, since a before/after subroutine has precisely two arguments). It may be that the process of upgrading or creating a new account has overloaded Kim's routine with the supplied one...

Where, and with what authority (login), are you attempting to use the UNLOCK command?

Try using the Cleanup Resources option in Director.

WriteSeq ID To objFileVar Then ...

Change the requirement. Or use CAST in the extraction SQL to convert the NTEXT to LongVarChar.

Construct a string containing all non-alphanumeric characters, perhaps in a stage variable. Use the Convert() function to convert these to "".

That's very surprising. Check its spelling and casing where you've used it as a job parameter. Did you add it via "Add Environment Variable" button?

The only thing you can do, if you can't change the representation of NULL, is change the column definition from Char(13) to VarChar(13) - which is not fixed-width.

Create one large file using DataStage then use the UNIX command split to break it into many smaller files.

For starters, NEVER kill job processes.

What errors occur? "Not working fine" is insufficient diagnosis. What are the operating system permissions on the source file, the target file, and the parent directory of each?

The moral of the story is that one should never hand-code table metadata; always import table definitions from the data source/target.

If the metadata remain untouched by human hands, there is no possibility to introduce error.

The number of nodes in the configuration is completely unrelated to a broken pipe, which can occur on any single node or between two nodes.

Abt was an engineer who invented a cogged railway system for steep inclines. There, you have Abt explained, as requested.

Show us precisely what you did with stage variables. An approach based on stage variables can certainly work, provided your data appear sorted as in your example here. You need stage variables to "remember" Inv and RecType from the previous row, others to detect whether there's been an change in Rec...

The bonus question should be added to one or more of the DataStage Interview Question web sites.


I should love to hear how you replied (provided it's clean, of course).

Check the source code for DSJobReport and verify that it has five input arguments.