On Tue, May 30, 2023 at 5:14 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
Personally, I don't see the solution to this behaviour as simple as
'choose another character in your password.' How would I maintain a
database of email addresses?
A database of email addresses is a completely different thing than passwords.
For one, if you successfully connect to a database, then the
handshaking that occurred in order to create that connection will
either have worked completely (all characters translated in the proper
and expected way) or you will see incorrect translations and can
usually take corrective action. At the very least, you should be able
to get an idea what's going wrong.
If there is an encoding issue with a password, then you may not be
able to connect to the database at all, and there might not be a
practical way to know what is going wrong, let alone correct it.
I guess the big picture answer is that I need to know the CCSID of the
target system/job/user and set up a specific ACS session with matching
CCSID.
The whole reason OP started this thread was that they couldn't create
a working FTP session from their PC command line. Nothing at all to do
with ACS or indeed any 5250 emulation whatsoever.
The desired connection is to PUB400, so most likely nothing critical
if it doesn't work. And the problem isn't insurmountable in any case.
But if they had a business requirement to get it working, it may well
be more expedient to use a less trouble-prone password than to jump
through the hoops that would be necessary to get it working with the
'@'-containing password. (For some shops, the hoops wouldn't be much
of an issue. If Python is allowed from the PC, for example, it would
be quite easy. But some places might not have, or might not know they
can get, easy solutions from that angle.)
John Y.
midrange.com
