About Rodcjones

Rodcjones · ‎07-24-2020

Thank you @Quentin, @PaigeMiller and @Tom for your super quick and thorough replies. The %global was the concept I was missing and it is going to be great knowledge for me going forward. One note about macro variables vs. FREQ. The scenario I set up was just to illustrate the macro issue with a generic dataset I had handy. I agree - I almost always use ODS OUTPUT of FREQs and PROC REPORT, but in this particular (real, not generic) scenario macro was a better option . . . hence my knowledge limitations were exposed!

Rodcjones · ‎07-24-2020

I have a process in which I would like to use a macro process to create several dozen macro variables for later use. My preferred way of creating macro variables defined through a queried dataset is PROC SQL SELECT COUNT (...) INTO. The code to generate the macro variables appears to work. I can see a listing such as this in the log. SYMBOLGEN: Macro variable ADM_IN_24_XW resolves to 0 However if I try to use that same macro variable to populate a variable in a new dataset I get an error and the log gives me a warning and an error. WARNING: Apparent symbolic reference ADM_IN_24_XW not resolved. ERROR 22-322: Syntax error, expecting one of the following: I am wondering if the cause of the problem comes from my macro program, or did I make a typo of some sort in the data step? I think the former so am reaching out to the community for help. data have; input id $ point1 $ START :mmddyy8. POINT2 $ END: MMDDYY8.; format START END yymmdd10.; datalines; 1 Z 2/1/20 X 2/2/20 1 X 2/2/20 W 2/3/20 1 W 2/3/20 V 2/5/20 2 A 2/1/20 B 2/2/20 2 B 2/2/20 B 2/3/20 2 B 2/3/20 B 2/6/20 2 B 2/6/20 B 2/7/20 2 B 2/7/20 C 2/10/20 2 C 2/10/20 D 2/11/20 2 D 2/11/20 E 2/12/20 ; %MACRO Agegroups(p1,p2,&DT); Title "Adm_In_24_&P1.&P2"; proc sql; select count ( distinct id ) into: Adm_In_24_&p1.&p2 from admits where POINT1="&P1" AND POINT2="&P2" and start GE "&dt"D; quit; %put &&Adm_In_24_&p1.&p2; %MEND; %Agegroups(X,W,03FEB20); %Agegroups(B,B,03FEB20); DATA ONE; V=&ADM_IN_24_XW; V2=&ADM_IN_24_BB; RUN;

Rodcjones · ‎04-06-2020

Thanks all for the ideas and valuable code snippets. ChrisNZ's solution is the one that I ended up going with. There are parts of it that I would like to understand better, so if you can help with these questions I'd be very appreciative. 1. The code has no problem keeping the IDs straight/not mixing the rows of ID 1 and 2. It's not clear to me why? Is it because the dataset is presorted? But even so, how does it know not to analyze these two rows because they pertain to different IDs? 1 W 2/3/20 V 2/5/20 2 A 2/1/20 B 2/2/20 2. This is probably just a vocabulary thing, but I didn't follow what "holp up" referred to in the comments, e.g., %* Holp up found, save start info; Thanks again.

Rodcjones · ‎03-19-2020

I have a scenario that's probably easier to illustrate through the HAVE and WANT datasets below. But here is the scenario: Individual ID is on a journey and her starting location POINT1 and starting date START are recorded, as are her ending location POINT2 and date END. ID 1 in the example below had a different POINT2 for each value of END, but ID 2 got held up at POINT B, so several entries have repeat values of POINT2 despite distinct values of END. In order to conduct the necessarily analysis, I want to reduce the dataset to rows where POINT1 <> POINT2 but somehow capture the START value from the first row of a value of POINT1 and in the same row capture the value of POINT2 and END for the first subsequent row where POINT1 <> POINT2. Like I said, the datasets probably show it better! data have; input id $ point1 $ START :mmddyy8. POINT2 $ END: MMDDYY8.; format START MMDDYY8. END MMDDYY8.; datalines; 1 Z 2/1/20 X 2/2/20 1 X 2/2/20 W 2/3/20 1 W 2/3/20 V 2/5/20 2 A 2/1/20 B 2/2/20 2 B 2/2/20 B 2/3/20 2 B 2/3/20 B 2/6/20 2 B 2/6/20 B 2/7/20 2 B 2/7/20 C 2/10/20 2 C 2/10/20 D 2/11/20 2 D 2/11/20 E 2/12/20 ; data WANT; input id $ point1 $ START :mmddyy8. POINT2 $ END: MMDDYY8.; format START MMDDYY8. END MMDDYY8.; datalines; 1 Z 2/1/20 X 2/2/20 1 X 2/2/20 W 2/3/20 1 W 2/3/20 V 2/5/20 2 A 2/1/20 B 2/2/20 2 B 2/2/20 C 2/10/20 2 C 2/10/20 D 2/11/20 2 D 2/11/20 E 2/12/20 ; I use LAG to get the actual dataset into this shape so have tried using it for this task but have come up short. Also tried RETAIN, but that also seems impossible/inefficient (i.e. requiring multiple DO loops where the number of loops is dependent on attributes of the data . . . lots of extra steps). Any ideas? Thanks! Using SAS EG 7.1 (SAS 9.4)

Rodcjones · ‎03-12-2020

I am interested in opening programs and projects that are stored on a network drive. In SAS EG I am able to navigate freely, just as I would in Windows Explorer. But it seems in SAS Studio I am limited to opening content that I have stored on the SAS server. Is that correct? If so, does this imply that the only way to generate programs and projects for use in Studio is to create them within Studio, or have the files copied to the server? If not, are there instructions on how to navigate to network folders? I searched but came up empty.

Rodcjones · ‎10-22-2019

I'm still unable to get it to work -- same error -- despite using URL. My best guess at this point is that AUTHODOMAIN= might be needed to get me through to the site (which is an on-prem SharePoint document library). Still working on it.

Rodcjones · ‎10-16-2019

I am seeking to use the code in this usage note http://support.sas.com/kb/40/934.html but applied to a file that resides within a Sharepoint document library. I took a stab at putting in the http address, like this /** Non-macro technique **/ filename fileref 'http://sites/philtest/Shared%20Documents/runs.xlsx'; data a(drop=fid); infile fileref truncover obs=1; fid=fopen('fileref'); Bytes=finfo(fid,'File Size (bytes)'); crdate=finfo(fid,'Create Time'); moddate=finfo(fid,'Last Modified'); run; proc print; run; But I get the error ERROR: A component of C:\sas\sasconfig\Lev1\SASApp\http:\\sites\philtest\Shared%20Documents\runs.xlsx is not a directory. I would welcome any hints on how to adjust my code to get this to work. Thanks! I am using SAS 9.04 TS1M6 EG 7.1

Rodcjones · ‎11-19-2017

Thanks for the question. The architecture is robust. What I meant to convey is that the jobs scheduled are associated with quality improvement projects with an intentionally high rate of change in how items are documented and stored within the database. New workflows are implemented frequently, and while the intention is to communicate the downstream impacts to developers, sometimes the impact is not understood right away or not communicated.

Rodcjones · ‎11-16-2017

I have a growing number of SAS enterprise guide .egp projects that are set on a schedule. Unfortunately many of them depend on very dynamic databases – by which I mean there are relatively frequent changes to tables and columns. There are also less frequent ETL failures. These collectively have the impact of messing with the outputs and deliveries that the .egp’s produce. I would like to incorporate data integrity checks into all of my process flows that would halt processing and notify me/the admin that the task did not complete. I am thinking there are probably two kinds of checks. Make sure one (or multiple) datasets have the expected number of records (or meet a minimum threshold of number of records). Make sure no errors have been logged at one or more points in the process flow. My questions to the community are Is my perception of the kinds of integrity checks good (or are there other kinds of integrity checks I should also be considering)? Are the best practices for achieving this? Aside from the integrity checks, are there recommended approaches to halting a process flow? This question comes from some challenges I see when the .egp contains a relatively large number of programs, rather than a small number of programs with %include statements that could be enclosed in a macro that is based on the results of the integrity check. In other words is it possible to enclose a series of *programs* within a macro using the SAS EG process flow functions? SAS 9.4, EG 7.1, Server 2012 R2 Thank you all for taking a look.

Rodcjones · ‎11-16-2017

I have SAS enterprise guide .egp projects that are set on a schedule. They generally run fine. But I have had failures that show the error code 0xE0434352 in the task scheduler. I think that what’s causing the failure is that the project log has gotten too big. (If I run the process flow manually, I get the pop ups saying it has exceeded a certain size.) After I clear the log and turn it off, the task runs as scheduled. I’m a little bit dubious that oversized project log prevents scheduled tasks from completing, so I wanted to ask for the community’s wisdom. Is it correct that SAS EG scheduled tasks won’t run when the project log reaches a particular size? If yes, is it possible to prevent this or have a workaround so a large project log won’t interfere with the scheduled task? The reason I’m asking #2 is because I find utility in having the project log for troubleshooting. If I have to turn off all my project logs to allow schedules, I’ll do it, but I’d prefer to not have to. SAS 9.4, EG 7.1, Server 2012 R2 Thanks!

Rodcjones · ‎09-07-2017

Liz Edwards at SAS tech support worked through this with me and determined my use of the original data set in a data= statement in the last PROC SHEWHART was the fatal flaw. Deleting it and going only with the history= statement gives the desired results. proc shewhart data=month4vp1 history=history4;

Rodcjones · ‎09-07-2017

I have only a tiny bit of experience so far, but I only added the tasks/programs that I wanted to run and it executed successfully. So it seems you don't have to add everything into the ordered list.

Rodcjones · ‎09-07-2017

This was a great find for me. Even though the thread is closed, I wanted to add in case other searchers end up here. In newer versions of Enterprise Guide the instructions are different. I am pasting this from the Help section of version 7.13 HF3: You can create a list of tasks and programs in the current project that can be run in the order that you choose. You can select objects from more than one process flow. In this way, you can group objects without changing their positions in process flows or their relationships to other objects. Each ordered list is available from the recently viewed items button at the top left of the workspace and in the project tree. To create an ordered list of tasks and programs Select FileThen NewThen Ordered List. In the Ordered List window, click Add to display the tasks and programs that are in the current project. Select one or more items and click OK to add them to the ordered list. To change the position of an item in the list order, select the item in the Ordered List window and click Up or Down. To remove an item from the list, select the item and click Remove. When the list is complete, click Run to run the tasks and programs in the list, or click Save to save the list.

Rodcjones · ‎08-14-2017

Thank you, Bucky. This is very helpful and opened up a lot of new info for me. One follow up I have is that this method doesn’t seem to work for p charts or X-bar S charts. I assume that’s because those are driven off the record level values rather than those summarized by group. But not sure. I’m pasting example below. Is there an alternative that will work for p and X-bar S charts? Or maybe I’m mistaken and I can get pointed in the right direction. proc sql; create table work.month4vp1 (_year_month char(7), defects num(8),population num(8),percentage num(8)); insert into work.month4vp1 values('2013-10',87,115,75.65) values('2013-11',59,97,60.82) values('2013-12',56,102,54.9) values('2014-01',15,39,38.46) values('2014-02',24,40,60) values('2014-03',34,62,54.84) values('2014-04',41,72,56.94) values('2014-05',55,76,72.37) values('2014-06',21,35,60) values('2014-07',29,52,55.77) values('2014-08',75,123,60.98) values('2014-09',144,288,50) values('2014-10',76,129,58.91) values('2014-11',38,83,45.78) values('2014-12',46,70,65.71) values('2015-01',36,50,72) values('2015-02',31,53,58.49) values('2015-03',51,83,61.45) values('2015-04',32,70,45.71) values('2015-05',77,117,65.81); quit; ***run it first without ghosting the 2013-10 group; ;proc shewhart data=month4vp1 ; pchart defects*_YEAR_MONTH / subgroupn = population totpanels=1 DISCRETE skiphlabels=1 markers yscale=percent tests=1 to 4 testnmethod=standardize CTEXT=BLACK CTESTS = (1 BLACK 2 blue 3 ORANGE 4 GREY) test2run=8 TESTLABEL1="*" TESTLABEL2="8 pts on 1 side" TESTLABEL3="6 point trend" TESTLABEL4="alternating pattern" ; RUN; *now ghost out using _exlim_ and _comp_; ******************************; proc shewhart data=month4vp1 ; pchart defects*_YEAR_MONTH / subgroupn = population nochart outhistory=hist4 outtable=tab4 ; run; data tab4; set tab4; if _EXLIM_ ne '' then _COMP_='N'; else _COMP_='Y'; keep group _COMP_; run; data history4; merge hist4 tab4; run; ;proc shewhart data=month4vp1 history=history4; pchart defects*_YEAR_MONTH / subgroupn = population totpanels=1 DISCRETE skiphlabels=1 markers yscale=percent tests=1 to 4 testnmethod=standardize CTEXT=BLACK CTESTS = (1 BLACK 2 blue 3 ORANGE 4 GREY) test2run=8 TESTLABEL1="*" TESTLABEL2="8 pts on 1 side" TESTLABEL3="6 point trend" TESTLABEL4="alternating pattern" ; RUN;

Rodcjones · ‎07-23-2017

I am seeking to implement and automate (to the extent possible) the guidelines regarding calculating and extending baseline centerlines in SPC charts as descrbed in the The Health Care Data Guide: Learning from Data for Improvement by Lloyd P. Provost & Sandra Murray, p. 123-125. The problematic paragraphs are <<If it is desirable to extend the limits after they are calculated, any points affected by special causes should be removed from the baseline and the limits recalculated. The limits should only be extended when they are calculated using data without special causes . . . When recalculating the limits so that they can be extended, the special cause data should not be used, but it is usually desirable to leave the data points affected by special cause on the chart. One way to do this is to "cause" or "ghost" the data points affected by the special cause . . . . "Ghosting" here means leaving the data visible on the graph but excluding it from teh calculation of the mean and limits. The limits revised by this technique will reflect only common cause variation in the process and may now be extended into the future.>> I am comfortable generating limits, extending baselines, and displaying the charts with SAS. And I can think of ways to "ghost" out special cause points when calcuating a mean (for example) and then using that value to overwrite what is in a Limits data set. But that right now it is a clunky and manual process. I wanted to pose the question whether any fellow users had come up with efficient ways to take baseline calculations and remove special cause from centerline and limits calcuations but retain the point in graphic output. I'm pasting some of the relevant code (in this case for a p chart) just for the step of generating the baseline statistics if it helps with context. Thank you! ods output crosslist=MONTH&run; PROC FREQ DATA=&ds (where=( DATEPART(DISCH_DATE_TIME) GE "&start"D AND DATEPART(DISCH_DATE_TIME) Le "&end"D)) ; TABLES _YEAR_MONTH*&v/CROSSLIST ; &subset; run; data month&run.V; set month&run; if &v=" &value"; if _year_month ne ''; run; 　 data month&run.p; set month&run; if F_&v="Total"; if _year_month ne ''; run; proc sql; create table month&run.vp1 as select month&run.v._year_month, month&run.v.frequency as &v label="&label (N)", month&run.p.frequency as Population label="Population", month&run.v.rowpercent as Percentage label="&label (%)" from month&run.v right join month&run.p on month&run.v._year_month=month&run.p._year_month; QUIT; 　　 goptions reset=goptions ; ods graphics on/ imagefmt=png reset iMAGENAME="&v &period" height=4.5in border=off ; title; symbol v=dot width=2; ods listing gpath="\\Data"; ;proc shewhart data=month&run.vp1 ; pchart &v*_YEAR_MONTH / subgroupn = population ODSTITLE= "&chart of &label, &period by &unit" totpanels=1 DISCRETE skiphlabels=1 markers yscale=percent tests=1 to 4 testnmethod=standardize CTEXT=BLACK CTESTS = (1 BLACK 2 blue 3 ORANGE 4 GREY) TESTLABEL1="*" TESTLABEL2="9 pts on 1 side" TESTLABEL3="6 point trend" TESTLABEL4="alternating pattern" ; ; label &v ="&LABEL (%)"; RUN;

Online Status	Offline
Date Last Visited	‎02-13-2024 01:50 PM

Re: Has the distribution of values in categorical variable been stable...

Has the distribution of values in categorical variable been stable or ...

Re: Interpretation of Zelen's Exact Test for homogeneity of odds ratio...

Interpretation of Zelen's Exact Test for homogeneity of odds ratios

Re: Creating a positive-negative bar chart

Creating a positive-negative bar chart

Re: Counting consecutively-dated observations of a Yes value with attr...

Re: Counting consecutively-dated observations of a Yes value with attr...

Re: Counting consecutively-dated observations of a Yes value with attr...

Re: Counting consecutively-dated observations of a Yes value with attr...

Re: Has the distribution of values in categorical variable been stable...

Re: Has the distribution of values in categorical variable been stable...

Re: Has the distribution of values in categorical variable been stable...

Re: Has the distribution of values in categorical variable been stable...

Re: Has the distribution of values in categorical variable been stable...

Best practices for integrity checks & halting a scheduled EG process w...

Does an oversized SAS EG project log prevent a scheduled task from run...

Re: Macro variable not resolved if created within a macro program, usi...

Macro variable not resolved if created within a macro program, using m...

Re: LAG and RETAIN not quite doing it -need to "ignore" variables from...

LAG and RETAIN not quite doing it -need to "ignore" variables from con...

Possible to open a program or project from a network folder in SAS Stu...

Re: Retrieve file size, create time, and last modified date of a file ...

Retrieve file size, create time, and last modified date of a file with...

Re: Best practices for integrity checks & halting a scheduled EG proce...

Best practices for integrity checks & halting a scheduled EG process w...

Does an oversized SAS EG project log prevent a scheduled task from run...

Re: How to "ghost" points in calculating baseline limits & centerline ...

Re: Suspend or disable tasks in EG 6.1

Re: Suspend or disable tasks in EG 6.1

Re: How to "ghost" points in calculating baseline limits & centerline ...

How to "ghost" points in calculating baseline limits & centerline in P...