The Session ID is really the Short Name Session Identifier in BlueZone. You can find it under the Options Menu under API, and then under Short Name Session Identifier. It will always be A-Z.

One of my coworkers discovered a simple workaround for this.  He created a new BlueZone session using one of the valid IDs (A-Z) and it worked.  The only issue with this is we will need to make sure that the BlueZone sessions that exist on client machines follow same naming convention since it seems that at our organization they are setup with S1, S2, etc.  That is an entirely separate issue that can't be solved here.

S1 is the Session Name - not the Short Name.  Normally, you will see the Short Name assigned in the status bar at the bottom.  Often this is left to be auto assigned, which can cause issues with hooking the correct session.

I made it work by saving up a BZ session prior to calling it from the automation. It worked for me.

But,now that I am using the Generic WinHLLapi adapter for Bluezone I am stuck with few issues:

1. Unlike Mainframe terminals (used to demonstrate Text adapters in the webinar session) the Bluezone terminal has no defined map for the screen , and hence no dedicated field space neither any fixed matching values. The whole sreen is dynamic and is editable. So, what should be the best way to grab the field values.

2. The HLLapi Start method is not working and throwing me errors. I have attached the snaps here.