0.2.37
- Your keyboard stays where you are while SAS runs. After a run, the SAS Log (and the SAS Output when there is output) came to the front and also took the keyboard: you could not keep typing in your program while a long run ended. The views now come to the front without the keyboard.
- Format SAS Program: the options of INFILE and FILE in upper case.
DSD,TRUNCOVER,MISSOVER,MODand the other options that are a word alone, andFILE PRINT/FILE LOG, were written in lower case as if they were names. They are keywords and are now written in upper case.
0.2.36
- Macro debugger: a value you change in the Variables view now works in a WHERE. Setting
whereto(race = 'WHITE')was accepted, but the step that usedWHERE &where.;then stopped with ERROR 22-322. The value is now stored as%LETstores it. A value with a quote that is not closed (O'Brien) is kept as you typed it. - %pry:
nextstops on the next line after a%prywritten without parentheses. Before, the run went on to its end. Step Over (F10) works the same way after any macro call without parentheses of a macro that has parameters. - Step Into (F11,
stepat the pry prompt) goes into the macros of a macro library: also when a loader file%INCLUDEs them, and when the macro is in a file named after it in the same folder. When DataStep Studio finds no definition, F11 runs the macro as one step, and the Debug Console and the pry prompt sayNo source for %name: stepped over. - %pry:
count,freq,means,profileanddupsshowedN = NaNand 0 rows in a session withVALIDVARNAME=UPCASE. A blank text value in a result showed as.; it is now a blank cell.
0.2.35
- The data viewer, the complete tutorial. Seven minutes, recorded on SAS OnDemand with the CDISC pilot ADAE: open a
data set, move around, frequencies and statistics with
f, a WHERE, a filter per column, the value picker, sort, columns, labels and raw values, search and Open…, and severe adverse events from the first click to the count. It is on the Marketplace page, on the website and in the manual (chapter 8, each part linked). - Manual, chapter 8 names more keys and buttons: Home/End, the first and last page, finding a column, sorting by a
click on the heading, the actions of the
fpanel, removing a column's filter, Only matching, SQL and Open…. - The value picker starts with the value of the current cell ticked; the manual and the how-to now say so.
0.2.34
- A new Marketplace page. It starts with the film and a new preview of it, says in one table which tool answers
which question (the DATA step debugger, the macro debugger or
%pry), links the three complete tutorials, names the SSH connection to a SAS 9.4 server, and shows how to try DataStep Studio in your browser with the free book.
0.2.33
- A new film, 70 seconds, recorded in VS Code on SAS OnDemand: run and read the log, look at your data, write
faster, and when a number looks wrong, the DATA step debugger, the macro debugger and
%pry. - The manual's tutorial links open at the right moment. Each step in chapters 12 and 13 and in the
%prysection opens its tutorial on the website at that chapter; the videos can be dragged forward and back there. - Which tool when? Chapter 12 starts with a short guide: the DATA step debugger for one row at a time, the macro
debugger for one macro line by line,
%pryfor your real program stopped where you want. The website has it too.
0.2.32
- Two new complete tutorials, recorded on SAS OnDemand. The DATA step debugger in 6 minutes: start it, one statement at a time, stop at one subject, try a fix in the Variables view, watch a variable, MERGE and the IN= flags, a step that calls a macro; it finds and fixes a counter that never starts again. The macro debugger in 5 minutes: start it, one line at a time, a breakpoint with a condition, look without changing the code, step into the called macro, try another path, what ran and how often, debug a call in your program. Both are on the website, on the Marketplace page and in the manual (chapters 12 and 13), where each step links to its part of the film.
- A new website: calmer and simpler, one idea per section, with the three tutorials in their sections.
0.2.31
- %pry, the complete tutorial. A 7-minute video in 8 chapters shows everything
%prydoes, recorded on SAS OnDemand: why it beats MPRINT, MLOGIC and SYMBOLGEN, your first stop, the data as it is at the stop, how you got there (bt,up,show-source), moving through the run, trying a fix before you change the program, stopping at the first ERROR withrescue=Y,%pryin a DATA step and between steps. It is on the Marketplace page, on the website and in the manual (chapter 13), with the start time of each chapter.
0.2.30
- The macro debugger is explained with two macros from the book SAS for Clinical Programmers. The manual, the
website, the videos and the film now use
%by_sev, which makes one subset of a small ADAE per severity, counts its subjects and calls%nobsfor its records, instead of%sum_of_squares. The example makes its own data, so you can run it on any SAS: at the stop in the third round you see whynrecstill holds the value of round two. - Edit Breakpoint… The manual and the how-to name the menu item as VS Code shows it (they said "Edit Condition").
0.2.29
- In a codespace (VS Code in the browser), SAS programs are in color from the start. When a codespace opens for the first time, VS Code installs DataStep Studio into the window that is already open, and that window showed SAS programs as plain text until you reloaded it. Now DataStep Studio reloads the window once by itself, right after the install. If a file has unsaved changes, it asks first.
0.2.28
- A SAS server whose log lines start with a date, time and user works. Some companies set up SAS so that every
log line starts with extra text, for example
2026-11-03T10:13:02,840 INFO [00000006] user -. DataStep Studio then did not find its own lines in the log: Open SAS Server Folder said "SAS did not report its home folder", and the File Manager, project sync and the links from an ERROR to its line failed too. Now DataStep Studio learns at connect what your server writes before each line and leaves it out, whatever the date format or order. - SAS 9.4 through SSH. A server that you reach through SSH works with your own SASPy configuration; the manual (3.3) shows one. The DATA step debugger does not start through SSH and now says that it needs an IOM connection, instead of asking for another SASPy version.
0.2.27
- Run accepts a quote masked with
%STR(%")inside a double-quoted string. A line in a macro such asLABEL="%QSYSFUNC(TRANWRD(&lab., %STR(%"), %STR(%"%")))"doubles the quotes in a label. SAS runs it, but DataStep Studio took the rest of the program as text, said the macro had no%MEND, and did not run the program. Now it reads the macro call inside the quotes as SAS does, and the program runs. Run Step, Run To Line, the debuggers and the formatter see the statements after such a line correctly too.
0.2.26
- Debug Macro steps into macros from your other files. Your macro calls a helper macro that lives in another
file, for example
%check_ninlib/qc_tools.sas, compiled earlier by a run of that file or brought in with%INCLUDE. Before, the debugger stepped over that call. Now Step Into goes into it, and a breakpoint in that file stops there. After the run the helper macro works as before. A stored compiled macro without its source file is still stepped over. - The call pane opens the first time in a new window. With the cursor on a call of a macro from another file, Debug Macro right after opening the window said that the definition was not found; the second try worked. It now waits until your files are read (a few seconds at most) and opens the call pane at once. Open Macro Definition and Go to Definition behave the same way.
- The end of a macro debug run comes sooner. After the last Continue, the log, the coverage marks (×n) and the end of the debug session now come about 0.5 s after the run, instead of about 2 s. The coverage marks no longer wait for SAS to clean up after the run.
0.2.25
- Debug Macro now runs a macro without parameters. For a macro written as
%MACRO outer;the call pane wrote%outer(). SAS then took the()as a statement of its own, and the debugger stopped withERROR 180-322. The call pane now writes%outer. A macro with an empty parameter list,%MACRO outer();, still gets%outer(). A call pane that already holds%outer()keeps it: change it to%outeronce.
0.2.24
- A new 80-second film shows DataStep Studio at work: a real DATA step on SAS OnDemand, row by row, a macro step by
step, a run that stops at
%pry, and why SAS answers faster since 0.2.23. Watch it on the website. The program itself is the same as in 0.2.23.
0.2.23
- SAS answers faster. Every request to SAS comes back about 40% sooner: a run, a page in the data viewer, a step in the debugger, a folder in the File Manager. On SAS OnDemand (Europe) a short request now takes about 0.14 s instead of 0.23 s.
- The first run after connecting is faster: fewer requests go to SAS before it, so its log shows after about 0.6 s instead of 1 s.
- The output of a run always comes with that run. Before, output that a step wrote at the very end of a run could show up with the next run instead.
0.2.22
- Stop at the first ERROR:
%pry(rescue=Y). Write it after the part of your program that fails, and run as always. The run stops right after the first step that ends with an ERROR, before the next one, with every macro variable and data set as it was. The SAS Pry terminal shows the ERROR. Withwarning=Ya WARNING stops it too. When nothing fails, the run stops at the%pryas usual. %prybetween two steps now works too, outside any macro: the program runs up to it and waits.nextruns the next step and waits again,cruns the rest. Continue After %pry (also in the status bar) does the same.- At a
%prystop the SAS Pry terminal opens by itself.next 3takes three steps at once, and Enter alone repeats the lastnextorstep. - The File Manager and the project sync no longer hang when SAS OnDemand does not answer: they ask once more and, if there is still no answer, say so. Copying a few megabytes could hang the File Manager before.
- Programs reach the server faster: they travel zipped, so 500 KB of programs take under a second instead of two.
- The log of code you run at a
%prystop shows only what your code did. - The manual explains
%pryfrom the start: the idea, your first%pryin four steps, where it can stop and what you can do there. The how-to guide has two new recipes: find the step that breaks a long run, and go through a program step by step.
0.2.21
- %pry: a stop written in the code (Professional). Write
%pry(or%pry(when=&i. = 3)) into a macro and run your program as always: the run waits there, with every macro variable and data set as they are at that moment. No more%PUT _USER_;and running everything again. At the stop, in the Debug Console or the new SAS Pry terminal:whereami,ls,bt,step,next,finish,continue,break,watch, code in the paused session,show-source,?for the SAS language,wtf?for the last error. Only the macros around%pryare prepared, so a large macro library runs as fast as without. Manual, chapter 13. - Code at the stop, in the editor: New SAS Program at the %pry Pause (or
editat the prompt) opens a SAS program with autocomplete and all; F4 there, or in any SAS program, runs it inside the paused macro, with its WORK and macro variables. Autocomplete knows the data sets the run has made so far. In the SAS Pry terminal a DATA or PROC step can go over several lines (the prompt shows*untilRUN;orQUIT;). - Data at the stop, as in VIEWTABLE: the first 20 rows, other rows chosen as in PROC PRINT
(
vt work.big(FIRSTOBS=101 OBS=120),print (OBS=50),WHERE=,KEEP=,DROP=);where age > 13,show,forward,find,contents,keep,drop,sort, and with the same WHEREcount,freq,means,profile,dups,compare,sql. %pryinside a DATA step stops the DATA step debugger at the next statement; the code before the step runs first, the code after it when the step has ended.- DataStep Studio: Open Pry Terminal works without a stop too, on your SAS session: a console for data and macro variables with line editing, history and Tab completion.
- DataStep Studio: Open pry.sas:
%pryin plain SAS for SAS Studio, Enterprise Guide or batch, steered from a second session (no stepping there). - Settings
datastepStudio.debug.pry(on:%prystops a run) anddatastepStudio.debug.pryTerminal(off: open the SAS Pry terminal at each stop). - Code run in a paused macro (Debug Console, SAS Pry terminal, F4 at a stop) over several lines: an empty line no longer
stops the code from running, a comment with
%or&no longer breaks it, and%PUTshows its text in the log.
0.2.20
- Install on Windows with one command, in PowerShell:
irm https://datastep-studio.pages.dev/install.ps1 | iex. It is new on Windows; the steps of chapter 2 of the manual work as before. Manual, 2.6. - The default of
datastepStudio.sync.excludeDirsis shorter: two folders whose names start with a dot are no longer listed, because such folders are not copied anyway whiledatastepStudio.sync.includeHiddenis off (the default).
0.2.19
- Install with one command (Mac and Linux):
curl -fsSL https://datastep-studio.pages.dev/install.sh | shputs the extension into your editor and reports what else your computer needs to connect to SAS: Java, Python, SASPy, a connection profile, and whether the SAS server answers from your network. For everything that is missing it names the next step for your system (Homebrew, apt, dnf, or the download). Manual, 2.6. - The setup tool
datastep-setup, in the extension's folder, works without the editor being open:checkreports,fixinstalls SASPy into DataStep Studio's own environment,profilewrites a SAS OnDemand or SAS 9.4 connection profile. It needs nothing installed (it runs with the editor's own program) and never takes a password. - A connection profile written by the setup tool appears in the editor by itself, with Connect Now.
0.2.18
- Format SAS Program keeps IF under ELSE IF, and THEN in one column, also when one of the statements goes on over the next lines; those lines move with their statement. Before, such a statement ended the group and IF went back to the left. When the lines would get longer than the line length, the group stays as it was.
- Format SAS Program sets
DEFINEstatements of PROC REPORT that follow each other with their/in one column. - Format SAS Program keeps the blank of an argument that is left out:
COMPRESS(x, , "c"), notCOMPRESS(x,, "c"). - The built-in keyboard macro
reporthas itsDEFINElines in columns.
0.2.17
- Format SAS Program sets a
LABEL,ATTRIB,FORMAT,INFORMAT,LENGTHorRENAMElist in columns also when its first entry stands behind the keyword (LABEL x = "One", the next entries underx). Before, only a list that started on the line under its keyword was set in columns.
0.2.16
- New: programs that SAS writes are formatted after the run. A run that reports a file with the log line
NOTE: Generated program: <path>.sas(a code generator, a macro that saves the code it produced) gets that file brought into the house style on the SAS server, without anyone asking, and with the same check as Format SAS Program that only the layout changed. SettingdatastepStudio.format.generatedProgramsturns it off. - Format SAS Program breaks a statement that is longer than the line (a long
KEEPlist, a long data set option): a list goes on under its first item, other statements two levels in. Texts in quotes and macro text are not broken. - Format SAS Program sets a statement written with one entry per line (an
ATTRIBorLABELlist under its keyword) in columns, when every entry has the same parts. Before, such a table lost its alignment. - Format SAS Program, two corrections: data set options after
lib.memberin a PROC statement (OUT=adam.adsl(LABEL='x')) keep their=unspaced like everywhere else, and the routine of aCALLbehindTHENorELSE(IF x THEN CALL SYMPUTX(...)) is written in upper case. - Write to the author. Send Feedback and Report a Problem now offer a private way to ask: an email to the author opens in your own mail program, with the versions filled in (no code, no data, no log; the names of your home folders are hidden). You read it and send it yourself. For questions you would rather not put on a public page, such as your company's SAS server.
0.2.15
- New: File Manager (Professional). DataStep Studio: Open File Manager opens a tab with a folder of your
computer on the left and a folder of the SAS server on the right.
F5copies andF6moves the chosen files to the other side,F7makes a folder,F8deletes,F2renames,F3/F4open a file;Spacemarks files, typing shows only the names that hold the letters. Dragging, a right-click menu, and copy and paste work too. A name that exists in the target folder is asked about first, and a move removes the source only after the copy is checked. It is fast: twelve programs go up in about half a second, a hundred files with four megabytes in about three seconds, and it keeps working while SAS runs a program. See "Work on the SAS server" in the manual. - Open Included Program (right click or
Cmd/Ctrl+clickon a%INCLUDE) now also works when the path holds a macro variable, as in%INCLUDE "&studydir./run_all.sas";. The value comes from the%LETabove the statement, or from the SAS session. Before, it said the file was not found. - Fixed: when more than 40 changed files (or more than 512 KB) were copied to the server in one run, a file
whose name has letters outside A to Z, such as
Größe.sas, arrived empty on the server. A program that read such a file there by its path found nothing in it;%INCLUDEwas not affected.
0.2.14
- The tour video's title card says "Every feature in two minutes" (it said three).
0.2.13
- A new tour video: every feature in two minutes, each with what it saves you (DataStep Studio: Watch the 2-Minute Tour). The Marketplace page opens with a one-minute preview.
0.2.12
- The Marketplace name is now DataStep Studio for SAS, with a clearer description and more search words, so SAS programmers find it when they search for SAS. Nothing changes in the extension itself.
0.2.11
- The Marketplace page explains what DataStep Studio does, feature by feature, with pictures. The manual on this page shows its pictures too.
0.2.10
- Fixed: F5 in a folder with a
launch.jsonwritten before the rename (debug typesas-workbench) said "Configured debug type 'sas-workbench' is not supported". Such configurations now start DataStep Studio's debugger. - The manual is rewritten as a tutorial: a short motivation and "Try it" steps in every chapter, and a new "Start here: your first five minutes".
0.2.9
- Open Macro Definition / Included Program (Community): right-click a macro call and the file that defines it opens at
its
%MACROline (the program, its%INCLUDEd files, its folder and the macros folders, on the SAS server also SASAUTOS); on a%INCLUDE "file"the included program opens.Cmd/Ctrl+clickand Go to Definition do the same.
0.2.8
- Keyboard macros (Community), as in the SAS Enhanced Editor: a name typed in a program, Tab writes the code.
80 built in, in house style with Tab stops, each one run on SAS OnDemand: steps (
sort,merge,sql,join,ifelse,select,firstlast,hash), data set and variable information (%nobs,%varfmt,%varlabel,%varlist), checks (dupcheck,bign,%required,qcopts), output (report,odsoutput,rtf,xpt,import,export), session and headers. All listed with their code in the manual's appendix. - Import Keyboard Macros from SAS (.kmf) and Export (.kmf): SAS Enhanced Editor files, both ways.
- Save Selection as Keyboard Macro (right-click), New / Edit / Delete in the Keys tab; any keyboard macro can have its own key.
- After an update with Restart Extensions, VS Code may not know the new settings until the window is reloaded: DataStep Studio says so and offers Reload Window.
- Fixed (Format SAS Program): the statement after
OTHERWISEandWHEN (...)was not recognised (putstayed lower case,usubjid=became upper case); the second data set of aMERGEgot spaces in its options; hash objects (DECLARE HASH h(DATASET: ...),h.DEFINEKEY(...));BREAK AFTER/COMPUTE BEFOREin PROC REPORT; PROC SQL column modifiers (LENGTH=500); ODS OUTPUT table names; PROC IMPORT statements (GETNAMES=) taken for assignments;IF ... THEN DO i = 1 TO n;did not indent its block. - Format SAS Program: IF / ELSE without ELSE IF start in one column (the ELSE statement under the THEN statement).
- Format SAS Program: one statement per line:
DATA x;SET a;is split; a whole step on one line (PROC SORT DATA=a; BY id; RUN;) stays. SettingdatastepStudio.format.oneStatementPerLine. - Format SAS Program: blanks inside a line: one between words, none inside brackets or before the semicolon
(
BY studyidbecomesBY studyid); the indent, comments and macro text stay. - Keys you know from SAS: F3 and F8 run too (unless the official SAS extension is installed; F4 and
Cmd/Ctrl+Enteralways),Ctrl+Kcomments and uncomments line by line (/* */),Ctrl+Shift+U/Ctrl+Shift+Lupper and lower case,Alt+PageUp/Alt+PageDownto the start and end of a DO, %DO, %MACRO or DATA/PROC block,Ctrl+Shift+Fformats the highlighted code,Shift+F4closes the open data set (F3 in a data set tab).Ctrl+F4is VS Code's close-tab key again (Run To Line keepsCtrl+Alt+Up). - Stop SAS: a button while SAS runs (status bar, the program's title bar, the run menu) stops the running code, like Ctrl+Break in SAS; the session, WORK and macro variables stay.
- Removed: the style hints in Problems (and the
datastepStudio.lint.*settings). - Fixed:
SUBSTRwas missing from autocomplete, hover, parameter hints and the formatter.
0.2.7
- Website: datastep-studio.pages.dev with Get started, the user manual, the how-to guide, the release notes and the videos; linked from the Marketplace page and the extension's details.
- The manual has a What's new section.
0.2.6
- Format SAS Program (right-click; also Format Document / Format Selection) (Community): keywords upper, names lower, 2 spaces per level,
=and IF / ELSE aligned, long macro calls comma first, long PROC SQL statements one clause per line, short PROC SORT on one line,&var.periods. Macro text, strings, comments, DATALINES, the header and your line breaks stay; a token comparison proves that only the layout changed. Only when asked. - Style hints in Problems:
*comments, unsplit ERROR: / WARNING:, Boolean flags, macro variables without a period. - Fixed: removing breakpoints while the DATA step debugger finished could leave a debugger command in SAS; the next statement then failed with "Statement is not valid". Debugger commands now go one at a time, and nothing after QUIT.
0.2.5
- Fixed: the DATA step debugger waits until a query of a view still running in SAS is done before it starts (they could mix, and the next statement then failed with "Statement is not valid").
- Debug Macro on a call: with the cursor on a call in a program, the definition is found (in the
%INCLUDEd files, the folder, the macros folders), and the call pane holds the call as written. - Debug DATA Step on a step that calls a macro: the step is expanded beside the program (the macro's statements
written out) and the debugger steps through it; a breakpoint with a condition such as
midtc = "2024-12"stops at that observation. The expansion only compiles the step; it reads and writes no data. - Fixed: a data set without variables shows a clear message instead of "could not read the SAS result".
- Fixed: while the macro debugger is paused, Libraries lists the data sets the macro has made so far (it said "SAS is busy"); a double-click opens them. It refreshes when the macro rests a moment, so stepping stays fast.
0.2.4
- Watch the Installation Video: every step from installing to the first run and both debuggers, also in Get Started.
- The manual says what VS Code asks on the first install (trust the publisher DataStep Labs).
0.2.3
- Fixed: a new SAS Server window that VS Code did not trust yet (Restricted Mode) showed a "!" on its folder and no DataStep Studio commands. DataStep Studio now works in Restricted Mode and asks once for trust, for the debuggers.
- Fixed: while the macro debugger is paused, a data set the macro created opens in the data viewer (the query runs inside the paused macro, which sees its WORK library).
- The guide programs are no longer part of the extension.
0.2.2
- Help on the Marketplace page: manual, videos, questions, the SAS Community thread, Report a Problem.
- Send Feedback offers the SAS Community thread.
- An empty window's Explorer has an Open SAS Server Folder button.
0.2.1
- The user manual and the how-to guide are on the Marketplace page, below the overview.
0.2.0
- Run in Batch (Community): right-click programs or a folder in the Explorer. Each program runs in a new SAS
session, one after another;
program.logandprogram.lstare written next to it, errors appear in Problems, and a summary shows how the batch went. Your own SAS session stays free. - Open Manual and Open How-To Guide: the manual and the how-to guide ship with the extension.
0.1.1
- Videos inside VS Code: Watch the 2-Minute Tour and Watch the Macro Debugger Video.
- Get Started shows pictures of every step.
- Guide example 5 and the manual's macro debugger chapter use a new example:
%sum_of_squarescalls%square.
0.1.0 (Community Early Access)
First public version: run modes, SAS Log and Suspicious Log, data viewer, Libraries, Variables and Options, SAS Server window and project sync, autocomplete with SAS 9.4 documentation, smart code, DATA step and macro debuggers, connection profiles with the password in the system keychain, Check Setup, Send Feedback.