MQSeries.net :: View topic - Cannot Connect after Mirate from 5.3 to 6.0

belchman

Hello All,

I am looking for some breadcrumbs here. I am at a loss.

I have a JCL job that could connect to qmgr and do puts/gets prior to upgrade but now it won't connect. I get a 2059. I am the MQ admin doing the upgrade. The z/OS mq admin left the company and I am trying to pick up the slack. My strength is on the distributed side.

Can someone pose any ideas as to why I now get a 2059?

I was thinking maybe MQA1 is no longer the default QMgr but I do not know if this is relevant on z/OS. If it is, how do I set MQA1 as default?

Overview

MQA1CHIN and MQA1MSTR are running

Here is the JCL that gets 2059

//QAEGW01P EXEC PGM=MQPMONQP,REGION=1024K,
// PARM=('MQA1,TEST,1,*,1,N')
//STEPLIB DD DSN=MY.LOD,DISP=SHR
// DD DSN=MY.SCSQAUTH,DISP=SHR
// DD DSN=SYS1.SCSQAUTH,DISP=SHR
// DD DSN=SYS1.SCEERUN,DISP=SHR
//SYSDBOUT DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//*

MQPMONQP is a COBOL LE program. With above PARM, it should put 1 1-byte non-persistent message containing '*' to TEST queue.

Here is the output

===========================================
PARAMETERS PASSED :
QMGR - MQA1
QNAME - TEST
NUMMSGS - 000000001
PADCHAR - *
MSGLENGTH - 000000001
PERSISTENCE - N
===========================================
================================================
MQCONN
COMPLETION CODE : 000000002
REASON CODE : 000002059
===============================================*

Any ideas would be appreciated.