DSXchange

That is odd indeed.

Could you try to create a new project in the administrator, then use both your user-id and the administrator-id to go into that new project and see if you can create a PX job?

Did you also check the .xml licensing file to see if that includes the PX product?
From UNIX, go to $DSHOME/bin and execute the "dslictool" program without parameters to see what is installed.

Could you be getting DOS format of <CR><LF>? This would require a convert command of "CONVERT(Char(10):Char(13),'',ipcol)" for you.

Sort the rows by ascending portfolio_no In a transform stage use the following stage variable logic svNo IF In.portfolio_nr = svLastPortfolioNr then svNo + 1 else 1 svLastPortfolioNr In.portfolio_nr Just use "svNo" for the derivation of "no" and you will get your required result.

I didn't know of an internal change requiring "landing" at an interim version. Perhaps one could try editing the .dsx and changing the version number manually to see if all jobs load & compile.

Certainly no stages have been removed between versions 4 and 7.

The Programmer's Guide documents the routines you can call from c, and they include both of those you mentioned.

Yes, you can import the old jobs into version 7.5. The one significant change that affected many old jobs was that you used to be able to modify job parameter values inside the jobs and that won't work anymore. Detailing the differences between the two versions is a bit much to do. This would be lik...

The CONVERT() function can be used to remove characters from a string. It is not clear which characters you consider to be "special", but the function CONVERT('\#`','',In.OracleStringColumn) would strip out all "\", "`" and "#" characters from the "Oracle...

If you were to use English language pseudo code would the following logic be what you want? Read record from input If Record contains the string "(OCCURS " then a number then " TIMES)" then output the record string before the "(OCCURS" substring a total number of times ...

You have a data record that is 109 bytes long, but your record definition for this record only read 103 bytes and cannot account for the missing 6 bytes at the end of the record. Those bytes will be ignored but the warning tells you that you should check both your definitions and data to make sure t...

I am not sure and can't check from here, but that port number(31531) might be that of the ASBnode. Can you check to see if that is running on your machine? Does WebSphere and DataStage function correctly (apart from this problem)?

I suspect that if you remove those 4 offending columns the warnings will persist. Can you check and post what your unique index "D_Employee_NK" consists of?

When you de-install the client you must make sure to "regedit" your registry and remove all remaining entries. Did you also re-apply all patches after your re-install?

udayk_2007 wrote:The disk location mentioned in pxresource section of configuration file , defines the location where datasets will be stored on the server

Not always, that is just the default. The location is actually specified within the DataStage descriptor file itself.

Thanks!