LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (December 2006)Back to main SPSSX-L pageJoin or leave SPSSX-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Sun, 10 Dec 2006 15:54:46 -0500
Reply-To:     Richard Ristow <wrristow@mindspring.com>
Sender:       "SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>
From:         Richard Ristow <wrristow@mindspring.com>
Subject:      Re: XSAVE vs SAVE
Comments: cc: Brian Pickerill <bpickerill@bsu.edu>
In-Reply-To:  <7.0.1.0.2.20061208170702.02a70a78@mindspring.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed

Correction, to an inadequately edited posting: At 03:50 PM 12/9/2006, I wrote:

><Input and transformations> >XSAVE <output file>. ><procedure>. >GET FILE <output file> > >is approximately equivalent to > ><Input and transformations> >XSAVE <output file>. ><procedure>. >GET FILE <output file>.

Since they're identical, they OUGHT to be equivalent. The first example was supposed to use CACHE, like this:

<Input and transformations> CACHE. <procedure>.

is approximately equivalent to

<Input and transformations> XSAVE <output file>. <procedure>. GET FILE <output file>.

It is correct, as I stated, that

>Using XSAVE lets you bypass CACHE restrictions, including that ".. A >cache file will not be written during a procedure that uses temporary >variables." (SPSS 14 Command Syntax Reference p. 177).

-Embarrassed, Richard


Back to: Top of message | Previous page | Main SPSSX-L page