I use MFC and understand how to skip configuration menu (set pInfo->m_bDirect to false). But I want to set the folder and filename programmatically, without a special dialog. If it is impossible, can you advise me about a PDF printer with this functionality (may be changing configuration file for this goal)?
One question at a time, has limitations so here goes.
Q.) I want set folder and filename programmatically without special dialog.
A.) If you look at the output port of a recent windows installation of Microsoft Print To PDF
You may note it is set to PORTPROMPT: and that is exactly what causes the request for a filename.
You might note lower down, I have several ports set to a filename, and the fourth one down is called "My Print to PDF"
So very last century methodology; when I print with a *duplicate printer but give it a different name I can use different page ratios etc., without altering the built in standard one. The output for a file will naturally be built:-
Exactly in one repeatable location, that I can file monitor and rename it, based on the source calling the print sequence, such that if it is my current default printer I can right click files to print to a known \folder\file.pdf
Your next question will be how to change the target location and that is done behind the scenes when using apps such as WordPad Command Line printing where we can specify the port name on the command line.
Some users will use a Port Redirection Monitor (Do NOT use RedMon as unsupported in Win 10, consider Multi Port Redirector)
Other Users will interact with the duplicate named printer directly via PrintUI where you can alter output port, rotation or paper format etc.
And for your usage you could try one of these for hints, with your newly defined PDF printer:-
Microsoft Web Browser ActiveX control - printing to a specified (non default) printer
Programmatically set filename and path in Microsoft Print to PDF printer
I'm trying to make a permanent change to my SAS config file (sasv9.cfg). Specifically, I want to increase the MEMSIZE option from -MEMSIZE 2G to -MEMSIZE MAX.
The instructions from SAS on how to do this are on this page under *Overview of Changing SAS System Option Settings' ... http://support.sas.com/documentation/cdl/en/hostwin/69955/HTML/default/viewer.htm#p0drw76qo0gig2n1kcoliekh605k.htm#p0273uv4qrgcrjn16vg7muluuhrz
Using SAS' text editor I am able to access the config file (sasv9.cfg) and make the changes to the appropriate line of code.
The problem is that SAS won't let me save those changes, stipulating that the 'administrator' has to approve them. I am the administrator but I don't know enough about how SAS' OS works to enable the save.
Any suggestions on workarounds to this issue would be most welcome.
You need to edit the file as an Administrator since I'm guessing you are on Windows,
Right click in notepad app and select run as an Administrator:
Then open the file sasv9.cfg through menu > file > open
I use a customized setup within the Enhanced Editor which sets Emacs-like bindings for many tasks. For example, Move cursor down is assigned to C-n, Move cursor left is assigned to C-b, etc.
Unfortunately, whenever I need to reinstall SAS or use a different computer, I have to reassign everything by hand, a non-trivial process. I know it's possible to export keyboard macros as .kmf files. Are the assigned keys stored somewhere that I could back up?
I am using SAS 9.4 on Windows (otherwise I would just use Emacs).
Your sasuser.profile catalog contains preferences and settings, amongst other things. Copy that to the new sasuser folder and things should be as before.
Find your current SAS session sasuser path with %put %sysfunc(pathname(sasuser));
You can test this by creating a new SAS shortcut with a new -sasuser setting.
For example:
create folder c:\temp\sasuser
copy existing sasuser profile.sas7bcat file to the new sasuser folder
create a new SAS shortcut
edit properties and append -sasuser "c:\temp\sasuser" to the target.
open the shortcut
All your preferences and settings will be the same as you had in the old session.
tl;dr: Can SAS libraries be nested within one another in the Enhanced Editor Explorer?
I am working with code which generates a plethora of data sets. Although there are many individual data sets, they can be grouped into various categories. For instance, perhaps 30 of them are incoming "raw" data, another 50 are analysis "results" and the remaining 20 are "intermediate" steps.
Currently, all 100 data sets reside in the Work directory. They have been well named so that they appear next to one another in the SAS Explorer window. However, I would prefer to organize them in folders.
One way to do this is to create new directories within the temporary Work folder.
%let dirWORK = %sysfunc(pathname(Work));
options dlcreatedir;
libname raw "&dirWORK./raw";
libname interm "&dirWORK./intermediate";
libname results "&dirWORK./results";
As sub-directories of Work, these directories and their contents will be deleted when the session ends. This is agreeable.
Not agreeable is how the raw, iterm, and results libraries appear one level up in 'Active Libraries' instead of within the 'Contents of "Work"'. This behavior is somewhat counter-intuitive and awkward.
Is there a way to view the sub-folders of Work within the 'Contents
of "Work"' in the SAS Explorer?
Perhaps there's another way to separate the data sets (DCREATE?) which causes the Explorer window to behave like a typical file browser?
Libraries can contain many things.. But not other libraries. Your 'Active Libraries' will always show your (available) list of libraries at the same level, regardless of where or how they were defined:
One option if you'd like to view your datasets like a typical file browser is to use the Explorer window. Just click View / Explorer, and navigate to your datasets that way..
eg:
%let dirWORK =C:/temp/work;
options dlcreatedir;
libname raw "&dirWORK./raw";
libname interm "&dirWORK./intermediate";
libname results "&dirWORK./results";
data raw.test;
set sashelp.class;
run;
SAS librefs are just single words, so by definition there is no heirarchy. You could try using librefs that will place them next to each other alphabetically? Perhaps WORKIN, WORKMID, WORKOUT. Then they would sort in logical order.
You could use a file explorer to browse the directory structure you have created, but I don't think the SAS Explorer tool in SAS Display Manager can handle that.
DMS does have a file explorer tool you could try. You can start directly on your current WORK directory by running this command from the command line of any window, or via the DM statement in a program.
exproot dir="%sysfunc(pathname(work))" title="Work Directory"
There appears to be no ideal solution. The best I could devise requires the use of two part names, a non-trivial amount of extra code, a custom setup, and is potentially confusing to other programmers. The easiest configuration appears to be the default behavior: simply dumping all data sets in the Work library and sifting through all of them.
For prosperity, here is the best solution I could devise to organize things.
Understanding the Display Manager and Explorer Window
The Display Manager (DM) controls the various windows in the Enhanced Editor. This includes windows such as log, results, pgm, output and explorer. It is the latter which is of principle interest here.
A user may configure windows per session using the menus. There exist, however, a set of commands which may be used to automatically configure the DM for each session. When used with the AUTOEXEC.sas facility, this allows the user to 'permanently' configure the SAS editor to their preferences.
The default explorer view for the Enhanced Editor is the "Contents of 'SAS Environment'".
When the explorer window is selected, a tree hierarchy view can be toggled. There are several ways to do this. Here is one way:
Select the explorer window
View > Show Tree
Having to do this every time SAS is opened becomes a pain. After we clean up the library tree, we will automate this.
Remove any extraneous libraries
SAS loads a variety of libraries by default. These include WORK, SASHELP, and SASUSER, as well as others that are part of non-base products. In my case, the MAPS, MAPSGFK, and MAPSSAS libraries are also loaded (see above picture). As I never have used these (and likely never will), they only serve to clutter up my library directory. To remove these, one can edit their config file.
SAS implements a whole web of config files. On a Windows system, the likely relevant sasv9.cfg file is located here:
C:\Program Files\SASHome\SASFoundation\9.4\nls\en
You will need admin rights to edit it. Disregarding the DO NOT EDIT BELOW THIS LINE warning, comment out the the following using PL/I style comments.
Un-commented:
-MAPS !SASROOT\maps
-MAPSGFK !SASROOT\mapsgfk
-MAPSSAS !SASROOT\maps
Commented:
/* -MAPS !SASROOT\maps*/
/* -MAPSGFK !SASROOT\mapsgfk*/
/* -MAPSSAS !SASROOT\maps*/
Now when SAS opens, the MAPS, MAPSGFK, and MAPSSAS library will not be automatically loaded. Unfortunately, there does not seem to be a way to disable the loading of the SASUSER and SASHELP libraries. If someone knows how, please let me know!
Configure the Explorer Window
The explorer window can be 'configured' using the DM statement and the AUTOEXEC.sas facility.
Navigate to the directory containing SAS.EXE. On a default Windows installation, it is located here:
C:\Program Files\SASHome\SASFoundation\9.4
Create a SAS program named AUTOEXEC.sas containing the following code and place it in the directory which contains SAS.EXE. This step requires admin privileges. I find it easiest to create the file in a non-privileged environment and simply copy the AUTOEXEC.sas program into the directory.
Include this in the AUTOEXEC.sas program:
dm 'dmsexp; tree; expand libraries; expand work;';
When SAS intializes, the AUTOEXEC.sas code is executed before any user input is accepted. The above code does the following:
dmsexp - Brings the explorer window into command focus.
tree - Toggles the tree hierarchy view.
expand libraries - Within the "Active Libraries" pane, drills down into Libraries.
expand work - Within the "Active Libraries" pane, drills down into the Work library.
Each of these is a separate command and could be issued on separate lines. Instead of this, semi-colons are used to issue them in a single line.
Now when SAS is opened, the tree menu is available and the contents of the Work library are viewed. The picture below is somewhat deceiving. The "SAS Environment" pane is not set to a convenient width as pictured. It must be manually adjusted. If anyone has a way to automate this, please let me know!
Storing data sets in sub-folders
To ensure that data sets are deleted when the SAS session ends, sub-folders needs to be created within the temporary system folder where the Work library points to.
The following structure can now be followed:
/*Determine location of Work directory*/
%let dirWORK = %sysfunc(pathname(Work));
/*Allow LIBNAME statement to create new directories*/
options dlcreatedir;
/*Create sub-folders within the temporary Work directory
and assign librefs*/
libname raw "&dirWORK./raw";
libname interm "&dirWORK./intermediate";
libname results "&dirWORK./results";
Now, all the raw data sets can be assigned to the raw library. Within SAS, they will be logically separated from Work. That is, if the data set foobar is created in the raw library, it can only be accessed via raw.foobar. A statement such as data = foobar or data = work.foobar will not work. Yet because the raw library is in fact a sub-folder of Work, it will be deleted when the SAS session is ended.
I forgot to printto my log and it filled up. I tried to choose the 'save' option from the popup window. I entered a name+path for the log and it didn't accept it. I tried entering just a name and it accepted it, but I have no idea where it saved to.
I've searched around and found many answers on how to avoid this situation, but no answers on where the save option puts your log.
It is saved as a catalog entry in SASUSER.PROFILE with whatever name you gave it. FILE is the way to get it saved as a text file rather than a catalog entry.
Note, this only works if you have write access to SASUSER; if you regularly run SAS with rsasuser or if you share user profiles for whatever reason (or if you're running a second+ copy of the same SAS session), the save option will not work at all (and should give you an error).
You can also specify -altlog="<path to log>" on the SAS exe invocation/shortcut. This writes the entire session log to file as you go along.