Re: How to do FTP using TN5250 Mochasoft

Hi,


I have also noticed one strange thing that password with special characters
(more than one) is also being accepted inside IBM i ACS but if it's set
with these special characters then by using the same password I can't login
to MOCHASOFT and if it's set like this( with more than one special
characters in the password) inside Mochasoft then it can't be used while
trying to login to IBM i ACS . And in both of these cases I get the same
error ("CPF1120-CPF1120-User does not exist
or password not correct for user profile".)


Thanks.

On Sat, 3 Jun 2023 at 15:47, tim ken <timk2574@xxxxxxxxx> wrote:

Hi,


Just for more clarification :-

1) I just changed Host Code Page value to '273 Germany' whereas inside
Mochasoft DSPJOB -option 2 CCSID values were like this :- "Country or
region identifier . . . . . . . . . . : US
Coded character set identifier . . . . . . . . . : 273
Default coded character set identifier . . . . . : 273
Character identifier control . . . . . . . . . . : *JOBCCSID"

my question is just by making changes here in IBM i ACS for this Host Code
Page value to '273 Germany' here I was able to bypass that earlier
authentication error from IBM i ACS ("CPF1120-CPF1120-User does not exist
or password not correct for user profile.) and could login successfully to
IBM i ACS (to pub400.com )with the password which has '@' character in.
Also I can login successfully through other ways as well like FTP,SSH, VS
Code,FileZilla without changing any of their settings separately so by just
changing this 'Host Code Page' value inside this IBM i ACS what does is
change for other channels(FTP,SSH,VS Code, Filezilla) settings
automatically without changing any of these channel's settings individually?


2) Since I was able to change my password inside Mochasoft by inserting
some other special characters apart from '@' so i tried to login to IBM
iACS with this changed password but this again started giving that old
CPF1120 error and I could not login to 'pub400.com' through other
channels ( VS Code, FTP,SSH,FileZilla) as well with this changed password
as they started giving their own set of errors like mentioned in my
previous posts.

My assumption is that whatever password I could set inside Mochasoft for '
pub400.com', the same I should be able to use if I try to login through
IBM i ACS,VS Code, FTP,SSH,Filezilla etc. for 'pub400.com'. If my
assumption is true then what should be my one time change inside this Host
Code Page value for IBM i ACS or any other such change somewhere else ?

Earlier I responded like " I tried changing codePage=273 in IBMi.kmp for
IBM i ACS and also changed it under communication- configure- host code
page - 273 Germany. and then tried various ports as well like 23,992,2222
but each time I got the same error here." I am not sure why I am not
getting this error now and password with '@' character is being accepted
through all the channels for this 'pub400.com' without any such
authentication errors.



Thanks






So My question here is if the Host Code Page value '273 Germany' for IBM
i ACS Could handle this single '@' special character in the password

On Wed, May 31, 2023, 17:50 tim ken <timk2574@xxxxxxxxx> wrote:

Hi,

1) After changing Host code page in IBM i ACS as per DSPJOB option 2 in
mochasoft it's getting connected with password '@' as well through all the
channels (filezilla just gave status 'Status: Server does not support
non-ASCII characters.'
in between the connecting process but got connected.)

So by just changing this IBM i VS Code Host page value, what changes were
made in VS Code ,FTP, SSH and FileZilla settings automatically (without
changing each of these separately) which helped to bypass this
authentication hurdle this time?

2) I just tried making the password a little more complex by adding a few
more special characters along with '@' but now the same error is appearing
so what changes in this Host code page or somewhere ( or somewhere else
like keyboard mapping file) else should be done to accommodate all these
extra special characters here?


Thanks.



On Wed, 31 May 2023 at 13:35, Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Peter,

Am 31.05.2023 um 01:23 schrieb Peter Dow <petercdow@xxxxxxxxx>:

Tim mentioned changing the configuration for iACS to ccsid 273 and

reported that it still failed. I'm not sure if that's because iACS ignored
the configuration value, or needed to be restarted after the change, or
what.

Probably because the OP set the password with an already mismatched
CCSID, thus garbling up things completely.

:wq! PoC

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.