![]() Here's another example of debugging a different DATA step program. If you want to the DATA step to break processing when a certain variable changes value, check the Watch box for that variable. ![]() When a variable changes value, it's colored red. With every step, the watch window is updated with the latest values of the variables in your step. You can use keyboard shortcuts (F10), the toolbar, or type a command ("step") to execute that line and advance. That's all of the variables defined in the DATA step, plus automatic variables like _N_ and _ERROR_.Īs you step through the DATA step, the line pointer in the source window advances to show the next line that will execute. You see the source window on top and the console window at the bottom, plus a convenient "watch" window that shows much of the content in the program data vector (PDV). (You can also press F5 to debug the active DATA step.)Įxamine the screenshot below. Once activated, you can click the bug in the left "gutter" of the program editor to begin a debug session. To activate the debugger, click the new "bug" toolbar icon in the program editor window. But keyboard junkies, don't worry - that command line is still there too! And it's much more usable, with toolbars and windows that allow you to control its behavior. The new debugging environment, introduced in SAS Enterprise Guide 7.13, has all of the features of its ancestor. (Even though I'm writing this in the past tense and it seems like I'm eulogizing, this debugger still lives on in Base SAS!) The new DATA step debugger ![]() You could set breakpoints, variable watch conditions, examine variables and calculate values - all with commands that you typed. It had only two windows: one for the source, and one for the "log", meaning the debugger console log. Introduced as production in SAS 6.09E (E="enhanced!"), it was basic but it did the job, relying on command-line processing to direct the debugger actions. If you've been around SAS programs for a while then you might remember the full-screen DATA step debugger in the SAS windowing environment. (Workaround: load your data in a separate step, then debug your more complex DATA step logic in a subsequent step.) Ye olde DATA step debugger 1986 called they want their debugger back. That's an unfortunate limitation, but it's a side effect of the way the DATA step "debug" mode works with client applications like SAS Enterprise Guide. Next, it can't be used to debug DATA steps that read data from CARDS or DATALINES. It can't be used to debug PROC SQL or PROC IML or SAS macro programs. This tool is for debugging DATA step code. (I admit that I might have buried the lead in that post.) Let's use this post to talk about the new debugger and how it works.įirst, let's address some important limitations. ![]() And if someone searches the internet for that error message, he might find this post and this information would be helpful.In my earlier post about WHERE and IF statements, I announced that the DATA step debugger has finally arrived in SAS Enterprise Guide. But not clear why it only shows this cryptic error message. Well, after the fact it is clear why things failed. But in my case it was simply that somehow this check box was *not* enabled in the GDB launch configuration: It seems that the The system tried to join a drive to a directory on a joined drive.Ĭan have many reasons. Localhost:2331: The system tried to join a drive to a directory on a joined drive. The error message in the dialog is: Error in final launch sequence ![]() The system tried to join a drive to a directory on a joined drive ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |