X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A42F3844026 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1617715031; bh=Tj9ZNJM0ukEYEYlxHAjI+YqlRFxWwV9NBaoCiwOVEpE=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=jnDaa2NDGFX3OyUPBfLVogNDNcT6cI1/e3RFay/FGz1gDrIJAmkXWx8UE+Kw7YDph djTHu/T6EgEzMVCv+bCBz5j2tAeEWBEM6KOZcRqO+HKN3Tjnkkh/sduxa9CDu+p4SA KKRTkzKEaWM9vbzuaF7yWRc3/g1JEEfbcWoxXwh0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7CBD93846035 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=i0gJMkqB78oBWCwnp6j+iQSKhbel0Tf8YVxA4DfbUwU=; b=P3ALAyVfapcMmJh8IU1zdoY0nwXEYjR97BBwD18nCFUtGiqauOOG7ltzJ7WCMhUwDs asHNTvowbGqhgExeZ+9z0QjQCRfKWOR5/NuWf/EyYueQOEIkfcDMAHHEncyobVB5RvV/ grNd5Cpeey3YKEMaO4chn8INC1zAdI3Pr/Q5AOqLQkwJ5rn6C7pojs+XJ1znGEo94yrP XFjm1dFzXO98ag81XU2MIpS0GknVd27mjrZVqpijZa9DdmzVgFLvkXH86aq68WSap8az NuQo1FFQbcHYeKC1JtnrPcyisg7ev8G4jMM5Z9pS9Yg8vyQdDRShSrkjhrWXrNg1J+6l iX7w== X-Gm-Message-State: AOAM531WQnkdrASgYnWDM5LQZEiiTStEmqly2zfUS/z4pD7Xn3jTkp1Y yLSUjsksFgRtvFeijGxhO/YuS2k/wywECbSM9G79hY9Qd3I= X-Google-Smtp-Source: ABdhPJzi4IOiGUjNBn5v84rwG6jFY22SwAIYpM9pmDG6veypnvhNRaJbn3Hpfjc6uYHeCyQ97aScEqvgqw1TlS2xV+w= X-Received: by 2002:a17:906:4e82:: with SMTP id v2mr16502335eju.128.1617715027524; Tue, 06 Apr 2021 06:17:07 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 6 Apr 2021 15:16:56 +0200 Message-ID: Subject: IBM MQ client application fails on latest cygwin To: cygwin AT cygwin DOT com X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: =?utf-8?q?Morten_Kj=C3=A6rulff_via_Cygwin?= Reply-To: =?UTF-8?Q?Morten_Kj=C3=A6rulff?= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" Hi, Came back from easter vacation today and updated my cygwin installation. I havn't touched my PC since March 26. 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? /Morten -- 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