Hello Skid,
It is bad form to ask a question on a public forum then send private messages to people. If you have a question, then ask it in your public post.
Message From: Skid Minix
is there a way to tell if the client is 32 or 64 bit? The client version is 9.2 LTS.
The MQ Client for Windows includes both the 32-bit and 64-bit releases of the DLL stub (aka Library) which is stated in the link above that I gave you.
Did you set the LIB environment variable to the correct path as per section 3 bullet point 1 from the web page I gave you above?
later
Roger
------------------------------
Roger Lacroix
CTO
Capitalware Inc.
London ON Canada
https://capitalware.com------------------------------
Original Message:
Sent: Fri March 04, 2022 02:12 PM
From: Roger Lacroix
Subject: application issuing the call to MQCONN
Hi Skid,
I agree with Luc, it looks like you did not pick the right DLL stub (aka library).
You should review the information on the following page in the MQ Knowledge Center:
Preparing COBOL programs in Windows
It covers various COBOL compilers on Windows.
Finally, you need to determine what CPU architecture that you are compiling and linking your COBOL program for. i.e. 32-bit vs 64-bit.
Hope that helps.
later
Roger
------------------------------
Roger Lacroix
CTO
Capitalware Inc.
London ON Canada
https://capitalware.com
Original Message:
Sent: Thu March 03, 2022 03:43 PM
From: Luc-Michel Demey
Subject: application issuing the call to MQCONN
Message From: Skid MinixHi Luc, thanks for the follow up, I also have another question from the programmer trying to run a program to perform a connection from an MQ client to a Windows MQ queue manager, I verified he has all of the access needed. Here is what he is asking and seeing. He has configured the client connection channel to the queue manager in his env. variables. I do not see any errors on the queue manager side.Error:I'm trying to link the COBOL program to the MQ Client. When I run "cbllink EP163CBL.obj mqiccb.lib" I receive "fatal error LNK1113: invalid machine type".
It looks like a bitness problem.
Was the module accidentally compiled in 64-bit, with a 32-bit MQ Client machine?
------------------------------
Luc-Michel Demey
DEMEY CONSULTING
lmd@demey-consulting.fr
#IBMChampion
Original Message:
Sent: Mon February 28, 2022 04:14 PM
From: Luc-Michel Demey
Subject: application issuing the call to MQCONN
2012 means: MQRC_ENVIRONMENT_ERROR
I think the Microfocus application was compiled to use MQServer and not MQ Client.
The application must be linked to the MQ Client ddl and not to the MQServer dll.
HTH, LMD.
------------------------------
Luc-Michel Demey
DEMEY CONSULTING
lmd@demey-consulting.fr
Original Message:
Sent: Mon February 28, 2022 12:04 PM
From: Skid Minix
Subject: application issuing the call to MQCONN
I have a programmer trying to run a process and connect to WIndows MQ server, the server he is using has the MQ client installed and his program is executed from a DB2 command window and when he attempts the connection he receiver this error:
The call returns a COMPCODE of 02 and a REASON code of 2012.
Also he performed some research and found this online in reference to DB2:
I did a little Googling and found the environment error could be caused by the application issuing the call to MQCONN is running in a DB2 Stored Procedure address space. Stored Procedures wishing to use the MQ RRS adapter must run in a DB2 WLM-managed Stored Procedure address space.
My program is executed from a DB2 command window. I don't know if that qualifies as a DB2 Stored Procedure address space, but could that be the cause?
Also this is what he is trying to accomplish:
I'm trying to connect using a Micro Focus COBOL program. The program executes a call to 'MQCONN'. The call returns a COMPCODE of 02 and a REASON code of 2012.
------------------------------
Skid Minix
------------------------------