About H

H · ‎01-24-2017

Correct, the Wizard will save the PROC IMPORT code in a file. I am familiar with this option/procoss, though in case a SAS Inc. person is reviewing these messages, I wanted to voice my dislike in the change where it is not displayed in the log that seed like if happened around 9.3. Now, back to my actual problem... So check this out: The source file of interest is saved in my personal server workspace, so no one else should ever have access to the file. That can be confirmed by examining the file properties. The above issue only happens to certain files. The other 95% of files I want to import are fine and never have these issues. I have tried many things, such as renaming the source file and Cutting-N-Pasting its content into a new file, but whatever SAS doesn't like about the file sticks with it. The following is even more interesting. So the piece of code generated from the PROC IMPORT works when it is intitially created. Though when I go to use the generated code (which you reference) it won't work. Though, if I just retyped the code verbatim in my Editor window it will work? Also, if I use the Import Wizard again that will work, but not its generated code, but reruning the originally produced code PROC IMPORT doesn't work. So Imporrt wizard code works the first time when creating it, then not again, cut-N-pasting doesn't work. but retyping it in its entiety works as well as rerun the import wizard. Work = importing the file without the Log warning above???????

H · ‎01-23-2017

P.S., I was not a fan of when SAS removed the PROC IMPORT code out of the Log, now it only prints it in the Log if there is an issue. In prior SAS versions it printed the generated PROC IMPORT code in the log everytime and I could Cut-N-Paste it into my editor window for future use.

H · ‎01-23-2017

I come across this error about once or twice a year for different projects. So I am going to try and understand its possible source. I am trying to import an excel file '.xlsx'. I use the import wizard and everything is fine. I am currently going through a data cleaning phase, so when I notice a data anomaly or a formatting issue, I correct the source document. Then when I go to use the code from the import wizard again to check that the source issue has been fixed I get the following error. Examples of source document fixes that I am making are trivial (e.g., changing yes to Yes, etc.). 239 PROC IMPORT OUT= WORK.NIV_bust 240 DATAFILE= "X:\Pediatrics\NI V Asthma\Data\2017 January 240! Data 241 Files\Final NIV Dataset Jan_17.xlsx" 242 DBMS=EXCEL REPLACE; 243 RANGE="'Final NIV Data$'"; 244 GETNAMES=YES; 245 MIXED=NO; 246 SCANTEXT=YES; 247 USEDATE=YES; 248 SCANTIME=YES; 249 RUN; ERROR: Unable to open file X:\Pediatrics\NI V Asthma\Data\2017 January DataFiles\Final NIV Dataset Jan_17.xlsx. It does not exist or it is already opened exclusively by another user, or you need permission to view its data. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE IMPORT used (Total process time): real time 0.07 seconds cpu time 0.03 seconds To try and pre-empt possible questions, I am using SAS 9.4 probably maintenance 1 or 2 and I am also closing the excel file before trying to use the proc import code for the second time. The only way I can get the dataframe to re-import is to go through the whole PROC IMPORT process all over again, and it works with no problem. I commonly maintain a master data fille for a project in excel and reuse PROC IMPORTS code, similarly as mentioned above without any issues. So this is a sporadic issue.

H · ‎12-28-2016

I went with Reeza's first solution, which works nicely given my coding context. Thank you.

H · ‎12-27-2016

Thank you Roger and Reeza. Reeza, I am on my way out the door, but your reponse appears to work and is exactly what I was desiring. GRAND in deed! I will mark the post solved tomorrow morning after I verify that it works in my actual context and that I have no more questions. Much appreciation!

H · ‎12-27-2016

Well, I believe I will need someone to actually use my toy dataset, in that I appear inept in this area. I blindly jammed my vars into the above code and got a very long data set to kick out what I would imagine code be created in a single PROC SQL command. And I still have no idea how to link this to a '%Let' statement??? I am going to need someone to hold my hand throughout this post, since as I mentioned I am walking around with no compass or relevant knowledge! Thanks you.

H · ‎12-27-2016

Thanks for the quick input. I am in the process of reviewing it. Though, I wanted to mention that I am absolutely terrible with MACROS and fairly inexperienced with PROC SQL.

H · ‎12-27-2016

Hello, I am excited to get some input. I have a two part (sequential) question. Part 1: I would like to run a PROC PRINT which has a WHERE statement based on a function, see following: PROC PRINT DATA=SAS_Comm; WHERE MAX value for X; RUN; Part 2: I would like to create a "%LET", kind of based on the PROC PRINT result. I get that the answer to this can probably be better derived from a different procedure, if so, I would happlily use that (e.g., PROC MEANS instead of PROC PRINT), though I still need the PROC PRINT part in to work as a quality assurance measure in my coding. So what I am looking for is, I have two variables X and Y. So I want the value for Y for the Max X. And in particular, I want that Y value to be inserted into '%LET Z = 98;. data SAS_Comm; input X Y; CARDS; 1 4 2 9 9 98 5 2 0 0 6 8 2 7 ; So all together the final code would be a functional form of the following: DATA SAS_Comm; INPUT X Y; CARDS; 1 4 2 9 9 98 5 2 0 0 6 8 2 7 ; PROC PRINT DATA=SAS_Comm; WHERE MAX value for X; RUN; %LET Z = 98; P.S., Let us assume that there is only one unique Y associated with each X. Thus, the code won't kick out a row with X = 9; Y=98 and say X = 10; Y=78. Let me know if I need to clarify any part of this post.

H · ‎11-09-2016

Admittedly, I always forget the answer to this question and have to search through old code. Question: How do I create a list of variables to run one at a time through a procedure. I want to run the below piece of code once for each individual variable. So it will run 23 models. Y= Dependent Variable X1-X23: Independent Variables PROC LOGISTIC DATA = Dataset_Name ALPHA=0.002; CLASS Y; MODEL Y (EVENT="1") = X1 / LACKFIT FIRTH; RUN;

H · ‎07-26-2016

Alright, I figured out the font question. Thought if anyone has an approach to make my binary outcome group gray and light gray on the graph I would be 1 step closer to the output I had been desiring. proc template; define statgraph mosaicPlotParm; begingraph; layout region; MosaicPlotParm category=(time epab_13) count=Frequency / colorresponse=epab_13 name="mosaic" colormodel=twocoloraltramp labelattrs=(size=12pt) valueattrs=(size=12pt); endlayout; endgraph; end; run;

H · ‎07-26-2016

Below gets me closer to my desired output. I would like to increase the label's font size and attr marker (which are words) font size. I am getting confused since I use layout region and most examples I see are layout overlay, and I don't know how to incoporate both. proc sort data=epa_rev; by descending epab_13 time; run; proc freq data=epa_rev order=data; tables time*epab_13/ norow cellchi2 expected stdres crosslist; ods output CrossList=FreqList(where=(Expected>0)); run; /* color by response (notice that PROC FREQ reverses Y axis) */ proc template; define statgraph mosaicPlotParm; begingraph; layout region; MosaicPlotParm category=(time epab_13) count=Frequency / colorresponse=epab_13 name="mosaic" colormodel=twocoloraltramp; endlayout; endgraph; end; run; proc sgrender data=FreqList template=mosaicPlotParm; format time time_fmt.; FORMAT epab_13 epab_1_fmt.; LABEL epab_13 = ''; LABEL TIME = "Time (days)"; run; P.S., I would prefer the colors to be black and white, but currently I can just save this output on the gray scale as a work around.

H · ‎07-08-2016

I just reviewed the webpage and this should definitly help (given that I can figure it out). I am gonna move on to something else until I have more time to come back to this and determine how to use all dark grays for epa_b = 1 and light gray for its complement. Thanks and I will likely have follow-up questions early next week.

H · ‎07-08-2016

Thank you. I will examine the link and update you all on my questions. Though, I have entered the world of the ODS Graphics Editior! It seems like the right place, but perhaps it only augments the graph and won't let me manipulate its current content? Any feedback on how the Editor may help?

H · ‎07-08-2016

I have created a MosaicPlot using the below code. Though, I would like to change the tile colors, say pink = light gray and blue = dark gray. I can go into the images properties after copying it, but my options are horrific: black/white or gray/gray. Also I added the line of code that Rick suggested on another post but I still get the obligatory title on top (https://communities.sas.com/t5/ODS-and-Base-Reporting/Outputting-a-graph-from-PROC-FREQ/m-p/226441/highlight/true#M14375). Dropping that would be great. Also bolding labels and increasing font would be nice. Thank you. PROC FORMAT; VALUE epab_1_fmt 1 = "Confident" 0 = "Not Confident"; VALUE time_fmt 1 = "0 Months" 2 = "3 Months" 3 = "6 Months" 4 = "12 Months"; RUN; ODS GRAPHICS ON; ods select MosaicPlot; title; /* clear the title */ %modtmplt(options=replace, template=Base.Freq.Graphics.MosaicPlot, steps=t); PROC FREQ DATA=EPA_rev; TABLE (epab_1)*time / TREND MEASURES CL PLOTS=MosaicPlot; LABEL epab_1 = "EPA 1"; TEST SMDRC; EXACT TREND / maxtime=60; FORMAT epab_1 epab_1_fmt.; Format time time_fmt.; RUN; ODS GRAPHICS OFF;

H · ‎03-10-2016

ods graphics on ; proc glm data=dka_please PLOTS=all; model HOURS_PH_NORM = total_fluid INTITIAL_PH; run; ods graphics off; Code is above for 2 IV model. In the final graph I would like to use labels to get rid of "_" and add units to variable names. Side note, your Sim book was great Rick.

Online Status	Offline
Date Last Visited	‎02-15-2021 03:25 PM

Re: PROC QUANTREG BY STATEMENT with ODS OUTPUT

Re: PROC QUANTREG BY STATEMENT with ODS OUTPUT

PROC QUANTREG BY STATEMENT with ODS OUTPUT

Randomization Scheme

Re: PROC HPSPLIT: How to force a variable into a decision tree (SAS 9....

Re: Date var getting converted to BEST12

Re: Date var getting converted to BEST12

Re: Date var getting converted to BEST12

Re: Date var getting converted to BEST12

Date var getting converted to BEST12

PROC HPSPLIT: How to force a variable into a decision tree (SAS 9.4)

Re: Date var getting converted to BEST12

Re: Date var getting converted to BEST12

Re: Convert PROC GENMOD BAYES model to PROC MCMC

Re: Convert PROC GENMOD BAYES model to PROC MCMC

Re: PROC QUANTREG BY STATEMENT with ODS OUTPUT

Re: Excel Import

Re: Excel Import

Excel Import

Re: WHERE statement based on function

Re: WHERE statement based on function

Re: WHERE statement based on function

Re: WHERE statement based on function

WHERE statement based on function

Varlist List for Repeating Procedure

Re: Mosaic Plot (Proc Freq) - changing tile colors

Re: Mosaic Plot (Proc Freq) - changing tile colors

Re: Mosaic Plot (Proc Freq) - changing tile colors

Re: Mosaic Plot (Proc Freq) - changing tile colors

Mosaic Plot (Proc Freq) - changing tile colors

Re: Custom Scatter Plot