*
The moose likes Websphere and the fly likes error 2033 on mq mvs/esa Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "error 2033 on mq mvs/esa" Watch "error 2033 on mq mvs/esa" New topic
Author

error 2033 on mq mvs/esa

Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2053
I have a servlet to connect via mq to mainframe.

I am getting null returned. Nothing was logged in my mainframe log, so I guess it never reached the mainframe.

This is the first time for my system to connect to mainframe via mq.

Anyone familiar with this error?
Scott Selikoff
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3704
    
    5

How are you making the connection and/or which API are you using? If the mainframe didn't logging statements (and the mainframe is reliable) it is likely the problem is on the client side so I would experiment more with the establishment of the connection.

One general debugging tip, never try to do too much at first. Try the simplest "Hello World"-style application for the connection and get that working first.


My Blog: Down Home Country Coding with Scott Selikoff
Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2053
Yes, I used a simple hello mainframe program.

How do I conclude that the mainframe program is reliable? I tested it by executing a cics transaction and called the simple hello mainframe program, using Link, and it went well. I am confident therefore that the mainframe side is okay. Anything else I should do in the mainframe side?

The mq queue names, and other details are provided by the system administrators.

They provided us with some java classes, that does the mq stuff. The codes of those are not provided; only sample codes on how to use them.
[ November 22, 2005: Message edited by: Jesus Angeles ]
Scott Selikoff
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3704
    
    5

Are you publishing to an active service or a messaging queue? Ergo, is this a synchronis or a-synchronis call?

As for checking the server, depends how much access you have to it. It sounds you have limited access, so I'm not sure how you can check other than running your client in debugging mode and watching the data.
Brian Hennessy
Ranch Hand

Joined: Oct 24, 2005
Posts: 57
How many qmanagers are in the picture here.

On your java side are you connecting to a queue manager running on a local machine/or a deployed app on WAS either of which has a queue manager communicating to a queue manager running on the mainframe. Could you post the servlet code of the method in which you tried to establish a connection to the qmanager in the classes supplied to you ?

Also are there any RACF/MCA user ids needed in a channel/connection between the two queue managers(assuming 2 queue managers are being used).

Are there any messages hitting your queue manager running on windoz/aix which your servlet sends the messages to

Are you checking your apps CICs logs or the mainframes MQ logs, from TSO
sd a ENTER

then look for MQ jobs

pre MQ* ENTER

you may be able to see other MQ errors here
Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
MQ Series return code 2033 is: "NO_MSG_AVAILAIBE".

This is in response to a GET, correct?

The CONN and OPEN calls complete OK, correct?

My guess is you are trying to GET a message from a Queue, but there is nothing on the queue ..........

Regards, Guy
Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2053
Thanks, I appreciate the replies.

It is okay now.

What happened is that this project started long time ago. And the queues were defined long time ago. Somewhere during that long time, it got expired, disabled, or something like that.

It took only 1 call to the system administrator.

By the way, it is synchronous.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: error 2033 on mq mvs/esa