<?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 Killing an application… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Mainframe-Attach-after-Process-kill/m-p/50957#M6105</link>
    <description>Killing an application should always be the very last course of action, you should always build in a clean close/exit in the same way that manual users do.&amp;nbsp; For some applications or interfaces killing an application can cause locking or api issues.&amp;nbsp; &amp;nbsp;It sounds like your application has this issue, probably killing the app is impacting the Hllapi interface that Blue Prism is trying to use&amp;nbsp;- I suggest building a clean exit routing/object that keeps pressing whatever the exit keys are for that mainframe (usually a mixture of F3s and/or F12s in my experience - but could be anything, ask an SME), and cleanly exit.&amp;nbsp;&amp;nbsp;</description>
    <pubDate>Fri, 16 Feb 2018 14:17:00 GMT</pubDate>
    <dc:creator>Denis__Dennehy</dc:creator>
    <dc:date>2018-02-16T14:17:00Z</dc:date>
    <item>
      <title>Mainframe Attach after Process kill</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Mainframe-Attach-after-Process-kill/m-p/50956#M6104</link>
      <description>Hi,

&amp;nbsp;

I am restarting Mainframe after using the kill process "Kill pcsws.exe". The whole thing worked fine till now. I am observing a new issue with mainframe attach. the BP fails to attach to proper instance (however it says that&amp;nbsp; it has attached to existing session only). As a result, BP fails to read screens or match the screen or detect anything else on the screen. Any advices please?</description>
      <pubDate>Thu, 15 Feb 2018 17:00:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Mainframe-Attach-after-Process-kill/m-p/50956#M6104</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-02-15T17:00:00Z</dc:date>
    </item>
    <item>
      <title>Killing an application…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Mainframe-Attach-after-Process-kill/m-p/50957#M6105</link>
      <description>Killing an application should always be the very last course of action, you should always build in a clean close/exit in the same way that manual users do.&amp;nbsp; For some applications or interfaces killing an application can cause locking or api issues.&amp;nbsp; &amp;nbsp;It sounds like your application has this issue, probably killing the app is impacting the Hllapi interface that Blue Prism is trying to use&amp;nbsp;- I suggest building a clean exit routing/object that keeps pressing whatever the exit keys are for that mainframe (usually a mixture of F3s and/or F12s in my experience - but could be anything, ask an SME), and cleanly exit.&amp;nbsp;&amp;nbsp;</description>
      <pubDate>Fri, 16 Feb 2018 14:17:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Mainframe-Attach-after-Process-kill/m-p/50957#M6105</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2018-02-16T14:17:00Z</dc:date>
    </item>
  </channel>
</rss>

