RE: FTPing from the IFS

[michael@xxxxxxxxxxxxxxxxxx]

If you're going from an AS/400 client to a Windows server, and you issue
this command:

 quote site na 1                        
 500 'SITE na 1': command not understood

the Windows server won't understand the command. NAMEFMT is a command
only known to the AS/400. 

Now, if you were going from a Windows client to an AS/400 server, and
you issued this command:

ftp> quote site na 1
250  Now using naming format "1".

Then the AS/400 would return with the 250 message indicating that it
changed to NAMEFMT 1. This would also work:

ftp> cd /wcslog
250-NAMEFMT set to 1.
250 "/wcslog" is current directory.


> -------- Original Message --------
> Subject: RE: FTPing from the IFS
> From: ron_adams@xxxxxxxxxxxxxx
> Date: Thu, March 31, 2005 12:48 pm
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> Interesting, I wasn't aware of that.
> 
> Call me anal or a perfectionist, but I just prefer my commands to have a 
> good return code when I run them.  So, I guess I'll stick to the "QUOTE 
> SITE" methodology.
> 
> Ron Adams
> 
> 
> 
> 
> 
> michael@xxxxxxxxxxxxxxxxxx
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 03/31/2005 11:38 AM
> Please respond to Midrange Systems Technical Discussion
> 
>  
>         To:     Midrange Systems Technical Discussion 
> <midrange-l@xxxxxxxxxxxx>
>         cc: 
>         Subject:        RE: FTPing from the IFS
> 
> 
> you don't need the quote site...it won't matter anyway because Windows
> doesn't recognize it...here's an example of an AS/400 client to a
> Windows server...after I logged on I issued the namefmt command...
> 
> > na 1 
>   500 'SITE NAMEFMT 1': command not understood
>   Client NAMEFMT is 1. 
> > lcd /wcslog 
>   Local working directory is /wcslog 
> 
> the 500 message is coming from the windows server..it doesn't
> understand...the Client NAMEFMT is 1 message comes from the AS/400
> client...and you can see that it worked because the next statement is a
> Local Change Directory to a directory in the IFS.
> 
> > -------- Original Message --------
> > Subject: Re: FTPing from the IFS
> > From: ron_adams@xxxxxxxxxxxxxx
> > Date: Thu, March 31, 2005 12:33 pm
> > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > 
> > After you login, try , " quote site namefmt 1"   then just CD to the 
> > desired directory.
> > 
> > Ron Adams
> > 
> > 
> > 
> > 
> > 
> > "Fred Horvat" <fmhcom@xxxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 03/31/2005 10:49 AM
> > Please respond to Midrange Systems Technical Discussion
> > 
> > 
> >         To:     MIDRANGE-L@xxxxxxxxxxxx
> >         cc: 
> >         Subject:        FTPing from the IFS
> > 
> > 
> > Hello,
> > 
> > I am having trouble trying to FTP from the AS/400 to a Windows Server. 
> The 
> > AS/400 is the client and the Windows machine is the server in my case. I 
> 
> > am able to log into the Windows FTP server just fine but I can not 
> figure 
> > out how to get to the IFS on the AS/400 while in a 400 FTP session.  I 
> can 
> > easily get into the get to that desired folder from an AS/400 command 
> line 
> > and from Qshell but while I am in the FTP session nothing I have tried 
> has 
> > worked.  LCD and  SYSCMD CHGCURDIR do not get it into the IFS.  The 
> > Windows server does not recognize the NAMEFMT 1 command allowing me to 
> get 
> > more specific in my commands also.
> > 
> > It's easy to get to the IFS when FTPing into the AS/400 but I can't 
> figure 
> > it out from the opposite side.  Does anybody have any experience with 
> > getting to the IFS from an AS/400 FTP session? 
> > 
> > -- 
> > _____________________________________________________________
> > Web-based SMS services available at http://www.operamail.com.
> > >From your mailbox to local or overseas cell phones.
> > 
> > Powered by Outblaze
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> > 
> > 
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.