MVSFORUMS.com

[Shankarganesh_gopal]

Hi all,

I need to clarify a question.

We are facing a error 2085 (Mq unknown object) while trying to call MQPUT1. I searched the entire website, but couldn't able to find a valid reason. All the link says that we might not have given the queue name properly. How this could be? The same MQ was running fine all other time and only during between some specific intervals, we are receiving this error message.

I suspect that this issue could be because of MQ connection lost and when we try to call MQPUT1, it is giving trouble.

Can some one throw some light on this issue?

Thanks a ton.
Shankar.

[dbzTHEdinosauer]

My experience with 2085's:

1. MVS-z/OS mainframe
2. Ran under RRS - DB2 & MQS
3. Batch job ran 24/7
4. made the connect & open only one time at BOJ (begining of job)
5. performing MQGET's
6. Performed a ROLLBACK and went EOJ
7. error routine interrogated OBJ handle and name to insure they were valid
   1. if valid assumed MQS was brought down to force EOJ and created non-critical EOJ
   2. if invalid created critical EOJ

In any case, job was automatically restarted and failure to connect was considered critical EOJ, thus no automatic restart.

Never attempted to re-connect, more than likely operators wanted the system to come down. Anyway, job was automatically restarted after only 1 critical, not after two. Operation's people wanted it that way, and it was easier and required no programmer intervention until 3rd critical EOJ
_________________
Dick Brenholtz
American living in Varel, Germany

[dbzTHEdinosauer]

MQPUT1 & GET1 are a combination of CONNECT/OPEN/PUT or GET.

I would say that your guess is correct:

1. either MQS is down
2. the QUEUE is not enabled
3. you are in CICS and the connection was lost

.
Does not matter why.

I hope you have some restart methodology. You need to save the input that triggered the need for a PUT.
_________________
Dick Brenholtz
American living in Varel, Germany

[Shankarganesh_gopal]

Thanks a lot for your valuable suggestion.