DSXchange

This question has been asked so often that it might be worth doing a FAQ.

Samsuf2002 - please try the search facility; If you do a search for "must match field's fixed width " (all terms) you'll find a large number of threads on this subject that will point you in the correct direction.

What is your exact error message and in which stage is this happening?

That is odd. Are you certain you are using absolute paths, particularly for the source file? A common mistake is that the CWD for jobs started through DSExecute is that of the DataStage project directory; if the source isn't found that would explain the empty (but created) output file.

This is a common task. Make the job a multi-instance job and pass in the path and name of the source file via parameters.

A Google search for the keywords "convert xls to csv" will also return a number of packages that purport to be able to do this. I would stick with the original method of doing it from within Excel.

Dimensioned arrays are used only in BASIC programs DIM A(20) FOR i = 1 to 20 A(i) = RND(1000) NEXT i DataStage also uses what are called dynamic arrays, these are string with special separator characters (named @FM, @VM, @SM and @TM) that many of the BASIC builtin functions c...

Annataylor is right, you can also check the dataset's definition using ORCHADMIN at the command line or the dataset management menu items in the GUI

Mohan,

you cannot dynamically assign column names at runtime the way you envision it in DataStage server jobs.

Only if your file has the field names in the first line will this work. You can import this from the manager using the sequential file metdata import.

The license key you got from IBM/Ascential/Service Provider usually has an expiry date. Some licenses expire in the far future, at least one expires on October 10 of this year. You will need to get new license key(s) from your support provider and can then use the administrator to update your licens...

Umm, if you add the directory that contains the dsjob command to your session's PATH variable you do not need to do that. This is independant of your UNIX version. Whether or not you need to specify the "." is also a function of your PATH setting, if the "." is contained there then you do not need t...

Have you tried the same job from another PC, I seem to remember I couldn't reproduce the issue on another system and thought some of the cause might lie in the libraries I had on that particular system.

It looks like VarBinary has the underlying datatype of "raw" which PX won't let you do anything with (except to determine the length). If the length is short enough, can you just declare this as VarChar in the job and/or do a cast to this datatype in your SQL?

Mundane,

did you follow the link? Are you experiencing the same problem as described there?

The same way.