Good luck with that @japsas100 , I hope you can get the help you need.   In any case, worst case scenario, with the txt file and the SAS Deployment Manager you can update the password without much of a hassle. In my case, this is what I would do right away unless there are heavy integrations with other applications - and I would advise to never use sasadm@saspw in code or other applications. Security and time are very valuable to me.     ... View more

Hi @japsas100 ,   only your SAS Technical Support team can help you to recover the password. If they tell you the cannot, that is a voice to trust. I suggest you to contact them and to follow their indications.   Best regards, Juan ... View more

Hi @Madhan_cog1 ,   yo need to split the certificates as I instructed. Then you need to import the certificates in order, as described in your certificate path: first the CA, then the intermediate, and the last one your server certificate. ... View more

Hi @Madhan_cog1 ,   I would say the certificate looks good. I believe your certificates are complete and you should be ready to continue your deployment.   See how SAS documentation explains: https://documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=secref&docsetTarget=p1jf3or94q48y9n1om73rtgo0bct.htm&locale=en   I would expect the certificate in the following format, but yours is probably OK too: https://docs.aws.amazon.com/acm/latest/userguide/import-certificate-format.html   -----BEGIN CERTIFICATE----- Base64–encoded certificate -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- Base64–encoded certificate -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- Base64–encoded certificate -----END CERTIFICATE----- You will need a Private key as well (please do not post it here) -----BEGIN RSA PRIVATE KEY----- Base64–encoded private key -----END RSA PRIVATE KEY-----     As side note, if you are interested in transforming the certificate into a certificate chain, you could: 1- rename extension to .cer 2- extract individual certificates ( Novo ... Root CA, Novo ... Issuing CA, scedevweb)     You can do this by opening your .cer, then click details tab and "Copy to File" button. For the other certificates, go to Certification path tab, click View Certificate and repear the Copy to file step) 3- You can build it by copy/paste contents of each into a .pem file in the following order: https://www.digicert.com/kb/ssl-support/pem-ssl-creation.htm   -----BEGIN CERTIFICATE----- (Your Primary SSL certificate: scedevweb.pem) -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- (Your Intermediate certificate: Novo_Issuing_CA.pem) -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- (Your Root certificate: Novo_Root_CA.pem) -----END CERTIFICATE-----   ... View more

Hi @MarianaG ,   it is possible with SAS/CONNECT sessions, when you want to run SAS code in the other servers besides the one you are connected to. If it is about just data from other servers, you don't need to bring data from several locations to SAS local, you only need to bring that to one of the SAS servers, the one you are connected to. File shares and mounts are great for that. Does it help? Best regards, Juan     ... View more

Hello @prashantprash17 ,   this is a very interesting discussion, but let me put it in an easy and short manner to you:  what you are asking is not possible from the application point of view. And there is no documentation for what you are asking.    If you want to be creative, the solution must come from the infrastructure point of view. Still, I suggest not to be very creative. As you have been told, this is clear case of "medicine to be worse than the illness".   I also suggest to pay attention to @MargaretC advise. You do not want to be out of proper support in production in 3 months.   I do not intend to be harsh, but you really need to re-think your approach and assess the impact. ... View more

Hello @pmaturi83 ,   I think most of your questions have been pretty well answered by @SASKiwi  and @AnandVyas .   My 2 cents to the story are:   - "locale" C in AIX (I guess you mean LC_ALL, but you also have LANG and other LC_* environment variables), is a tricky one, as basically overrides defaults in terms of locale, but also modifies the sorting https://unix.stackexchange.com/questions/87745/what-does-lc-all-c-do  Nonetheless, in RedHat you should have the same environment variables, and I highly recommend to set them up in the same manner (unless there is a very good reason for it, architecturally. In that case, your architect should have assessed the impact of the change already. Check with your architects).   - Indeed, you will probably have CEDA messages as @AnandVyas mentioned. This has got 2 caveats: a) all your SAS processes will run slower, as SAS has to traconscode on-the-fly. b) your logs will reflect this fact as @AnandVyas mentioned, and not all companies will accept to have this information in the logs, as good practice. Not only that, if you have SAS catalogs, they won't work at all, you need to migrate them. I understand you have big chunks of data to process, and to migrate the data can be tedious, but I recommend to have it done.   This is an area that should have been assessed by your architects as well. If this is done, they will have a plan of actions. From my perspective, and from a very high level, a very common approach is to identify what is operational (used every day/month) and what is historical data (almost not used at all). This will help you with prioritization of data that needs to be migrated first, hopefully only 5 - 15% of the total data, which is a massive difference. The rest of the data can be migrated once you are in production phase, in much smaller chunks.   I hope it helps. Best regards, Juan     ... View more

Hello @Madhan_cog1 ,   check the contents of the certificate. Probably this certificate it is just the server certificate (last one in the path).   You will need either the depending certificates (Root CA, Intermediate CA) in the same certificate, or separate. If they are together, you only need to point to that new certificate and import it with SDM. If they are separate, import them in order: first the Root CA, then the Intermediate CAs, then the server certificate as last one. The order is defined in the server certificate.   I personally like to work with separate certificates, but it is not needed, you can work with a chain certificate.   You are almost there, good luck! ... View more

Hello @MG18 ,   gerat topic, although really broad, you would need proper architecture sessions to determine. You can hear many stories here, which can be great for their specific environments, but not necessarily can be applied to your environments.   In any case, ideally, your DR site should be updated every time your main site is updated, following D-T-A-P-DR procedures of promotion. The data of course should be in sync all the time, as frequent as possible, while ot blocking/locking your Production data and minimizing performance reduction.   In terms of technologies, it matters a lot the type of machines and infra you have in place: physical machines? VMs? In any Cloud?    You will always need licenses, legally speaking, for different servers. The costs is something to discuss and negotiate with your SAS Account Manager/Representative, and the type of DR site and method (cold, standby, hot) will influence the total costs.   This being said, keep in mind that all is part of the DR plan, and insights from one topic, will determine changes in another topic. I.e: license for hot DR is too expensive, I want to be cost-savvy, therefore I need to change my DR design to implement additional procedures and have a cold or standby DR, and each of these 2 will have different costs, different design, different procedures and policies.   I hope it helps,   Best regards, Juan ... View more

Thank you @MariaD , this helps me to better understand your background.   I must admit that I feel very intrigued by this error. I would navigate in your system to try to find the root cause and solve it, but I can't.   For now these are my suggestion for both environment, and compare: - From SAS, try to get as much information as possible: %put _all_, proc contents, proc options, etc. Perhaps you could run as well the SAS Content Assessment Tool and https://support.sas.com/kb/20/390.html . I would check as well what is the patch/hotfix of SAS. - From UNIX, try to get the variables, and the patching level of the OS, the mounts, the system logs (such as messages, etc), lsof, etc - From the underlying storage, I would try to get also the messages.   ... View more