It appears that on one of my z/OS 2.4 systems I don't have this ssh issue but on another I do. The difference is that one has a /etc/ssh/zos_ssh_config file and the one that fails does not. Updating the /etc/ssh/zos_ssh_config file thus fixed the problem:
Change from: ChannelConvert shell to: ChannelConvert shell,exec _____________________________________________________________________________ Lionel B Dyck <sdg>< Website: www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -----Original Message----- From: lbd...@gmail.com <lbd...@gmail.com> Sent: Monday, March 1, 2021 8:11 PM To: 'IBM Mainframe Discussion List' <IBM-MAIN@LISTSERV.UA.EDU> Subject: RE: z/OS ssh git issue I tried that forum over a month ago - I will do so once again. _____________________________________________________________________________ Lionel B Dyck <sdg>< Website: www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of David Crayford Sent: Monday, March 1, 2021 8:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS ssh git issue Can post on the Rocket Software open source forum with all the details from this thread. I don't think it's a Git problem as ssh also has the issue which is not part of ported tools. The forum is well monitored and the open source tools team are very helpful. I will give Vladimir Ein a heads up. On 1/03/2021 9:00 pm, Lionel B Dyck wrote: > That is exactly what I have which is why this is baffling .... ☹ > > ______________________________________________________________________ > _______ > Lionel B Dyck <sdg>< > Website: www.lbdsoftware.com > > "Worry more about your character than your reputation. Character is > what you are, reputation merely what others think you are." - John > Wooden > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Jousma, David > Sent: Monday, March 1, 2021 6:58 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS ssh git issue > > I know you responded back with the TAG ENV vars. Here are all of mine > that are set in GITENV.sh > > # ASCII support environment values > export _BPXK_AUTOCVT='ON' > export _CEE_RUNOPTS="FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)" > export _TAG_REDIR_ERR=txt > export _TAG_REDIR_IN=txt > export _TAG_REDIR_OUT=txt > > > > ______________________________________________________________________ > _______________________________ > Dave Jousma > AVP | Director, Technology Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > Rapids, MI 49546 > 616.653.8429 | fax: 616.653.2717 > > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Lionel B Dyck > Sent: Monday, March 1, 2021 6:03 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS ssh git issue > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > They are set. > > _TAG_REDIR_IN=txt > _TAG_REDIR_OUT=txt > _TAG_REDIR_ERR=txt > > Thanks for the suggestion. Now you can see why we are baffled. > > ______________________________________________________________________ > _______ > Lionel B Dyck <sdg>< > Website: www.lbdsoftware.com > > "Worry more about your character than your reputation. Character is > what you are, reputation merely what others think you are." - John > Wooden > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of David Crayford > Sent: Sunday, February 28, 2021 6:25 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS ssh git issue > > Make sure you also have the following set: > > export _TAG_REDIR_ERR=txt > export _TAG_REDIR_IN=txt > export _TAG_REDIR_OUT=txt > > > On 28/02/2021 10:45 pm, Lionel B Dyck wrote: >> I have in the environment on this system and on the working systems. >> >> _BPXK_AUTOCVT=ON >> _CEE_RUNOPTS=FILETAG(AUTOCVT,AUTOTAG) POSIX(ON) >> >> And I'm not sure which files you are asking about being tagged? >> >> My ssh keys are untagged if that is your question - the same as on my >> working system. >> >> _____________________________________________________________________ >> _ >> _______ >> Lionel B Dyck <sdg>< >> Website: www.lbdsoftware.com >> >> "Worry more about your character than your reputation. Character is >> what you are, reputation merely what others think you are." - John >> Wooden >> >> -----Original Message----- >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On >> Behalf Of Michael Babcock >> Sent: Saturday, February 27, 2021 8:02 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: z/OS ssh git issue >> >> Is AUTOCONVERT turned on in USS? And the files are tagged? >> >> On Sat, Feb 27, 2021 at 2:24 PM Lionel B Dyck <lbd...@gmail.com> wrote: >> >>> I’m having an issue on a test lpar with git for z/OS – both version >>> 2.14 and the latest 2.26 ports. >>> >>> >>> >>> I’ve looked at this as have several others without success. >>> >>> >>> >>> When I attempt a git clone I get this error: >>> >>> >>> >>> fatal: protocol error: bad line length character: ---Á >>> >>> >>> >>> When I do a ssh g...@github.com <mailto:g...@github.com> >>> git-receive-pack lbdyck/qtab.git I get this: >>> >>> >>> >>> >>> --ÄÁ---Ä--Ã----Ã-À--ÄÂÂ--Á-/ÄÁ-------À----/--ÊÁÃËÇÁ/ÀË_/ËÈÁÊÊÁø?ÊÈ-Ë >>> È / ÈÍË-ÊÁ ø?ÊÈ-ËÈ/ÈÍË-Î--ÀÁ%ÁÈÁ-ÊÁÃË-ËÑÀÁ-Â/>À---,-ÉÍÑÁÈ-/È?_ÑÄ-?à >>> >>> Ë-ÀÁ%È/-øÍËÇ-?øÈÑ?>Ë-?¦ÁÄÈ-Ã?Ê_/È-ËÇ/--/ÅÁ>È-ÅÑÈÅÑÈÇÍÂ-Å-ÃÃ-Ä/À---- >>> - >>> - >>> ---- >>> >>> >>> >>> >>> If I do the same ssh g...@github.com <mailto:g...@github.com> >>> git-receive-pack lbdyck/qtab.git on one of my other systems it looks >>> like >>> this: >>> >>> >>> >>> 00ce342c27f0363f6d24cbb68e8ace7454218d4828a2 >>> refs/heads/masterreport-status >>> report-status-v2 delete-refs side-band-64k quiet atomic >>> >>> ofs-delta push-options object-format=sha1 >>> agent=git/github-g2ff1cad44179 >>> >>> >>> >>> >>> We’ve looked at the TCP/IP setup, the SSH setup, and the Git setup >>> with no joy. We’ve also confirmed that the ssh public key has been >>> properly added to github. >>> >>> >>> >>> Can anyone provide any suggestions that will help resolve this? >>> >>> >>> >>> Thank you >>> >>> >>> >>> >>> >>> _____________________________________________ >>> _ >>> _ >>> ______ >>> ________________________ >>> >>> Lionel B Dyck <sdg>< >>> >>> Website: <http://www.lbdsoftware.com/> www.lbdsoftware.com >>> >>> >>> >>> "Worry more about your character than your reputation. Character is >>> what you are, reputation merely what others think you are." - John >>> Wooden >>> >>> >>> >>> >>> -------------------------------------------------------------------- >>> - >>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO >>> IBM-MAIN >>> >> -- >> Michael Babcock >> OneMain Financial >> z/OS Systems Programmer, Lead >> >> --------------------------------------------------------------------- >> - For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO >> IBM-MAIN >> >> --------------------------------------------------------------------- >> - For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO >> IBM-MAIN > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message was > misdirected. After replying, please erase it from your computer system. Your > assistance in correcting this error is appreciated. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
