home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!darwin.sura.net!paladin.american.edu!auvm!ESPRESSO.BOEING.COM!OLDENKMP
- From: oldenkmp@ESPRESSO.BOEING.COM ((P. Oldenkamp 5-4481))
- Newsgroups: bit.listserv.sas-l
- Subject: Re: WHERE statement in PROC PLOT?
- Message-ID: <9211100048.AA16664@espresso.bcs.eca>
- Date: 10 Nov 92 00:48:37 GMT
- Sender: "SAS(r) Discussion" <SAS-L@UGA.BITNET>
- Reply-To: "(P. Oldenkamp 5-4481)" <oldenkmp@ESPRESSO.BOEING.COM>
- Lines: 30
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Comments: To: sas-l@uga.cc.uga.edu
-
- ----------------------------------------------------------------------
- CONTENT: UPDATE--WHERE statement in PROC PLOT doesn't work right
- REL/PLTF: 6.07TS302--MVS/ESA
- E-ADDR: oldenkmp@ESPRESSO.boeing.com
- NAME: Paul OldenKamp
- PHONE: 206-865-4481
- ----------------------------------------------------------------------
- Here is what I have learned about the use of where statments in run
- groups of interactive procs. I have encountered an incorrect result
- when I used a where statement in the second or subsequent run groups of
- a PROC PLOT with 6.07TS302 on MVS. I did not get this error on SunOS,
- 6.07TS203, and Kernon did not get it when he tried VMS. So far no one
- has sent me a report of what happens for them on MVS.
-
- It seems that this use of the where statment never works in PROC REG since
- both Kernon on VMS and I on MVS and SunOS got an error, but a different
- error message that I got with PROC PLOT.
-
- This use of the where statement works fine for me with PROC GPLOT on
- both MVS and SunOS.
- ----------------------------------------------------------------------
- // Paul OldenKamp
- // BCS Research and Technology .
- // P. O. Box 24346, MS 7L-21 |\
- // Seattle, WA 98124-0346 | \____oo_
- //==========================================((__| /___>
- // ___ ___ ___ ___ __ | //
- // /__// //__ / /\ // _ |//
- // /__//__//__ _/_ / //__/ ''
- /
-