DSXchange

Also define "truncated". DataStage's data browser can be fooled into believing rows are truncated because VarChar columns have been padded with "\0" characters (which is the default setting of APT_STRING_PADCHAR environment variable). Viewing the output file with od -xc or a similar command (or vi) ...

According to the Mainframe Job Reference Guide (page 6-5) any three digit ASCII code value can be used for the delimiter (on the Format tab). You can also use &hA8 instead of 168. If the Delimited Flat File stage won't allow 168 you probably need to read the entire row as a single VarChar (strin...

In the Sequential File stage provide Null Field Value property for the nullable columns. This property specifies how you want null to be represented when rows are written into the text file. It is necessary to do this because there are no data types in text files, only text, so that there can be no ...

Enterprise Edition probably has both parallel jobs and server jobs licensed. Check. If so, then you can run server jobs as always.

The name Parallel Extender (PX) was only ever a marketing exercise and no longer exists.

How did you represent the "ASCII values of control characters" in your Convert function?
Why do you believe control characters to be the root cause of the problem you are experiencing?

Since there are no data types in hashed files, I think you need to look elsewhere for the cause of your problem if you're using the Hashed File stage. If you're using the UniVerse stage then there ARE "casting" issues, as the data types are checked. Is there any reason not to use a Hashed File stage?

So you want one row in the output for each date between start date and end date for each employee? Is that correct? If so you need to effect a user-defined range query against the DATES table. This multi-row return lookup can only be accomplished with an ODBC stage, or a UV stage referring to a hash...

This may sound silly, but try using a number with a decimal place character as the initial value. Possibly for the increment also.

Can you also try the same generator using a data type of dfloat? If that works, at least you have a workaround.

There is no Oconv() function in the parallel Transformer stage. Convert the timestamp to a string, and substring off the am/pm designator (Right() function is ideal). Substring out the hours field, convert to int8 and, if the designator is PM add 12. Convert back to string. Use concatenation to reas...

All you need to do is to set the Null Field Value and/or Default property for each column in the table definition prior to loading it into the job design. No active stage is needed.

This is a warning in the sense of an alert, rather than anything necessarily being wrong. Both "double" (SQL terminology) and "dfloat" (Orchestrate terminology) mean "double precision floating point number". These are huge beasts, and can certainly contain more than 18 significant digits. You can de...

There must not be a space between the function name (Trans) and the following left parenthesis.

My guess is that the routine lacks DSAttachJob() and DSDetachJob() calls. Probably lacks appropriate error handling also. But let's wait till the first attempt is posted.

Can you post that part of the generated OSH related to the modify operator?

Are these values reported by View Data (data browser), which is known to have issues, or by inspection of a text file?