On a 9.2TS2M3 EBI, we ran across a similar issue caused by some invisible characters sequence (<Tab> ?) trailing the Group Names in metadata :   eg. somethinhg like    IdentityGroup@Name = MyUserGroup<TAB>   Our group bulk loading script in metadata was buggy somehow since it didn't filter out enough the Name value (coming from some Datasets not properly cleaned, I guess).  ... View more

We use both. Generally speaking, it depends upon your SLA: if the SAS platform is for mission-critical tasks or is qualified for High Availability (strict downtime rules etc.) then I suggest choosing network drives which can better fit such needs whereas local drive obviously wouldn't. Another point to consider is extensibility and scalability : local drives are expensive to upgrade and to increase once installed; you must be absolutely sure that the workload (more users and/or bigger data) won't increase so much during the next few years; this is a strong assumption.  Network drives, on the other hand, must also be specified carefully : if the storage system (eg fiber channel interface, router, SAN) is too much shared - especially with no Service Class or priority rules applicable - then the I/O performance for the SAS server may sometimes hugely vary even to the point of bottlenecks (think of multi-tenant storage heavily shared with third systems mission critical like payment/credit computations in a bank : better isolated then than put together !) . Third and last point : operating cost. Even today, SSD for business class servers remain costly, so that it might be cheaper to buy a simple "share" of SAN capacity (LUNs spread on a mix of > 50% SSD, for instance).  ... View more

Hi Kurt,   We've been asked almost the same thing, namely to lauch stored process reports using SAS Add-In.   The following ports required to be opened between the PC and the SAS server(s) (standards 9.4 ports : adapt to your own specs accordingly) :   SAS metadata server : 8561   SASApp server : 8591 #workspace initial session   SASApp server : 8601, 8611, 8621, 8631 # stored process ports   Check also with the SAS EG log files that there aren't any DNS resolution issues between the PC network and the servers :   https://support.sas.com/kb/17/730.html   https://support.sas.com/kb/55/414.html   ... View more

It depends which ones :   1. so called "platform" or infrastructure services like Metadata server, Midtier Web AppServer etc.   or   2. user sessions which comprises :       2.1 . interactive sessions launched by a SAS PC client like SAS Enterprise Guide, Enterprise Miner, SAS Studio etc.      2.2 interactive shared server sessions : Stored Process sessions, Web Report Studio, VA LASR sessions   or even   3. SAS batch sessions     For real-time monitoring and reporting as well of user & batchs sessions, UK based SAS partner Boemska has developed a promising tool named  ESM standing for Enterprise Session Monitor. Have a look :   http://boemskats.com/esm/   Worth its price (not free but definitely worthy of attention !)   There is also some technical API provided by SAS. Chris Hemedinger from SAS has given a very useful sample code to display some kind of running sessions (2.1).   http://blogs.sas.com/content/sasdummy/2016/02/15/using-proc-iomoperate/   As mentioned previously, platform servers (case 1.) are monitored using SAS Environment Manager.     ... View more

@ucvikas wrote: Dear experts,   I am using SAS 9.4 + SAS management consol 9.4 I have below specific questions.   1. How to create metadata libraries in batch mode . For example If my end user needs a library then I have to create that in SAS management consol manually , I want to do that by using some code where I just pass required details and its done , instead of point and click in management consol. This is called Registering a Library in the SAS metadata server. I am not aware of any handy code or API/pre-built tool to register a new Library. If you're not afraid of coding and maintaining OMI XML requests then you may try this example :   https://support.sas.com/documentation/cdl/en/omaref/59983/HTML/default/viewer.htm#addobj.htm   Registering a new library is tricky : to be actionable , the library must be assigned to a SAS server (Application Context like SASApp). Then , there is a uniqueness constraint in the metadata server that requires that 'Library names must be unique within a SAS Application Server' :   https://support.sas.com/documentation/cdl/en/bisag/64088/HTML/default/viewer.htm#a003139364.htm  (point no. 4)   Therefore, you must code some request& existence test routine to be run before trying to create a new library (the uniqueness rule applies mercilessly and generates orphans libraries objects named 'Copy Of <LIBRARY>').   In addition to this, the library once registered must be populated with tables (that means, references of tables)  which, fortunately can be done quite easily using Proc METALIB :   https://support.sas.com/documentation/cdl/en/lrmeta/67971/HTML/default/viewer.htm#p1cqb9ofazns8pn1by7t2smnimsf.htm   As other members have mentioned, another way to go would be to give access to your users team - ast least to some Data Steward among them - in order to perform the manual tasks themselves. The SMC is not the only tool to register a Library.    Since you are using SAS 9.4 client/server, you might have SAS Environment Manager already deployed. This comes with a new Web console Admin (a handful of SMC plugins have been put on-line) called the EVM Admin ; the Library Module works exactly like the SMC Data Library Manager plug-in :   https://support.sas.com/documentation/cdl/en/evadmug/68379/HTML/default/p0rgl1rwibcrc3n1kxys3aa3n3b9.htm     The EVM Admin console can be accessed within the Web Environment Manager application or directly using this adress :   HTTP(s)://<sas root URL or MidTier Hostname):7980/SASEnvironmentMgrMidTier   The following permissions are required to register a new library :   access to capability : Management Console 9.4:/Plug-ins/Data Library Manager SASApp server context authorization (through an ACT) : +RM,+WM       ... View more

We have some experience with NIS authentication on RHEL 5/6 servers. The following page describes at length the NIS protocol :   http://www.yolinux.com/TUTORIALS/NIS.html   see also https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/nis.html   Strictly speaking, NIS/Yellow Page does not require PAM as far as I know. Implementation amongst Linux/Unix flavours may vary, of course. I only know Linux Red Hat in this respect. With RHEL, NIS works independenly of PAM which looks like a centralized identity provider :   https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Smart_Cards/PAM_Configuration_Files.html   NIS impersonates authentication requests to the local host (/etc/passwd, /etc/groups, shadow etc.) and thus enables to use transparently a central identity directory. Applications that need to launch authentication calls to Linux/Unix host stack don't have to be modified.   By default, SAS Unix/Linux authentication proxies (a SAS process remotely launched for a SAS Studio terminal rely on the so called SAS Object Spawner daemon, which in turn uses authentication proxies) use local host authentication, with the methods=pw as shown above.   If in your case, the server also uses PAM then you'll have to modify the sasauth.cfg file accordingly and restart all SAS services (even the Metadata Server) to take it into account.   Take care at the GROUP_NO_CASE parameter , if your NIS accounts have secondary group memberships, the authentication request made on behalf of SAS proxy could not retrieve the Primary group correctly sometimes.  This happens also when the cache is active (NSCD daemon running).   To go further with SAS authentication on Unix/Linux :   https://support.sas.com/kb/15/231.html    https://support.sas.com/resources/papers/proceedings14/SAS111-2014.pdf ... View more

To be sure, SAS EG 6/7 can be installed in two ways :   1. using SAS Deployment Wizard and a SASDepot   2. with SAS EG independent installation package (~ MSI format ) See. appendix A in the reference below :   https://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/default/user.pdf   SAS EG independent installer can be found inside the SASDepot itself :   <SAS Depot root folder>\standalone_installs\   Either ways no. 1 & 2 can use silent installs with Response properties but neither (officially) can invoke environment variables storing installation paths, or something approaching which would answer your need like for instance :   SET SYS_VAR_HOME=<choose one> setup.exe -install %SYS_VAR_SASHOME%    Usage no. 2 requires only one path (SAS_HOME) in its response properties. I suppose usage no. 1 also requires the SAS licence path.  Of course, you could also try to script some shell launcher that dynamically creates a disposable response.properties for each installation, taking the install path(s) as parameters , broadly like :   launcher_install_sas_eg.cmd, PS1 etc. <SAS_HOME>   :: launcher script :: create response.properties echo SAS_HOME=%1% > ...\response.properties echo SAS_EG_MODE=32-bit >  ...\response.properties echo LANGUAGE_SELECTION=en etc. > ...\response.properties :: run SAS installer based on previous response.properties setup.exe -install ...\response.properties   ... View more

The security reporting macros in 9.2 as far as I can remember do not provide with such details about ACT.    To do this job, SAS does provide another API  which goes by the sweet name of "Data Step Functions for Metadata Security Administration" :   https://support.sas.com/documentation/cdl/en/lrmeta/60739/HTML/default/a003121439.htm   Using this tools, you shall be able to build comprehensive reports as regards ACT list & scope (objects, permissions etc.).  Ths might be tedious if you're not very familiar with this kind of coding, which rarely happens from my experience. I succeeded once in 2011/2012 to enroll a seasoned coder with this, & I must say he remained the only one of his kind I know on a large portion of the entire SAS world (perhaps until today !).   Metacoda ACT plugin is the way to go if you haven't much time to code from scratch.      ... View more