Table of contents:

• %superq( ) (21 messages)
• %sysfunc and catx (3 messages)
• 'SAS IML Studio' on 'Enterprise Guide OnDemand'
• Add Missing Records to Table and Impute Values of Last Non Missing. (5 messages)
• Add-on IDE for SAS
• Automatic reply: %superq( )
• Automatic reply: SAS-L Digest - 10 Dec 2011 to 11 Dec 2011 (#2011-1073)
• Automatic reply: SAS-L Digest - 8 Dec 2011 - Special issue (#2011-1069)
• Can one use a sorted file as an index? (7 messages)
• Cobol-to-SAS Conversion Question (5 messages)
• Data step adding blanks (9 messages)
• Ebcidic to Ascii with PDw.d conversion fix
• FW: ODS and graphs from procedures (2 messages)
• Fwd: %superq( ) (2 messages)
• GLIMMIX Large Variance Component Estimate (2 messages)
• Generate Macro variables inside a datastep. (7 messages)
• Good News!
• Howto read old bases (5.18 MVS) (2 messages)
• Is there an easy way to search all the logs in an EG project (4 messages)
• Is today Friday the 13th??? (Mainframe Issue) (5 messages)
• Job Posting - SAS Programmer in Baltimore, MD
• Log-likelihood tests of random effects (4 messages)
• Macro's (3 messages)
• NEED HELP: SAS ODS Tagset & PIVOT Table Question
• NLMIXED MAXTIME option (2 messages)
• OT: New CDC and US Census Bureau Data Available on Health Insurance Coverage
• Odds ratio (3 messages)
• Pls do help for code (3 messages)
• Quasi Complete Separation in Logistic Regression
• Removing variables with all missing values (6 messages)
• Request for Proposal: Algorithms for Normalization of Clinical Data to Enable Advanced Predictive Healthcare Systems
• Running scheduled SAS jobs in Windows 7 Scheduler (5 messages)
• SAS Global Forum (hotel alternatives)
• SAS ODS Tagset & PIVOT Table Question
• SAS in interactive mode - UI configuration tip (4 messages)
• SQL code equivalent to data set operation. (5 messages)
• Survival Analysis - Cumulative Hazard to Survival score conversion
• XML code appears instead of opening an Excel file (12 messages)
• a macro checking invalid variable name (9 messages)
• best way to find the worst 6 month
• comparing quality of teaching of two instructors (8 messages)
• if the mixture of data step and proc iml can be the execution statement in if-then
• masking marks, macro
• native sas datasets 64bits from elsewhere (5 messages)
• one to many merge (2 messages)
• programmatically querying SAS metadata server using BASE SAS
• sgscatter procedure datalabel option
• tip: SAS Technical papers
• trend analysis with weighted survey data

1. %superq( )
   • Re: %superq( ) (269 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: %superq( ) (259 lines)
     From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
   • Re: %superq( ) (416 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: %superq( ) (359 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>
   • Re: %superq( ) (347 lines)
     From: T J <tj_noreply@YAHOO.COM>
   • Re: %superq( ) (339 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: %superq( ) (251 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: %superq( ) (62 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: %superq( ) (219 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: %superq( ) (249 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: %superq( ) (38 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: %superq( ) (252 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: %superq( ) (35 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: %superq( ) (179 lines)
     From: Sterling Paramore <gnilrets@GMAIL.COM>
   • Re: %superq( ) (146 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: %superq( ) (136 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: %superq( ) (90 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: %superq( ) (78 lines)
     From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
   • Re: %superq( ) (103 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: %superq( ) (42 lines)
     From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
   • Re: %superq( ) (70 lines)
     From: Mike Rhoads <RHOADSM1@WESTAT.COM>

2. %sysfunc and catx
   • Re: %sysfunc and catx (96 lines)
     From: Ya Huang <ya.huang@AMYLIN.COM>
   • Re: %sysfunc and catx (69 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>
   • %sysfunc and catx (59 lines)
     From: Ya Huang <ya.huang@AMYLIN.COM>

3. 'SAS IML Studio' on 'Enterprise Guide OnDemand'
   • 'SAS IML Studio' on 'Enterprise Guide OnDemand' (23 lines)
     From: Ehsan Karim <wildscop@HOTMAIL.COM>

4. Add Missing Records to Table and Impute Values of Last Non Missing.
   • Re: Add Missing Records to Table and Impute Values of Last Non Missing. (164 lines)
     From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
   • Re: Add Missing Records to Table and Impute Values of Last Non Missing. (131 lines)
     From: b miner <b_miner@LIVE.COM>
   • Re: Add Missing Records to Table and Impute Values of Last Non Missing. (83 lines)
     From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
   • Re: Add Missing Records to Table and Impute Values of Last Non Missing. (105 lines)
     From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
   • Add Missing Records to Table and Impute Values of Last Non Missing. (60 lines)
     From: b miner <b_miner@LIVE.COM>

5. Add-on IDE for SAS
   • Add-on IDE for SAS (14 lines)
     From: polyphonic48@gmail.com <polyphonic48@GMAIL.COM>

6. Automatic reply: %superq( )
   • Automatic reply: %superq( ) (11 lines)
     From: Rick Smith <Ricky_L_Smith@DELL.COM>

7. Automatic reply: SAS-L Digest - 10 Dec 2011 to 11 Dec 2011 (#2011-1073)
   • Automatic reply: SAS-L Digest - 10 Dec 2011 to 11 Dec 2011 (#2011-1073) (21 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

8. Automatic reply: SAS-L Digest - 8 Dec 2011 - Special issue (#2011-1069)
   • Automatic reply: SAS-L Digest - 8 Dec 2011 - Special issue (#2011-1069) (30 lines)
     From: Kathy Jorgensen <Kathy.Jorgensen@MEREDITH.COM>

9. Can one use a sorted file as an index?
   • Re: Can one use a sorted file as an index? (80 lines)
     From: Paul Dorfman <sashole@BELLSOUTH.NET>
   • Re: Can one use a sorted file as an index? (81 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>
   • Re: Can one use a sorted file as an index? (107 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Can one use a sorted file as an index? (95 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Can one use a sorted file as an index? (84 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Can one use a sorted file as an index? (68 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Can one use a sorted file as an index? (59 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>

10. Cobol-to-SAS Conversion Question
    • Re: Cobol-to-SAS Conversion Question (80 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • Re: Cobol-to-SAS Conversion Question (79 lines)
      From: William W. Viergever <william@VIERGEVER.NET>
    • Re: Cobol-to-SAS Conversion Question (59 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Cobol-to-SAS Conversion Question (49 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Cobol-to-SAS Conversion Question (52 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

11. Data step adding blanks
    • Re: Data step adding blanks (1296 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Data step adding blanks (116 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Data step adding blanks (1128 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Data step adding blanks (1115 lines)
      From: Santosh Nazare <santosh.nazare@MAINE.GOV>
    • Re: Data step adding blanks (98 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Data step adding blanks (81 lines)
      From: Santosh Nazare <santosh.nazare@MAINE.GOV>
    • Re: Data step adding blanks (59 lines)
      From: Santosh Nazare <santosh.nazare@MAINE.GOV>
    • Re: Data step adding blanks (54 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Data step adding blanks (40 lines)
      From: Santosh Nazare <santosh.nazare@MAINE.GOV>

12. Ebcidic to Ascii with PDw.d conversion fix
    • Ebcidic to Ascii with PDw.d conversion fix (51 lines)
      From: Byron Kirby <byronkirby@GMAIL.COM>

13. FW: ODS and graphs from procedures
    • Re: FW: ODS and graphs from procedures (33 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • FW: ODS and graphs from procedures (25 lines)
      From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>

14. Fwd: %superq( )
    • Re: Fwd: %superq( ) (71 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Fwd: %superq( ) (61 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

15. GLIMMIX Large Variance Component Estimate
    • Re: GLIMMIX Large Variance Component Estimate (75 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>
    • GLIMMIX Large Variance Component Estimate (67 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>

16. Generate Macro variables inside a datastep.
    • Re: Generate Macro variables inside a datastep. (163 lines)
      From: Gabriel Farkas <g.farkas@GMAIL.COM>
    • Re: Generate Macro variables inside a datastep. (184 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Generate Macro variables inside a datastep. (123 lines)
      From: Worlund, Max (CDC/OID/NCIRD) (CTR) <zqy3@CDC.GOV>
    • Re: Generate Macro variables inside a datastep. (153 lines)
      From: Sagar Ankola <spankola0616@EMAIL.CAMPBELL.EDU>
    • Re: Generate Macro variables inside a datastep. (78 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: Generate Macro variables inside a datastep. (65 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Generate Macro variables inside a datastep. (36 lines)
      From: Max Worlund <zqy3@CDC.GOV>

17. Good News!
    • Good News! (12 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

18. Howto read old bases (5.18 MVS)
    • Re: Howto read old bases (5.18 MVS) (44 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Howto read old bases (5.18 MVS) (31 lines)
      From: flavigny <flavigny@FREE.FR>

19. Is there an easy way to search all the logs in an EG project
    • Re: Is there an easy way to search all the logs in an EG project (43 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Is there an easy way to search all the logs in an EG project (24 lines)
      From: Charles Patridge <Charles_s_patridge@PRODIGY.NET>
    • Re: Is there an easy way to search all the logs in an EG project (45 lines)
      From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM>
    • Is there an easy way to search all the logs in an EG project (15 lines)
      From: Charles Patridge <Charles_s_patridge@PRODIGY.NET>

20. Is today Friday the 13th??? (Mainframe Issue)
    • Re: Is today Friday the 13th??? (Mainframe Issue) (57 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Is today Friday the 13th??? (Mainframe Issue) (30 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Is today Friday the 13th??? (Mainframe Issue) (43 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: Is today Friday the 13th??? (Mainframe Issue) (58 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Is today Friday the 13th??? (Mainframe Issue) (26 lines)
      From: Michael Marcus <Michael.Marcus@US.FUJITSU.COM>

21. Job Posting - SAS Programmer in Baltimore, MD
    • Job Posting - SAS Programmer in Baltimore, MD (58 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

22. Log-likelihood tests of random effects
    • Re: Log-likelihood tests of random effects (237 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: Log-likelihood tests of random effects (161 lines)
      From: Katie McGhee <kemcghee@ILLINOIS.EDU>
    • Re: Log-likelihood tests of random effects (104 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Log-likelihood tests of random effects (68 lines)
      From: Katie McGhee <kemcghee@ILLINOIS.EDU>

23. Macro's
    • Re: Macro's (51 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Macro's (34 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Macro's (14 lines)
      From: anon <rhian.pilling@GMAIL.COM>

24. NEED HELP: SAS ODS Tagset & PIVOT Table Question
    • NEED HELP: SAS ODS Tagset & PIVOT Table Question (52 lines)
      From: John RR <john_rr_irc@YAHOO.COM>

25. NLMIXED MAXTIME option
    • Re: NLMIXED MAXTIME option (53 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>
    • NLMIXED MAXTIME option (28 lines)
      From: SUBSCRIBE SAS-L Ameribrit <FRP3@PITT.EDU>

26. OT: New CDC and US Census Bureau Data Available on Health Insurance Coverage
    • OT: New CDC and US Census Bureau Data Available on Health Insurance Coverage (47 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

27. Odds ratio
    • Re: Odds ratio (35 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Odds ratio (34 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Odds ratio (9 lines)
      From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

28. Pls do help for code
    • Re: Pls do help for code (64 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Pls do help for code (52 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Pls do help for code (33 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>

29. Quasi Complete Separation in Logistic Regression
    • Quasi Complete Separation in Logistic Regression (34 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>

30. Removing variables with all missing values
    • Re: Removing variables with all missing values (130 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: Removing variables with all missing values (108 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Removing variables with all missing values (79 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Removing variables with all missing values (107 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Removing variables with all missing values (97 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Removing variables with all missing values (46 lines)
      From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU>

31. Request for Proposal: Algorithms for Normalization of Clinical Data to Enable Advanced Predictive Healthcare Systems
    • Request for Proposal: Algorithms for Normalization of Clinical Data to Enable Advanced Predictive Healthcare Systems (17 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

32. Running scheduled SAS jobs in Windows 7 Scheduler
    • Re: Running scheduled SAS jobs in Windows 7 Scheduler (113 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Running scheduled SAS jobs in Windows 7 Scheduler (102 lines)
      From: JD <jdiebal@GMAIL.COM>
    • Re: Running scheduled SAS jobs in Windows 7 Scheduler (73 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Running scheduled SAS jobs in Windows 7 Scheduler (83 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Running scheduled SAS jobs in Windows 7 Scheduler (44 lines)
      From: JD <jdiebal@GMAIL.COM>

33. SAS Global Forum (hotel alternatives)
    • SAS Global Forum (hotel alternatives) (35 lines)
      From: Wu Consulting <wuconsulting2@HOTMAIL.COM>

34. SAS ODS Tagset & PIVOT Table Question
    • SAS ODS Tagset & PIVOT Table Question (50 lines)
      From: John RR <john_rr_irc@YAHOO.COM>

35. SAS in interactive mode - UI configuration tip
    • Re: SAS in interactive mode - UI configuration tip (105 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: SAS in interactive mode - UI configuration tip (74 lines)
      From: William W. Viergever <william@VIERGEVER.NET>
    • Re: SAS in interactive mode - UI configuration tip (52 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • SAS in interactive mode - UI configuration tip (31 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

36. SQL code equivalent to data set operation.
    • Re: SQL code equivalent to data set operation. (94 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: SQL code equivalent to data set operation. (44 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: SQL code equivalent to data set operation. (37 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: SQL code equivalent to data set operation. (39 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • SQL code equivalent to data set operation. (16 lines)
      From: baogong jiang <bgjiang@GMAIL.COM>

37. Survival Analysis - Cumulative Hazard to Survival score conversion
    • Survival Analysis - Cumulative Hazard to Survival score conversion (17 lines)
      From: paul wilson <paulwilsn@YAHOO.COM>

38. XML code appears instead of opening an Excel file
    • Re: XML code appears instead of opening an Excel file (304 lines)
      From: Alan Churchill <alan.churchill@PROGNOSINC.COM>
    • Re: XML code appears instead of opening an Excel file (228 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: XML code appears instead of opening an Excel file (166 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: XML code appears instead of opening an Excel file (182 lines)
      From: Alan Churchill <alan.churchill@PROGNOSINC.COM>
    • Re: XML code appears instead of opening an Excel file (146 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: XML code appears instead of opening an Excel file (129 lines)
      From: Alan Churchill <alan.churchill@PROGNOSINC.COM>
    • Re: XML code appears instead of opening an Excel file (105 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: XML code appears instead of opening an Excel file (44 lines)
      From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>
    • Re: XML code appears instead of opening an Excel file (69 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: XML code appears instead of opening an Excel file (52 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: XML code appears instead of opening an Excel file (34 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • XML code appears instead of opening an Excel file (20 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>

39. a macro checking invalid variable name
    • Re: a macro checking invalid variable name (129 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: a macro checking invalid variable name (115 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: a macro checking invalid variable name (55 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: a macro checking invalid variable name (61 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: a macro checking invalid variable name (96 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: a macro checking invalid variable name (80 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: a macro checking invalid variable name (101 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: a macro checking invalid variable name (92 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • a macro checking invalid variable name (52 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

40. best way to find the worst 6 month
    • best way to find the worst 6 month (30 lines)
      From: Jenny Lee <goproc@HOTMAIL.COM>

41. comparing quality of teaching of two instructors
    • Re: comparing quality of teaching of two instructors (234 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: comparing quality of teaching of two instructors (213 lines)
      From: Francois van der Walt <francoisw@GJI.COM.AU>
    • Re: comparing quality of teaching of two instructors (78 lines)
      From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV>
    • Re: comparing quality of teaching of two instructors (69 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: comparing quality of teaching of two instructors (49 lines)
      From: David J. Moriarty <djmoriarty@CSUPOMONA.EDU>
    • Re: comparing quality of teaching of two instructors (65 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: comparing quality of teaching of two instructors (43 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • comparing quality of teaching of two instructors (26 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

42. if the mixture of data step and proc iml can be the execution statement in if-then
    • if the mixture of data step and proc iml can be the execution statement in if-then (30 lines)
      From: Rong Jin <rongjin2006@GMAIL.COM>

43. masking marks, macro
    • Re: masking marks, macro (45 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

44. native sas datasets 64bits from elsewhere
    • Re: native sas datasets 64bits from elsewhere (81 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: native sas datasets 64bits from elsewhere (38 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: native sas datasets 64bits from elsewhere (43 lines)
      From: WIELKI Andre <wielki@INED.FR>
    • Re: native sas datasets 64bits from elsewhere (112 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • native sas datasets 64bits from elsewhere (91 lines)
      From: Andre Wielki <wielki@INED.FR>

45. one to many merge
    • Re: one to many merge (75 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: one to many merge (92 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

46. programmatically querying SAS metadata server using BASE SAS
    • programmatically querying SAS metadata server using BASE SAS (25 lines)
      From: Shanks N <shanks.n@GMAIL.COM>

47. sgscatter procedure datalabel option
    • Re: sgscatter procedure datalabel option (13 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>

48. tip: SAS Technical papers
    • tip: SAS Technical papers (28 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

49. trend analysis with weighted survey data
    • trend analysis with weighted survey data (22 lines)
      From: Charlotte Baker <charlotte.m.h.baker@GMAIL.COM>