Thank you for your response! For connecting to ssl3270.nccourts.org, we turn on the SSL/TLS option in the TN3270 app. I'm not familiar with the CLI options to offer a correction, if one is necessary. I understand you're saying that TCP connections can "tear" when an app is suspended. The strange thing is that the TN3270 app is otherwise stable until our app is installed. Our customer needs both apps working simultaneously, and it's difficult to tell them "that's just how the protocol works" in this situation. Not saying you're wrong, you obviously know much more about this than we do. Just stating the difficult spot we're in. I'll read your article to learn more! I will give your idea of a test connection app a try! It might help us see what's happening from the other app's perspective. Thank you!

@DTS Engineer Our customer noticed that if they have the iPad in a state where TN3270 is disconnecting when suspended, allowing the device to auto-lock will allow TN3270 to maintain a connection when suspended. Get the device in a state where TN3270 disconnects when suspended. Close the TN3270 app (and any other apps that would prevent auto-lock) Allow the device to auto-lock Unlock the device TN3270 will now maintain a connection even when suspended or used with EpochField. This behavior persists until the device is restarted. Would you have any idea why auto-locking the device would affect how the kernel decides if a connection gets defuncted? Maybe garbage collection or some other resource optimization routine? Is there anything we can do in the EpochField app to influence whether the TN3270 TCP connection is maintained? Would we be able to invoke, directly or indirectly, the same routine or process involved with the auto-lock workaround? (I know that's a long shot but I have to ask!)

FYI: I will be out of the office on vacation starting 5PM Mountain on 8/8, returning Monday 8/18. I'll respond to any updates when I'm back. Thanks again!

We were able to work with the developer of the MochaSoft TN3270 app to resolve this issue. Ultimately this had nothing to do with EpochField, as we were able to replicate the behavior without EpochField installed. Thank you for your help!