×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello,
Am 30.05.2023 um 15:31 schrieb tim ken <timk2574@xxxxxxxxx>:
2) for the Variable characters which can be used in identifier (for the
mentioned IBM docs link) what exact changes should be done in the whole
keyboard mapping file( https://code.midrange.com/8dadee7174.html) to bypass
the errors caused by '@' character in the password here?
As said earlier, do not use "special" chars which are prone to translation due to different code points in different CCSIDs. Period. Peter Dow gave you small table.
Change your password over the correctly working Mocha to something without the @ sign. Problem solved.
If this answer doesn't satisfy your demand, you're probably on your own. If you think recycling passwords is a good idea: it's not. I have no other idea why you insist on an @ character in your password.
If you still insist on having this @ sign, that's what I would do:
- Change my password to something comprised entirely from characters and digits.
- Run dspjob, take option 2 and note down the CCSID.
- Sign off, close session.
- Change settings in Mocha and and iACS accordingly. If Mocha doesn't support the given CCSID (e. g. 1140 for Germany, use a compatible one: 273). Compatibility of CCSID is documented on the IBM website. Use Google.
- Sign on again.
- Set password with the desired @.
Should now work even with ssh and ftp.
If not, change your password again to something without the @ sign. Problem solved.
Ah, and btw. saying "thank you all for helping" doesn't hurt.
:wq! PoC
midrange.com
