DSXchange

The function would be

With a fixed width file any length errors are fatal. Or do you have a line separator defined?

You are making it too complex. the hex values you showed "31 32 33 34 35 36 37 38" are simple ASCII representations of the numbers you need, just read the field as ASCII instead of as a binary one.

Naah, I'm just doing long multiple job compiles and surf DSXchange while they run:)

Is it a pure binary format? Try reading it as "binary" into an integer.

For the moment, let us not use "hex" conversion, but ask what datatype you are converting from. Is is a COBOL type COMP-3 field? If so, there are builtin conversions in the SDK or the CFF stage available to you.

DataSets can be backed up as well, and most development databases I know of are not backed up. DataSets are usually such that they can be re-created quickly as well.

I have to disagree with Con #2. Both databases and dataset files are equally susceptible to data corruption.

DataSets are very fast when staying within the DataStage PX framework, much faster than database operations.
Database tables allow random access and updates/deletions. Datasets do not.

Both the ACCT-N nor PERS-BRTH-D are COMP-3 fields and can be read as such using the CFF stage without having to do any Hex conversions.

What datatype is Column A? If it is Char(1) or VarChar(1), just use "Char(37)" - Char() convert a decimal number to a character and 37 is the decimal value of 0x25

You can trim any character using the trim command, and the "enter" character on UNIX is <LF> which is Char(10), thus to trim leading and trailing <LF>'s from the string.

Your original subject/problem was not related to rcp. Your second (new) topic in this thread was related to rcp and was answered, even though it is better to keep only one topic per thread.

The userid question must be answered by your Sybase admin, most likely the GRANTs are insufficient. DataStage has no requirements - just that the ID you specify has sufficient access to perform the action required.

Just after I posted this thread the system I am working on came back up and I wrote a quick job to test this. I have now learned that DataStage takes a single hash of the combined keys and distributes accordingly. Thus, if I partition on "Name" and "Month" then a record with &quo...

Assuming I have a file with columns "Name", "Month" and "Salary" containing a company's employee names and their paid out salary values for months 1-12. If I explicitly hash partition on "Name" (primary) and "Month" (secondary) with a multinode confi...