DSXchange

A DATUM is, in C terminology, a structure. One of the items in that structure is an indicator of what kind of item is currently being held in that DATUM. For example, if it's an integer, then it's stored in four bytes. If it's a float, then it's stored in eight bytes using a 51-bit mantissa and an 1...

Probably nothing. Most of the characters that appear to concern you appear to be in control set 0 (Char(1) through Char(31)), none of which has its high bit set.

If they're EBCDIC, you need to convert to ASCII (or Unicode) before you can do anything sensible with them in DataStage.

Lookups are intended to be made against database (DB2) tables. In this case, the table is opened once and a cursor established based on the query - in non-mainframe environments this is called "prepared SQL". DataStage then passes the search key value and receives a row in return. I believe the prob...

Can you convert the residual ^M to \n (explicit newline)? Or explicit space?

Need 8.x in the version drop-down, since 8.0 TX is now out.

Need not to have version (or platform) mandatory where it's irrelevant, such as Editor's Corner.

Balance that whispered advice with the fact that the sales dude's commission is far greater for EE than for server.

A job sequence is a special case of a server job (with job control code). The server engine functionality is not going away any time soon.

Convert(Char(13), "", InLink.TheString) Even more efficient would be to initialize a stage variable, let's call it svCtrlM, to Char(13) and not derive it for every row. This way the Char(13) function is evaluated only once. Convert(svCtrlM, "", InLink.TheStri...

Did you mean Roy? I have seen this behaviour - admittedly on XP Pro SP2 - and it has since gone away, after I applied the SP2 patch. But I made some other changes too so I can't be sure what actually fixed it. There was also a related issue where jobs in the top level category could be seen but jobs...

You will probably need to scroll the Columns grid to the right to find the Missing Columns rule.

Take a backup. Verify the backup. Take an export of the whole project. Verify the export. If you have a good backup nothing will go wrong (4017th corollary to Murphy's Law). The rest is simply following the instructions in the manual and any recent advice in the readme file or paper documentation th...

Nothing wrong with that. Whatever you do, if you've read multiple columns you have to test them all. The only other approach is to read the file as if it contains just one column, and only allow it to pass if it contains more than just commas (you could test its length, for example Len(InLink.TheSin...

"Nothing" is not the correct answer. Either you've run out of disk space on your client PC or you don't have write permission where you need it on that machine.

Version 7.5 was the first that will not install on Windows NT 4.0. Versions earlier than 7.5 can be installed on this O/S.

Version 7.5 requires Windows 2003 Server (officially) but will install on Windows 2000 Server and Windows XP Pro - though you won't get support in either of these cases.

I don't see why there's any need for a hashed file at all, if the value already exists as a job parameter.

My DataStage server is on NT and Files are on UNIX Box, So these files are external sources to Datastage Server. Ah, new information not in original post. (Notes that original post specified UNIX as the platform.) Yes, you can pass values to job parameters from job control code. For example a job s...