<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic A Character not working with the Mainframe interface in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/A-Character-not-working-with-the-Mainframe-interface/m-p/78336#M30377</link>
    <description>I thought I would share a recent internal discussion between Blue Prism consultants.

One of my colleagues could not send specific keystroke to a Mainframe emulator using our built in hllapi interface:

Firstly - if you are having issues with the Mainframe interface, make sure you have read your Mainframe Automation guide on the portal first.  Sending keystrokes to a mainframe are slightly different, you either just us a write stage for sending text, or you use a navigate stage with global send keys to send control keys (such as @E or {ENTER} for sending enter).

If there is a specific key that you are unable to send it is most likely the cause of how the hllapi interface has been implemented on the mainframe itself - all that Blue Prism does is wrap that standard interface.  You will have two potential options to send the problem keystroke:

1. Create a second Win32 windows interface just for attaching to the mainframe and sending that one keystroke.  I had a problem sending the £ symbol once and this is the technique I used.  Every time my object detected some text containing the £ symbol needed to be sent it called my second windows object to send the £ symbol using Global Send Keys.

2. Your other option is to play around with the keyboard mapping within the mainframe emulator itself.  Some mainframes have a feature that allows you to map a characcter to a different keyboard key - so simply map the problem key to a different keyboard key that you are not using and experiment with sending that keystroke.</description>
    <pubDate>Thu, 25 Feb 2016 14:02:00 GMT</pubDate>
    <dc:creator>Denis__Dennehy</dc:creator>
    <dc:date>2016-02-25T14:02:00Z</dc:date>
    <item>
      <title>A Character not working with the Mainframe interface</title>
      <link>https://community.blueprism.com/t5/Product-Forum/A-Character-not-working-with-the-Mainframe-interface/m-p/78336#M30377</link>
      <description>I thought I would share a recent internal discussion between Blue Prism consultants.

One of my colleagues could not send specific keystroke to a Mainframe emulator using our built in hllapi interface:

Firstly - if you are having issues with the Mainframe interface, make sure you have read your Mainframe Automation guide on the portal first.  Sending keystrokes to a mainframe are slightly different, you either just us a write stage for sending text, or you use a navigate stage with global send keys to send control keys (such as @E or {ENTER} for sending enter).

If there is a specific key that you are unable to send it is most likely the cause of how the hllapi interface has been implemented on the mainframe itself - all that Blue Prism does is wrap that standard interface.  You will have two potential options to send the problem keystroke:

1. Create a second Win32 windows interface just for attaching to the mainframe and sending that one keystroke.  I had a problem sending the £ symbol once and this is the technique I used.  Every time my object detected some text containing the £ symbol needed to be sent it called my second windows object to send the £ symbol using Global Send Keys.

2. Your other option is to play around with the keyboard mapping within the mainframe emulator itself.  Some mainframes have a feature that allows you to map a characcter to a different keyboard key - so simply map the problem key to a different keyboard key that you are not using and experiment with sending that keystroke.</description>
      <pubDate>Thu, 25 Feb 2016 14:02:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/A-Character-not-working-with-the-Mainframe-interface/m-p/78336#M30377</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2016-02-25T14:02:00Z</dc:date>
    </item>
  </channel>
</rss>

