Create Audit Dataset for users accessing which dataset and library

[Amitkmr1979]

Dear Friends,

I am trying to find which user accessed which dataset in past or create a trace for coming days where I can have a script which gathers this information. 

I cam across a topic where it says to add the logger and appender xml. 

I added the 'logger' and 'appender' to capture it in a SAS Dataset and restarted the dev server.

And ran the below SAS code in DEV Server, but the log dataset I created is empty. 

Also, when I try to test logical stored process server connection it fails with below message:

   <!-- Caution: Do NOT edit or change this appender configuration    (DB Appender changes delete this and logger if issues)    -->
   <appender name="dblog" class="DBAppender">
    <param name="ConnectionString" value="DRIVER=base;CATALOG=base;
       schema=(name=mywork;primarypath='C:\temp');" /> 
    <param name="MaxBufferedEvents" value="300" /> 
    <param name="TableName" value="LOG" /> 
    <!-- The column parameters must be specified in exactly the same order that the columns occur in the table. -->
     <param name="column" value="sn" /> 
     <param name="column" value="d" /> 
     <param name="column" value="c" /> 
	 <param name="column" value="u" /> 
     <param name="column" value="m" /> 
   </appender>

Logger
   <logger name="Audit.Data.DB" additivity="false">
     <appender-ref ref="dblog"/>
	 <level value="Info"/>
   </logger>

[JosvanderVelden]

Before using DBAppender, you must first create the table to which the log events are to be written. The Column parameters must be specified in exactly the same order that the corresponding columns occur in the table. Details in the documentation: https://documentation.sas.com/doc/en/pgmsascdc/v_036/logug/p0w1cv36n6ududn1gnzzkh6h8fr7.htm

[Amitkmr1979]

I did in the same sequence for column parameters, when I spoke to SAS Support they advised stored process is bunch of concurrent processes and assigning a single dataset for all sessions won't help. Awaiting resolution.

[Amitkmr1979]

DDL is as below
libname test "C:\temp";

libname x 'c:\temp';
data x.LOG;
length seqno $10;
length date $24;
length logger $100;
length user $30;
length msg $500;
run;

[Amitkmr1979]

Kindly ignore test libref allocation.