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 <[email protected]> On Behalf Of David Crayford Sent: Sunday, February 28, 2021 6:25 PM To: [email protected] 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 <[email protected]> On > Behalf Of Michael Babcock > Sent: Saturday, February 27, 2021 8:02 PM > To: [email protected] > 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 <[email protected]> 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 [email protected] <mailto:[email protected]> >> git-receive-pack lbdyck/qtab.git I get this: >> >> >> >> >> --ÄÁ---Ä--Ã----Ã-À--ÄÂÂ--Á-/ÄÁ-------À----/--ÊÁÃËÇÁ/ÀË_/ËÈÁÊÊÁø?ÊÈ-ËÈ >> / ÈÍË-ÊÁ ø?ÊÈ-ËÈ/ÈÍË-Î--ÀÁ%ÁÈÁ-ÊÁÃË-ËÑÀÁ-Â/>À---,-ÉÍÑÁÈ-/È?_ÑÄ-?à >> >> Ë-ÀÁ%È/-øÍËÇ-?øÈÑ?>Ë-?¦ÁÄÈ-Ã?Ê_/È-ËÇ/--/ÅÁ>È-ÅÑÈÅÑÈÇÍÂ-Å-ÃÃ-Ä/À----- >> - >> ---- >> >> >> >> >> If I do the same ssh [email protected] <mailto:[email protected]> >> 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 [email protected] 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 [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
