I'm looking for some information on how we might customize the batch log location by user. We have a fairly large installation and scheduled work flows use the default $BATCh_LOGPATH unless each job is customized at time of scheduling. That works....but it is a bit of a pain and is subject to being reset by accidental clicks.
Hi,
my first approach for what you need, would to to create new BatchServers, each batch server with a new default log directory.
If you have different departments due to a big SAS environment, I would go even one step further: to create different SASApps for each department, which would provide good independency and security for departments from each other.
Some other option, and under the supposition you use LSF/Platform Computing for the scheduling. If that is the case, you could try to use Global Variables in the Process Manager to set up the log directories per department.
Regards,
Juan
We have what I would consider to be a fairly large (300+ users) grid environment across 10 or so different departments. Many of the users automate their processes by creating Flows in Management Console schedule manager. When trying to troubleshoot, it is sometimes difficult to find the right log file when all of the logs get put in the same location ($BATCH_LOGPATH).
The path can be changed manually (a minor pain in itself) when adding a job to a flow, but an accidental click resets the location to $BATCH_LOGPATH.
I'm looking for how to set the $BATCH_LOGPATH variable by user so that the logs can be segregated by department.
Hi,
my first approach for what you need, would to to create new BatchServers, each batch server with a new default log directory.
If you have different departments due to a big SAS environment, I would go even one step further: to create different SASApps for each department, which would provide good independency and security for departments from each other.
Some other option, and under the supposition you use LSF/Platform Computing for the scheduling. If that is the case, you could try to use Global Variables in the Process Manager to set up the log directories per department.
Regards,
Juan
Thanks...I'll forward this to the admins for evaluation.
I think they are going to look at setting $BATCH_LOGPATH different for the different users.
Sounds good. Thanks for the feedback
Indeed, setting up different SASApps is a major architectural decision. Just pointed up to the functional requirement regarding department variables and security.
Let me specify that the information provided it is just an overview of options.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.