DSXchange

The log is not a file, so restoring it "with the unix" is not a straightforward procedure.

Where is the library/object that contains your parallel routine? Is its parent directory in LIBPATH? (Other UNIX variants may use SHLIB_PATH or LD_LIBRARY_PATH as the library search list environment variable.)

What exactly do you mean by "moved"? Certainly the two usual methods work OK - they are export/import and update in place.

Check your library search path.

Can you please check the Score of the job (set APT_DUMP_SCORE to True and inspect it in the log) to determine the characteristics of the export operator associated with REJECT_2_FF ?

Can you also verify that the pathname, filename and other properties of this Sequential File stage are correct?

Please post the exact error message. What you have provided is not clear. Copy/paste from Director log.

What is the maximum size of a line in a file in your operating system? (This may be the limit you have encountered.)

Welcome aboard. In this case "export" is the action performed by the Sequential File stage in writing to a human-readable (text) file. Do you have problems with other Sequential File stages? Can you please outline your job design - in particular does your Lookup stage have one or two outpu...

Good advice. Treat the state file as a "black box". It works - be happy with that.

API = Application Programming Interface All that means is a library of functions that programmers can use to achieve some result. For example IBM provides an API that you can use to access DB2 programmatically. This is the DB2 API. Someone once authored a DataStage stage that invokes functions in th...

Why re-invent the wheel? The routine already exists in the SDK routines. It is called UtilityRunJob.

These results suggest that the dsadm and Administrator users and the dstage and ANALYZERPROJECT projects are correctly recorded. Therefore the error messages may be misleading. Go to the web console for Information Server and open the session management page, and see whether there appear to be any d...

Look carefully at the error messages - the first three are referring to the UV project (the DataStage server engine). So there is a problem of some kind there. Unfortunately there is no single diagnostic tool, but you might like to run queries against the UV.ACCOUNT table, the UV_USERS table and the...

DS_TEMP* and RT_* are not "old". They are run-time data for jobs, with each job having a unique number. They are removed when the jobs are correctly deleted using the Designer or Director client. Until then they are required.

Has PNav been updated to handle Parameter Sets?