FTP NameFmt V5R2

["Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxx>]

Couldn't find my problem in the archives. 

We recently upgraded to V5R2. That was when we found out that a
security loophole was fixed.

Now, I find that FTPing from our production to our develop machine is
not the same as from dev to prod. Dev PUTs NameFmt = 0 where prod PUTs
NameFmt = 1. Finally found the file in the IFS - which we don't use.

Enter an FTP subcommand.             
> CD /TRSFDD                         
250-NAMEFMT set to 1.                
250 "/TRSFDD" is current directory.  
Enter an FTP subcommand.             
> SENDPASV                           
SENDPASV is off.                              
Enter an FTP subcommand.                      
> BINARY                                      
200 Representation type is binary IMAGE.      
Enter an FTP subcommand.                      
> NAMEFMT 0                                   
550 Current directory requires name format 1. ********************* 
why?
Server NAMEFMT is 0.                          
Client NAMEFMT is 0.                          
Enter an FTP subcommand.                      
> PUT TRSFDDSAVD                              
250  Now using naming format "1".             
257  "/TRSFDD" is current directory.          
          

Apparently NameFmt = '1' is required for current directory. Is there
some command that I can use to view the settings on each machine?
CHGFTPA doesn't display settings. Apparently we are OK going to/from the
prod/dev machines to our servers (not AS/400).

Thanks for your help





Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me 
Unsolicited Commercial Email