DSXchange

WeekdayFromDate() allows you to specify the origin day as an optional parameter.

Returns the day number of
the week from the given
date. Origin day optionally
specifies the day regarded
as the first in the week and
is Sunday by default

Do you have enough space in your destination directory? Try adding "TRACE ON" in your FTP command to see if you get more debugging information from the program.

cygwin does not magically make DataStage Windows run under UNIX. The "dsjob.exe" windows command starts jobs, and that can be called from the command regardless of whether or not cygwin is installed. You can install the dsjob.exe on any networked PC and call that up to start jobs on your s...

Unless you specify number-of-runs, in which case an instance will be correctly and completely removed; the director entry will still be present, but the contents will be purged. Autopurge on multiinstance jobs can cause problems if an autopurge is executed upon job completion and deletes log entries...

What is your OS and what is your system or file system's limit for file size? If you manually start a FTP command to get the file, does it come over correctly? Are there any FTP warning or error messages generated?

"writing the code" means as a derivation? Are you certain that you didn't surround that code with '(' and ')' or use it in another manner outside of a derivation? What happens if you replace the derivation, as a test, with 'Hello', what is your output?

The syntax will work as posted, thus the assumption that your output might be VarChar(1) or Char(1) and thus truncates the output string.

You can use the vertical pivot of the enterprise pivot stage at V8 to convert multiple input rows into one output row for MQ.

I can't check right now, but on lookups I would think it returns NULL for nullable fields.

Yes, that is the case with premium posts.

It will use 0 if the field is non-nullable.

You cannot get the clear-text value for an encrypted parameter. To avoid the error add

If your DDL and database read stage both specify a non-nullable "Field1" then I would add "$OSH_PRINT_SCHEMA" to your job parameters and see what the actual schemas that DataStage uses are. If they differ from the database DDL then you should submit this issue to your support pro...

Add "$OSH_PRINT_SCHEMAS" to a job's parameters and experiment for yourself how the key column setting is reflected in a schema.

I can't see anything wrong at first look. Try changing the DSJ.PARAMVALUE to DSJ.PARAMTYPE as a test - do you now get some integer value to the right of the '=' sign?