Hi folks,
I have debugged this a bit further, and it appears that my SSHD is
also behaving strangely.
If I connect to port 22 I can see the SSH-version string (you know,
the "SSH-2.0-OpenSSH_8.4p1 Debian-5" equivalent) - but it is sent in
EBCDIC!
I can also see the connection closed with the message "Protocol
mismatch", also in EBCDIC - of course it would since the z/OS SSHD
server would be getting absolute gibberish from its point of view.
If I try to login to my CBDQDISP as the user "" I see the same in
the logs - that it registered an attempt to login as "".
I am pretty sure I am to blame for this in my journey to level up my
sysprog skills, but I have no idea what I could have done to enable an
"extra" EBCDIC/ASCII conversion.
Any ideas?
Regards,
On Wed, May 12, 2021 at 7:17 PM Christian Svensson wrote:
>
> Hi folks,
>
> I am playing a bit with CBDQDISP and trying to get it to run with HCM for
> z/OS.
> I tried using the SYS1.PROCLIB(CBDQDISP) and SYS1.SAMPLIB(CBDQDISJ), the
> latter while adding SYS1.SAMPLIB to APF (lab system, so no harm done security
> wise).
>
> The issue I am having is that when connecting with HCM (trying with user-ID
> "TEST") I get the following error in SDSF:
> CBDG983I CBDQTDIS -- start-agent request for user ( received
> CBDG985I CBDQTDIS -- HCM validation for client user id <( > failed
>
> On HCM I receive the following error on HCM: https://imgur.com/RO0rRIv.
>
> Are the error messages simply missing an EBCDIC conversion and something else
> is the issue, or am I missing something crucial with the communication?
>
> Regards,
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
