Hi Martin,
if I try the command "cd /prova" it goes to the correct folder.
But if I run "cd prova" (without the slash), I get an error. If I subsequently run "cd /prova" (which previously worked), I get a second error.
From now on any "cd" you play will not work.

That's stil ftp client cd command. But ok, the ftp client maps cd command directly to FTP CWD protocol command (try running ftp with -d switch). So what's the logic on AS400 to tell, when the leading slash is needed and when not with cd/CWD?

Sure FTP command, see screenshot

I mean FTP protocol command, not WinSCP command.

Hi Martin, CWD in an "invalid command". If I run CD /prova it works fine.

It seems that to get to the /prova path, WinSCP would have to do CWD /prova, not CWD prova. What's the logic on AS400 to tell, when the leading slash is needed and when not?

Hi Martin, with FtpWorkFromCwd=on both the commands are working, but not the file transfer.
Instead with the parameter FtpWorkFromCwd=auto the file transfer works but not the second command.
I'll send you both logs.
Best regards

Did you try to set FtpWorkFromCwd to on? Can you post log file for that?

I'm using WinSCP 6.5.5 .NET assembly in PowerShell script.
In my script I did these tests:

1. launch just one or more commands using the ExecuteCommand: works fine
   
2. launch just one or more commands using ExecuteCommand and transfer a file with GetFiles: works fine
   
3. launch one or more commands using ExecuteCommand, transfer a file with GetFiles and relaunch a command with ExecuteCommand: this last command fails
   
4. if I remove GetFiles the last command works fine
   

Can anyone tell me what the problem is?
I'm attaching the following files:

• PowerShell script
  
• Execution result
  
• winscp.log