DSXchange

Sreeni,

I have run a test installation on an AMD64 processor and Windows XP professional; you will need to check the documentation to see if this is a supported combination, though. (actually, I am quite certain that this is not supported by IBM/Ascential)

Do you get any error messages? You will need at least XP Professional to install into, not the home edition.

..I have no problem with this log. You know the job runs fine and everything, except for the whole bunch unnecessary logs that may flood the sytem... You will need to get rid of these messages, and it sounds like Ray has discovered why and given you a solution. Writing that many records to the log ...

Craig, now I see what you want - hash a text using MD5 and then run that through a uuencoder. The uuencode part (Base64 encoding you were talking about) is easy, whereas the algorithm is too complicated to make it worthwhile doing in basic [I looked at the public-domain code this morning and it is p...

Craig, what do you want to do - take an input decimal number and convert to base 64 representation in display format? From your first post... take 3 bytes of data (24 bits) and group into 4 units of 6 bits -- this part is easy to do in DS; then the next step confuses me (24 bits condensed into an 8 ...

It remains that you are using ODBC to access your source data, regardless of where it comes from. The metadata definition from Oracle and those of your DataStage job differ and it is telling you that you are truncating data. Declare your column in the ODBC stage as having length 1024 and keep your t...

It is not the data type that is being complained about, but the lengths! Describe your table in the database and use those lengths in the datastage column widths. Better yet, import the table metadata and use that declaration in your job to guarantee identical definitions.

Sure, the data coming in from the SQL query is longer than the column declarations you have in the DataStage job; i.e. you are using a varchar(32) field in Oracle but in your job you only declared it as varchar(16).

Craig,

I've done some coding with Base-N system in Uv/Basic in the past (guess where those binary thingies in the SDK came from in the first place ). I have to run now but I'll do it for you tomorrow. I would use OCONV/ICONV and the MB and MB0X functions. Are you using base64 for math?

There is an internal problem with your project. As Sainath suggested, a reindex might solve the problem, but since you said this is a fresh install I am guessing that something has gone awry during the installation, either of the server and/or the project. Please check your installation logs for war...

If you log in as the DataStage administrator and go into the designer for a New Server Job, go into the Job Control tab and put in one line of (dummy) program code "CALL DSLogWarn('I am a warning','')". Compile this job and run it in the designer. Does anything show in the log file? You should have ...

What about if you try to compile & run from the designer? Do other jobs run in the director? Are you logged in as administrator or as another user? If you go to the project directory and it's subdirectory &PH&, delete the files therein and try to run the job in the director, do one or mo...

LegendKiller,

no inputs until you tell us more. Does the job status in the director change from "Compiled" to something else? Is it a Px job or a Server job? Does it do anything special? Can you do a Validate on the job, or a Reset? Can you run it from the Designer?

arindami,

there is no option available, the dscmdexport always does a full project export.

There is a tool on ADN called DataStageBackup.zip which you can download that might address your problem.

Ray,

darn, takes the wind out of our sails...