Re: No new SSL-telnet connections

On 10-Nov-2015 11:24 -0600, James Rich wrote:

On Mon, 9 Nov 2015, James Rich wrote:

I've got a bit of a puzzle here. Existing SSL telnet connections
work fine, but trying to start a new SSL telnet connection either
doesn't work at all, or in one case, took 20 minutes to connect.
I've checked that the certificates are ok and both the CA
certificate and the server certificate are ok until next year.
Firewall isn't the problem as this is occurring over the LAN as
well, plus as I mentioned, existing SSL telnet connections are
working just fine. Any ideas where I should look?

A little more information on this puzzle. Suddenly SSL connections
are working, with no apparent changes at all. Nothing was restarted,
no error messages ever logged. But for nearly 24 hours new SSL
connections either wouldn't start at all or would be extremely slow
to start. Doing a NETSTAT revealed that the iSeries was receiving
bytes from the client but showed zero bytes sent. We are still
scratching our heads over this. We don't know why it stopped working
or why it suddenly started working. The one oddity is that many of
the new connections are now coming in under QCTL instead of QINTER.
Any more thoughts?

Seems like there might [have been] a device allocation issue specific to a defaulted initial allocation by QINTER, and now the Work Station Entry (WSE) allocation is successful via an alternate specification; perhaps there is a generic Work Station [name] (WRKSTN) or Work Station Type (WRKSTNTYPE) specification under the QCTL subsystem enabled for AT(*SIGNON). Maybe there is a TELNET exit program or QAUTOVRT exit program involved? Although clarified nothing suspicious with virtual display devices, what about controllers?; See: wrkcfgsts *ctl *vws

Perhaps a review the joblogs of the QCMNARB## [QCMNARB03?] system jobs and the QINTER SBS [monitor] job, plus a review of the history log since some time prior to noticing any issues might prove fruitful?