DSXchange

ray.wurlod wrote:The Field() function may have three or four arguments, Arnd. The fourth is number of fields to return.

I shouldn't have tried that without having a BASIC to check; for some reason I thought that PX didn't allow the 4th arg. But the arguments were incorrectly ordered as well in the OP.

Have you tried doing a search on Windows drives c:\ and d:\ for the missing files just to make sure that they were not extracted elsewhere? Also, try creating a file "C:\test.txt" and instead of issuing the WinZip from DS try just an ExecDOS of "move test.txt done.txt" to see if this is executed.

The problem is most likely access rights. Does your non-admin user have the access rights that the DataStage documentation requires? If this is a test or development project you can chmod all the files to 775 and check; but I'm fairly certain that this is the root of your issues unless you have a co...

The Field() function only has 3 parameters, the string, the delimiter and the occurrence number.

Have you tried to create dummy project on the system to if the errors disappear?

Use the comma separator between the columns and name the file "xxx.csv"; then Excel will automatically do what you would like.

You can compile a group or all jobs from within the graphical interface, but not on the command line. There are tools out there that will do this; and it would be a good idea for you to experiment with the forum's "Search" facility as it will show you many, many posts on this subject.

I meant the "Exchange Administrator". Perhaps if you change to html format as the default output it will go away. I do know I had the problem about 2 years ago and managed to get rid of it with some internal setting.

Most common change required is you need to check for using the correct paths and you'll find out how diligent you were in not using hardcoded paths. This is easier when going from Unix to Windows as the path syntax is portable, but not vice-versa. Another possible difference is when specifying termi...

I remember having had the same problem, I think by changing the default output format from html to text did the trick, but your Exchanginator should know about this since it affects all non-Exchange target systems.

if you don't care what you convert it to to then use OCONV(In.ColumnName,'MCP') to convert unprintable characters to a "." (period).

You can use the convert() function to replace that character with some other one.

No, I haven't noticed it before. Did you just change the link name in the designer graphical canvas and suddenly get those errors? Can you reproduce the problem in a simple job for IBM/Ascential support or was it a one-off issue?

the StringToDate() function will do that for you.

This is a duplicate post - please respond to this thread in the Server section.

Moderator - please remove this duplicate post.