FIRST STEP - ADDITIONS TO THE CONFIGURATIONS FILE (CONFIG FILE) SECOND STEP Creating the to send

Transcription

1 Using SAS to Reports and Results to Users Stuart Summers, Alliant, Brewster, NY ABSTRACT SAS applications that are repeatedly and periodically run have reports and files that need to go to various end users. SAS is able to use Simple Mail Transfer Protocol (SMTP) to send completion notices and logs, lists and any other reports as attachments. With three lines in the config file you can set up the code in your process to your results to individuals and/or distribution lists. This paper will provide the lines to add to the config file as well as an example of how to set up your code to send the s. INTRODUCTION We have all been there. You create, test and release an application using SAS that creates files and various reports and listings for your clients and/or end users and they want to get notifications via with their reports as attachments in the . The application is run perhaps monthly, weekly, daily or even at odd hours of the day or night. Instead of having someone monitor when the application completes and sending out the , SAS is able to use Simple Mail Transfer Protocol (SMTP) to send the out with whatever reports and information that you want to give your users. This paper will lay out the initial set up and the steps/code that can be included in your application to your job to send the for you. 1

2 FIRST STEP - ADDITIONS TO THE CONFIGURATIONS FILE (CONFIG FILE) This step needs the assistance/cooperation of your Systems Administrator. The following in an example of what options are needed in the config file (by your Sys Admin person): - host testhub.nesug.com - sys smtp - port 24 The first line is the domain name for the SMTP server for your site. The second one is obvious since we are telling SAS to use SMTP to send s. The last one is the port that SAS needs to connect to in order to send the . SECOND STEP Creating the to send Everyone knows the parts of Who is supposed to get it ( To:, CC:, BCC: ), Who is sending it ( From ), the heading/subject of the , any attachments, and the main body which has the text of the . EXAMPLE CODE /* */ /* Use ODS to set up the html reporting that will be attached to the */ /* */ ods html body = '/home/ssummers/nesug/nesug_install_report.html'; proc means data=nesug.nesug_install n nmiss min max mean; title1 j=left "Alliant "; title2 j=left "Data Licensing Install - Variable Means Report"; title3 j=left "Produced for client: NESUG "; title4 j=left "Metrics report on Consumer Attributes for Client Evaluation (2 percent cross section of total file)"; Footnote1 j=left height=8pt "Confidentiality Note: This report, including any attachments,is intended only for the person or entity to which it is addressed and may"; Footnote2 j=left height=8pt "contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of"; Footnote3 j=left height=8pt "the report or the information herein by someone other that the intended recipient, or an employee or agent responsible for delivering"; Footnote4 j=left height=8pt "the report to the intended recipient, is prohibited. If you have received the report in error, please call Alliant, LLC at (845) "; footnote5 j=left height=8pt "and destroy the original report and all copies."; ods html close; /* */ /* Now set up and send the with the SAS log, SAS list and the HTML report */ /* as attachments */ /* */ filename sendmail Subject="NESUG Basic Example" Attach=("/home/ssummers/nesug/ _example.log" "/home/ssummers/nesug/ _example.lst" "/home/ssummers/nesug/nesug_install_report.html"); data _null_; file sendmail; name='ssummers@alliantdata.com'; sender='production@alliantdata.com'; put '!em_to!' name; put '!em_from!' sender; 2

3 put '!em_sender!' sender; put 'This is an example of a simple message with three attachments:';; put 'The SAS log, the SAS list and an HTML report';; put /'A two percent cross_section of consumer attributes from the Alliant Database is available for evaluation as an install file.';; put /'Attached is a metrics report on some of these attributes'; put //; put '!em_send!' ; put '!em_abort!'; BREAKING (DOWN) THE CODE It s pretty much straight forward code. The FILENAME statement will let the system know we are setting up an and what goes in the subject line. I ll get to attachments soon. The rest is just writing code to write records to the file you just set up. Keywords to be aware of (And yes, all of these keywords are supposed to be bracketed by exclamation points):!em_to! identifies would is supposed get the (the To: line)!em_from! and!em_sender! identifies who it is from (the From: line) and who the sender is. If they are not same then the s with put Sender ON BEHALF OF From in the From: line. The PUT statements after this contains the text body of the . With the text lines use two semi colons at the end to start the next text line on the line (single spaced). If you don t, the next line will be tacked on to the end of the one above it. Use / to insert a blank line above the text ( // will put two blanks above if you need to).!em_send! Everything is in place, so send the ;!em_abort! This is what I call a safety valve in that it prevents a second copy of the to go out after the DATA step is finished. 3

4 PROCESS AS A MACRO If you a process that runs on a regular (or sometimes irregular) schedule consider adding the as a macro. It is also a possible approach if the s differ only by report names. The basic logic is similar to the prior code example. %macro nesug_ (client=nesug, qcreport=, client_file=, _list=ssummers ); /* */ /* Macro: /a21/sas/macros/nesug_ .sas */ /* Author: Stuart Summers Date: 07/25/2012 */ /* Function: Macro example of using SAS to files */ * */ /* Macro Parameters: */ /* client - Name and/or abbreviation of client */ /* qcreport - directory and file name of audit report */ /* client_file - directory and file name for file to */ /* return to client */ /* _list - recipient list for alert */ /* */ %put Set up list ; %put ; data _null_ ; call execute("data _list; "); call execute("length temp_name $ 32; "); call execute("input temp_name "); call execute("cards; "); call execute("& _list "); call execute("; "); call execute(" "); /* Send print of recipent list to */ /* SAS listing for manual confirmation */ proc print data= _list; %put Send out alerts ; %put ; /* Set up subject and attachments */ /* for file */ filename sendmail Subject="Data Contribution - ETL Transaction Completion: %trim(&client)" Attach=("%cmpres(&qcreport)" );; /* Build out recipient address */ /* for em_to */ /* set up from and sender addresses */ data _null_; set _list end=lastobs; name=quote(trim(cats(temp_name,"@alliantdata.com"))); 4

5 file sendmail; put '!em_to!' name; put '!em_from!' sender; put '!em_sender!' sender; /* Only need to create message */ /* once so only create it on the */ /* first obs */ IF _N_=1 THEN DO; put 'This is an example of a simple message'; put 'generated and issued using SAS'; put /; put 'Skipping two lines by add /'; put //; /* add the em_send for each recipient */ /* for em_to */ /* set up from and sender addresses */ put '!em_send!'; if lastobs=0 then return; /* loop back to get next recipient */ else put '!em_abort!'; /* send abort flag (only send once)*/ %exit: %mend nesug_ ; CONCLUSION Automating the distribution of reports for processes that run on a regular basis is an obvious time saver. SAS provides a fairly easy process tool for that purpose. REFERENCES: SAS 9.1 Language Reference: Dictionary. Cary, NC: SAS Institute Inc. ACKNOWLEDGMENTS SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. CONTACT INFORMATION Your comments and questions are valued and encouraged. Contact the author at: Stuart Summers Senior Data Analyst Alliant 301 Fields Lane Brewster, NY Work Phone: ext. 242 Fax: ssummers@alliantdata.com Web: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 5