This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Additional Audit entries for Netserver authentication and access
Would like to have additional Netserver authentication, connection and IFS file access events posted to QAUDJRN.
Our company uses several IFS shares and would like a reliable way of capturing Netserver authentication, connection and IFS file access information on a continuous basis. I attempted to use the QAUDJRN's VC & VN entries but found that that the entries are no longer written to the audit journal. I know we can query QAUDJRN for OM entries for IFS file access/changes but it would be nice to have all these types of events under a Netserver or IFS auditing group.
I was able to use this query to capture IP connection information for SMB ports: SELECT CONNECTION_TYPE, REMOTE_ADDRESS, LOCAL_ADDRESS, lOCAL_PORT, PROTOCOL, TCP_STATE, IDLE_TIME
FROM QSYS2.NETSTAT_INFO WHERE LOCAL_PORT IN ('139','445')
Also, the GO NETS option 15 gives us the information we need; however, it is purely interactive and doesn't allow us to create an outfile or spoolfile. Capturing these events for syslog RFC format would be a plus.
Do not place IBM confidential, company confidential, or personal information into any field.