DSXchange

The issue is that you don't know what character set you are using in your database (the 7 bit one is patently incorrect), so you won't be able to get DataStage to read it correctly using NLS. Go into DB2 and enter 'get db cfg for {your database};'

My first guess would be that, in your transform, you have a column that is marked in red in the designer. OR go and check line 6322 in the source code.

I don't understand your answer - character set 37 and 284? Are those codesets? What does "GET DATABASE CONFIGURATION" output?

If the job is not running and in a reset state, what process are you killing (which should not normally be done)? Have you tried resetting the job from the command line?

What is the datatype of the column and what do you mean by 'null' - empty string or a null value?

sohasaid,

You stated that the two characters listed in the subject are coming in from
Oracle in a US7ASCII table.

Those characters are not in the 7-bit US ASCII table and therefore are not displayable and changed to '?'.

What is the character set of your source database, or source table? You need to tell DataStage this value on order for the DB2 read stage to work correctly

In the first case, look into the column attributes, particularly the 'default' value, which you can set to 0, or more likely to the hex 00 value. Most likely you are getting cobol copybooks with COMP-3 or other non-DISPLAY columns; plus if you have an OCCURS DEPENDING ON clause then you need to use ...

Change your select to only get rows that have the character in that column. Then find out which position the character is in, i.e. 8, then output SEQ(Input.Column[8,1]) to get the ASCII value as the DataStage job sees it.

As I mentioned before, Server jobs perform lookups through transform stages and parallel jobs perform lookups through lookup stages. The example is a server job and you are working with a parallel job in the designer.

I assume you have different config files. At runtime the value of $APT_CONFIG_FILE determines which file is used, either the default as set in DSParams or a value passed in to the job with this parameter.

Question 1 - are you trying to write to a PIC X(4) field and want to default to using '0'? Or reading from a Cobol file and wanting to set default values? Question 2 - Please explain the problem in more detail. NLS for reading or writing? There are many NLS settings so it is hard for me to understan...

Parallel jobs work differently from Server jobs. In server the lookup is done through a transform stage, while in Parallel you have to use a lookup stage.

The second log entry in the director show which file is actually being used at runtime, please do check there after a run to make 100% certain that this is the actual configuration file being used.

Furthermore, does that directory exist on both nodes?

The reason I asked about director sessions is that they (by default) refresh automatically and thus don't timeout the way an idle Designer session might; so even if you have an aggressive timeout limit set in the Administrator those sessions shouldn't die. That they do might point more towards netwo...