DSXchange

nani0907 wrote:...populate top five decimal values...

Could you explain what you mean by that? Is it the rows with the 5 largest values in one column, or 5 decimal columns and getting the highest among them or some other action?

Never , ever delete files and directories inside a project directory from outside of DataStage. The only acceptable exception is the contents of the &PH& directory. Doing such a deletion will cause problems in the project, ranging from mildly annoying pop-boxes to complete project corruptio...

Yep, unsupported. We have a couple of jobs here that send over 40 VarChar2 columns containing XML (and SOAP) to Oracle, where they are combined into one BLOB for compression and storage. The same happens on the way back into DataStage and the whole thing is a complex and unwieldy system - I wish we ...

Oracle even has that datatype. One caveat is that if you want more than 2Kb of XML then you will have to use a CLOB or BLOB in Oracle or comparable datatypes in other databases.

A Derivation along the lines of In.Column[1,LEN(In.Column)-1]:IF NUM(RIGHT(In.Column,1)) THEN CONVERT('0123456789','ABCDEFGHI',RIGHT(In.Column,1) ELSE RIGHT(In.Column,1) might do what you are looking for. I haven't checked it syntactically, but it should g...

In that case, look at the schema of the existing files (either in the Director with Tools -> Data Set Management, or via the orchadmin command line tool) and most likely you will see mismatching metadata.[/i]

If the AS/400 character set is 8859-1 then you cannot store and display that character. If the character set used is another one and the 8859-1 is just used for the interface then you should be OK by specifying another character set, as the AS/400 will perform the appropriate conversion to the inter...

Where do you fill the COMMON block - are you certain that it is being initialzed?

Yes, the data will flow through the ETL server in both cases.

The once job that is working as you expect is probably doing so because it is using runtime column propagation and the column actually does still exist in the data stream.

By using the "DELETE DS_JOBS JobName" you have ensured that your repository has become corrupt. A job and its metadata is stored in many places, and as of V8 in even more, by just deleting that one entry instead of fixing the original problem you have generated even more issues.

Are you sure that neither you nor anyone else has a job monitor or a director session open to that job?

How about

Sort your data by Brand and Code. Create a stage variable to detect when Brand:Code changes, create another that stores the concatenated string value of "Position" and output that when the Brand:Code changes.

SDKSequences is the hashed file, the UNIX files can be found in the project directory, but as a hashed file it won't be readable from UNIX. The parameter you pass to the KeyMgtGetNextValue() routine will be a record key in that file and the value of field 1 will be the current high value.