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.
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 ]
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.
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