Hello @Fredrik_Hansson,   first, this is a post that has tome time already... I would like to know from you... when you arrived to this post, was it google-ing? What are you interested of this post?    Secondly: hpf = High performance forecast (if you google sas hpf you find is as first result) aa = typo, context tells me @LinusH wanted to say "as". it happens to me every time, but we are better than Text Analytics, right" 🙂   Thirst, answering to your question: big data engines that can be used from SAS? Yes, but of course. Just for starters, the most basic base, SAS provides SAS/CONNECT. which enables to create multiple SAS sessions, local or remote, and parallelize jobs and processing. And you have command line access, access to DB drivers and ODBC.  ... View more

Hi all,   i'm able to resolve this issue, Basically the SQL-pass through i mentioned was using the execute query as below which submits the code to database which is having stored procedures and return back the results. All-though its nothing to do with pre-assigned libraries or SQL-pass thru it was probelm with stored procs, So we had same stored procs copied and it worked.   execute executeoraclequery @query =    Thanks. ... View more

I would: stop the Web Application Server, and make sure that no tomcat instance is left running move the file to another place start the Web Application Server Note that stopping/starting the WAS takes quite some time, so get some scheduled downtime for that (unless your situation is already critical and services have stopped working) After that, inspect the file. Start at the end to see if some rapidly repeating pattern caused the size increase. If not, you might contemplate to use SAS to read the log and do statistical analyses to see if a lot of messages were written within a rather short timeframe.   You might find that it was caused by someone trying some kind of brute force attack (intentional or unintentional). This can happen when penetration tests are run by security people.  ... View more

Hi,   From the error I believe its port issue. Can you check and confirm if Hive is configured to same port 10000 and you have opened firewall from SAS to Hadoop environment.  ... View more

Hi, It depends on the database on which port they configured. But by default port for db2 on mainframe would be 50000. I would Suggest to check with your dba on that. ... View more

Adding new posts on the end of old ones is not a good idea. You will get a better response by creating a new post. If you think it would be helpful you can always add a link to the old post.   Please note that what ports you need to open on your SAS servers is dependent on what OS they are running on, what version of SAS you are using, what SAS products are being used, and the architecture of your SAS servers (how many you have of each type). Every SAS server install I've been involved with, a required port list is provided by SAS or the SAS installer. ... View more

DB2 drivers are an IBM specific question, so you would be better off asking that on an IBM specific forum. ... View more

Hi Veenam,   It should go in to compute server, you can copy some where on installation folder by creating separate folders for jars and conf, then copy all Jar and xml files into respective folders. Later you need to make config changes to sasv9_local file and add the paths as below.   -set SAS_HADOOP_JAR_PATH "/path/to/sas/hadoop/jars" -set SAS_HADOOP_CONFIG_PATH "/path/to/sas/hadoop/conf" ... View more

  So, for the SAS dataset migration, there are couple of methods which should work, so I don't want to delve into the merits of each. But I can share a couple experiences from our migration a while back.   Our migration was also from SAS 9.2 on Solaris 10 SPARC to SAS 9.4 on SUSE.   To migrate the datasets (~150TB), we ended up writing a very simple macro that simply assigns a local libname on Solaris and a remote libname on Linux using SAS/Connect. When the users were ready to migrate their data, they simply invoked the macro from Enterprise Guide. This had the following pros and cons:   PROS: - The moment SAS 9.4 creates the dataset on Linux, is already ""converted" to Linux x64 encoding. No export->import, one action and it's done. - You don't need to double up on you disk space on Linux (for packages) since the data goes straight into it end state - We had ~150TB of SAS datasests and didn't have a single issue in terms of compatibility, data loss, data corruption, etc. - It is user driven, The users can decide exactly when they want to migrate as not to disrupt current business processes.   CONS: - It takes long. SAS/Connect is not the fastest engine, but given the benefits we derived from this approach, it didn't matter. If you allow yourself enough time to migrate the data, then you're fine. It's the lastminute.com users that were a problem.   REMEMEBER: - Switch on dataset compression on Linux from day 1. This way all your migrated datasets are compressed from the beginning. - Do not allow users to FTP the data across. They will try and take shortcuts to move the data, but then you land up with Solaris-encoded data on Linux. Although SAS does handle this by means of CEDA, you increase you CPU usage and you cannot update those datasets until converted.   All the best !   ... View more

Hello,   I succeded to solve the problem and bypass the error in step 12.  Here's what I did: When configuring Web server and when the stage 12 is running , I have generated manually the scripts for launching the services sas (sas.servers, sas.servers.mid, sas.servers.pre) by launching the script " generate_boot_scripts.sh ". Step 12 has passed and the installation has ended successfully. I am finalizing the post-installation and it seems to work. I don't have a logical explanation of this until now.   Thanks. ... View more

Hi Woo, If krb5.conf is correctly configured with required KDC then kerberos authentication should work. Can you check basic test with kinit on linux server. ex: kinit userid it prompts for password ... View more

Then, you probably won't need any conversion/migration of the data.   I would give it a chanceto SMU, and, just to be sure, I would align with SAS Technical Support, to ensure that you can SMU from AIX to Linux.   My current expectation is that, some config files and scripts (as the usermods) you will need to change the header from ksh to bash, but I would not expect much more impact than that. ... View more

Login to SMC using unrestricted Access. Click on the + sign for the server context you want to change this, for example SASApp. Right click on the Workspace server for that server context and click properties. Under the options tab where you have the physical path of Workspace server defined you have an button - advanced properties. Click that and go to file navigation tab, where you would be able to see three options i.e. system root, home directory, any path you wish to add. Thanks Anand ##- Please type your reply above this line. Simple formatting, no attachments. -## -- -Anand! ... View more