DSXchange

As mentioned before, change the field to a CHAR one and see what the contents are. DataStage is expecting a delimiter and not seeing one; I would point towards data changes.

RCP can be confusing at first, since you can do manipulations on columns that don't seem to exist. Along the same lines, you can get confusing warnings in joins when a column is marked as "duplicate" because it is coming from RCP. In terms of execution and compile times there is no differe...

The recommendation remains to demote this to an informational level message as the message cannot be avoided and is generally not a valid warning.

What datatype is "NEWCHABIM" - if you look at your code your are treating it as a string in the THEN clause, but as a date in the ELSE clause.

The solution given in the thread solves your problem as well. Add 1 to the month then subtract a day. That also solves leap year issues.

I liked on of Ray's old posts on this subject: It's all Oracle bin Larry's fault for not having a proper Integer data type. You can not prevent this message without adjusting your metadata precisely to match that of Oracle, and even then you will get a message logged (a slightly different one). This...

Since you already have a transform stage in the job then use that stage and a NullToValue() function.

I'm not at a location where I can check now, but I would suggest using a normal INTEGER instead of smallint for MI_NBR_OF_TABLE_ENTRIES.

Sunny is mostly correct but I do need to correct one fallacy. If a dataset is written with a 2-node configuration there is nothing that prevents a 4-node configuration job to read it; DataStage will automatically and implicitly repartition the dataset.

What happens when you remove all record delimiters in the CFF stage, that should either work or give a different error message.

That config file is just a temporary one, not the one stored in the dataset. Use "orchadmin describe {dataset}" or "orchadmin ll {dataset} to get the configuration file information.

You will need to provide more information in order to get a good answer to this one. Does your DB stage (which one is it, by the way?) use hardcoded variables or job parameters and what are the runtime values?

Sree569 - your question, if asked at a car repair shop is like asking "The red light goes on in my instrument panel. What is wrong?". :) Please add some more information to your post. Has this ever worked before or have you already successfully connected to SQL Server from your DataStage i...

Generally COBOL files have no delimiters.

What is the PICture for MI_NBR_OF_TABLE_ENTRIES and what datatypes are you defining in DataStage for that column? Which stage is generating that runtime warning message?

Write a DataStage Routine passing in InString: AValue = SEQ('A') ZValue = SEQ('Z') WorkString = UPCASE(InString) StringLength = LEN(WorkString) Ans = '' FOR I = 1 TO StringLength CharValue = SEQ(WorkString[I,1] IF CharValue => AValue AND CharValue <= ZValue THEN Ans := FMT(CharValue-AValue+1,"2...