Table of contents:

• %qupcase, which & got masked (2 messages)
• %qupcase, which & got masked ( typos corrected, please see this one) (2 messages)
• %str and & (3 messages)
• & and %str, another question (2 messages)
• 10 High performance PROC of new SAS (17 messages)
• Anyone want some free SAS Press books?
• Automatic reply: Proc Report, Across, style(column) tagattr
• Block Diagonal Covariance Matrix for GLMM
• Chinese Characters (2 messages)
• Computer Advice (5 messages)
• Data import (4 messages)
• FW: note: SAS/IML incompatible with latest releases of R
• Free SGF take-out videos this year
• Fwd: opening data set error
• In search of better way to exploit the proc means (7 messages)
• Is this something that would be useful on sasCommunity.org? (8 messages)
• Jegadeesh and Titman (Momentum) SAS Code Help (5 messages)
• Job: 3-month full-time SAS Administrator (Toronto)
• Macro variables from a dataset. (3 messages)
• Michigan SAS Users Group 1-Day Conference in May
• NLMIXED Versus Proc Mixed (2 messages)
• NLMIXED versus PROC MIXED (3 messages)
• Need Help Recalculatinng Vallues in One Dataset Based on Values in another Dataset
• ODS HTML and PRINT procedure with a BY statement (5 messages)
• OT: Jackknife estimates (3 messages)
• PharmaSUG, Not Income Taxes, on April 15th
• Placing frequency counts into Excel (3 messages)
• Print two reports on one page (3 messages)
• Proc Report, Across, style(column) tagattr (9 messages)
• Proc freq for binomial CI (6 messages)
• Proc sql - summary (4 messages)
• Question on statistical/econometric modeling (2 messages)
• RES: Simple Scenario - Sum One
• RES: ranuni() versus call ranuni
• Regarding Proc export (4 messages)
• Regular expression to parse filepath (2 messages)
• SAS Drill Down Examples / Reference (8 messages)
• SAS Excel DDE Hyperlink Object
• SAS Global Forum 2011 Interviews
• SAS related position in Toronto, Canada
• SELECT group and IF-THEN/ELSE statements (6 messages)
• Simple Scenario - Sum One (5 messages)
• Speech Sounds to Alert Data Discrepancies! (2 messages)
• The "cheaper, faster and better" challenge from Roland Berry ( indirect)
• The 2011 SAS-L BOF Stats Presentation (21 messages)
• Tips for optimizing sql data pull from SYBASE database (7 messages)
• Tracking peak temp disk space usage? (7 messages)
• Transfer the structure of the data set, using macro and macro variables: Warning, the message is long (5 messages)
• Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (24 messages)
• Using first.variable to get more than one observation? (6 messages)
• Using parallel SAS variable and macro variable lists
• Value-Added Analyses in Education
• Who Was Datanull to You? (4 messages)
• XML MAP support in unix
• a simple macro code (8 messages)
• barletts test (2 messages)
• get name of current include file (3 messages)
• htmSQL
• job: USA, Washington DC == Hyattsville, MD
• job: statistician NIH Washington DC == Bethesda MD
• logit plot
• long macro variable as SET statement (3 messages)
• moving windows - help needed! (2 messages)
• note: SAS/IML incompatible with latest releases of R (4 messages)
• oledb connection trouble
• opening data set error (2 messages)
• proc g3d note statement question (4 messages)
• ranuni() versus call ranuni (3 messages)
• sas and 32 / 64 coexistence (3 messages)

1. %qupcase, which & got masked
   • %qupcase, which & got masked (36 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: %qupcase, which & got masked (65 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>

2. %qupcase, which & got masked ( typos corrected, please see this one)
   • %qupcase, which & got masked ( typos corrected, please see this one) (38 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: %qupcase, which & got masked ( typos corrected, please see this one) (58 lines)
     From: Yu Zhang <zhangyu05@GMAIL.COM>

3. %str and &
   • %str and & (26 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: %str and & (40 lines)
     From: Lorne Klassen <lk1@ROGERS.COM>
   • Re: %str and & (52 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>

4. & and %str, another question
   • & and %str, another question (29 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: & and %str, another question (50 lines)
     From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

5. 10 High performance PROC of new SAS
   • 10 High performance PROC of new SAS (37 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: 10 High performance PROC of new SAS (55 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: 10 High performance PROC of new SAS (61 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: 10 High performance PROC of new SAS (92 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: 10 High performance PROC of new SAS (93 lines)
     From: Charlie Huang <charlie.chao.huang@GMAIL.COM>
   • Re: 10 High performance PROC of new SAS (127 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: 10 High performance PROC of new SAS (138 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: 10 High performance PROC of new SAS (148 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: 10 High performance PROC of new SAS (156 lines)
     From: Charlie Huang <charlie.chao.huang@GMAIL.COM>
   • Re: 10 High performance PROC of new SAS (169 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: 10 High performance PROC of new SAS (183 lines)
     From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
   • Re: 10 High performance PROC of new SAS (177 lines)
     From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: 10 High performance PROC of new SAS (46 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: 10 High performance PROC of new SAS (87 lines)
     From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: 10 High performance PROC of new SAS (72 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: 10 High performance PROC of new SAS (94 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: 10 High performance PROC of new SAS (45 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>

6. Anyone want some free SAS Press books?
   • Anyone want some free SAS Press books? (19 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>

7. Automatic reply: Proc Report, Across, style(column) tagattr
   • Automatic reply: Proc Report, Across, style(column) tagattr (16 lines)
     From: McGuire, Joanmarie - Division of Assessment Design and Implementation <joanmarie.mcguire@EDUCATION.KY.GOV>

8. Block Diagonal Covariance Matrix for GLMM
   • Block Diagonal Covariance Matrix for GLMM (52 lines)
     From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>

9. Chinese Characters
   • Chinese Characters (14 lines)
     From: Lucy Hoch <lucy.hoch@GMAIL.COM>
   • Re: Chinese Characters (37 lines)
     From: Murphy Choy <goladin@GMAIL.COM>

10. Computer Advice
    • Computer Advice (21 lines)
      From: SUBSCRIBE SAS-L Ameribrit <FRP3@PITT.EDU>
    • Re: Computer Advice (40 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Computer Advice (33 lines)
      From: Charlie Huang <charlie.chao.huang@GMAIL.COM>
    • Re: Computer Advice (55 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Computer Advice (47 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>

11. Data import
    • Data import (27 lines)
      From: Rodrigo Guerrero <Rodrigo.A.Guerrero@KP.ORG>
    • Re: Data import (60 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Data import (84 lines)
      From: Rodrigo Guerrero <Rodrigo.A.Guerrero@KP.ORG>
    • Re: Data import (120 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

12. FW: note: SAS/IML incompatible with latest releases of R
    • FW: note: SAS/IML incompatible with latest releases of R (67 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>

13. Free SGF take-out videos this year
    • Free SGF take-out videos this year (10 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

14. Fwd: opening data set error
    • Fwd: opening data set error (97 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

15. In search of better way to exploit the proc means
    • In search of better way to exploit the proc means (106 lines)
      From: SUBSCRIBE SAS-L Anonymou <tonysingsong@GMAIL.COM>
    • Re: In search of better way to exploit the proc means (90 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: In search of better way to exploit the proc means (156 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: In search of better way to exploit the proc means (164 lines)
      From: SUBSCRIBE SAS-L Anonymou <tonysingsong@GMAIL.COM>
    • Re: In search of better way to exploit the proc means (156 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: In search of better way to exploit the proc means (202 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: In search of better way to exploit the proc means (231 lines)
      From: dynamicpanel@YAHOO.COM

16. Is this something that would be useful on sasCommunity.org?
    • Is this something that would be useful on sasCommunity.org? (32 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is this something that would be useful on sasCommunity.org? (52 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Is this something that would be useful on sasCommunity.org? (61 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is this something that would be useful on sasCommunity.org? (53 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Is this something that would be useful on sasCommunity.org? (71 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Is this something that would be useful on sasCommunity.org? (90 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: Is this something that would be useful on sasCommunity.org? (109 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is this something that would be useful on sasCommunity.org? (103 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>

17. Jegadeesh and Titman (Momentum) SAS Code Help
    • Jegadeesh and Titman (Momentum) SAS Code Help (156 lines)
      From: Sameem Lutfi <slutfi@MBA2011.HBS.EDU>
    • Re: Jegadeesh and Titman (Momentum) SAS Code Help (194 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Jegadeesh and Titman (Momentum) SAS Code Help (225 lines)
      From: Lutfi, Sameem <slutfi@MBA2011.HBS.EDU>
    • Re: Jegadeesh and Titman (Momentum) SAS Code Help (242 lines)
      From: Lutfi, Sameem <slutfi@MBA2011.HBS.EDU>
    • Re: Jegadeesh and Titman (Momentum) SAS Code Help (296 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

18. Job: 3-month full-time SAS Administrator (Toronto)
    • Job: 3-month full-time SAS Administrator (Toronto) (11 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

19. Macro variables from a dataset.
    • Macro variables from a dataset. (28 lines)
      From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG>
    • Re: Macro variables from a dataset. (43 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Macro variables from a dataset. (48 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

20. Michigan SAS Users Group 1-Day Conference in May
    • Michigan SAS Users Group 1-Day Conference in May (90 lines)
      From: Nancy Brucken <brucken@PROVIDE.NET>

21. NLMIXED Versus Proc Mixed
    • NLMIXED Versus Proc Mixed (24 lines)
      From: SUBSCRIBE SAS-L Ameribrit <FRP3@PITT.EDU>
    • Re: NLMIXED Versus Proc Mixed (34 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>

22. NLMIXED versus PROC MIXED
    • NLMIXED versus PROC MIXED (73 lines)
      From: SUBSCRIBE SAS-L Ameribrit <FRP3@PITT.EDU>
    • Re: NLMIXED versus PROC MIXED (226 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: NLMIXED versus PROC MIXED (263 lines)
      From: Robin R High <rhigh@UNMC.EDU>

23. Need Help Recalculatinng Vallues in One Dataset Based on Values in another Dataset
    • Re: Need Help Recalculatinng Vallues in One Dataset Based on Values in another Dataset (158 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

24. ODS HTML and PRINT procedure with a BY statement
    • ODS HTML and PRINT procedure with a BY statement (58 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: ODS HTML and PRINT procedure with a BY statement (60 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: ODS HTML and PRINT procedure with a BY statement (59 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: ODS HTML and PRINT procedure with a BY statement (123 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: ODS HTML and PRINT procedure with a BY statement (86 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

25. OT: Jackknife estimates
    • OT: Jackknife estimates (35 lines)
      From: Reeza K <fkhurshed@HOTMAIL.COM>
    • Re: OT: Jackknife estimates (52 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: OT: Jackknife estimates (71 lines)
      From: Reeza K <fkhurshed@HOTMAIL.COM>

26. PharmaSUG, Not Income Taxes, on April 15th
    • PharmaSUG, Not Income Taxes, on April 15th (56 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

27. Placing frequency counts into Excel
    • Placing frequency counts into Excel (23 lines)
      From: Laughing Beggar <laughing_beggar@HOTMAIL.COM>
    • Re: Placing frequency counts into Excel (39 lines)
      From: Adelina Gschwandtner <adelina.gschwandtner@UNIVIE.AC.AT>
    • Re: Placing frequency counts into Excel (64 lines)
      From: John Birken <zbq5@CDC.GOV>

28. Print two reports on one page
    • Print two reports on one page (18 lines)
      From: js8765 <js8765@GOOGLEMAIL.COM>
    • Re: Print two reports on one page (19 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Print two reports on one page (47 lines)
      From: Andre Wielki <wielki@INED.FR>

29. Proc Report, Across, style(column) tagattr
    • Re: Proc Report, Across, style(column) tagattr (113 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • Re: Proc Report, Across, style(column) tagattr (148 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: Proc Report, Across, style(column) tagattr (180 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • Re: Proc Report, Across, style(column) tagattr (181 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • Re: Proc Report, Across, style(column) tagattr (221 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: Proc Report, Across, style(column) tagattr (485 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Proc Report, Across, style(column) tagattr (543 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • Re: Proc Report, Across, style(column) tagattr (1165 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Proc Report, Across, style(column) tagattr (1162 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>

30. Proc freq for binomial CI
    • Proc freq for binomial CI (47 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Proc freq for binomial CI (36 lines)
      From: David J Moriarty <djmoriarty@CSUPOMONA.EDU>
    • Re: Proc freq for binomial CI (111 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Proc freq for binomial CI (79 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Proc freq for binomial CI (119 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Proc freq for binomial CI (107 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

31. Proc sql - summary
    • Proc sql - summary (17 lines)
      From: Kevin Y <kevin77711@YAHOO.COM>
    • Re: Proc sql - summary (83 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Proc sql - summary (44 lines)
      From: Kevin Y <kevin77711@YAHOO.COM>
    • Re: Proc sql - summary (108 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

32. Question on statistical/econometric modeling
    • Question on statistical/econometric modeling (47 lines)
      From: Haigang Zhou <haigang.zhou@GMAIL.COM>
    • Re: Question on statistical/econometric modeling (70 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

33. RES: Simple Scenario - Sum One
    • RES: Simple Scenario - Sum One (141 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

34. RES: ranuni() versus call ranuni
    • RES: ranuni() versus call ranuni (54 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

35. Regarding Proc export
    • Regarding Proc export (167 lines)
      From: sudha Rajendran <srajend@HEALTHFIRST.ORG>
    • Re: Regarding Proc export (190 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Regarding Proc export (34 lines)
      From: sudha Rajendran <srajend@HEALTHFIRST.ORG>
    • Re: Regarding Proc export (101 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

36. Regular expression to parse filepath
    • Re: Regular expression to parse filepath (23 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Regular expression to parse filepath (61 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

37. SAS Drill Down Examples / Reference
    • SAS Drill Down Examples / Reference (23 lines)
      From: Rick Smith <Ricky_L_Smith@DELL.COM>
    • Re: SAS Drill Down Examples / Reference (43 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: SAS Drill Down Examples / Reference (50 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: SAS Drill Down Examples / Reference (36 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: SAS Drill Down Examples / Reference (52 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: SAS Drill Down Examples / Reference (61 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: SAS Drill Down Examples / Reference (55 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS Drill Down Examples / Reference (43 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

38. SAS Excel DDE Hyperlink Object
    • SAS Excel DDE Hyperlink Object (23 lines)
      From: Aaron Evans <aaronevans@HOTMAIL.COM>

39. SAS Global Forum 2011 Interviews
    • SAS Global Forum 2011 Interviews (14 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

40. SAS related position in Toronto, Canada
    • SAS related position in Toronto, Canada (201 lines)
      From: Hiten Patel <hpatel@GIVEGET.COM>

41. SELECT group and IF-THEN/ELSE statements
    • SELECT group and IF-THEN/ELSE statements (48 lines)
      From: Seung-min Baek <760105@HANMAIL.NET>
    • Re: SELECT group and IF-THEN/ELSE statements (79 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: SELECT group and IF-THEN/ELSE statements (100 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: SELECT group and IF-THEN/ELSE statements (115 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SELECT group and IF-THEN/ELSE statements (137 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: SELECT group and IF-THEN/ELSE statements (91 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

42. Simple Scenario - Sum One
    • Simple Scenario - Sum One (61 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: Simple Scenario - Sum One (119 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Simple Scenario - Sum One (136 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Simple Scenario - Sum One (69 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Simple Scenario - Sum One (111 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

43. Speech Sounds to Alert Data Discrepancies!
    • Re: Speech Sounds to Alert Data Discrepancies! (94 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Speech Sounds to Alert Data Discrepancies! (120 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

44. The "cheaper, faster and better" challenge from Roland Berry ( indirect)
    • The "cheaper, faster and better" challenge from Roland Berry ( indirect) (38 lines)
      From: Andre Wielki <wielki@INED.FR>

45. The 2011 SAS-L BOF Stats Presentation
    • Re: The 2011 SAS-L BOF Stats Presentation (58 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (69 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: The 2011 SAS-L BOF Stats Presentation (79 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (84 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (92 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (109 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: The 2011 SAS-L BOF Stats Presentation (22 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (36 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (56 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: The 2011 SAS-L BOF Stats Presentation (61 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (55 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: The 2011 SAS-L BOF Stats Presentation (87 lines)
      From: Richard Read Allen <peakstat@WISPERTEL.NET>
    • Re: The 2011 SAS-L BOF Stats Presentation (90 lines)
      From: Adelina Gschwandtner <adelina.gschwandtner@UNIVIE.AC.AT>
    • Re: The 2011 SAS-L BOF Stats Presentation (93 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (63 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: The 2011 SAS-L BOF Stats Presentation (52 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (93 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (103 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (50 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (34 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: The 2011 SAS-L BOF Stats Presentation (63 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>

46. Tips for optimizing sql data pull from SYBASE database
    • Tips for optimizing sql data pull from SYBASE database (39 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Tips for optimizing sql data pull from SYBASE database (52 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Tips for optimizing sql data pull from SYBASE database (67 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Tips for optimizing sql data pull from SYBASE database (24 lines)
      From: Gabriel Rosas <rosas.gabe@GMAIL.COM>
    • Re: Tips for optimizing sql data pull from SYBASE database (24 lines)
      From: Gabriel Rosas <rosas.gabe@GMAIL.COM>
    • Re: Tips for optimizing sql data pull from SYBASE database (156 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Tips for optimizing sql data pull from SYBASE database (170 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

47. Tracking peak temp disk space usage?
    • Tracking peak temp disk space usage? (21 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Tracking peak temp disk space usage? (46 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Tracking peak temp disk space usage? (67 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: Tracking peak temp disk space usage? (93 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Tracking peak temp disk space usage? (55 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Tracking peak temp disk space usage? (76 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Tracking peak temp disk space usage? (85 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

48. Transfer the structure of the data set, using macro and macro variables: Warning, the message is long
    • Transfer the structure of the data set, using macro and macro variables: Warning, the message is long (240 lines)
      From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM>
    • Re: Transfer the structure of the data set, using macro and macro variables: Warning, the message is long (317 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Transfer the structure of the data set, using macro and macro variables: Warning, the message is long (58 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Transfer the structure of the data set, using macro and macro variables: Warning, the message is long (53 lines)
      From: Richard DeVenezia <rdevenezia@GMAIL.COM>
    • Re: Transfer the structure of the data set, using macro and macro variables: Warning, the message is long (168 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

49. Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13
    • Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (91 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (132 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (135 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (149 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (152 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (151 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (162 lines)
      From: Gabriel Rosas <rosas.gabe@GMAIL.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (150 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (169 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (130 lines)
      From: Lingqun <lingqun@GMAIL.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (186 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (195 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (146 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (181 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (196 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (111 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (130 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (218 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (126 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (156 lines)
      From: Eric Lecoutre <ericlecoutre@GMAIL.COM>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (144 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (170 lines)
      From: Zack, Matthew M. (CDC/ONDIEH/NCCDPHP) <mmz1@CDC.GOV>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (95 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Trouble reading a very large ASCII file perhaps due to '0d0a'x (Carriage-Return + Line-Feed) within variable: SAS v 9.13 (26 lines)
      From: Hoyle, Larry <larryhoyle@KU.EDU>

50. Using first.variable to get more than one observation?
    • Using first.variable to get more than one observation? (35 lines)
      From: J. Sandhu <jashuminhas@HOTMAIL.COM>
    • Re: Using first.variable to get more than one observation? (51 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Using first.variable to get more than one observation? (59 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Using first.variable to get more than one observation? (55 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Using first.variable to get more than one observation? (75 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Using first.variable to get more than one observation? (12 lines)
      From: J. Sandhu <jashuminhas@HOTMAIL.COM>

51. Using parallel SAS variable and macro variable lists
    • Using parallel SAS variable and macro variable lists (184 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

52. Value-Added Analyses in Education
    • Re: Value-Added Analyses in Education (132 lines)
      From: Richard Hake <rrhake@EARTHLINK.NET>

53. Who Was Datanull to You?
    • Who Was Datanull to You? (91 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Who Was Datanull to You? (57 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Who Was Datanull to You? (105 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Who Was Datanull to You? (133 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

54. XML MAP support in unix
    • Re: XML MAP support in unix (41 lines)
      From: OBrien, Craig <COBrien@CPSC.GOV>

55. a simple macro code
    • a simple macro code (48 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: a simple macro code (59 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: a simple macro code (91 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: a simple macro code (96 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: a simple macro code (64 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: a simple macro code (123 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: a simple macro code (77 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: a simple macro code (140 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

56. barletts test
    • barletts test (28 lines)
      From: Trish Bous <tboussard@GMAIL.COM>
    • Re: barletts test (47 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

57. get name of current include file
    • get name of current include file (34 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: get name of current include file (73 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: get name of current include file (93 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

58. htmSQL
    • htmSQL (29 lines)
      From: Richard DeVenezia <rdevenezia@GMAIL.COM>

59. job: USA, Washington DC == Hyattsville, MD
    • job: USA, Washington DC == Hyattsville, MD (41 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

60. job: statistician NIH Washington DC == Bethesda MD
    • job: statistician NIH Washington DC == Bethesda MD (43 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

61. logit plot
    • logit plot (17 lines)
      From: Bous <tboussard@GMAIL.COM>

62. long macro variable as SET statement
    • long macro variable as SET statement (62 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: long macro variable as SET statement (84 lines)
      From: OBrien, Craig <COBrien@CPSC.GOV>
    • Re: long macro variable as SET statement (109 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

63. moving windows - help needed!
    • moving windows - help needed! (226 lines)
      From: Adelina Gschwandtner <adelina.gschwandtner@UNIVIE.AC.AT>
    • Re: moving windows - help needed! (228 lines)
      From: Robin R High <rhigh@UNMC.EDU>

64. note: SAS/IML incompatible with latest releases of R
    • note: SAS/IML incompatible with latest releases of R (30 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: note: SAS/IML incompatible with latest releases of R (46 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: note: SAS/IML incompatible with latest releases of R (51 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: note: SAS/IML incompatible with latest releases of R (26 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

65. oledb connection trouble
    • Re: oledb connection trouble (214 lines)
      From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM>

66. opening data set error
    • opening data set error (17 lines)
      From: Lucy Hoch <lucy.hoch@GMAIL.COM>
    • Re: opening data set error (38 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

67. proc g3d note statement question
    • proc g3d note statement question (25 lines)
      From: Robert Feyerharm <rfeyerha@TRAVELERS.COM>
    • Re: proc g3d note statement question (73 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: proc g3d note statement question (23 lines)
      From: Robert Feyerharm <rfeyerha@TRAVELERS.COM>
    • Re: proc g3d note statement question (49 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

68. ranuni() versus call ranuni
    • ranuni() versus call ranuni (24 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: ranuni() versus call ranuni (99 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: ranuni() versus call ranuni (42 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

69. sas and 32 / 64 coexistence
    • sas and 32 / 64 coexistence (40 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: sas and 32 / 64 coexistence (69 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: sas and 32 / 64 coexistence (56 lines)
      From: Andre Wielki <wielki@INED.FR>