Table of contents:

• $varying9. and strange input statement (6 messages)
• An Invalid third argument to function SUBSTR at line 231 column 66 (7 messages)
• Automatic reply: SAS-L Digest - 23 Nov 2010 - Special issue (#2010-1256) (2 messages)
• Automatic reply: problems labelling bar charts in SAS
• Better way to handle MISSING test (5 messages)
• Chance to Make SAS-L History Index (3 messages)
• Converting Narrow Data Set to Wide Data Set (2 messages)
• Crossover trial (5 messages)
• Exact Poisson CI (2 messages)
• Extra-multinomial (Extra-binomial?) variation in SAS (2 messages)
• HL Goodness of fit statistic Chi-Square statistic for PROC LOGISTIC (2 messages)
• Happy Thanksgiving!
• How many number "4" across different Columns until a # between 9701-200810 (6 messages)
• How to substact (minus) in datastep? (2 messages)
• ICD9 CM Removing large blocks text (4 messages)
• If VARIABLE Does Not Exist Then Do... (9 messages)
• Incorporating a Baseline Hazard for a Binomial Logit (2 messages)
• Initialization of array variables (4 messages)
• Lag Function (14 messages)
• NLMIXED Restrictions (2 messages)
• Non linear Optimization using NLPQN
• ODS Graphics question.... (3 messages)
• OT: Some Thankgoving Cheer for the hoard (2 messages)
• OT: Some Thanksgiving Cheer for the hoard
• PLS Path Modeling Certificate
• PROC COMPARE Output
• PROC COMPARE Output (slight correction)
• Paired choice analysis assistance
• Parsing a big but seemingly simple file (5 messages)
• PharmaSUG submission question (3 messages)
• Proc POWER question
• Q on fitting random change point model using nlmixed
• RES: NLMIXED Output combinations
• RES: NLMIXED Restrictions (2 messages)
• Read text file with missing values (4 messages)
• Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (8 messages)
• SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (8 messages)
• SAS DDE and Excel..... (3 messages)
• SAS EG: where is the help for SAS procedures and functions (syntax)? (2 messages)
• SAS Graph Symbols (3 messages)
• SEM value
• SQL LIKE condition with macro variable (8 messages)
• Shell escape is not valid in this SAS session (9 messages)
• Shocking News............................ Michelle Zunnurain (4 messages)
• THANK YOU SO MUCH! RE: Converting Narrow Data Set to Wide Data Set
• UltraEdit, SAS and Linux
• WHERE LIKE operator wants to ESCAPE (3 messages)
• covariance structures and spatial autocorrelation (3 messages)
• data merging question
• data sets used in SAS Help and Documentation (8 messages)
• file shortcuts question remade (4 messages)
• funny code, formatted input or list input or neither (2 messages)
• how to calculate average for below data? (4 messages)
• how to change the default value "1" under proc report across varaible? (5 messages)
• how to change the default value "1" under proc report across variable?
• how to convert one variable into multiple columns according its value? (2 messages)
• how to get macro variable length
• if, where, executable (9 messages)
• infile option DLMSTR (3 messages)
• logistic regression default probability to credit score, how?
• nonlinear optimization
• percent2. (4 messages)
• problems labelling bar charts in SAS
• reading data columns (13 messages)
• regarding low-cost or free video tutoring (2 messages)
• repost: problems labelling bar charts in SAS (5 messages)
• set nomail
• sum statement, if/then, loop (2 messages)
• system options: LS ? (2 messages)
• the line holder @ (4 messages)
• transformation in proc prinqual
• using put without file (2 messages)
• variable-length records (2 messages)
• writing SAS code in MS outlook (2 messages)

1. $varying9. and strange input statement
   • Re: $varying9. and strange input statement (91 lines)
     From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: $varying9. and strange input statement (104 lines)
     From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
   • Re: $varying9. and strange input statement (79 lines)
     From: bbser2009 <bbser2009@GMAIL.COM>
   • Re: $varying9. and strange input statement (45 lines)
     From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: $varying9. and strange input statement (47 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • $varying9. and strange input statement (28 lines)
     From: bbser2009 <bbser2009@GMAIL.COM>

2. An Invalid third argument to function SUBSTR at line 231 column 66
   • Re: An Invalid third argument to function SUBSTR at line 231 column 66 (16 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
   • Re: An Invalid third argument to function SUBSTR at line 231 column 66 (10 lines)
     From: Tom Smith <need_sas_help@YAHOO.COM>
   • Re: An Invalid third argument to function SUBSTR at line 231 column 66 (22 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: An Invalid third argument to function SUBSTR at line 231 column 66 (10 lines)
     From: Tom Smith <need_sas_help@YAHOO.COM>
   • Re: An Invalid third argument to function SUBSTR at line 231 column 66 (276 lines)
     From: Tom Smith <need_sas_help@YAHOO.COM>
   • Re: An Invalid third argument to function SUBSTR at line 231 column 66 (48 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • An Invalid third argument to function SUBSTR at line 231 column 66 (26 lines)
     From: Tom Smith <need_sas_help@YAHOO.COM>

3. Automatic reply: SAS-L Digest - 23 Nov 2010 - Special issue (#2010-1256)
   • Automatic reply: SAS-L Digest - 23 Nov 2010 - Special issue (#2010-1256) (18 lines)
     From: Kathy Jorgensen <Kathy.Jorgensen@MEREDITH.COM>
   • Automatic reply: SAS-L Digest - 23 Nov 2010 - Special issue (#2010-1256) (15 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

4. Automatic reply: problems labelling bar charts in SAS
   • Automatic reply: problems labelling bar charts in SAS (16 lines)
     From: McGuire, Joanmarie - Division of Assessment Design and Implementation <joanmarie.mcguire@EDUCATION.KY.GOV>

5. Better way to handle MISSING test
   • Re: Better way to handle MISSING test (95 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>
   • Re: Better way to handle MISSING test (42 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Better way to handle MISSING test (79 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: Better way to handle MISSING test (48 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Better way to handle MISSING test (29 lines)
     From: Lizette Koehler <starsoul@MINDSPRING.COM>

6. Chance to Make SAS-L History Index
   • Re: Chance to Make SAS-L History Index (55 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Chance to Make SAS-L History Index (42 lines)
     From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
   • Chance to Make SAS-L History Index (31 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>

7. Converting Narrow Data Set to Wide Data Set
   • Re: Converting Narrow Data Set to Wide Data Set (244 lines)
     From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM>
   • Re: Converting Narrow Data Set to Wide Data Set (208 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>

8. Crossover trial
   • Re: Crossover trial (13 lines)
     From: SUBSCRIBE SAS-L Sharavi <dollsai@YAHOO.COM>
   • Re: Crossover trial (46 lines)
     From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
   • Re: Crossover trial (9 lines)
     From: SUBSCRIBE SAS-L Sharavi <dollsai@YAHOO.COM>
   • Re: Crossover trial (48 lines)
     From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
   • Crossover trial (29 lines)
     From: SUBSCRIBE SAS-L Sharavi <dollsai@YAHOO.COM>

9. Exact Poisson CI
   • Re: Exact Poisson CI (40 lines)
     From: Viel, Kevin <kviel@SJHA.ORG>
   • Exact Poisson CI (55 lines)
     From: Viel, Kevin <kviel@SJHA.ORG>

10. Extra-multinomial (Extra-binomial?) variation in SAS
    • Re: Extra-multinomial (Extra-binomial?) variation in SAS (43 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Extra-multinomial (Extra-binomial?) variation in SAS (19 lines)
      From: Randall Powers <powers_r@BLS.GOV>

11. HL Goodness of fit statistic Chi-Square statistic for PROC LOGISTIC
    • Re: HL Goodness of fit statistic Chi-Square statistic for PROC LOGISTIC (52 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • HL Goodness of fit statistic Chi-Square statistic for PROC LOGISTIC (31 lines)
      From: Tanmoy Mukherjee <tkmcornell@YAHOO.COM>

12. Happy Thanksgiving!
    • Happy Thanksgiving! (9 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

13. How many number "4" across different Columns until a # between 9701-200810
    • Re: How many number "4" across different Columns until a # between 9701-200810 (86 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: How many number "4" across different Columns until a # between 9701-200810 (34 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: How many number "4" across different Columns until a # between 9701-200810 (13 lines)
      From: Gerard Ghislain Tano <tano.tano.2008@GMAIL.COM>
    • Re: How many number "4" across different Columns until a # between 9701-200810 (162 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: How many number "4" across different Columns until a # between 9701-200810 (161 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • How many number "4" across different Columns until a # between 9701-200810 (88 lines)
      From: Gerard Ghislain Tano <tano.tano.2008@GMAIL.COM>

14. How to substact (minus) in datastep?
    • Re: How to substact (minus) in datastep? (63 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • How to substact (minus) in datastep? (30 lines)
      From: Nway <hymadsk@GMAIL.COM>

15. ICD9 CM Removing large blocks text
    • Re: ICD9 CM Removing large blocks text (258 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: ICD9 CM Removing large blocks text (251 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: ICD9 CM Removing large blocks text (250 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: ICD9 CM Removing large blocks text (212 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

16. If VARIABLE Does Not Exist Then Do...
    • Re: If VARIABLE Does Not Exist Then Do... (68 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: If VARIABLE Does Not Exist Then Do... (61 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: If VARIABLE Does Not Exist Then Do... (51 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: If VARIABLE Does Not Exist Then Do... (54 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: If VARIABLE Does Not Exist Then Do... (41 lines)
      From: Adriano Rodrigues <adriano@GPP.COM.BR>
    • Re: If VARIABLE Does Not Exist Then Do... (36 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: If VARIABLE Does Not Exist Then Do... (122 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>
    • Re: If VARIABLE Does Not Exist Then Do... (103 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • If VARIABLE Does Not Exist Then Do... (63 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>

17. Incorporating a Baseline Hazard for a Binomial Logit
    • Re: Incorporating a Baseline Hazard for a Binomial Logit (38 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: Incorporating a Baseline Hazard for a Binomial Logit (55 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>

18. Initialization of array variables
    • Re: Initialization of array variables (155 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: Initialization of array variables (164 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: Initialization of array variables (89 lines)
      From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
    • Initialization of array variables (25 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

19. Lag Function
    • Re: Lag Function (64 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: Lag Function (188 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • Re: Lag Function (225 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Lag Function (217 lines)
      From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Lag Function (207 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Lag Function (184 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Lag Function (170 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Lag Function (146 lines)
      From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Lag Function (140 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Lag Function (231 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Lag Function (150 lines)
      From: Mahesh <peesari.mahesh@GMAIL.COM>
    • Re: Lag Function (141 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: Lag Function (97 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Lag Function (67 lines)
      From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM>

20. NLMIXED Restrictions
    • Re: NLMIXED Restrictions (169 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • NLMIXED Restrictions (80 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

21. Non linear Optimization using NLPQN
    • Non linear Optimization using NLPQN (15 lines)
      From: Amal Helu <helu.amal@GMAIL.COM>

22. ODS Graphics question....
    • Re: ODS Graphics question.... (71 lines)
      From: Sally Muller <sallymuller@BELLSOUTH.NET>
    • Re: ODS Graphics question.... (55 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • ODS Graphics question.... (45 lines)
      From: Sally Muller <sallymuller@BELLSOUTH.NET>

23. OT: Some Thankgoving Cheer for the hoard
    • Re: OT: Some Thankgoving Cheer for the hoard (33 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • OT: Some Thankgoving Cheer for the hoard (103 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

24. OT: Some Thanksgiving Cheer for the hoard
    • Re: OT: Some Thanksgiving Cheer for the hoard (60 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

25. PLS Path Modeling Certificate
    • PLS Path Modeling Certificate (60 lines)
      From: Geoffrey Hubona <ghubona@GMAIL.COM>

26. PROC COMPARE Output
    • PROC COMPARE Output (150 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

27. PROC COMPARE Output (slight correction)
    • Re: PROC COMPARE Output (slight correction) (188 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

28. Paired choice analysis assistance
    • Paired choice analysis assistance (72 lines)
      From: Adam Smith <raptorbio@HOTMAIL.COM>

29. Parsing a big but seemingly simple file
    • Re: Parsing a big but seemingly simple file (206 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Parsing a big but seemingly simple file (271 lines)
      From: Marc Mooney UMN <moon0078@UMN.EDU>
    • Re: Parsing a big but seemingly simple file (183 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Parsing a big but seemingly simple file (151 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Parsing a big but seemingly simple file (95 lines)
      From: Marc Mooney UMN <moon0078@UMN.EDU>

30. PharmaSUG submission question
    • Re: PharmaSUG submission question (46 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: PharmaSUG submission question (60 lines)
      From: Richard Read Allen <peakstat@WISPERTEL.NET>
    • PharmaSUG submission question (38 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

31. Proc POWER question
    • Proc POWER question (12 lines)
      From: Jill Stoltzfus <jillstol@YAHOO.COM>

32. Q on fitting random change point model using nlmixed
    • Q on fitting random change point model using nlmixed (59 lines)
      From: Lei <kiki886@GMAIL.COM>

33. RES: NLMIXED Output combinations
    • RES: NLMIXED Output combinations (236 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

34. RES: NLMIXED Restrictions
    • Re: RES: NLMIXED Restrictions (347 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • RES: NLMIXED Restrictions (223 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

35. Read text file with missing values
    • Re: Read text file with missing values (112 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Read text file with missing values (97 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Read text file with missing values (54 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Read text file with missing values (31 lines)
      From: Sophia Tong <sophiDT@HOTMAIL.COM>

36. Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule!
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (58 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (47 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (38 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (72 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (44 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (53 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (88 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Register for SAS Global Forum 2011 _AND_ Add a Pre-Conference Seminar to Your Schedule! (62 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

37. SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (121 lines)
      From: r.hockey@SPH.UQ.EDU.AU
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (99 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (90 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (57 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (68 lines)
      From: r.hockey@SPH.UQ.EDU.AU
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (35 lines)
      From: templerr <templerr@CLEAR.NET.NZ>
    • Re: SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (42 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • SAS 9.2 Hot Fix Analysis, Download and Deployment Tool,SAS92HFADD Ver 1.0 (24 lines)
      From: Andre Wielki <wielki@INED.FR>

38. SAS DDE and Excel.....
    • Re: SAS DDE and Excel..... (152 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: SAS DDE and Excel..... (115 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>
    • SAS DDE and Excel..... (97 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>

39. SAS EG: where is the help for SAS procedures and functions (syntax)?
    • Re: SAS EG: where is the help for SAS procedures and functions (syntax)? (24 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • SAS EG: where is the help for SAS procedures and functions (syntax)? (14 lines)
      From: Mary <mlhoward@AVALON.NET>

40. SAS Graph Symbols
    • Re: SAS Graph Symbols (83 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: SAS Graph Symbols (68 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • SAS Graph Symbols (48 lines)
      From: Jules Bosch <jbosch1@OPTONLINE.NET>

41. SEM value
    • SEM value (15 lines)
      From: Ugur SERBESTER <ugurserbester@GMAIL.COM>

42. SQL LIKE condition with macro variable
    • Re: SQL LIKE condition with macro variable (166 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: SQL LIKE condition with macro variable (138 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SQL LIKE condition with macro variable (154 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: SQL LIKE condition with macro variable (119 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: SQL LIKE condition with macro variable (164 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: SQL LIKE condition with macro variable (107 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: SQL LIKE condition with macro variable (113 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • SQL LIKE condition with macro variable (75 lines)
      From: Jerry <i89rt5@GMAIL.COM>

43. Shell escape is not valid in this SAS session
    • Re: Shell escape is not valid in this SAS session (81 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Shell escape is not valid in this SAS session (58 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Shell escape is not valid in this SAS session (96 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Shell escape is not valid in this SAS session (69 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Shell escape is not valid in this SAS session (89 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Shell escape is not valid in this SAS session (83 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: Shell escape is not valid in this SAS session (61 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Shell escape is not valid in this SAS session (50 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Shell escape is not valid in this SAS session (40 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

44. Shocking News............................ Michelle Zunnurain
    • Re: Shocking News............................ Michelle Zunnurain (57 lines)
      From: John Burton <jrburtonsaspro@GMAIL.COM>
    • Re: Shocking News............................ Michelle Zunnurain (76 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Shocking News............................ Michelle Zunnurain (65 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Shocking News............................ Michelle Zunnurain (50 lines)
      From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>

45. THANK YOU SO MUCH! RE: Converting Narrow Data Set to Wide Data Set
    • THANK YOU SO MUCH! RE: Converting Narrow Data Set to Wide Data Set (199 lines)
      From: Sally Muller <sallymuller@BELLSOUTH.NET>

46. UltraEdit, SAS and Linux
    • Re: UltraEdit, SAS and Linux (85 lines)
      From: Paul Bartells <paul.bartells@TARGETBASE.COM>

47. WHERE LIKE operator wants to ESCAPE
    • Re: WHERE LIKE operator wants to ESCAPE (129 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: WHERE LIKE operator wants to ESCAPE (88 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • WHERE LIKE operator wants to ESCAPE (72 lines)
      From: Badrish Prakash <badrish.prakash@GMAIL.COM>

48. covariance structures and spatial autocorrelation
    • Re: covariance structures and spatial autocorrelation (121 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: covariance structures and spatial autocorrelation (101 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • covariance structures and spatial autocorrelation (76 lines)
      From: Keith Larson <keith.larson@ZOOEKOL.LU.SE>

49. data merging question
    • Re: data merging question (74 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>

50. data sets used in SAS Help and Documentation
    • Re: data sets used in SAS Help and Documentation (76 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: data sets used in SAS Help and Documentation (85 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: data sets used in SAS Help and Documentation (67 lines)
      From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: data sets used in SAS Help and Documentation (58 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: data sets used in SAS Help and Documentation (78 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: data sets used in SAS Help and Documentation (53 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: data sets used in SAS Help and Documentation (32 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • data sets used in SAS Help and Documentation (16 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

51. file shortcuts question remade
    • Re: file shortcuts question remade (101 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: file shortcuts question remade (96 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: file shortcuts question remade (82 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: file shortcuts question remade (69 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

52. funny code, formatted input or list input or neither
    • Re: funny code, formatted input or list input or neither (61 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: funny code, formatted input or list input or neither (113 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

53. how to calculate average for below data?
    • Re: how to calculate average for below data? (94 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: how to calculate average for below data? (76 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: how to calculate average for below data? (64 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • how to calculate average for below data? (46 lines)
      From: Nway <hymadsk@GMAIL.COM>

54. how to change the default value "1" under proc report across varaible?
    • Re: how to change the default value "1" under proc report across varaible? (120 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: how to change the default value "1" under proc report across varaible? (109 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: how to change the default value "1" under proc report across varaible? (61 lines)
      From: Zibiao Zhang <zzhang@HSPH.HARVARD.EDU>
    • Re: how to change the default value "1" under proc report across varaible? (50 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • how to change the default value "1" under proc report across varaible? (30 lines)
      From: Steven Chang <zzhang@HSPH.HARVARD.EDU>

55. how to change the default value "1" under proc report across variable?
    • Re: how to change the default value "1" under proc report across variable? (143 lines)
      From: Huang, Ya <Ya.Huang@AMYLIN.COM>

56. how to convert one variable into multiple columns according its value?
    • Re: how to convert one variable into multiple columns according its value? (34 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: how to convert one variable into multiple columns according its value? (28 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

57. how to get macro variable length
    • Re: how to get macro variable length (51 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

58. if, where, executable
    • Re: if, where, executable (107 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: if, where, executable (71 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: if, where, executable (49 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: if, where, executable (32 lines)
      From: Andrew Howell <info@ANJGROUP.NET.AU>
    • Re: if, where, executable (67 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: if, where, executable (66 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: if, where, executable (48 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: if, where, executable (29 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • if, where, executable (17 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

59. infile option DLMSTR
    • Re: infile option DLMSTR (39 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: infile option DLMSTR (20 lines)
      From: Pradeep <chittiprolupradeep@GMAIL.COM>
    • infile option DLMSTR (31 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

60. logistic regression default probability to credit score, how?
    • logistic regression default probability to credit score, how? (13 lines)
      From: Jeff <zhujp98@GMAIL.COM>

61. nonlinear optimization
    • nonlinear optimization (21 lines)
      From: Amal Helu <helu.amal@GMAIL.COM>

62. percent2.
    • Re: percent2. (35 lines)
      From: Jack F. Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: percent2. (58 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: percent2. (45 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • percent2. (23 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

63. problems labelling bar charts in SAS
    • problems labelling bar charts in SAS (89 lines)
      From: Taylor Harchak <tharc@DOH.HEALTH.NSW.GOV.AU>

64. reading data columns
    • Re: reading data columns (130 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: reading data columns (42 lines)
      From: oslo <hokut1@YAHOO.COM>
    • Re: reading data columns (30 lines)
      From: oslo <hokut1@YAHOO.COM>
    • Re: reading data columns (59 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: reading data columns (112 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: reading data columns (95 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: reading data columns (82 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: reading data columns (73 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: reading data columns (61 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: reading data columns (24 lines)
      From: oslo <hokut1@YAHOO.COM>
    • Re: reading data columns (44 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: reading data columns (40 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • reading data columns (16 lines)
      From: oslo <hokut1@YAHOO.COM>

65. regarding low-cost or free video tutoring
    • Re: regarding low-cost or free video tutoring (61 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • regarding low-cost or free video tutoring (14 lines)
      From: Ki Se Lee <lee.kise@GMAIL.COM>

66. repost: problems labelling bar charts in SAS
    • Re: repost: problems labelling bar charts in SAS (9 lines)
      From: Taylor Harchak <tharc@DOH.HEALTH.NSW.GOV.AU>
    • Re: repost: problems labelling bar charts in SAS (35 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: repost: problems labelling bar charts in SAS (216 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: repost: problems labelling bar charts in SAS (176 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • repost: problems labelling bar charts in SAS (116 lines)
      From: Taylor Harchak <tharc@DOH.HEALTH.NSW.GOV.AU>

67. set nomail
    • set nomail (10 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>

68. sum statement, if/then, loop
    • Re: sum statement, if/then, loop (58 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • sum statement, if/then, loop (28 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

69. system options: LS ?
    • Re: system options: LS ? (32 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • system options: LS ? (12 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

70. the line holder @
    • Re: the line holder @ (156 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: the line holder @ (141 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: the line holder @ (78 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • the line holder @ (32 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

71. transformation in proc prinqual
    • transformation in proc prinqual (15 lines)
      From: Ratna Patel <patelratna74@GMAIL.COM>

72. using put without file
    • Re: using put without file (34 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • using put without file (22 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

73. variable-length records
    • Re: variable-length records (49 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: variable-length records (35 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

74. writing SAS code in MS outlook
    • Re: writing SAS code in MS outlook (41 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • writing SAS code in MS outlook (20 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>