DSXchange

Add it and find out Actually, I think you have found your cause; the installation guide PDF should list this if you want to check.

I thought this was an oracle library, not part of the DS set. If you do an ls-al on that file what is the size (and what version of DS do you have on what platform) and are the access rights set correctly with R and X rights?

Check the 1st line of your job in the director, this displays the actual runtime ENV settings. Are they in there?

Find the library "dsstpora.so" on your system and make sure that directory is in the library path of the job. If not, add it to the entry in your dsenv file.

In a transform stage put a derivation in

I had this issue about a year ago and posted it here. Let me search....

here it is

Use RTRIM and check whether the last character is space or '-'

Could you please explain that? RTRIM doesn't exist in Server, but even if you used TRIMB I don't see how that can be used in this example.

Using the generation attributes will let you either cycle through a list of values or increment from a starting epoch, but won't give you the current date/time. You should use the transform stage for that derivation.

In that case it is probably unsigned COMP-3, but I'm just guessing. If you could post the HEX values plus the correct numeric representation I could tell you, though.

The ICONV(In.DateStringColumn,"D4/YMD") function will return a number if it can be converted to internal format or will return the original string if it cannot.

sdfasih, Here is some sample metadata for a file on my system: VarChar(128). Do you see that the question, at least as I understand it, is somewhat vague? What are you trying to achieve? Most files that you will use will have different metadata - in this case we are talking about the definitions on ...

Look at your error message. The data type is DOUBLE precision numeric. If you write an empty string value to this type of field DS has no choice but to set it to NULL. Strings are a different matter entirely.

You can use the SDK functions that convert binary COBOL datatypes to do this. Do you know what sort of binary data you have?

At byte offset 50 in the first line of data your metadata expected a character representation of a date (assuming that is the definition of "Start_Date"). But at that location the source file has the characters "StPr" and this is what is causing the job to abort. Try doing a "view data" in the desig...

Define "Batch"? If you mean a DataStage sequence you can call routines directly. Is this a BASIC routine or a C++ PX one?