Hi: I am at SAS Global Forum and not on my machine right now. It looks to me like MWIMAGE is a dynamically generated HTTP reference for a TIF file and MWIMAGE2 is a dynamicallly generated URL that is meant to execute a PHP file. Remember that when you GROUP on MWIMAGE and MWIMAGE2, that only the first occurence of the group will have a value -- the other rows for that group will have a blank value for MWIMAGE and/or MWIMAGE2. Your best bet for a quick resolution is to contact Tech Support. They can help you figure out the best way to do what you want. Even though my example was a static URL, by the time your PROC SQL is finished, your column values are essentially static URLs. If I have a chance after SAS Global Forum, I'll try to work up a dynamic example with PROC REPORT. If you need help quickly, however, Tech Support can help you in a more timely fashion. cynthia ... View more

Hi! A SAS Catalog is a special kind of SAS file. If, for example, you ever use SAS macro language to create a macro program, or create SAS formats or create SAS/Graph output, then SAS catalogs are being used behind the scenes. If you follow this path in the SAS Help files: Contents --> Using SAS Software in Your Operating Environment --> Glossary --> pick your operating system --> Glossary In the glossary, you will find a basic description of a SAS catalog and a SAS catalog entry. For example, here is the Windows glossary entry for catalog: SAS catalog a SAS file that stores many different kinds of information in smaller units called catalog entries. A single SAS catalog can contain several different types of catalog entries. See also SAS catalog entry. SAS catalog entry a separate storage unit within a SAS catalog. Each entry has an entry type that identifies its purpose to SAS. Some catalog entries contain system information such as key definitions. Other catalog entries contain application information such as window definitions, Help windows, SAS formats and informats, macros, or graphics output. See also entry type. A SAS catalog will have different operating characteristics (for example, if you needed to allocate them on MVS or z/OS), so before you change or move a SAS catalog, you should be careful to read about how your operating system stores catalog information. If you need more help with SAS catalogs, your best bet is to contact SAS Tech Support for help. http://support.sas.com/techsup/contact/index.html cynthia ... View more

Hi: The TITLE (and FOOTNOTE) statement accepts standard SAS/Graph options for justification and bolding, such as: [pre] title bold j=l 'Left Justified' j=c 'Center' j=r 'Right Justified'; OR title2 bold j=l 'Left Justified' c=red j=c 'Center' c=blue j=r 'Right Justified'; [/pre] BUT, these title statements may work differently in different destinations. For example, if you use LISTING destination, these text strings will not have differing justification, if you use the MSOFFICE2K tagset, each of these text strings would be on a different line, but in the PDF destination, then the text strings are justified appropriately. However, SAS titles and footnotes already have BOLD turned on in the style template, so I am curious what destination you are using where the titles are NOT bolded. Since SAS Title statements are global statements, they are not affected by Proc Report, Proc Tabulate, etc. The SAS title as shown above would work in a PROC MEANS step as well as a PROC REPORT step. It is the destination in ODS that determines how the title will be rendered. And, of course, there is no style in the LISTING destination. You can use in-line formatting in the SAS TITLE statement, but should not need to to accomplish BOLDing or differing justification. For more help with SAS Titles and using SAS/Graph options in the title (such as Bold, Italic, Color, Font, Height), consult the SAS/Graph documentation. If you need more help, the Tech Support FAQ has some information about using these options in the SAS TITLE or FOOTNOTE. Good luck, cynthia ... View more

Hi: I am at SAS Global Forum right now and not on my machine. But I -do- have some memory of a Tech Support Note involving ANCHOR= and PDF. For a quick response to this question, your best bet is to contact Tech Support. cynthia ... View more

Hi... And the PROC REPORT (to which you have an allergy) would also work with the format approach: DEFINE SEX / DISPLAY STYLE(COLUMN)={preimage=$seximg.}; the only warning is that the format value may have to change depending on what your ultimate destination may be: HTML -- location where image will be located WHEN HTML page is LOADED (possibly a location on a web server machine): PROC FORMAT ; VALUE $seximg "F" = "http://webserver/dir/female.gif" "M" = "http://webserver/dir/male.gif"; RUN ; PDF/RTF -- location where image will be located WHEN output file is CREATED: PROC FORMAT ; VALUE $seximg "F" = "c:\temp\female.gif" "M" = "c:\temp\male.gif"; RUN ; ;-) cynthia ... View more

Hi! I don't think that's entirely true -- the folks who support BI -do- participate in these forums -- there's a stored process forum and an EG forum and if you look, both of those forums do get postings about the BI platform that are answered by these people. However, a lot of times, a question has so many dependencies on which piece of the BI platform you're talking about or raises issues (as this one does) about how Access Controls work in SAS Management Console to control resources, that's it's NOT a simple question with a simple answer. When you install and configure the Enterprise Intelligence platform/BI Platform, you have to set up your users and groups in the metadata. You control access to the data, to the libraries, to their ability to access stored processes. I do not recall a specific way to tell which -users- are "registered" to access particular client applications like Web Report Studio or EG or the SAS add-in -- it was my understanding that the model was that you set security on the resources available to the client application -- not to the client application itself. In my mind, this is a question best answered by Tech Support -- where they can direct the question to somebody who really KNOWS how the security model and access controls work. cynthia ... View more

Hi! Remember that you need to provide a way for the macro processor to tell when the end of the macro variable name has been reached. so if you had this: &lib..&dsn then the first . will signal the end of &lib and the second . will be inserted after &lib resolves. so if &lib is SASHELP and &dsn is CLASS then &lib..&dsn would resolve to SASHELP.&dsn which would resolve to SASHELP.CLASS So in your case, you should do: &position._t also, you were probably typing fast, but I thought, just in case, I'd mention that since your macro statement has %macro LOC(position), then the correct invocation would be: %loc(xyz) good luck, cynthia ... View more

Hi: I am not currently on a computer with SAS or my sample library; however, you can do a search on support.sas.com FAQ for further information. One thing to try is using the ASIS=ON style attribute, which preserves leading spaces: define month / sum style(column)={asis=on}; The other thing to try is to pad the beginning of the string with a non-breaking space -- so, if ODS ESCAPECHAR is set to '~', then the non-breaking space would be ~_ (tilde underscore). mon= "~_2ND QUARTER "; You would need an ODS ESCAPECHAR statement in order for this to work: ODS ESCAPECHAR='~'; However, with a proportional-spaced font, there is NO guarantee, that the single non-breaking space will be EXACTLY under the 2nd character of the month name above. In a mono spaced font, the letter 'i' takes the same amount of space as the letter 'w' (which is why it looks OK in LISTING), but in a proportional spaced font, the letter 'J' for June or July, could take up less space on the line than the letter 'A' for August. A third option is to use the INDENT= style attribute on a CALL DEFINE statement for the row that contains the quarter information. For the best approach in this situation, you best bet might be to contact Tech Support. Good luck. cynthia ... View more

Hi: I am not on my computer right now, so I don't have access to SAS or to my library of sample programs; however, what you want to do can be accomplished with CALL DEFINE. Look in the support.sas.com FAQ for information on CALL DEFINE. In addition, the PROC REPORT documentation has an example of using the URL argument for CALL DEFINE. In short, what you have to do will be something like this compute third; call define(_COL_,'URL','code to set URL'); endcomp; OR compute third; myurl= call define(_COL_,'URL','myurl'); endcomp; Tech Support can help you figure out the exact syntax you need. Good luck! cynthia ... View more

Hi: NEWFILE= did not work for PDF in SAS 8.2 (or it was experimental). So, SAS Macro would be the correct way to create your files. Since it looks like you are on a mainframe system, I would also recommend that you convert your program to use the FILE PRINT ODS syntax, instead of FILE PRINT and PUT statements. Your best bet for a quick answer to this question is to contact Tech Support. They can help with macro code AND with the syntax for ODS. The reason I suggest this is that PUT _PAGE_ in SAS 8.2 did not work exactly the same way with ODS as it did to the OUTPUT window or LISTING FILE (or SYSOUT). For information on contacting Tech Support, go to: http://support.sas.com/techsup/contact/index.html cynthia ... View more

Hi! I knew that you knew that! 😉 Questions that don't fit other categories generally turn out to be Tech Support questions. I have not actually done the ETL tutorial for 2 reasons 1) my hard drive crashed and ate my install of ETL Studio (really) and 2) the image that I've been using for course development has DI Studio (the successor to ETL studio). Also, since I've been travelling the stored process road I haven't concentrated that much on ETL. I suspect that the tutorial is either making an assumption about your particular install of SMC (SAS Mgt Console) and ETL OR, it was instructing you to associate an SMC folder with a location on your local PC -- going through the metadata. But as I said, I really don't know for sure how this particular tutorial works. The difficulty with BI questions on the forum is that everybody's particular installations will be different depending on the PLAN.XML for their installation. If you had a single user install of the SAS Enterprise Intelligence Platform on your personal PC -- which is one possible configuration -- then folders on your personal PC would actually be the storage location for the SAS metadata.... but you would still have to get to them via SAS Management Console or ETL or Information Map Studio or OLAP Cube Studio, etc. Good luck! cynthia ... View more

Hi! This is really not an ODS or BASE SAS Reporting question. Since you are using the SAS Enterprise Intelligence Platform and are doing the ETL tutorial, you have moved outside the realm of BASE SAS and into the Business Intelligence world. Even though the tutorial instructed you to create those files on your local computer, I believe that almost everything you do in ETL has some involvement with the metadata server. So, your best bet for a quick response is to contact Tech Support on this one. Good luck, cynthia ... View more

EG is way cool for registering stored processes using the Stored Process Wizard -- but I consider EG to be the "automated" way to create your SP from either a task or an entire project or even from existing code. When I create stored processes for the Stored Process class, however, I use good, old-fashioned DMS and then I manually register the SPs with SAS Management Console. Almost all of the SPs that I write for class are PROC REPORT examples, since that is currently something that you cannot do with EG. In a regular BI configuration, there is already a location built in for your SAS macro library and your "code snippet" collection and your format library. Macro programmers do have to make a few changes to their macro code -- but the changes are minor and they should be able to convert their legacy programs to SPs fairly easily. This is the subject of one of my SGF presentations this year. Of course, my macro program won't be as complex as those used by most Pharmas, because I only have 50 minutes to talk. At any rate, I don't think that Stored Processes are difficult to write. What was difficult for me was the "paradigm shift" from the DMS way of doing things to the BI way of doing things. But since I'd already gone through that same kind of shift with SAS/IntrNet, it wasn't such a huge change. One of the notes in my SGF paper is the observation that "Stored Process Consumers Don't F3" -- and I'm just hoping that there are enough folks in the audience who actually use F3 enough to get the lighthearted joke. Of course, Stored Process AUTHORS might still use F3 -- but there's a real difference between how you test and debug the SP, as an author, and how the end user or SP consumer will experience and execute the SP. For the really heavy duty SAS programmers, I agree that they may not do more than use EG in order to use the Stored Process Wizard. In class, we tell students that they don't actually have to open SAS to modify their programs and sometimes, I challenge them to make the required code changes just using Notepad -- which is an interesting exercise because it reinforces that in order to test their code, they have to break out of their dependency on DMS and actually test in the client applications. But SAS in batch (via DMS or via command programs) still has a place in the BI platform -- there's no reason to put all of the nightly number-crunching and file updating into Stored Processes -- these processes might be better turned into DIStudio jobs or even kept as batch SAS jobs to update the appropriate files. Then you can let your SPs zip in and out of the data to do the on-demand reporting against the updated files. So that's my 2 cents plus your 2 cents and we still can't go to Starbucks on that! ;-) cynthia ... View more

Hi: One other thing you could try is this: In EG Tools--> Options --> Results General Make sure that ONLY HTML is checked under Results Formats Then under Tasks --> Custom Code check insert custom code before task and click EDIT Then type this into the custom Code window:[pre] ods _all_ close; ods msoffice2k file='c:\temp\Shop1.xls' style=egdefault newfile=bygroup; [/pre] Click SAVE in the code window. Then click EDIT for the After code choice and type this: [pre] ods _all_ close; [/pre] Then click SAVE to close this custom code window. Click OK to close the Options window. Then choose your Data for the shops and choose Describe --> List Data Choose your variables for the List data task (or some other task).Be sure to use your SHOP variable as the "group by" variable. (so that SAS generates a BY statement for BY SHOP. You are not REALLY creating an Excel file, but you ARE creating an HTML file using MSOFFICE2K (Microsoft specific HTML) that Excel can open. EG will only show you the first file that you create in the project window (Shop1.xls), but, if you go to the c:\temp directory (outside of EG), then you should see all your SHOP files there -- SHOP1.xls thru SHOP??.xls that you can then open with Excel. Now, this does not get them into one workbook, but into multiple workbooks using the NEWFILE= logic. And, of course, after you're done, you have to remember to go back and clear out the custom code nodes. At this point, you'd probably be just as well off to build a code node to either use PROC EXPORT or the LIBNAME Excel engine to create a single workbook with multiple sheets in a code node. Here's the Proc Export method:[pre] proc export data=sashelp.shoes(where=(Region EQ 'Pacific')) outfile= "exp_method.xls" dbms=excel2002 replace; sheet="Pacific"; run; proc export data=sashelp.shoes(where=(Region EQ 'Asia')) outfile= "exp_method.xls" dbms=excel2002 replace; sheet="Asia"; run; [/pre] And here's the LIBNAME method: [pre] libname WrkBk excel 'lib_method.xls' ver=2002 data WrkBk.Asia; set sashelp.shoes; where region = 'Asia'; run; data WrkBk.Pacific; set sashelp.shoes; where region = 'Pacific'; run; libname WrkBk clear; [/pre] You will need SAS/Access for PC file formats for either of these methods to work. Or, if you're building a code node anyway and you want to create a workbook for each shop, you could just put this ODS code into an EG code node: [pre] ** close the ODS destination that EG opens by default; ods _all_ close; ** create an MS Office HTML file -- and "fool" the Windows registry by; ** giving the file an XLS extension. When you double click on the file; ** FROM WINDOWS EXPLORER (not EG), you will launch Excel; ods msoffice2k file='c:\temp\shop1.xls' style=egdefault newfile=bygroup; *** your procedure of choice with; by shop; run; ods _all_ close;[/pre] Good luck, cynthia ... View more

Selvi: I'm glad that you're learning a lot about SAS. I think that SAS is very cool, too and I have fun with it. I am constantly amazed at the business/information problems that can be solved using SAS. If you want to contact me, my email is cynthia.zender@sas.com -- although I am about to be out of the office for training committments and the SAS Global Forum. So, if you need immediate help with your report, you should contact Tech Support. cynthia ... View more