Gunnar, there are a lot of logfiles and even more can be configured. Having many of those you have to manage them. Saving in those managing costs it mostly ends in not being traceable auditable. At start of the objectspawner you will find the information it reads from the metadata using a metdataserver connection. Runnig an objectspawner for very lang time you can lose those startup messages. (rollover by day) The metadataserver (service process) will generate its own logging. When it is on the same server (machine/os) you can find it aside that of the objectspawner. The metadataserver can be located on his own machine (very advisable). Every SAS proces could generate the ARM logging as configured by APM/eventmanager. Seeing those one you have the owner (the process it has been run by) and the contents events. The best thing would be to audit the SAS metadata. The SMC is no storage location although often being told by SAS sales, but just a handy tool to manage the SAS metadata. With a well defined metadata security there is room for audit level (read access for all) with na access to run real processes. That kind of requirement altough rather sensible is a rather difficult one at SAS institute guys. How far do you need to go for your reviewing?
... View more
