BookmarkSubscribeRSS Feed
jakarman
Barite | Level 11

Having  user groups as of regular reporting analysts developers on the same system you should segregate.  Explain why not using different Saswork file systems for each group.

When a member in a group is needing more resources and could block others those are his Co workers. Let them sort out what they are find the most important.

That cartesian product is an issue that should not happen with regular usage as that should have been validated at acceptance testing. Monitoring on the os level by techies is only disturbing. The process is using a lot of cpu ...alert. That situation can be quite normal with Sas.  Filling up work quickly (spool in dbms). It can be quite normal. The only requirement

of the business is their normal operational like processing should proceed without too much problems.

When someone is filling work quickly and having a good IO system you are most likely never in time to do the right decision. Or is the fill up will cause an abend the cleaning of work is already done. It doesn't help to schedule the cleanwork every hour. Lost space should only be create by abends that are not able to close gracefully.  Do not use " kill -9 pid " by default.

---->-- ja karman --<-----

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

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.

Discussion stats
  • 15 replies
  • 4238 views
  • 1 like
  • 7 in conversation