X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9BEE8384402F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1617719115;
	bh=zRTqsDRN1DcrPq+5ut1G9uZVAwoCVI8UwA8oLy76pxE=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=Dl6l5ZFMKfQNV4y9OknJ34cJ8lIqRu63E0MNn11GurwgAkEjx2ZWAIVVEVV8BgL5+
	 aztxCUbk/NZWuwgvnXhKGOgHlNgte0q10nDOi4I9Eti5GwrpHs46Klhv2/O++wNlqw
	 IlacrJFkC/vyXelz+G1ZwjVCYwK0v2m6xCo73dWw=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0F4793857816
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 136EOkno005836
X-Nifty-SrcIP: [124.155.50.190]
Date: Tue, 6 Apr 2021 23:24:49 +0900
To: cygwin AT cygwin DOT com
Subject: Re: IBM MQ client application fails on latest cygwin
Message-Id: <20210406232449.5c90771b8f9a8c684e9871db@nifty.ne.jp>
In-Reply-To: <CA+7cx1p2BNhah1wNB2gNPVDR6y6eXD44ALFaUhjcinJuVOFWRw@mail.gmail.com>
References: <CA+7cx1p2BNhah1wNB2gNPVDR6y6eXD44ALFaUhjcinJuVOFWRw AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 136EPIrj022841

On Tue, 6 Apr 2021 15:16:56 +0200
Morten Kjærulff wrote:
> I have a non-cygwin IBM MQSeries client application which I call from
> a script. It connects to my z/OS MQ server.
> 
> When I run it from a windows command prompt, it works fine.
> 
> When I run it from mintty, it fails in a strange way.
> On my PC I see
> 2539 (09EB) (RC2539): MQRC_CHANNEL_CONFIG_ERROR
> On z/OS I see
> CSQX575E QMGR CSQXRESP Negotiation failed for channel
> CSQX228E QMGR CSQXRESP Listener unable to start channel,
> channel ????
> TRPTYPE=TCP INDISP=QMGR
> So it seems some garbage has been sent.
> 
> Installing old versions of mintty gives the same result.
> 
> Installing an old version of cygwin seems to resolve the issue:
> 3.2.0-1 fail
> 3.1.7-1 fine
> 
> How can I help?

Could you please try the followings and let me know
the results?

1) Execute 'cmd /c bash' in mintty and run MQ clint.
2) Run cygwin in command prompt and execute 'script', then run MQ client.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple