Well, if it stopped working before the upgrade, the upgrade is not the problem. Possibly somebody else tried to login with the wrong value and locked it up. Has it been reset, or did somebody disable it otherwise?
On Fri, Jun 21, 2024 at 2:11 PM Bob Bridges <00000587168ababf-dmarc-requ...@listserv.ua.edu> wrote: > > My client just asked me to look into an FTP.bat script that started failing > after we upgraded to z/OS 2.2. It's odd; it says the PASS command fails, but > a) the password in the script matches the password that's expected, and b) it > looks like the password is being correctly transmitted during the logon > process. Here's a transcript of a manual attempt: > > H:\>ftp > ftp> open [IP address] > Connected to [IP address]. > 220-FTPD1 IBM FTP CS V2R2 at [URL], 17:57:49 on 2024-06-21. > 220 Connection will close if idle for more than 5 minutes. > 501 command OPTS aborted -- no options supported for UTF8 > User (10.2.11.200:(none)): [ID] > 331 Send password please. > Password: > 530 PASS command failed > Login failed. > ftp> quit > 221 Quit command received. Goodbye. > > 1) Why do I say "since the 2.2 upgrade"? The user used to run it about > weekly, and when it stopped working a few months ago he simply stopped using > it. So he has a pretty good lock on when the problem started. > > 2) Is the password itself correct in the script? Yes: The script itself was > last changed in 2015. The user showed me the script, and just to be sure I > changed the ID's password to match what the script claimed it should be. > > 3) Where does that OPTS command come from? It's not in the script. Web > research tells me that Win 10 adds that automatically right after the OPEN > command. The -d option reveals that the command is "OPTS UTF8 ON". > > 4) So does the failure of the OPTS command cause the correct password to be > interpreted incorrectly on the other end? No, for two reasons: The original > poster of an identical problem back in 2018 eventually said "I did receive an > explanation that OPTS UTF8 ON is not the problem", and I see at > https://support.sas.com/kb/57/165.html that this error message does not > affect the FTP results. Furthermore I ran FTP with the -d option and got > this: > > H:\>ftp -d > ftp> open [IP addr] > Connected to [IP addr]. > 220-FTPD1 IBM FTP CS V2R2 at [URL], 18:19:32 on 2024-06-21. > 220 Connection will close if idle for more than 5 minutes. > ---> OPTS UTF8 ON > 501 command OPTS aborted -- no options supported for UTF8 > User ([IP addr]:(none)): [ID] > ---> USER [ID] > 331 Send password please. > Password: > ---> PASS [password] /* this was the correct password */ > 530 PASS command failed > Login failed. > ftp> quit > ---> QUIT > 221 Quit command received. Goodbye. > > So the correct password is getting there. Or, wait, maybe it isn't; the > mainframe connection didn't sent it back to the client, so it's gotta be Win > FTP that told me what it sent. May still be wrong at the other end. > > I gotta believe this is happening to others, and that the fix is well > understood. Can anyone explain? > > --- > Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 > > /* Let the righteous smite me in kindness and reprove me. > It is oil upon my head; do not let my head refuse it. -Psalms 141:5 */ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
