Hello The following statement in your code makes me think that you are having SAS EG on your desktop and connected to SAS Server in a Unix/Linux environment. " INFILE '/usr/local/saswork/SAS_work22F8000037C7_LINX107717A15/#LN00016'". In case this has to be done once in a while, It would preferable  to use SAS EG. Detailed programming is not worth the hassle. In the event this has to done on a regular basis as a scheduled batch process, then the file should be on the Unix server for it to be imported. Replace the location of the file  in the infile statement with the actual location. This type of scenario is of common occurrence in the corporate environment. Lastly in my experience with files of very large sizes (few GB's) , I had situations where I could not open the file in notepad or notepad++.. I would prefer to use the UNIX shell, to have an understanding of the file.in such cases.     ... View more

  From your statement 1. "we can connect to metadata with sas ID, after changing the password of sasadm@saspw its throwing permission error"  However from your log the error is for the user sas. user sas is denied access to metadata server. "[GetObjectProperties] Error connecting to the metadata server: Access denied. [GetObjectProperties] Host: XXXXXXX [GetObjectProperties] Port: 8561 [GetObjectProperties] User: sas" Are you able to connect to sas metadata server with sasadm@saspw? It is possible that it is not defined in the SAS metadata server. Can you check your Metadata server logs.? 2. "We are facing issue while resting the password with sas ID. SAS is installer account."  Typically the password for this account is set at the operating system level and is a pretty straight forward process.  Once this is done it needs to be updated in the sas metadata server using sas deployment manager. Most SAS Administrators are aware of this process what is the issue you are facing resetting the password?   ... View more

Can you clarify what exactly you need. sasadm@saspw is an internal account. SAS installer account (sas) is an external account. ... View more

In the following code observations with closed date are ranked based on the closeness. The closest date will have rank 1, the next will have 2,  You can filter based on how many records you want.. I have named the ranking variable as time_rank. You can call anything else. For each customer there will be a different rank. Please let me know if you have questions. Here is the code: /*---------------------------------------------*/ data test; Retain customer_id order_date delivery_date; format order_date delivery_date date9.; informat order_date delivery_date date9.; input customer_id order_date delivery_date; date_diff=delivery_Date -order_date; datalines; 1 01JAN2021 01JAN2021 1 01JAN2021 10JAN2021 1 02JAN2021 10JAN2021 1 02JAN2021 11JAN2021 2 02JAN2021 10JAN2021 2 02JAN2021 20JAN2021 ; ; run; proc sort data=test; by customer_id order_date delivery_date;; run; proc rank data=test out=test2 (drop=date_diff) ties=low; by customer_id; var date_diff; ranks time_rank; run; proc sort data=test2; by customer_id time_rank; run; The output will be like this: customer_id order_date delivery_date time_rank 1 01JAN2021 01JAN2021 1 1 02JAN2021 10JAN2021 2 1 01JAN2021 10JAN2021 3 1 02JAN2021 11JAN2021 3 2 02JAN2021 10JAN2021 1 2 02JAN2021 20JAN2021 2   ... View more

The xls files generated by SAS Excelxp Tagset are xml files. They have xls extension instead of xml. The simplest approach is to open the file in excel and save either manually or programmatically. Have a look here https://support.sas.com/kb/43/496.html  ... View more

If possible copy your code to  notepad and then copy back to SAS Eg in a new program window and try ... View more

From the following it is my understanding that your xml has been generated by SAS ExcelXP tagset. - <!-- Generated by the SAS Excelxp Tagset .v1.130, 08/02/2013 --> There may be many approaches to import these into SAS. One simple approach is to open this xml file in Excel and save as xlsx file. (It can be done programmatically using vb script if it is desired to automate.). Then it can be imported as xlsx.. There is a forum posting on this https://communities.sas.com/t5/Integration-with-Microsoft/How-to-import-XML-file-produced-by-ods-tagsets-excelxp/td-p/114748  My under ... View more

Hello Please have a look at this https://www.sqlshack.com/an-overview-of-the-column-level-sql-server-encryption/  and this https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15  The purpose of encryption of sensitive data is to prevent it being viewed without proper authorization and keys/certificate. ... View more

SAS provides user import macros. You should be able to customize them to your need. Have a look at the SAS documentation here. https://documentation.sas.com/?cdcId=bicdc&cdcVersion=9.4&docsetId=bisecag&docsetTarget=p02wesbzrochnbn1na7fqdy2gdvo.htm&locale=en ... View more

There could be many reasons, but the best approach is to ask your SAS  Administrator for help. The SAS Administrator know your environment better and can take the required action. ... View more

Agreeing completely with what Shmuel has said, I would suggest take computing to where the data resides(In database processing)  Either use SQL pass through or perform the processing to the extent possible in SQL server.. Here are some papers on the subject https://www.mwsug.org/proceedings/2014/SA/MWSUG-2014-SA03.pdf https://www.mssqltips.com/sqlservertip/2703/using-sas-access-and-proc-sql-to-retrieve-sql-server-data/  http://support.sas.com/resources/papers/proceedings10/300-2010.pdf  ... View more

I think yes. May be difficult but not impossible. Consider the following. We have the ability to create a ticket with SAS Tech Support by Sending an email. Once it is done a response comes with the ticket number. Therefore there may be a way. I suggest that you contact SAS Tech Support. They may be able to help. ... View more