Hi @Ronein    The SAS encryption algoritms  will always generate the SAME KEY for a given value. This can be used in the following way: 1. Generate data to the external part with an encrypted key only. 2. Join your original and the returned data on the encrypted key, which you generate once more from the original ID in the join condition. This way, you don't have and don't need a data set with both the original key and the encrypted key. I think that should satisfy all requirements. * What you have; data have; ID = 123456; Name = 'Ronein'; run; * You make encrypted data to external part; data xport; set have; drop ID; ID_encrypt = put(md5(cats(put(ID,12.))),$hex32.); run; * External part returns data with added information; data return; set xport; Occupation = 'SAS Programmer'; run; * You merge added infornmation onto orig data; proc sql; create table want as select a.ID, a.Name, b.Occupation from have as a full outer join return as b on put(md5(cats(put(a.ID,12.))),$hex32.) = b.ID_encrypt; quit;       ... View more

hi @Walternate    You could try removing '0A'x (the line feed char) also. Might solve your problem. ... View more

Hi @CraeSnolind  Our admin has agreed to let me keep the erlu2 adress that works, so case solved!  again, thank you.   Erik     ... View more

Hi @Shakti_Sourav  This happens now and then. In my experience, this particular behaviour is seen when a work table (or view) has one or more columns with empty names.   It is easy to fix if you have acces to the Metadata Browser found under Solutions -> Accssories in SAS Display Manager (also known as Base SAS).   Open the Metadata Browser and connect to the relevant Metatada Server Make sure you have Brwese mode unchecked. When the tree is displayed, right-click in the frame and select Find Enter the search string Column?@Name=' ' If there are any columns without names, a list of objects is displayed. For each column                - right click on it and select explore from here.                - in the right pane, right click on the Name attribute and select Modify                - enter a column name, just call then A, B C and so on.   Now the job should open, and you can open the transformations, locate the columns with names A, B, C and rename them. ... View more

Hi @Chris Thanks, I got the mail!   Yes, I changed to erlu2 as an alias, but it didn't work either, not last week at least, so it must be your removing/adding that worked.    Our admin wants me to change back from erlu2 to erlu again. I will use erlu2 for another couple of days before changing it back. It will be very interesting to see if it still works or the problem is back.    Again, thanks a lot! Erik       ... View more

Hi @TobiasL    More test. ... View more

Hi @TobiasL    Tak for svar ... View more

Hi lasoe@odense.dk Dette er en test. ... View more

@HenrikThiesson    Thanks.  ... View more

Hi @Anne_A    The SAS documentation has a good description of the steps in setting up change management. It is not complicated. see https://documentation.sas.com/doc/en/bicdc/9.4/bidaag/p0jwlqhvab11lrn130hwdiq02tsi.htm   In addition, you might want to do something with autorizations on the Custom Tree folder to prevent users from making direct changes without use of check-out and check-in. ... View more

Hi @BeverlyBrown    Thanks for help with RSS.   As expected, I didn't get a notification of your comment. Our admin is still working on it, and it seems that a copy of the "not receiving community mails" finally convinced him that the problem is his to solve.  ... View more

Hi @Ronein    Besides the &n problem mentioned by @PeterClemmensen , your code vil not work, because you don't refer to a macro variable in the version 3 data step. Compare  version 2 to  version 3: b4=&b4.; vs. b&i.=b&i.; This vill transfer the macro variables to data step variables: %let b1=1; %let b2=11; %let b3=12; %let b4=13; %macro RRR; %do i=1 %to 4; b&i.=&&b&i.; %end; %mend RRR; data want3; %RRR; run;   ... View more

Hi @AhmedAl_Attar , @acordes    If there are 180.000 code lines in the input file, one would expect them to be read into SAS as 180.000 lines. When this doesn't happen, it might be because SAS doesn't recognize the record terminator, but reads the file in chunks of 32767 bytes, the max.  allowed in an infile statement, though I cannot see why it would read more than one observation in this case.   But it could be an interesting experiment to see if a termstr= option on the infile statement specified to match the file (CR, LF or CRLF) could force SAS to read the file as 180.000 code lines. It might be simpler to parse the file this way.   An alternative could be to read the file in 16 chunks and concatenate the chunks in one variable/observation before output as a SAS varchar, so the parsing for proc/run wouldn't be compromized by broken lines.   ... View more