DSXchange

could you please cut-and-paste the error message?

Plus it is in the General forum; so I assumed that both were wrong. I don't know TX - are the functions and routines in that product?

Please Note - the initial response only applies to Server and (partially) to PX.

The FTP Stage requires an input link if it is writing data to a remote system, or an output link if it is reading from a remote system. The information you enter in the stage pertains to the file on the remote system.

The FTP stage in DataStage transfers data line-by-line using FTP calls; it doesn't use the classic FTP program as we are used to. Are you reading from or writing to the FTP stage? Are you specifying a valid userid and password (yes, I saw you mention "anonymous" ftp)?

You need to have a data stream going into the FTP Stage in order to perform a "put" operation. Is that what you have done? It sounds like you are using an FTP Input stage instead.

I would have expected the "date" command to display in the NLS format, but am not at a machine where I can check that. I seem to recall we always had to type in the same formatted date regardless of NLS settings, so that is probably not the issue after all. Do you get a different error if you try "0...

Ok, then you shouldn't have problems starting jobs (unless they are already running or not compiled). Do you use multi-instance jobs? Does this error always happen or just sometimes? Can you manually start the jobs that fail in the job sequence?

I just used the search facility in the menu above, and found this thread

What is your system's default date format? Perhaps it is yyyy-mm-dd and you might try entering the date in that format, i.e. 2500-01-01

The first step is making sure you can issue a FTP from the command line. Once you have that working, you know the necessary values for the FTP stage, namely remote system name remote userid remote password local directory remote directory It sounds like you haven't set the remote directory or your f...

Is the status of all jobs called by the job sequence "compiled" or "finished" or do you use the setting "reset then run" in your job activities?

mousazzi - does this happen at other PCs with the client installed or just on your PC? Do you have any patches installed from IBM? (There is a general patch available from your support provider which addresses a number of client issues, but I don't know if it applies to your current problem).

This is easy to do with the FTP Stage. What have you tried so far and what hasn't worked?

What has changed since the job ran correctly? Have you tried resetting the jobs to see if you can get more information from the log files?

What are your hashed file settings? If you pre-load to memory and/or use buffering try changing the settings to see if it might affect your error.