DSXchange

What is the state of the connection as shown by netstat -a? On some OS's these hanging connections will timeout automatically after a lengthy period (I think it might be 45 minutes by default on AIX) and on others, notably HP-UX, these sessions will not timeout and a reboot might be the only option.

A decimal field has no internal signs or spaces so you are OK; your problem is when you wish to display that value, in which case you are displaying a string that has been converted from the decimal value. If this output is going to a sequential file, the value written is actually a VarChar or Char ...

Ahh, when I responded I skipped over the "successful" keyword, I thought the poster just wished the last run information. As stated, this information is not directly available and perhaps not even available at all if the log has been cleared or purged. To date I've implemented systems wher...

How you name your dataset file is not critical to opening it; if you created a dataset called "mypictures.jpg" then you will be able to view it if you use the same name when reading. In your case you are not reading the same file that you wrote.

The error indicates that your job expects a fixed length of data, but that the data itself is different from the definition (it is longer). What fields have you defined?

I don't have access to the documentation here to give you the exact options, but the command is DSGetJobInfo()

Why did you open another thread when you have an active thread with the same question and also a couple of responses here.

Too bad you restricted your query to Ray and Craig.

Too bad you restricted your query to Ray and Craig.

I am not certain what is happening in your case. Is your repository on the same machine as the Datastage server engine? If not, could you stop and restart both the DataStage engine as well as the database?

Try doing a "truss-p <pid>" on the processes to see which, if any, system calls they are doing. Perhaps they are waiting on database locks in the repository. Also, try creating a dummy server job or job sequence and see if that has the same problems.

What compiler error are you getting in (2)? Typically your compiler options will be the same on similar machines (same OS and same version and same compiler).

The impact of changing compiler options is not part of DataStage but that of the c++ compiler and linker.

My guess is that you are not supplying a full 4 digit year in the returned value, and DataStage is using the setting of $APT_DATE_CENTURY_BREAK_YEAR to interpret that date as 2000 instead of 1900.

Although the path looks strange as it is not absolute, the file starts with ".nfs" which might indicate a NFS mounted device. What sort of hashed files are you writing to in this job? Is this path present on your system and if so, what are your user's access rights to the file?

As MarkB has already pointed out, the error message is a DataStage engine one, meaning that the command was entered at the ">" prompt of the engine, which most people will do when they enter an Admin command interface line. The "dsjob" executable is located in $DSHOME/bin and sho...