Posted: 23 Jun 2020 13:43 EDT Last activity: 23 Jun 2020 17:13 EDT
Changes to TextAdapter connection properties in robotics 19.1
Ever since upgrading our robots from 8.0.2021 to 184.108.40.206 we have been experiencing issues with TextAdapters (specifically PCOMM) and their connection properties. More specifically we are experiencing issues where the TextAdapter is losing it's connection to the mainframe when other running applications (or the user) are using the mainframe connections as well.
So far some combination of setting SerializeWinhllapiAccess and modifying the AdvancedConfiguration (changing session parameters to NWAIT SUPER_WRITE NODISPLAY) of the TextAdapter is providing success, but which changes solve the issue seem to be different for different packages.
Is there any documentation that outlines the changes that were made to how the TextAdapter connects to a mainframe session between 8.0.2021 and 220.127.116.11? We would like to gain a better understanding of what has changed and if we can use the AdvancedConfiguration to get the settings back to the way they used to be.
According to the build notes and the release notes, there haven't been any changes related to the PCOMM adapter specifically. There was a bug resolved in 19.1.17 which seems relevant, but nothing since. I would suggest you pursue this one via a support request as it will likely benefit from someone accessing your machine. If you do open a support request, please record the number here in case any resolution is helpful to the community.
This hotfix resolves an issue that could prevent other applications from using WinHllapi when Pega was using it.