Dan Kimmel wrote:
Check the QHST logs (DSPLOG). If a connection is refused, it'll
usually be logged there. Lots of stuff to look through there, so know
the time of the request within a few seconds.

Our contractor finally got back to me with a date and time when he made several attempts to connect: Monday, October 15, 2012 at 12:58:10 AM PDT

Looking at a WRKTCPSTS for ports 9000-9999 at 08:59 PDT, I see:
Local Port Idle Time
9004 +++++++++
9005 +++++++++
9006 +++++++++
as-cent > +++++++++
as-data > 132:57:52
as-dtaq-s +++++++++
as-file-s +++++++++
as-netp > +++++++++
as-rmtc > +++++++++
as-sign > 007:59:08
which, I'm guessing, appears to fit with an unsuccessful secured JDBC connection at the time specified, but when I do a DSPLOG, I don't see much of anything out of the ordinary, anywhere near that timeframe (only the names have been changed, to protect the innocent):
Job 251914/FOO/WTCPCHILDM ended on 10/15/12 at 00:45:55; .059 seconds used; Job 251923/QPGMR/WTCPVERIFY started on 10/15/12 at 00:46:16 in subsystem QBAS
Job 251924/FOO/WTCPCHILDM started on 10/15/12 at 00:46:17 in subsystem QBASE
Job 251923/QPGMR/WTCPVERIFY ended on 10/15/12 at 00:46:18; .016 seconds used;
Job 251925/BAR4/WTPOLLGGC started on 10/15/12 at 00:49:35 in subsystem QBASE
Job 251925/BAR4/WTPOLLGGC ended on 10/15/12 at 00:49:35; .027 seconds used; Job 251926/BAR4/WTPOLLGGC started on 10/15/12 at 00:54:35 in subsystem QBASE
Job 251926/BAR4/WTPOLLGGC ended on 10/15/12 at 00:54:35; .028 seconds used; Job 251927/BAR4/WTPOLLGGC started on 10/15/12 at 00:59:35 in subsystem QBASE
Job 251927/BAR4/WTPOLLGGC ended on 10/15/12 at 00:59:35; .027 seconds used; Job 251924/FOO/WTCPCHILDM ended on 10/15/12 at 01:00:00; .047 seconds used; Job 251928/QPGMR/WTCPVERIFY started on 10/15/12 at 01:01:19 in subsystem QBAS
Job 251929/BAR4/WTCPCHILDM started on 10/15/12 at 01:01:20 in subsystem QBAS
Job 251928/QPGMR/WTCPVERIFY ended on 10/15/12 at 01:01:21; .016 seconds used;
Job 251930/BAR4/WTPOLLGGC started on 10/15/12 at 01:04:35 in subsystem QBASE
Job 251930/BAR4/WTPOLLGGC ended on 10/15/12 at 01:04:35; .027 seconds used; Job 251931/QPGMR/WTCPVERIFY started on 10/15/12 at 01:09:06 in subsystem QBAS
Job 251932/WTANON/WTCPCHILDM started on 10/15/12 at 01:09:07 in subsystem QBA
Job 251931/QPGMR/WTCPVERIFY ended on 10/15/12 at 01:09:08; .016 seconds used;
Job 251932/WTANON/WTCPCHILDM ended on 10/15/12 at 01:09:09; .019 seconds used
Job 251933/QPGMR/WTCPVERIFY started on 10/15/12 at 01:09:15 in subsystem QBAS
Job 251934/FROBOZZ/WTCPCHILDM started on 10/15/12 at 01:09:17 in subsystem Q
Job 251933/QPGMR/WTCPVERIFY ended on 10/15/12 at 01:09:17; .016 seconds used;
Job 251935/QPGMR/WTCPVERIFY started on 10/15/12 at 01:09:26 in subsystem QBAS
Job 251936/BAR4/WTCPCHILD started on 10/15/12 at 01:09:29 in subsystem QBASE
Job 251935/QPGMR/WTCPVERIFY ended on 10/15/12 at 01:09:29; .016 seconds used;
Job 251937/BAR4/WTPOLLGGC started on 10/15/12 at 01:09:35 in subsystem QBASE
Job 251937/BAR4/WTPOLLGGC ended on 10/15/12 at 01:09:35; .027 seconds used; Job 251938/FROBOZZ/WTPOLLGGC started on 10/15/12 at 01:09:36 in subsystem QB
Job 251938/FROBOZZ/WTPOLLGGC ended on 10/15/12 at 01:09:36; .027 seconds use
*SIGNON server job 251796/QUSER/QZSOSIGN processing request for user FOO on User FOO from client connected to job 251391/QUSER/QZDASOINIT *SIGNON server job 251796/QUSER/QZSOSIGN processing request for user FOO on User FOO from client connected to job 251391/QUSER/QZDASOINIT
all but the last four of which are jobs starting and ending in our own proprietary servers (and those last four are well after the specified time). It doesn't even show anything to tie into what I see in the idle time on the one port.

Is there some system value that I need to be changed, for rejected connections to show up in the history log? Does this tell me something I simply don't understand?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.