Long story short. Older computer (windows server) ran SAS programs scheduled by Windows Scheduled Tasks. Mostly Proc SQL statements connecting to a Teradata database and retrieving data.    The programs ran (SAS 9.1.x) in such a way that once an error was encountered, NOEXEC would be invoked. If no error, the program ran all the way through.  Immediately following the error in the log would be the note:   NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements.   But ... I can't figure out how this was done. Newer computer (windows 2008 server, SAS 9.4) running some of the same programs does not kick into NOEXEC mode upon an error.     I'm not sure what to look for, or where. I don't see any OPTIONS statements that affect error-handling as far as I can tell.    Here is the main OPTIONS statement in the main program that calls other programs as needed: OPTIONS MPRINT MLOGIC SYMBOLGEN NODATE NONUMBER NOLABEL sastrace=',,,d' sastraceloc=saslog compress=yes replace workterm ;   The one thing I do not have access to is the sasv9.cfg on the old machine - this was lost in the transition and is unrecoverable. So there may be a system option for this. Or not.    it's probably simple and I'm going to kick myself when I hear the answer.   Thanks. ... View more

I am trying to create some calendars using a data set of simple single-day events. In my data set, the maximum number of "events" per day is 8 and the maximum string length of an event is 22 characters. Events occur on all days of the week so limiting to weekdays will not help. When I run Proc Calendar to create my output, it truncates my event entries and leaves some off (directing output to screen). I have tried setting the linesize and pagesize options, tried setting papersize to legal, tried portrait / landscape and nothing helps. Plus when I direct my output to PDF it shrinks the calendar to approximately 2/3 of a page wide and tall. I need to be able to display all events in their entirety - I realize it's probably a simple setting but most of what I do deals with raw data, not making it look pretty, so the output side of SAS is kind of a mystery. Thanks for any help. James Wilson, Dallas TX ... View more

Our department has several reports used by non-programmers.  The way they are currently set up is with a "macro" program and an "include" program.  A simplified version of the Macro program looks like this: %LET State = TX ; %LET Provider_Last_Name = Smith ; /* some more %let statements */ %include "path/someprogram.sas" ; Our users open this program in base SAS (9.2 or 9.3), change the appropriate inputs, and click "run." Needless to say, this is not a perfect system. I am trying to put together a SAS/AF form for one of these programs to see if it's feasible to use for a GUI to make things easier for our users.  We have other users who are programmers who use "power user" versions of the "macro" programs so I would like to have to make as few changes to the %included code as possible. I've created a test form with a radio button list with four state abbreviations and a text entry box called Provider_Last_Name, and a Push Button called "Run".   Now I'm trying to figure out how to assign the input values to macro variables.  I'm sure it's something very simple I'm missing.  I can %PUT the values from the input controls into the log, but my %LET statements aren't working. My SCL for the Run button (BTN_RUN) looks like this: BTN_RUN:                                                                                                                                /* this is the code that will execute when the RUN button (named BTN_RUN) executes */                                                   submit continue;                                                                                                                                                                                                                                                               %put NOTE: PROGRAM STILL INSIDE FRAME SUBMIT BLOCK - THESE ARE THE INPUTS ;                                                             %put NOTE- STATE:                  &STATE.selecteditem ;                                                                                %put NOTE- PROVIDER_LAST_NAME:     &PROVIDER_LAST_NAME.text  ;                                                                                                                                                                                                                 /* now put those inputs into macro variables */                                                                                         %LET STATE=                  &STATE.selecteditem ;                                                                                      %LET PROVIDER_LAST_NAME=     &PROVIDER_LAST_NAME.text  ;                                                                                                                                                                                                                       %put NOTE: PROGRAM STILL INSIDE FRAME SUBMIT BLOCK - THESE ARE THE INPUTS ;                                                             %put NOTE- STATE:                  &STATE;                                                                                              %put NOTE- PROVIDER_LAST_NAME:     &PROVIDER_LAST_NAME;                                                                                                                                                                                                                        /*eventually a %include will go here */                                                                                                      endsubmit;                                                                                                                              return;             And my Log looks like this after I populate my controls and click Run: 92   %put NOTE: PROGRAM STILL INSIDE FRAME SUBMIT BLOCK - THESE ARE THE INPUTS; NOTE: PROGRAM STILL INSIDE FRAME SUBMIT BLOCK - THESE ARE THE INPUTS 93   %put NOTE- STATE: TX;       STATE: TX 94   %put NOTE- PROVIDER_LAST_NAME: TEST;       PROVIDER_LAST_NAME: TEST 95   /* now put those inputs into macro variables */ 96   %LET STATE= TX; 97   %LET PROVIDER_LAST_NAME= TEST; 98   %put NOTE: PROGRAM STILL INSIDE FRAME SUBMIT BLOCK - THESE ARE THE INPUTS; NOTE: PROGRAM STILL INSIDE FRAME SUBMIT BLOCK - THESE ARE THE INPUTS 99   %put NOTE- STATE: 4425;       STATE: 4425 100  %put NOTE- PROVIDER_LAST_NAME: 4437;       PROVIDER_LAST_NAME: 4437 101  /*eventually a %include will go here */ You can see that the values that are input are %PUT to the log, but the %LET statement assigning them to the macro variables I need to use are not working. I'm guessing this is one of those simple things like when you have a macro variable resolve to another and you have to use 2 or 3 ampersands, I'm just stuck. I've tried a few things and could continue firing blindly, but I thought I'd ask for help. Also, perhaps I need to put these values into a data set using the DATA step inside the form SCL then  populate macro variables from that - I really don't know... ... View more