If the i is only receiving connections, you could change its IP and
subnet, and use a distro like pfSense to transparently NAT the ports, it's
logging facilities are a lot easier to use. You might break stuff like
passive FTP though...

On Fri, 26 Mar 2021 at 13:48, Rob Berendt <rob@xxxxxxxxx> wrote:

There's also this:

https://www.ibm.com/support/pages/logging-all-connections-system-specific-port-or-ip-address


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim
Franz
Sent: Friday, March 26, 2021 11:26 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Log connections from other servers

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


In a large corporate environment, need a way to create a simple log of
connections to the IBM i. Most are either connecting to stored procedures,
or direct sql calls (OLE DB, ODBC, JDBC). This is a legacy system for
historical data - and many of these connections have existed for 10 or more
years. No docs exist, and the people on Win/Unix have all changed...
Was looking at comm trace - but i need to keep this log for next month or
so, as some traffic is EOM only or day or two after.
Need IP address or domain name, and timestamp, user (would be nice)
Would be nice to have sql stmts but i know that gets into specific
protocols.
No $$ to spend.
There is a 2nd Power i that maintains a connection (development server).
No an option to shut down and see who squeals.
Solution may be comm trace, but how to manage?
tia
Jim Franz
W.R. Berkley
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.