FTP

[Guest.Visitor]

Need some help from AS/400 to mainframe users. We are moving away from SNA to TCP/IP. Our AS/400 data center does a large volume of file and spool transfers all month long, AS/400 to/from mainframe. I have a set of CLP to do batch FTP so the transfers can be scheduled for overnight. The problem is the mainframe side whether using FTP interactively or batch. After the login, the mainframe assigns a "home directory" named as your logon ID. This is appended to the front of any mainframe data set name preventing it from being found. I'm going to try to paste in test results to give illustration. I hope this works. Anyway, any ideas will be much appreciated. TIA. To the respondents.....thanks for your help. I found the solution. The command to use is CDUP. This positions you at the "root" directory.

[Guest.Visitor]

Have you tried using double quotes around the string. Here is the difference when I try using ftp to change directories against the mainframe. > cd "'LD'" 250 "'LD.'" is current prefix > cd 'LD' 250 "'LD.LD.'" is current prefix > cd "'LD'" 250 "'LD.'" is current prefix Enter an FTP subcommand. The single quote seems to do an append, whereas the double around them seems to clear and begin. Not sure if that helps.

[Guest.Visitor]

You need to specify the root directory for your mainframe file structure. On the AS/400 it is '/'. You may try 'root'. Specify the root on your GET command. For example: GET "ROOT.LD.AP065M.P030.M01(0)" AMINPORT/AP065R.AP065R07 (REPLACE John Panzenhagen

[Guest.Visitor]

Try: GET "/LD.AP065M.P030.M01(0)" AMINPORT/AP065R.AP065R07 (REPLACE The / should direct it to get it from the root directory. You should also be able to CD /LD / should be standard for the root, it has been on every FTP server I've been on, I believe it's in the standards. 'Believe' being the operative word here. I havent' read the RFC for FTP yet. Regards, Jim Langston

[Guest.Visitor]

John, Jamie, and John. Thanks for your replies. They were all good suggestions. I tried them all without success though. The problem is the mainframe assignment of the "working directory". I can't get rid of it, and it's destoying the integrity of the true data set name. I've attached the last 4 test results to show you what is not liked. Regards. Jack

[Guest.Visitor]

The problem there Jack is not on your send but on the mainframe TSO definition. Whatever ID you are using on the mainframe must have a TSO profile parameter set that appends the ID as a high level qualifier for dataset naming purposes. There is a TSO command to view it "Profile" will display it. Please see your MVS systems programmer as they would probably change it for you so that you don't have to worry about it anymore.

[Guest.Visitor]

I'm finding that there seems to be little consistency in the FTP commands across various mainframes, but you might try using CDUP. On some implementations of FTP, this backs up one level. Also on our mainframe, the commands must be in lower case, but the arguments of the command can be either. Go figure!