IBM Mainframe Forum

Hi,

One of our user is not able to connect to the mainframe session. We use the hummingbird software to connect the mainframe session.it shows that the user is authenticated by the firewall and IP is connected, but the mainframe session is not popping up. Can anyone please guide me. Please let me know if i can provide you more information. Apologies if it is out of mainframe scope.

There are many possible problems here -- it could be an emulator setting that is wrong (such as pointing to the wrong port for the mainframe session or attempting to use a terminal model not supported by the mainframe), mainframe TCP/IP not set up correctly, the network not passing data correctly ...

Your best bet is probably to start by taking an emulator that does connect to the mainframe and compare settings, one by one, until you find a difference or find that they all match. If that doesn't find anything, contact your site support group and work with them to get a TCP/IP trace going to determine how the mainframe sees the session connect request.

Hello,

One of our user is not able to connect to the mainframe session.

Has this user ever successfully connected to the mainframe or is this a new user? From their own terminal? Can they connect from some other terminal with their own id?

Yes the user is new. the user was authenticated for that site. When he clicks the emulator, he gets the message saying that the IP is successfully connected. Unfortunately the mainframe windows does'n pops up. From my perspective it should not be the case of a firewall issue. In our environment we dont use the IBM personal communication instead we use the hummingbird to connect the mainframe session.

Hello,

Hummingbird works correctly everywhere i've ever seen it. . . Do all of your users use Hummingbird?

Can this user connect to the mainframe using some other terminal?

From my perspective, i can think of 3 things to consider:
1. there is somthing wrong with this user's hummingbird configuration.
2. there is something wrong with this userid on the mainframe.
3. there is something wrong with the vtam interface.

All of these will need to be checked out by you and/or your support people.

Can you log onto the mainframe with your own id using the problem terminal?