QAUDJRN should record system _audit_ events against QDLS, just like anywhere else in the IFS. However, I _think_ that QAOSDIAJRN might be more what's wanted.

Of course, the strong recommendation from pretty much everywhere is to move away from QDLS.

Tom

In addition to the Navigator interface, QDLS (Document Library System) object authority can be managed using DLO (Document Library Object) commands.  

from a green-screen command line to view the available DLO commands.  Put your cursor on any command and press F1 for a description of the command.

Also, to expand on what Tom said:

The QDLS file system is slow compared to the root file system and QOpenSys, plus it has DOS file name limitations, and requires registration in the system distribution directory in order to use it.  It is a good idea to avoid using QDLS unless your applications leave you no choice.

- Gary Patterson

Check out my EE profile: https://www.experts-exchange.com/M_4382324.html

>  It is a good idea to avoid using QDLS unless your applications leave you no choice.

Gary's detail brings up thoughts for me of 'potential' future problems. Note that "applications" might even mean a PC operating system. It is within possibility that /QDLS shares might become incompatible with Windows networking.

After Windows 2000, Microsoft networking has become less and less compatible with the file server protocols. Each new Windows release (as well as one or two service packs within some releases) has brought connectivity issues. Microsoft patches and IBM PTFs have mostly kept things working, but either could choose to stabilize and to stop fixing things in the future.

Even if fixes keep coming out, they might come slowly enough to cause business interruptions.

Moving away from /QDLS early may avoid the need to do it on very short notice.

Tom