%concordance in SAS Logistic regressionRe: %concordance in SAS Logistic regression (43 lines) From: DNordlund <dnordlund@AOL.COM> Re: %concordance in SAS Logistic regression (43 lines) From: Ellen Hertz <ehertz@PATRIOT.NET> (MVS): Re(?): MVS SAS dataset # of tracks utility?(MVS): Re(?): MVS SAS dataset # of tracks utility? (121 lines) From: Michael A. Raithel <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM> (MVS): Rethinking Reply: MVS SAS dataset # of tracks utilit(MVS): Rethinking Reply: MVS SAS dataset # of tracks utilit (112 lines) From: Michael A. Raithel <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM> (No Subject)(No Subject) (23 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> 50 Million Email Addresses FREE!!!! -BKVD50 Million Email Addresses FREE!!!! -BKVD (213 lines) From: 50mil1ion@MAILCITY.COM <No subject><No subject> (79 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (113 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (41 lines) From: Esther Colwell <ecolwell@WELLSFARGO.COM> <No subject> (37 lines) From: Sarita Bedge <sbedge@BCIDAHO.COM> <No subject> (8 lines) From: Justin Prost <justinp@ASU.EDU> <No subject> (8 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
(MVS): Re(?): MVS SAS dataset # of tracks utility?(MVS): Re(?): MVS SAS dataset # of tracks utility? (121 lines) From: Michael A. Raithel <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM> (MVS): Rethinking Reply: MVS SAS dataset # of tracks utilit(MVS): Rethinking Reply: MVS SAS dataset # of tracks utilit (112 lines) From: Michael A. Raithel <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM> (No Subject)(No Subject) (23 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> 50 Million Email Addresses FREE!!!! -BKVD50 Million Email Addresses FREE!!!! -BKVD (213 lines) From: 50mil1ion@MAILCITY.COM <No subject><No subject> (79 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (113 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (41 lines) From: Esther Colwell <ecolwell@WELLSFARGO.COM> <No subject> (37 lines) From: Sarita Bedge <sbedge@BCIDAHO.COM> <No subject> (8 lines) From: Justin Prost <justinp@ASU.EDU> <No subject> (8 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
(MVS): Rethinking Reply: MVS SAS dataset # of tracks utilit(MVS): Rethinking Reply: MVS SAS dataset # of tracks utilit (112 lines) From: Michael A. Raithel <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM> (No Subject)(No Subject) (23 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> 50 Million Email Addresses FREE!!!! -BKVD50 Million Email Addresses FREE!!!! -BKVD (213 lines) From: 50mil1ion@MAILCITY.COM <No subject><No subject> (79 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (113 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (41 lines) From: Esther Colwell <ecolwell@WELLSFARGO.COM> <No subject> (37 lines) From: Sarita Bedge <sbedge@BCIDAHO.COM> <No subject> (8 lines) From: Justin Prost <justinp@ASU.EDU> <No subject> (8 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
(No Subject)(No Subject) (23 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> 50 Million Email Addresses FREE!!!! -BKVD50 Million Email Addresses FREE!!!! -BKVD (213 lines) From: 50mil1ion@MAILCITY.COM <No subject><No subject> (79 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (113 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (41 lines) From: Esther Colwell <ecolwell@WELLSFARGO.COM> <No subject> (37 lines) From: Sarita Bedge <sbedge@BCIDAHO.COM> <No subject> (8 lines) From: Justin Prost <justinp@ASU.EDU> <No subject> (8 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
50 Million Email Addresses FREE!!!! -BKVD50 Million Email Addresses FREE!!!! -BKVD (213 lines) From: 50mil1ion@MAILCITY.COM <No subject><No subject> (79 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (113 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (41 lines) From: Esther Colwell <ecolwell@WELLSFARGO.COM> <No subject> (37 lines) From: Sarita Bedge <sbedge@BCIDAHO.COM> <No subject> (8 lines) From: Justin Prost <justinp@ASU.EDU> <No subject> (8 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
<No subject><No subject> (79 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (113 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> <No subject> (41 lines) From: Esther Colwell <ecolwell@WELLSFARGO.COM> <No subject> (37 lines) From: Sarita Bedge <sbedge@BCIDAHO.COM> <No subject> (8 lines) From: Justin Prost <justinp@ASU.EDU> <No subject> (8 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
A LANDSCAPE Report on Web?(GPRINT/PS/PDF..)A LANDSCAPE Report on Web?(GPRINT/PS/PDF..) (77 lines) From: yude_lin@ROCKETMAIL.COM Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Accessing data on a Tandem machineAccessing data on a Tandem machine (27 lines) From: Daood, Susanne L. (Susanne Daood) <daood@MAYO.EDU> Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Advanced search in the SAS-L archiveRe: Advanced search in the SAS-L archive (95 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Analysis of covariatesAnalysis of covariates (15 lines) From: Bill Murry <murry@BINGHAMTON.EDU> Re: Analysis of covariates (31 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Anyone Using COGNOS?Anyone Using COGNOS? (20 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Anyone Using COGNOS? (39 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Call for papers on GIS in social science; advance table of contentsCall for papers on GIS in social science; advance table of contents (94 lines) From: David Garson <Garson@SOCIAL.CHASS.NCSU.EDU> Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Career OpportunityCareer Opportunity (25 lines) From: jim@FORTUNESAT.COM Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Changing order of variables in datasetChanging order of variables in dataset (20 lines) From: Melanie Barish <MelliJ@AOL.COM> Re: Changing order of variables in dataset (39 lines) From: mushtaq mohammad <mushtaq@UX6.CSO.UIUC.EDU> Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Clarifying my question on how to find fileref for last executed fRe: Clarifying my question on how to find fileref for last executed f (28 lines) From: LPogoda <lpogoda@AOL.COM> Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Clarifying my question on how to find fileref for last executed f ile statementClarifying my question on how to find fileref for last executed f ile statement (84 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Clean MemoryClean Memory (16 lines) From: Dong Li <dongli@TAMU.EDU> Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Clustering problemClustering problem (24 lines) From: O C Gopinath <gopi@DCS.SHEF.AC.UK> Re: Clustering problem (17 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Compressing datasetsRe: Compressing datasets (60 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Compressing datasets (54 lines) From: Don Stanley <don_stanley@IBM.NET> Compressing datasets (17 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: Compressing datasets (47 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Could use some advice about possibly too many if-then stRe: Could use some advice about possibly too many if-then st (93 lines) From: WHITLOI1 <WHITLOI1@WESTAT.COM> Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Could use some advice about possibly too many if-then statementsRe: Could use some advice about possibly too many if-then statements (103 lines) From: Keith J. Brown <kjb@GA.UNC.EDU> Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Could use some advice about possibly too many if-then statements -ReplyCould use some advice about possibly too many if-then statements -Reply (75 lines) From: Claudia Bullock <CBullock@HCFA.GOV> Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Could use some advice about... (Thanks)Could use some advice about... (Thanks) (12 lines) From: David E. Elkins <ELKINS@PICARD.EVMS.EDU> Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Deleting duplicate recordsRe: Deleting duplicate records (135 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Determine fileref currently in useDetermine fileref currently in use (21 lines) From: Scheibert, Valinda <Valinda.Scheibert@OFM.WA.GOV> Re: Determine fileref currently in use (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Determine fileref currently in use (54 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Re: Determine fileref currently in use (50 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Determine fileref currently in use (65 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Diplay numbers on graph object within a frameDiplay numbers on graph object within a frame (33 lines) From: MARIANNE NICOLAYSEN <marianne.nicolaysen@GOODYEAR.COM> Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Enhancement to magic string ( reset DMS ennvironment )Enhancement to magic string ( reset DMS ennvironment ) (39 lines) From: Xlr82sas <xlr82sas@AOL.COM> Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Enhancement to magic string ( reset DMS environment )Re: Enhancement to magic string ( reset DMS environment ) (95 lines) From: Self, Karsten <kself@VISA.COM> Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Excel to SAS via PROC ACCESSExcel to SAS via PROC ACCESS (64 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> Re: Excel to SAS via PROC ACCESS (88 lines) From: Edward Heaton <edheaton@FENIX2.DOL-ESA.GOV> Re: Excel to SAS via PROC ACCESS (104 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: Excel to SAS via PROC ACCESS (120 lines) From: Boylan, Dave <dboylan@UTILICORP.COM> Re: Excel to SAS via PROC ACCESS (22 lines) From: Jules Bosch <jxb@BELLATLANTIC.NET> FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
FW: Is there a connect session?FW: Is there a connect session? (66 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: FW: Is there a connect session? (102 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: FW: Is there a connect session? (23 lines) From: LPogoda <lpogoda@AOL.COM> FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
FW: Rutgers SeminarFW: Rutgers Seminar (68 lines) From: Barron, Alfred [PRI] <ABARRON@PRIUS.JNJ.COM> Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Fourier transforms with SAS?Fourier transforms with SAS? (24 lines) From: Puhong Gao <pgao@BROADWAY.GC.CUNY.EDU> Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Funny array subscript error.Funny array subscript error. (42 lines) From: IAS <iasinfo@MEDIAONE.NET> Re: Funny array subscript error. (78 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
GET CASH FOR YOUR HOME PROJECT!!!!!!GET CASH FOR YOUR HOME PROJECT!!!!!! (29 lines) From: steep@TOEBCBDV.CA General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
General Information Technology Services/SAS System Sub-ContractingGeneral Information Technology Services/SAS System Sub-Contracting (60 lines) From: Joe Whitehurst <joewhite@MINDSPRING.COM> Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Getting path and file name from user (VAX VMS, SAS 6.08)Getting path and file name from user (VAX VMS, SAS 6.08) (35 lines) From: James Donat <DONATJR@THIOKOL.COM> Re: Getting path and file name from user (VAX VMS, SAS 6.08) (50 lines) From: Phil Rack <philrack@CSI.COM> Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Hardware required to work on very large file.Re: Hardware required to work on very large file. (54 lines) From: Melvin Klassen <Klassen@UVIC.CA> Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Help with Reading IMF datafileRe: Help with Reading IMF datafile (28 lines) From: Quan Li <qxl4@PSU.EDU> Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Help with multiple line inputHelp with multiple line input (56 lines) From: Maria M. Corrada <mcorrada@WELCHLINK.WELCH.JHU.EDU> Re: Help with multiple line input (100 lines) From: Berryhill, Timothy <TWB2@PGE.COM> Re: Help with multiple line input (34 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help with multiple line input (103 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (58 lines) From: Lanning, Chris <clanning@AMGEN.COM> Re: Help with multiple line input (62 lines) From: Berryhill, Timothy <TWB2@PGE.COM> How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
How to temporarily stop sas-l ?How to temporarily stop sas-l ? (14 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (12 lines) From: Jun Wang <wang.j.2@PG.COM> Re: How to temporarily stop sas-l ? (34 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
How to translate SPSS->SAS with SPSS95, SAS 6.11How to translate SPSS->SAS with SPSS95, SAS 6.11 (24 lines) From: Javier <jportela@EUCMAX.SIM.UCM.ES> Re: How to translate SPSS->SAS with SPSS95, SAS 6.11 (50 lines) From: jjc@ASU.EDU Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Is there a connect session?Is there a connect session? (56 lines) From: David Johnson <david_johnson@TAC.VIC.GOV.AU> Re: Is there a connect session? (63 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
JFCB option in Infile Statement.JFCB option in Infile Statement. (28 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
JFCB option in Infile Statement.-- NB -- very long responseRe: JFCB option in Infile Statement.-- NB -- very long response (564 lines) From: Don Stanley <don_stanley@IBM.NET> JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
JOB--Risk Analyst II - SAS @ Portland, ORJOB--Risk Analyst II - SAS @ Portland, OR (84 lines) From: sevakumar@MY-DEJANEWS.COM Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Job opportunityJob opportunity (52 lines) From: Matthias Kehder <kehder@MEDIAONE.NET> MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MANN-WHITNEY/T-TESTMANN-WHITNEY/T-TEST (19 lines) From: Ulf Emanuelson <ulf.emanuelson@EPID.SLU.SE> Re: MANN-WHITNEY/T-TEST (43 lines) From: Mark S Dehaan <MSD@INEL.GOV> Re: MANN-WHITNEY/T-TEST (30 lines) From: John Whittington <medisci@POWERNET.COM> Re: MANN-WHITNEY/T-TEST (52 lines) From: Bertil Runström <bertil.runstrom@_REMOVE_MBOX300.SWIPNET.SE> Re: MANN-WHITNEY/T-TEST (28 lines) From: DNordlund <dnordlund@AOL.COM> MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MONEY FROM YOUR HOUSEMONEY FROM YOUR HOUSE (29 lines) From: steep@KNRYMMUP.EDU MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MORE CASH FOR FUN!MORE CASH FOR FUN! (21 lines) From: steep@RADEIURH.NET MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MS Access95 -> SAS via ODBC - very slow!Re: MS Access95 -> SAS via ODBC - very slow! (212 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: MS Access95 -> SAS via ODBC - very slow! (44 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: MS Access95 -> SAS via ODBC - very slow! (39 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> MS Access95 -> SAS via ODBC - very slow! (51 lines) From: Erik M Rasmussen <erik.rasmussen@LEO.DK> Re: MS Access95 -> SAS via ODBC - very slow! (194 lines) From: Allison from Intrawares <support@INTRAWARES.COM> MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MVS SAS dataset # of tracks (FIX)Re: MVS SAS dataset # of tracks (FIX) (13 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MVS SAS dataset # of tracks utility?MVS SAS dataset # of tracks utility? (23 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> Re: MVS SAS dataset # of tracks utility? (123 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> Re: MVS SAS dataset # of tracks utility? (129 lines) From: Steve Giblin <Steve_Giblin@VAPOWER.COM> MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
MVS SAS dataset # of tracks utility? (& input @'str')MVS SAS dataset # of tracks utility? (& input @'str') (115 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Macro Sub For INFILE StatementMacro Sub For INFILE Statement (58 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Re: Macro Sub For INFILE Statement (9 lines) From: Laurence P Adair <Laurence_P_Adair@SWRI.JA.DSWA.MIL.NOSPAM> Re: Macro Sub For INFILE Statement (29 lines) From: LPogoda <lpogoda@AOL.COM> Re: Macro Sub For INFILE Statement (69 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (14 lines) From: whiterr@MY-DEJANEWS.COM Re: Macro Sub For INFILE Statement (20 lines) From: Andreas Grueninger <grueni@STUTTGART.NETSURF.DE> Re: Macro Sub For INFILE Statement (70 lines) From: Myra Oltsik <Myra.Oltsik@RESPONSEINSURANCE.COM> Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Macro var. resolution when using RSUBMITMacro var. resolution when using RSUBMIT (43 lines) From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Re: Macro var. resolution when using RSUBMIT (28 lines) From: Clive Hunt <hunt@IAFRICA.COM> Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Macro-Var-resolution when using RSUBMITRe: Macro-Var-resolution when using RSUBMIT (55 lines) From: Olaf <Olaf.Kruse@VST-GMBH.DE> Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Macrovariables in ConnectRe: Macrovariables in Connect (63 lines) From: Rob Rohrbough <rob@ROHRBOUGH-SYSTEMS.COM> Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Money.....Money.....Money.....Money.....Money...Money.....Money.....Money.....Money.....Money... (20 lines) From: steep@DJXHWJRX.EDU Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Need CDC's, Data Manager's,SAS Programmer'sNeed CDC's, Data Manager's,SAS Programmer's (28 lines) From: Connie Quintal <ckq@ASG-INC.COM> OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
OK, Another Easy OneRe: OK, Another Easy One (97 lines) From: Steve Morton <steve_morton@ASK.U-NET.COM> ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
ORACLE via Pass-ThruRe: ORACLE via Pass-Thru (57 lines) From: O'Connell, Martin <MO'Connell@GEICO.COM> Re: ORACLE via Pass-Thru (31 lines) From: LPogoda <lpogoda@AOL.COM> Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Obtaining MVS File Creation Date From Within SASRe: Obtaining MVS File Creation Date From Within SAS (42 lines) From: HOANG, DUC D <duc.hoang@BELLSYGMA.COM> Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Optimal MEMSIZEOptimal MEMSIZE (13 lines) From: Lewis, Paul <Paul.Lewis@WL.COM> Re: Optimal MEMSIZE (55 lines) From: Ravi, Prasad <Prasad.Ravi@WL.COM> Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Options/Expiration DatesOptions/Expiration Dates (12 lines) From: SS <sseitz@MAILHOST.COL.AMERITECH.NET> Re: Options/Expiration Dates (25 lines) From: Self, Karsten <kself@VISA.COM> Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Ordering word tokensRe: Ordering word tokens (35 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Ordering word tokens (46 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Ordering word tokens (272 lines) From: Dorfman, Paul <pdorfma@UCS.ATT.COM> Re: Ordering word tokens (176 lines) From: Paul M. Dorfman <pdorfma@UCS.ATT.COM> PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PERMANENT SAS oppportunities?????PERMANENT SAS oppportunities????? (20 lines) From: Lauren Ellerbe <lle@SIGCONSULT-NC.COM> PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PROC FREQ LIMITATION: Question AnsweredPROC FREQ LIMITATION: Question Answered (18 lines) From: SFBAY0001 <sfbay0001@AOL.COM> PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PROC FREQ Limitation questionPROC FREQ Limitation question (23 lines) From: SFBAY0001 <sfbay0001@AOL.COM> Re: PROC FREQ Limitation question (18 lines) From: Michael Yu <Michael_Yu@FREDDIEMAC.COM> PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PROC SORT NODUP OptionRe: PROC SORT NODUP Option (154 lines) From: Rodney Marwick <rmarwick@SPS-OZ.COM.AU> Re: PROC SORT NODUP Option (17 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT NODUP Option (199 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re[2]: PROC SORT NODUP Option (22 lines) From: Jack Hamilton <jack_hamilton@FIRSTHEALTH.COM> Re: PROC SORT NODUP Option (18 lines) From: LPogoda <lpogoda@AOL.COM> Re: PROC SORT NODUP Option (159 lines) From: Steven E. Stevens <sstevens@COMCAT.COM> Re: PROC SORT NODUP Option (64 lines) From: Self, Karsten <kself@VISA.COM> Re: PROC SORT NODUP Option (61 lines) From: LPogoda <lpogoda@AOL.COM> PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PROC SORT NODUP vs PROC SQL DISTINCTPROC SORT NODUP vs PROC SQL DISTINCT (42 lines) From: Ray Pass <raypass@WORLDNET.ATT.NET> Re: PROC SORT NODUP vs PROC SQL DISTINCT (141 lines) From: Self, Karsten <kself@VISA.COM> PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PROC SORT; BY _ALL;Re: PROC SORT; BY _ALL; (14 lines) From: Gorrell_P <Gorrell_P@BLS.GOV> Re: PROC SORT; BY _ALL; (27 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (31 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (41 lines) From: Victor Kamensky <kamensky@AECOM.YU.EDU> Re: PROC SORT; BY _ALL; (45 lines) From: John Whittington <medisci@POWERNET.COM> Re: PROC SORT; BY _ALL; (49 lines) From: Bartells, Paul <paul.bartells@US.ORIGIN-IT.COM> Re: PROC SORT; BY _ALL; (59 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: PROC SORT; BY _ALL; (118 lines) From: Don Stanley <don_stanley@IBM.NET> Re: PROC SORT; BY _ALL; (54 lines) From: John Whittington <medisci@POWERNET.COM> PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
PathoGenesis PositionPathoGenesis Position (58 lines) From: Page, Terry <TPAGE@PATHOGENESIS.COM> Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Pharmaceutical SAS Job: Charlottesville VA, USAPharmaceutical SAS Job: Charlottesville VA, USA (43 lines) From: Walke, Lee <WalkeLee@PRA-WW.COM> Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Please tell me how to delete duplicate observations in a SAS sd fileRe: Please tell me how to delete duplicate observations in a SAS sd file (29 lines) From: TurnerCL@MISSOURI.EDU Re: Please tell me how to delete duplicate observations in a SAS sd file (48 lines) From: Self, Karsten <kself@VISA.COM> Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Poisson regressionRe: Poisson regression (43 lines) From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA> Re: Poisson regression (50 lines) From: sobrinj@TOWERS.COM Re: Poisson regression (39 lines) From: Terry Hyslop <Terry.Hyslop@MAIL.TJU.EDU> Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Posted But I Could Not See It.Posted But I Could Not See It. (53 lines) From: John T. Jones <jonesj@PHARMARESEARCH.COM> Re: Posted But I Could Not See It. (21 lines) From: Terry del Fuego <atrocity@MY-DEJANEWS.COM> Re: Posted But I Could Not See It. (79 lines) From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV> Re: Posted But I Could Not See It. (69 lines) From: F. Joseph Kelley <jkelley@ARCHES.UGA.EDU> Re: Posted But I Could Not See It. (73 lines) From: Michael Hines <mshines@PURDUE.EDU> Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Proc SQL to OracleProc SQL to Oracle (49 lines) From: Carl H. Ostermann <osterman@POBOX.UPENN.EDU> Re: Proc SQL to Oracle (60 lines) From: Carol Bristow <CBristow@DPRA.COM> Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Putting plot symbols in a titlePutting plot symbols in a title (18 lines) From: Rick Madsen <rmadsen@WIN.BRIGHT.NET> Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Q: Advanced search in the SAS-L archiveQ: Advanced search in the SAS-L archive (37 lines) From: Stuerzl, Heinr.,DE,Diagnostics <STUERZL@MSMBWMA.HOECHST.COM> Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Qu about data cleaning before matching in SASRe: Qu about data cleaning before matching in SAS (22 lines) From: christopher chan <wychan@U4000.STA.CUHK.EDU.HK> Re: Qu about data cleaning before matching in SAS (36 lines) From: Bruce Johnson <bjohnson@SACHS.COM> Qu about data cleaning before matching in SAS (17 lines) From: christopher chan <conjecture@GEOCITIES.COM> Re: Qu about data cleaning before matching in SAS (32 lines) From: Dr. Stuart Savory <savory.pad@SNI.DE> Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Re (?): MVS SAS dataset # of tracks utility?Re (?): MVS SAS dataset # of tracks utility? (28 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Remote Library Services question
Remote Library Services question