DSXchange

Vinaymanchinila,
even though I'm not Ray you can right pad your binary to 8 places by using the FMT(In.Column,'8"0"R') conversion. I'm not sure what you are trying to do with the "take 2 characters at a time" part.

You are using a key for your lookup and the error states that it didn't find a lookup record for that key and you have set the job to abort when this happens.

Is the definition CHAR(7) that you have from the DS job or have you done a describe on the actual Database tables? Also, if you increase your table definition in the DDL does the truncation still happen (just one position later)?

When you issue the uv command it will try to enter TCL in the current working directory. If the current directory is not a valid DataStage account then it will assume that you know what you are doing and attempt to create one. There are different flavors of accounts, and this is the question you are...

It isn't possible to use the server edition to write a parallel job. So you have the XE version of the softare. You should post your query into the appropriate PX forum to get an answer. "xpsread" is used to read informix (xps stands for E xtended P arallel S erver). Since this cannot be found in th...

Reading packed (i.e. binary) data from mainframes can be done; so the problem you are seeing probably has to do with the data definitions. You'll get more help if you explain exactly what is happening.

Craig has already identified the issue - the missing (hidden) .Type30 file. Often this happens when someone copies the two files without noticing the third one. Does your process include some scripts which might be doing some moving around of these hashed files?

How do you set the job to run only 947 rows? If it is via the normal job execution call then I've tried the same thing and can't reproduce your problem with AIX and 7.5

The PX functions are not documented in that detail anywhere that I know of.

(Are both Xpert and Mohanraj working the same problem?)
Does adding a <cr><lf> to the source file fix the problem?

What have you specified in your FTP stage? Is your file fixed width or delimited? What is your final delimiter set to (n.b. it is missing in the file, if you add a <CR> to the source file it will probably go through without a problem)

No, for PX writes to sequential files it is not sufficient to just state the nullability as "Yes", you need to set the properties. What have you tried?

You will need to uninstall and clean up the directories and your registry before re-trying. Sometimes I've had to wait quite a while during installs on slow machines and slow networks - how long did you wait?

mohanraj wrote:...My source file is located on ftp...

I'm not sure what that means. Does this mean you are using an FTP stage to read your source file? If the last record then it might be because of a missing terminator. What settings are you using?

You need to define the sequential file output handling of null values, this is where your error is originating. If you go into the output column in the designer, and right-mouse-click and do and "edit row" you will see the attributes that you can set for output.