About AnandVyas

AnandVyas · ‎01-11-2021

Hi @japsas100 Usually DB's have their own auth domain defined in SAS i.e. you will need an ID that is created in the database and can authenticate against it. It can be of same name that's not an issue, however the password could differ. You can check with your DBA about it. It's always better to try and connect from outside of SAS using DB client to confirm as well.

AnandVyas · ‎01-10-2021

Hi @gra_in_aus That's a lot of jobs!! I have done export/import of around 1000+ jobs and it can get very tedious if there are failures. Few points from myside: Suggest to break it into chunks of smaller jobs rather doing it in one shot Make sure Metadata server is running optimally i.e. no slowness observed or file system issues Take full cold backup of the system It could take a long time to process so better to run it in background Deployment directories created by users can be a lot and at different file system paths. Verify this from source and create it in the destination environment If there are a lot of them, better to reach out to TS to help create them automatically using code or if you can do it via code Take a backup again after deployment to fall back incase of issues later If you are planning to do it via multiple jobs, intermediate backups can help incase there is a failure in between jobs

AnandVyas · ‎01-07-2021

Hi @Phil_NZ Local server usually means BASE/SAS installed on PC. Do you know if you connect to remote SAS server for execution of code or run it local on your machine? You can run below code to check license expiry. proc setinit; run;

AnandVyas · ‎01-07-2021

Hi @SeunghoKang I understand. But SASPy is just an interface to SAS and since you are running your SAS Session on a remote server creating or downloading datasets would require an additional step. If your SASPy was running on a local machine along with your SAS, then you could have used SAS libraries to create a permanent dataset on your local machine itself.

AnandVyas · ‎01-07-2021

Hi @SeunghoKang Slow performance could be due to slow network speed for the data transfer between client and server. If your data is huge and the connectivity is shared or via VPN you can experience extreme slowness. To improve it see if you can connect to a better network or get your client connection as close as possible to the data storage and server. Since the SAS execution is happening on the remote server and what you see on the client is just the output, all the SAS libraries or data that you save will be on server storage. If you have any shared storage or network drive on server which can be shared on client, you should be able to access data seamlessly. There are other options as well that you can use to download data like using sFTP, Download procedure which requires SAS/Connect, or using download option from SAS Studio.

AnandVyas · ‎01-06-2021

Happy to help! 🙂

AnandVyas · ‎01-06-2021

Hi @BarryP I think table has to be reloaded to CAS with the changes for it to reflect.

AnandVyas · ‎01-06-2021

Hi @SeunghoKang I hope when you say you want to get data files on SAS Server you mean to access them and not copy. Since you are connecting to SAS installed on remote windows server there are two options available: IOM using Java The integrated object method (IOM) connection method supports SAS on any platform. This method can make a local Windows connection and it is also the way to connect to SAS Grid through SAS Grid Manager. This method can connect to a SAS Workspace Server on any supported SAS platform. IOM using COM This connection method is for Windows clients connecting to a remote SAS 9.4 host. This method takes advantage of the IOM access method, but does not require a Java dependency. SAS Enterprise Guide or SAS Integration Technologies Client (a free download from SAS Support) is required to install the SAS COM library on your client system. Since you already have SAS Enterprise guide and saspy installed on your machine, you need few details to make the connection using https://sassoftware.github.io/saspy/install.html#iom-using-com If you have access to remote SAS machine using EG run the below command to get the GUID. This is an identifier that you will need to make a connection. proc iomoperate; list types; run; Example output: SAS Workspace Server Short type name : Workspace Class identifier : 440196d4-90f0-11d0-9f41-00a024bb830c /* this is a constant that doesn't change */ If you don't have access then you can request your SAS admin to get this information for you. You will also need the remote SAS machine hostname. Follow the steps in the KB link below for a sample on the connect statement. https://support.sas.com/kb/64/755.html

AnandVyas · ‎01-06-2021

Hi @japsas100 You can reach out to IT to reset the password based on if it's a local or LDAP account. As long as it's used only for start/stop SAS services, owning the config/home directories/files and NOT a part of SMC it should not be a problem to change the password.

AnandVyas · ‎01-06-2021

Hi @Rajkumar20 If you are trying to invoke SAS (eg: workspace server) using external application you can use IOM. KB link: https://support.sas.com/kb/26/049.html JDBC eg: https://support.sas.com/rnd/itech/doc9/dev_guide/dist-obj/javaclnt/javaprog/jdbcconn.html If you have a specific web application that you want to access you can refer to the documentation guide for APIs that can be used to consume and perform actions.

AnandVyas · ‎01-06-2021

Hi @kannanmarappan Few points that I can think of: I don't see any issue during installation and configuration as all the files and directories will be owned by the same UID and GID which is recommended. Any SAS content files or logs that are generated during execution by default go under the SASConfig directories. If these files which are system generated during app execution (batch) or end-user execution will be then owned by the same group which owns the binaries and configuration files. User's will then be needed to be part of this primary group which isn't recommended as they can access these files. Workaround for this could be redirecting logs to a different filesystem during installation/configuration phase itself.

AnandVyas · ‎01-05-2021

Hi @saimaheswaran Check this KB link for this error. https://support.sas.com/kb/46/250.html

AnandVyas · ‎01-05-2021

Hi @bhuiyaas There are system requirements that might be in place for Teradata that is the reason you are able to connect to it directly using a libname statement or a pre-assigned library. SAS/Access interface to OLE DB can be used to access data from Microsoft Access. I think it's supported only on Windows. SAS/ACCESS Interface to OLE DB Base SAS software is required for the installation of SAS/ACCESS Interface to OLE DB. DBMS Product Required: An OLE DB data source provider Before you can use SAS/ACCESS Interface to OLE DB software, an OLE DB provider for the data source where you want to access data is required. OLE DB providers are often available from DBMS vendors and other third-party software vendors. The OLE DB provider that you select might require additional DBMS software for network access. All required network software supplied by your database system vendor must be 64-bit-compliant. The 64-bit version of the OLE DB provider is required for the data source. Ref: https://support.sas.com/documentation/installcenter/en/ikfdtnwx6sr/66390/PDF/default/sreq.pdf To make a connection via libname: https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=acreldb&docsetTarget=p1a9wh7qwv6vc9n18arz94i379q0.htm&locale=en#n0zimj0va0mz1un1p77mad7c4oql

AnandVyas · ‎01-04-2021

Hi @runrunbunny Check out this KB link mentioning about similar problem. https://support.sas.com/kb/14/487.html

AnandVyas · ‎01-04-2021

You will have to configure your JAVA_HOME environment variable or use the full path to your java executable. https://stackoverflow.com/questions/15796855/java-is-not-recognized-as-an-internal-or-external-command You can also use java installed with SAS. Example: "E:\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java" -jar sas.tools.viewregistry.jar