Skip to main content

Problems connecting to the mainframe in upgraded .Net application

  • April 20, 2018
  • 4 replies
  • 0 views
D

We have a Visual Basic 6 screen scraping application that was running in windows XP that I recently upgraded to VB.net running in Windows 7.  I have Rumba 9.5 running on my workstation and I am using the WdMFDsp.Ocx from that version in my new code with the same parameters as in the old code.  When I step through the .Net code, the pop form for the telnet does not appear and there is no connection to our mainframe.  I am using Visual Studio 2017 Community version.   Any suggestions on how I would resolve this?

Thank you.


#Rumba

4 replies

André Escudero

We have a Visual Basic 6 screen scraping application that was running in windows XP that I recently upgraded to VB.net running in Windows 7.  I have Rumba 9.5 running on my workstation and I am using the WdMFDsp.Ocx from that version in my new code with the same parameters as in the old code.  When I step through the .Net code, the pop form for the telnet does not appear and there is no connection to our mainframe.  I am using Visual Studio 2017 Community version.   Any suggestions on how I would resolve this?

Thank you.


#Rumba

Are you receiving any error message  /stack trace ?
Does it work when you manually configure a rumba mainframe session ?

I tested RUMBA 9.5 SP1 with VS 2017 Community Edition  and it works as expected

Can you try and apply SP1 ?

D

We have a Visual Basic 6 screen scraping application that was running in windows XP that I recently upgraded to VB.net running in Windows 7.  I have Rumba 9.5 running on my workstation and I am using the WdMFDsp.Ocx from that version in my new code with the same parameters as in the old code.  When I step through the .Net code, the pop form for the telnet does not appear and there is no connection to our mainframe.  I am using Visual Studio 2017 Community version.   Any suggestions on how I would resolve this?

Thank you.


#Rumba

I am not receiving any error messages.  This is the screen I am getting which is not our main frame screen:

Here is my Host Interface Configuration:

It may take me a while to get SP 1 so I hope we can figure it out using what I have.

Thanks for your help.

André Escudero

We have a Visual Basic 6 screen scraping application that was running in windows XP that I recently upgraded to VB.net running in Windows 7.  I have Rumba 9.5 running on my workstation and I am using the WdMFDsp.Ocx from that version in my new code with the same parameters as in the old code.  When I step through the .Net code, the pop form for the telnet does not appear and there is no connection to our mainframe.  I am using Visual Studio 2017 Community version.   Any suggestions on how I would resolve this?

Thank you.


#Rumba

Your screenshot shows a connection to the rumba demo host.
Try to set the the connection in your code.

MFDsp.HostInterface.Name = "WallData.TN3270Link"                            'Sets Telnet Interface
MFDsp.HostInterface.Interface.InsertName2("yourhost.com")                 'Insert Host Address
MFDsp.HostInterface.StartupModelType = 2                                           'Model 2

MFDsp.Connect()

D

We have a Visual Basic 6 screen scraping application that was running in windows XP that I recently upgraded to VB.net running in Windows 7.  I have Rumba 9.5 running on my workstation and I am using the WdMFDsp.Ocx from that version in my new code with the same parameters as in the old code.  When I step through the .Net code, the pop form for the telnet does not appear and there is no connection to our mainframe.  I am using Visual Studio 2017 Community version.   Any suggestions on how I would resolve this?

Thank you.


#Rumba
Thank you for your help. Adding the 1st and 3rd statement resolved my problem.

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement