We had a similar incident where we lost our ICC consoles. It took a call into IBM and a complicated procedure to get them back. Afterwards, we received an email which admitted there was a known bug and gave us a work around (unknown when patch would be out). Don't know if this will help you or not. Also, they recommended that Response Mode be turned on if it wasn't already turned on.
Mike Schmutzok Sr Systems Programmer Shands HealthCare =================================== Here is Some Additional Recommendation From Product Engineering on the Console Issue This appears to be a situation that we are aware of. The trace log lists o3270_Client_Listen_Accept_Err... which is an indication that OSC server socket has been shut down. This would explain why the client was not able to connect. We have a work-around for this until we can release a fix. No target for release of fix yet. The workaround for client disconnect, not able to reconnect: Go to the SE Advanced Facilities Edit server configuration, record the TCP port and change by any other value. Validate the panel values, Activate the configuration Edit server configuration, change the TCP port to the original value Validate the panel values, Activate the configuration. This has the effect to restart the server and the sessions should be able to reconnect then. ============================================ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
