×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Rob,
So I would have to turn on auditing for SNDDST, SNDNETSPLF, and any other command(s) that require a directory entry.
Audit for a few weeks, months, then review the QAUDITCD entries selecting those commands.
From that I could see which users are calling SNDDST, SNDNETSPLF, etc.
Not 100%, but a good start.
Am I on the right track?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, September 09, 2016 9:38 AM
To: Midrange Systems Technical Discussion
Subject: Re: Directory Entry ussage
See the section "Setting up security auditing"
at
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzarl/rzarlusesecjnl.htm
Not sure if it will tell you what parameters were actually used in the commands like SNDDST. But it should tell you the job, program, etc.
I keep thinking there are other things which use that. I don't think it's used for NetServer or anything like that.
WRKFLR
CPF9006 - User not enrolled in system distribution directory.
Easy. Stop using QDLS.
Rob Berendt
midrange.com
