AGGREGATE variables limitations?

[Egon Kraan]

Is there a limit to the number of variables allowed on the AGGREGATE
command?

I have a couple of vector elements, each of about 25000 elements, that I am
trying run through the AGGREGATE command, and I keep getting the following
error message.

>Error # 10945 in column 146.  Text: qy24310
>The AGGREGATE command specifies too many break variables plus new
>variables.  Rerun with more memory.
>This command not executed.

where qy is the vector

vector qy=qy1 to qy24310.

so my guess is that either there are some limits on the number of variables
that can be entered into a single vector element, which I don't think is the
case because the error message does not refer to the vector, but the
aggregate.

or there is some sort of limit on the Aggregate command.

compute nobreak =1.
exe.

aggregate
  /outfile='c:\temp\tempout.sav'
  /break = nobreak
  /basketcnt = mean(cnt)
  /qy1 to qy24310 = mean(qy1 to qy24310) .
exe.

Any ideas?

Thanks

Egon Kraan
Research Analyst
TNS NFO
600 Vine Street, Suite 300
Cincinnati, Ohio 45202

Phone:   [phone]
Fax:       [phone]
Email:    [hidden email]
Web:      www.tns-global.com
----------------------------------------------------------------------------
------------
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the addressee or authorized to receive this for the
addressee,
you must not use, copy, disclose or take any action based on this message
or any information herein. If you have received this message in error,
please advise the sender immediately by reply e-mail and delete this
message. Thank you for your cooperation.
----------------------------------------------------------------------------
------------

[Jason Burke]

Hi Egon,

The documentation provides some suggestions for using AGGREGATE with
large files. The key is to first sort your file by the break
variables(s), and insert the subcommand /PRESORTED into your syntax.

Since your break variable is a dummy variable the SORT is unnecessary,
so I have commented it out:  You can also omit the EXECUTE statements
that you had since they are both redundant.

compute nobreak =1.
#exe .

#sort cases by nobreak (A) .

aggregate
  /outfile='c:\temp\tempout.sav'
  /presorted
  /break = nobreak
  /basketcnt = mean(cnt)
  /qy1 to qy24310 = mean(qy1 to qy24310) .
#exe .


On 1/5/07, Egon Kraan <[hidden email]> wrote:

> Is there a limit to the number of variables allowed on the AGGREGATE
> command?
>
> I have a couple of vector elements, each of about 25000 elements, that I am
> trying run through the AGGREGATE command, and I keep getting the following
> error message.
>
> >Error # 10945 in column 146.  Text: qy24310
> >The AGGREGATE command specifies too many break variables plus new
> >variables.  Rerun with more memory.
> >This command not executed.
>
> where qy is the vector
>
> vector qy=qy1 to qy24310.
>
> so my guess is that either there are some limits on the number of variables
> that can be entered into a single vector element, which I don't think is the
> case because the error message does not refer to the vector, but the
> aggregate.
>
> or there is some sort of limit on the Aggregate command.
>
> compute nobreak =1.
> exe.
>
> aggregate
>  /outfile='c:\temp\tempout.sav'
>  /break = nobreak
>  /basketcnt = mean(cnt)
>  /qy1 to qy24310 = mean(qy1 to qy24310) .
> exe.
>
> Any ideas?
>
> Thanks
>
> Egon Kraan
> Research Analyst
> TNS NFO
> 600 Vine Street, Suite 300
> Cincinnati, Ohio 45202
>
> Phone:   [phone]
> Fax:       [phone]
> Email:    [hidden email]
> Web:      www.tns-global.com
> ----------------------------------------------------------------------------
> ------------
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the addressee or authorized to receive this for the
> addressee,
> you must not use, copy, disclose or take any action based on this message
> or any information herein. If you have received this message in error,
> please advise the sender immediately by reply e-mail and delete this
> message. Thank you for your cooperation.
> ----------------------------------------------------------------------------
> ------------
>