X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD9A7394741E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1617884793;
	bh=aPsCBQLc3NNaXsa00xE7QSQE9K88UzfGraU6CklCbLw=;
	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=WwstbRx0BhAWjZjNELQNQNoZLqFbeI+I/ugQFEN5ZVrqJueLws9lluOtplfP/Tz4K
	 pbCxgvw27HGc6iTPdv0IoE+quvjoIRqqFqfkF3+f2Gia0xYkrlgrGgKxm5ZwI1qW1u
	 btWmu+ZETHZk5PL8LD5Ug0YNLVAvzw07rujEgGPM=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E09F03945C2C
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com 138CPv2s008760
X-Nifty-SrcIP: [124.155.50.190]
Date: Thu, 8 Apr 2021 21:25:59 +0900
To: cygwin AT cygwin DOT com
Subject: Re: IBM MQ client application fails on latest cygwin
Message-Id: <20210408212559.bfa088414864757d8c7dc19d@nifty.ne.jp>
In-Reply-To: <20210408201600.9f70ffa0b828a785e70a891c@nifty.ne.jp>
References: <CA+7cx1p2BNhah1wNB2gNPVDR6y6eXD44ALFaUhjcinJuVOFWRw AT mail DOT gmail DOT com>
 <20210406233716 DOT 003ba116ca61f99632bb4dce AT nifty DOT ne DOT jp>
 <CA+7cx1o-Npm_ne8v+EB1QfCYPEZ4GB4dJSn3bQozEMm9pK4RgQ AT mail DOT gmail DOT com>
 <20210407195624 DOT d77b7459cbdd63504ea495d4 AT nifty DOT ne DOT jp>
 <20210407200441 DOT 860d8b421bf7d29d1e32a6ea AT nifty DOT ne DOT jp>
 <CA+7cx1rN2pkwV0P=jLQWKcuAU5hcvAgzsCD5si-wn4uk+fDthg AT mail DOT gmail DOT com>
 <20210408201600 DOT 9f70ffa0b828a785e70a891c AT nifty DOT ne DOT jp>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-4.2 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 138CQZ6j026714

On Thu, 8 Apr 2021 20:16:00 +0900
Takashi Yano wrote:
> On Thu, 8 Apr 2021 08:04:26 +0200
> Morten Kjærulff wrote:
> > On Wed, Apr 7, 2021 at 1:04 PM Takashi Yano wrote:
> > >
> > > On Wed, 7 Apr 2021 19:56:24 +0900
> > > Takashi Yano wrote:
> > > > On Wed, 7 Apr 2021 11:32:59 +0200
> > > > Morten Kjærulff wrote:
> > > > > On Tue, Apr 6, 2021 at 4:37 PM Takashi Yano wrote:
> > > > > >
> > > > > > On Tue, 6 Apr 2021 15:16:56 +0200
> > > > > > Morten Kjærulff wrote:
> > > > > > > When I run it from a windows command prompt, it works fine.
> > > > > >
> > > > > > In this case, did you run MQ client from cygwin shell
> > > > > > in command prompt? Or run it in cmd.exe?
> > > > >
> > > > > what works is:
> > > > > cmd.exe->bash->script->non-cygwin-mq-client.exe
> > > > >
> > > > > what fails is:
> > > > > cmd.exe->bash->mintty->bash->script->non-cygwin-mq-client.exe
> > > > >
> > > > > also fails:
> > > > > cmd.exe->bash->mintty->bash
> > > > > and then
> > > > > cmd /c bash -c 'script' # script->non-cygwin-mq-client.exe
> > > >
> > > > Thnaks for the report.
> > > >
> > > > What about:
> > > > mintty->cmd /c bash->non-cygwin-mq-client.exe ?
> > >
> > > Do you mean your script starting mq-client by "script" ?
> > > I meant /usr/bin/script by "script".
> > >
> > > > > cmd.exe->bash->script->non-cygwin-mq-client.exe
> > >
> > > If so, what about:
> > > cmd.exe->bash->/usr/bin/script->(your script)->non-cygwin-mq-client.exe ?
> > >
> > > --
> > > Takashi Yano
> > 
> > Hi,
> > 
> > I cooked the issue down to this.
> > 
> > My script:
> > $ cat tmq.sh
> > #!/bin/sh
> > 
> > export MQSERVER='BROWSE/TCP/mvs1(1414)'
> > amqsbcgc Q
> > 
> > amqsbcgc is a sample that comes with MQ:
> > $ which amqsbcgc
> > /cygdrive/c/Program Files/IBM/WebSphere MQ/tools/c/samples/bin64/amqsbcgc
> > 
> > It is a C program:
> > $ head /cygdrive/c/Program\ Files/IBM/WebSphere\ MQ/tools/c/Samples/amqsbcg0.c
> > /* @(#) MQMBID sn=p800-008-171121 su=_A5OAkM6qEeemCpCOEyy4yA
> > pn=samples/c/amqsbcg0.c */
> > /**********************************************************************/
> > /*                                                                    */
> > /* Program name: AMQSBCG0                                             */
> > /*                                                                    */
> > /* Description : Sample program to read and output the message        */
> > /*                 descriptor fields, any other message properties    */
> > /*                 and the message content of all the messages on a   */
> > /*                 queue                                              */
> > /*   <copyright                                                       */
> > 
> > When I run it from a bash prompt, started with cmd.exe->bash.exe, I
> > see correct output (2085 means Q not found, which means that we are
> > connected ok):
> > $ ./tmq.sh
> > 
> > AMQSBCG0 - starts here
> > **********************
> > 
> >  MQOPEN - 'Q'
> >  MQOPEN failed with CompCode:2, Reason:2085
> >  MQDISC
> > 
> > If I start mintty, I see:
> > $ ./tmq.sh
> > 
> > AMQSBCG0 - starts here
> > **********************
> > 
> >  MQCONNX failed with CompCode:2, Reason:2539
> > 
> > I also see errors at the server side, which means that some sort of
> > connection has been made, but it seems to be garbled.
> > 
> > When we are "under" mintty it does not matter how I call amqsbcgc, it
> > always fails, here is one example:
> > 
> > $ ./tmq.sh
> > 
> > AMQSBCG0 - starts here
> > **********************
> > 
> >  MQCONNX failed with CompCode:2, Reason:2539
> > 
> > $ cmd
> > Microsoft Windows [Version 10.0.17763.1817]
> > (c) 2018 Microsoft Corporation. Alle rettigheder forbeholdes.

Ah, you are using Win10 1809. Then the pseudo console should be
supported.

> > C:\mhome\mqadm>set MQSERVER=BROWSE/TCP/mvs1(1414)
> > set MQSERVER=BROWSE/TCP/mvs1(1414)
> > 
> > C:\mhome\mqadm>amqsbcgc Q
> > amqsbcgc Q
> > 
> > AMQSBCG0 - starts here
> > **********************
> > 
> >  MQCONNX failed with CompCode:2, Reason:2539
> 
> In the log above in cmd, input command are echoed twice.
> This happens when the pseudo console is not activated. Are you
> using Win7 or old Win10? Or do you set CYGWIN=disable_pcon by
> any chance?
> 
> If you set CYGWIN=disable_pcon, please try unset it.

Probably you set CYGWIN=disable_pcon in .bashrc or elsewhere.
Please try to unset it.

-- 
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