NAMEFMT 1 - 500 Subcommand NAME not valid

Discussions related to FTPAPI (An FTP client package for RPG programming.) http://www.scottklement.com/ftpapi/
Post Reply
Cinzia
Posts: 9
Joined: Fri Dec 01, 2023 11:48 am

NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Cinzia »

Good morning,
I added a new procedure by copying it from FTP_NamFmt because i need the NAMEFMT 1 command, in this new procedure I simply changed the "SITE NAMEFMT" to "NAMEFMT", everything else remains the same.
This however leads me to get the error "500 Subcommand NAME not valid"
What am I doing wrong? Is there another way to get the result I'm looking for?
Thank you

This the joblog
1: > USER PIPPO
1: 331 Enter password.
1: > PASS **********
1: 230 PIPPO logged on.
1: > NAMEFMT 1
1: 500 Subcommand NAME not valid.
Scott Klement
Site Admin
Posts: 732
Joined: Sun Jul 04, 2021 5:12 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Scott Klement »

What are you expecting to happen when you run 'NAMEFMT 1' without SITE in front of it?
Cinzia
Posts: 9
Joined: Fri Dec 01, 2023 11:48 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Cinzia »

Good morning,
I need both client and server to use namefmt 1, these are the differences between the two commands:

namefmt 1
250 Now using naming format "1".
Il server NAMEFMT è 1.
Il client NAMEFMT è 1.

quote site namefmt 1
250 Now using naming format "1".
Scott Klement
Site Admin
Posts: 732
Joined: Sun Jul 04, 2021 5:12 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Scott Klement »

There is no need to change FTPAPI to be in NAMEFMT 1, it is always in NAMEFMT 1. (It doesn't understand NAMEFMT 0)

The 'NAMEFMT' command that you type in the IBM FTP client is not sent to the server (which is what you're trying to do.) Instead, it sees the command and changes the client's behavior to use IFS naming. And it sends the SITE NAMEFMT 1 to change it from the server's perspective.

FTPAPI doesn't have an equivalent because FTPAPI only understands IFS naming. So there's no need to change the client side -- you only need to change the server side via FTP_namfmt.

Note: NAMEFMT is a proprietary IBM extension to FTP that does not exist anywhere else.
Cinzia
Posts: 9
Joined: Fri Dec 01, 2023 11:48 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Cinzia »

Hi scott,
this is the difference in the code between NAMEFMT 1 and SITE NAMEFMT 1.

Code: Select all

dcm_admin                                                              
331 Enter password.                                                    
230 DCM_ADMIN logged on.                                               
 OS/400 is the remote operating system. The TCP/IP version is "V7R5M0".
250  Now using naming format "1".                                      
257 "/IASP/QSYS.LIB/DSCOBJDCMW.LIB" is current library.                
bin                                                                    
200 Representation type is binary IMAGE.                               
quote site namefmt 1                                                   
250  Now using naming format "1".          
put /qsys.lib/DSCOBJDCMW.lib/WO00000023.file  /qsys.lib/DSCOBJDCMW.lib/WO00000023.file 
Formato nome file non valido.  Usare il formato: libreria/file.membro o file.membro.   
namefmt 1                                                
250  Now using naming format "1".                                                     
Il server NAMEFMT è 1.                                                                
Il client NAMEFMT è 1.                                                                
put /qsys.lib/DSCOBJDCMW.lib/WO00000023.file  /qsys.lib/DSCOBJDCMW.lib/WO00000023.file
229 Entering Extended Passive Mode (!!!10677!).                                       
150 Sending file to member WO00000023 in file WO00000023 in library DSCOBJDCMW.       
226 File transfer completed successfully.                                             
118272 byte trasferiti in 0.006 secondi. Velocità di trasf. 20185.088 KB/sec. 
Scott Klement
Site Admin
Posts: 732
Joined: Sun Jul 04, 2021 5:12 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Scott Klement »

I'm very familiar with the difference, Cinzia.

Please understand that not every software package in the world works the same way.

IBM's FTP is *NOT* the same thing as FTPAPI. FTPAPI works differently.
Cinzia
Posts: 9
Joined: Fri Dec 01, 2023 11:48 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Cinzia »

Hi Scott,
I understand that every software is different and I understand that IBM FTP and FTPAPI are different. I would just like to know if it is possible to do this or if I really have to change the logic of my program

Thanks
Scott Klement
Site Admin
Posts: 732
Joined: Sun Jul 04, 2021 5:12 am

Re: NAMEFMT 1 - 500 Subcommand NAME not valid

Post by Scott Klement »

FTPAPI is automatically in namefmt 1. It is already set up the way you want it.

Only the server has to be changed, you do this by calling FTP_namfmt.
Post Reply