I’ve never found a great user guide, not to say that one doesn’t exist. You should be able to schedule any type of executable/job like a batch file from using the Platform LSF client tools (packaged with the server tools). You can also use command line executables like bsub and
Author
The data table creation date is sometimes necessary, say in the footnote of your stored process. Included below is a sample to retrieve this date from the file system. /*Open the dataset*/ %let dsid=%sysfunc(open(sashelp.shoes)); data _null_; /*grab the CRDTE function*/ ddate=%sysfunc(attrn(&dsid;,CRDTE )); /*Format in DDMONYY*/ call symput('ddate', put(ddate, dtdate9.)); run;
In SP4, you can export OLAP cubes into .xml files. Right click the Cube from SAS OLAP Cube Studio, select 'Export Cube'. This is an appropriate part of a migration strategy through dev-test-production, since they can then be imported through the 'Import Cube' button on the left menubar.
Three different setups for SAS JMP are listed below. Upwards compatibility (i.e. level 1 to 2) available, downwards less likely (like we know STPs are not). Level 1. SAS JMP and SAS Base installed and licensed on individual desktop/laptop. Level 2. SAS Integration Technologies installed on server, SAS JMP installed
Pausing and restarting the Metadata Server manually will allow you to take a full copy of the foundation file structure. However, the %OMABAKUP macro does this for you, which reduces the metadata server's downtime. (Yes, do not run a manual pause or stop of the metadata server when executing %OMABAKUP)
Check this out:http://support.sas.com/techsup/unotes/SN/020/020072.html “IMPORTANT NOTE: You should NEVER use an Unrestricted User (the "unrestricted user" account; for example, the sasadm ID with a "*" prefix in the adminUsers.txt) to log on to any client application except SAS® Management Console. The "unrestricted user" account is intended to be used ONLY as
Included are some resources to help those of you who need to change SAS account passwords on your BI installation. (Notice: This is not for the faint of heart.) http://support.sas.com/rnd/papers/sugi31/securedeployment.pdf http://support.sas.com/documentation/configuration/bisecag.pdf (Chapter 5 & specifically pg98-102) http://support.sas.com/techsup/technote/ts736.pdf Side Note: SAS Technical Support and R&D; have a utility in their 'toolpool'
There is no good way to migrate MDDBs to V9Cubes. Here is an excerpt from the SAS migration website (http://support.sas.com/rnd/migration/planning/files/mddb.html): “There is no automated method to convert Version 8 MDDB code to SAS 9.1 OLAP code. PROC MDDB executes in SAS 9.1. However, it creates a Version 8 MDDB that
SAS BI-ogsource is now 2 years old! Hope everyone has enjoyed the content over the years. Please feel free to contact me with feedback, suggestions, or even ideas for new posts! BI Weblog Email Address
Overall, query response time dramatically decreases with the use of sets, therefore it is preferred that user selections (or the cube itself) prevents the potential of choosing multiple members within the same dimension. Queries that only included 1 member in the slicer but are still represented as a set are