Re: FTP Automation - NAMEFMT

Hello Vernon,

thanks for your input!


Am 19.08.2020 um 02:00 schrieb Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>:

I'm confused, Patrik - do you have a script on the IBM i, is that what "scripted client" means?

Sorry for confusion. I thought I was clear. The answer is: Yes, I'm scripting the client on IBM i.

Is the remote server an IBM i? Non-IBM i servers don't understand of use NAMEFMT, probably just ignore it.

No, the remote server is not IBM i. Therefore I get the aforementioned error messages back from the remote server.

If you have a script on the IBM, just use the namefmt 1 command - since v4r5, this will try to set namefmt on the server, as well.

That is what I do, so the client is able to handle (local) IFS paths. But I want the client to *not* forward this command to the remote server, just set itself to NAMEFMT 1 and nothing else. Or asked otherwise: How can I make the client behave like before V4R5? ;-)

Before v4r5 you use the site namefmt 1 command to set it on the server - no harm if the server is not an ibm i or as/400.

I know it's no harm, but I don't want this behaviour anyway. It's just not clean to have error messages logged "because there's no other way". :-)

I assume by "script" that you override stdin to a file member that has the commands.

Yes, exactly.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc