Problem with identifying screen on mainframe after changing machines.

[Ed__Bailey]

Hi

I have a mainframe automation that I have built and support. Its been working fine for many years. I have recently changed my support machine from a VM to a desktop and had the software reinstalled but I now cant get my new machine to recognise the mainframe screens. The reason for this seems to be a difference in the Class Name attribute value

If I respy the main window of the mainframe emulator on my new machine this is showing as AfxOleControl140 but the value from when I built the process - and for all the machines using this automation in Production its AfxOleControl90.

I'd like to know what it is that determines this value?

[bridgetoneill · Accepted solution]

Hi Ed,

From first glance, it looks like the change from 'AfxOleControl90' to 'AfxOleControl140' is likely due to differences between the environments, with your desktop using a newer Microsoft library/runtime.

If the automation needs to work across VMs and desktops, i'd reccomend either:

• Using a wildcard value to replace the version number
• Or, select a different attribute that remains static across environments.

Hope this helps!

Thanks,

Bridget

[naveed_raza]

Hi Ed,

you can add wildcard action after Control if last numbers are changing.

for Mainframe automation , you can install IBM Personal communication software and in Blueprism you can use Mainframe automation category instead of using Win32 

[Ed__Bailey]

Thanks. That makes a lot of sense and is a useful suggestion regarding the wildcard