DSXchange

Try /opt/ds/packages/ftp, or drill down into the dstage directory to look for something one level further down.

May I ask why you are installing such an old, and no-longer-supported, version?

OK then, if it's not privileges, it's something in the database preventing one of the jobs from creating a new value in the sequence - get your DBA to help - this problem would probably occur if two simultaneous non-DataStage clients were also trying to use the same sequence.

Your Windows code page is currently set to 874 (a Thai character map based on TIS620) but the code page of the machine that exported the DataStage components was set to 1252 at the time. To allow the import to occur, edit the DSX file and change the CharacterSet line so that it reads "PC874" (or, ma...

I don't need anything from it. You do. You use the Field() function and substring techniques to extract the various pieces. The delimiter character between lines is the system variable @FM.

Script.

Use a directory to which the executing user has read, write and execute permission.

-param is the correct option, not -parm

Yes, uninstall everything. Then install the .NET C++ compiler. Then install DataStage, licensing both server and parallel jobs. MKS Toolkit should automatically install.

Is PXEngine visible (copied to or mounted on) all nodes mentioned in your configuration file?

Almost certainly yes.

It comes with DB2 client software. It's not part of DataStage.

Looks like you lack privilege to use the schema name SYSTEM. Try using a more appropriate schema (owner) name.

Use the pipe character ("|") as the field delimiter in the Format properties.

Your wonderful invisible friend again? Port 23 (the telnet port) is one of the ones that is typically disabled when a site is "secured" and, yes, this means that port 22 (SSH - the "secure" equivalent of telnet) is the appropriate protocol to use. But, as Craig asks, why are you trying to telnet to ...

NEVER delete RT_LOGxxxx using operating system commands - it is a hashed file, and deleting it improperly will leave the repository database in an inconsistent state. When you delete a job, there are several other hashed files that also need to be deleted; the only correct way is to delete the job ...