FTP EE stage to access data on mainframe system

[verify]

Hi

We are trying to access a file on the mainframe using the FTP Enterprise stage and are using the following syntax in the URI tab(as per the parallel job developers guide):-

ftp://hostname/\'path.filename\'

However we get the following error.

##E IIS-DSEE-TFOR-00089 23:34:27(001) <FTP_Enterprise_0,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFSU-00186 23:34:27(000) <FTP_Enterprise_0,0> processing failed for output connection 1: exit status = 255.FTP_Enterprise_0
##E IIS-DSEE-TFOR-00089 23:34:27(001) <FTP_Enterprise_0,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFPM-00040 23:34:27(003) <FTP_Enterprise_0,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
##E IIS-DSEE-TFSC-00011 23:34:33(000) <main_program> Step execution finished with status = FAILED.

The username and password for the connection is correct and we are giving /usr/bin/ftp as the ftp command.

The stage works if we try to FTP to a unix system. Any help or tips will be greatly appreciated.

We are Using IBM Information Server version 8.0.

Thanks.

[lstsaur]

No way your mainframe is going to open up for you to do the FTP! Do you guys ever think about the security, virus...?

[UweOdrich]

The username and password for the connection is correct and we are giving /usr/bin/ftp as the ftp command.

The stage works if we try to FTP to a unix system. Any help or tips will be greatly appreciated.

We are Using IBM Information Server version 8.0.

Thanks.

Hi,

Unfortunately the Enterprise FTP Stage isn't verbose with it's error messages. There are some messages, but they say nothing about the cause of the error. Because of that situation we do not use any Field any field conversion inside the FTP-Stage. The errors which are caused by missing delimeters and wrong column definitions are not distinguishable from the errors which are caused by connection problems. In most of our jobs, the ftp stage reads only one binary field. Then the record is parsed in a separate column export stage. The possibilities to make something wrong are manageable with this approach.

We dont use the backslashes in our URLs, but we use always a fully qualified file name for the host. If you have checked URL , user and password, then look on the format tab of the FTP stage.

We have problems to use NLS support with the FTP-Stage. When we try to use it with an ebcdic codepage, we will get a error "invalid uri". We dont use NLS conversions, but the normal ascii / ebcdic conversion is working.

[ArndW]

ftp connections to host systems usually need more (and different) parameters than merely giving the name, userid, password and file. Can you connect to the host from the command line FTP program on your DataStage server?