MVSFORUMS.com

hari · Beginner Joined: 16 Dec 2002 Posts: 2 Topics: 1

Is there any way to Cross Check if the Q manager is really down when we get a MQ reason code of 28 which means connection failed because of wrong Q name or Q is down.

Manas Biswal · Posted: Mon Dec 16, 2002 11:39 pm Post subject:

Please give some details on the QM. Is the QM on S/390, NT Server or UNIX. On S/390, we don't get error codes like 28. We get 2058 or 2059 if QM is not available or the QM name is not valid.

Regards,
Manas

hari · Beginner Joined: 16 Dec 2002 Posts: 2 Topics: 1

Thanks! Yes you are right it is 2058 or 2059 Q mangaer not valid or Q manager not available for connection.
I am wondering if there is any other method to make doubly sure the reason code what I am getting is correct before calling System Adminstrator MQ/help desk.
I am working on S390.
Hari

Manas Biswal · Posted: Tue Dec 17, 2002 11:33 pm Post subject:

Hi Hari,

If you have administrative access to the QM installed on your mainframe, then there is no problem at all. You can go to the MQSeries Control Panel(Option M from the main menu in our installation) and check whether the QM is down or up.
If not, then there is nothing else to do but call up your SYS ADMIN. Are you writing your MQ API calls in batch or in the CICS region. In CICS, you don't have to issue a MQCONN call because there is one QM always connected to the CICS region and that is generally started on CICS Initialization. Confirm from your SYSPROG on whether you are using the correct QM or not. (The QM connected with the CICS region).

Regards,
Manas