If multiple SAS sessions try to update a SAS dataset at the same time, you will run into the file locking issues discussed in the other thread.  It doesn't matter if the the program is the same, or if the two users are the same.  When one process begins writing to the file, it will lock the file.  If another process tries to write to the file at the same time, it will error because the file is locked. ... View more

Still confused, what is SAS / MLE?  Is MLE a SAS product / solution? ... View more

Please update your question to show the PROC SQL join you have tried.  That will help others help you. ... View more

This thread shows column-level permissions being set in SAS 9 metadata with SAS Management Console: https://communities.sas.com/t5/Administration-and-Deployment/How-do-I-implement-Column-Level-Security-in-the-SMC/td-p/628777   ... View more

My memory is notes started in the grace period, and then warnings increased dramatically in the warning period.  But this year, you have no grace period.   The timing of the license is specific to the contract with SAS.  So if your institution (company or university) has a SAS license that expires on June 15 every year, that is when your license will expire, regardless of when you obtain a license from your institution.    If someone from your institution is saying "Don't worry, SAS will work until September" you should tell them now that it will stop working on Jul 15.   They are probably not aware that the grace period was eliminated and warning period was shortened.  If you send them the setinit (license file) with the dates highlighted, that should clarify it for them. ... View more

Interesting, I googled a bit of that XML block, and google's AI came back with below. In the context of the XML structure of an Excel file (which is in the Open XML format, essentially a zipped collection of XML files), the code snippet  <c r="A3" t="s">  represents a cell within a worksheet.  Here's a breakdown: <c> : This is the XML tag representing a cell. r="A3" : This attribute specifies the cell's location or reference, which is "A3" in this case. t="s" : This attribute indicates the data type of the cell's value. The value "s" signifies that the cell contains a shared string.  Shared String Table: When the  t  attribute is set to "s", the actual text content of the cell is not stored directly within the  <c>  element. Instead, the  <v>  element inside the  <c>  element will contain an index that refers to an entry in the Shared String Table.  The Shared String Table is a separate part of the Excel XML file, typically found in a file named  xl/sharedStrings.xml . It's a space-saving optimization where duplicate strings are stored only once and referenced by multiple cells. This means that multiple cells containing the same text can all point to the same entry in the Shared String Table, reducing file size.  In summary,  <c r="A3" t="s">  tells us: This is a cell. Its location is A3. It contains a string, and its value is stored in the Shared String Table, referenced by an index within the  <v>  element.  ... View more

I'm hoping SAS will continue to be generous with emergency 7-day  (30 day?) setinits.  Seems like the majority of years, at multiple employers, I've entered the warning period.  And then had IT tell me "don't worry, it's just a warning."  : ) ... View more

@ballardw wrote: I seem to recall there are two different warning messages. The one you are seeing is the heads up maybe 45 days. Then you get one with the DATE that things will stop working at about 15 days.    Or I could be remembering incorrectly as retirement is starting to rot my memory... You're correct. My current setinit looks like: Expiration: 14OCT2025. Grace Period: 0 days (ending 14OCT2025). Warning Period: 15 days (ending 29OCT2025). Which is actually a surprise to me, glad I looked.  In prior years we typically had 45 day grace period (after the expiration date) and 45 day warning period (I think that was after the grace period).  And needed all that time to get the purchase orders through... ... View more

This support note has some suggestions: https://support.sas.com/kb/61/382.html   But agree with Paige, first step is probably to run PROC CONTENTS to make sure that variable does not have a format attached. ... View more

This is still confusing, as you've introduced a new concept of a 'break'.  Please provide an example of the sample data you HAVE (schedule2), and the output you WANT from that sample data.   As a DATA step with CARDS statement, as Tom showed, and Paige asked for at the beginning of this thread. ... View more

Try tagsets.excelxp destination.  As discussed in this paper, it handles memory differently than the EXCEL destination.   https://support.sas.com/resources/papers/proceedings16/SAS5642-2016.pdf     ... View more

Thanks @Kathryn_SAS , that tech support note looks like exactly this problem.  Very interesting.  I tend to think in terms of the (logical) PDV, without worrying about registers and memory locations.  Very interesting to see the explanation in that note. ... View more

You could try tagsets.excelxp.   It might not have the same memory limitations as the EXCEL destination.  It writes .xml, but Excel will open it and you can do most of the same formatting. ... View more

Just for fun, what happens in M6 if you do: r = m-n; s = m-n; t = m-n; u = m-n; and what about: * r = m-n; s = m-n; t = m-n; u = m-n; And adding that PUT statement fixes the problem in M6?  That's a crazy part of the puzzle. ... View more

Please send the code and those images of 9.4M6 and 9.4M7 in to tech support.  Maybe they can explain and document this bug (assuming they agree it's a bug...) ... View more