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 (September 2010)Back to main SPSSX-L pageJoin or leave SPSSX-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 13 Sep 2010 17:34:23 -0400
Reply-To:     Richard Ristow <>
Sender:       "SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>
From:         Richard Ristow <>
Subject:      Re: Fw: Glitch in CASESTOVARS? (SPSS 14)
Comments: To: SPSS Support <>
In-Reply-To:  <OF8FA20861.B11E13CF-ON8625779D.0058BF19-8625779D.0059715E@
Content-Type: text/html; charset="us-ascii"

<html> <body> At 12:16 PM 9/13/2010, SPSS Support wrote:<br><br> <blockquote type=cite class=cite cite="">If the INDEX variable is a string and there is only one variable that varies within the ID values, then the RENAME and SEPARATOR subcommands (whether present or implied) are ignored&nbsp; and the actual string values are used as the new names without using the original name as a prefix.. If the string contains characters that are not allowed in a variable name, then warnings are issued and&nbsp; generic names, such as v1, are used. This behavior is intended for the case where there is only one variable&nbsp; that varies within each ID value and one want to use the index variable to generate names for the result variables.</blockquote><br> I figured that SPSS was being 'cute' like that. The problem, of course, is that it contradicts the documentation (as you note); and that it can 'break' code that would run if SPSS behaved according to the documentation.<br><br> <blockquote type=cite class=cite cite="">A documentation bug has been filed to request that the naming algorithm for the above situation be described in Help files and the Command Syntax Reference.</blockquote><br> Thank you; I appreciate that.<br><br> Ah, for 'cute'. I used to teach mini-courses in JCL for IBM's OS/360. JCL's notoriously confusing. I found a useful mantra: &quot;JCL isn't really so bad, except for the features that were put in to make it easy to use.&quot; It's always tempting to add such features.<br><br> Anyway, you write,<br><br> <blockquote type=cite class=cite cite="">As a current work-around, if you want the new variable names to have the root and separator, you could compute the new index by concatenating the root and separator to the front of the original index:<br> &nbsp; <br> <tt><font size=2>string root_inst (A7) . <br> compute root_inst = concat(&quot;Inst.&quot;,inst). <br> CASESTOVARS <br> &nbsp;/ID = Group <br> &nbsp;/INDEX = root_inst <br> &nbsp;/GROUPBY = VARIABLE <br> &nbsp; /drop = Inst .</font></tt> </blockquote><br> That's the solution I reached, and used in my posting<br><br> <tt><font size=2>Date:&nbsp;&nbsp;&nbsp; Thu, 9 Sep 2010 01:18:32 -0400<br> From:&nbsp;&nbsp;&nbsp; Richard Ristow &lt;;<br> Subject: Re: sorting out a nested data structure<br> To:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SPSSX-L@LISTSERV.UGA.EDU<br><br> </font></tt>But, again, making the feature significantly more complicated to use and to explain, by making it 'easier'.<br><br> -With thanks, and some sighs,<br> &nbsp;Richard</body> <br> </html>

===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@LISTSERV.UGA.EDU (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

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