Date:         Wed, 5 Jun 2002 14:10:02 -0400
Reply-To:     "Brucken, Nancy" <Nancy.Brucken@PFIZER.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Brucken, Nancy" <Nancy.Brucken@PFIZER.COM>
Subject:      PROC REPORT memory issues with BY groups- solved
Content-Type: text/plain; charset="windows-1252"

Thanks to Frank Poppe, Ray Pass and others who replied to this message.  It
turns out this is caused by a problem in 8.2;  a hotfix is expected to be
released sometime in the next several weeks.  The actual code generating the
error is as follows:

proc format;
  value grtitl
    1="0 to 23.99 hrs post dose      "
    2="24+ Hours Post Dose           " ;
run;


proc sort data=allgroups;
  by egtestcd _grId trtgrpcd _SummStatOrd;
run;

options linesize = 160;
options nocenter;

proc report nowindows data=allgroups split='£' spacing=2 headline missing;
  by egtestcd _grId ;
  columns ('__' trtgrp _summStat _GrTitle, _Value);
  define trtgrp/order order=data width = 12 flow;
  define _Summstat/display width = 10;
  define _GrTitle/across;
run;

Apparently the problem is triggered by the presence of a BY group and having
a report in the form of:
order  display   across,display

(to get this problem you had to be using by groups, and you had to have one
or more order variables, then one or more display variables, then an across
with one or more display variables underneath the across.)

Thanks again,
   Nancy

Nancy Brucken
Clinical/Regulatory Informatics
Pfizer Global Research & Development, Ann Arbor
(734) 622-5767
E-mail address:  Nancy.Brucken@pfizer.com

Original posting:

> Hi all,
> Has anyone encountered out of memory conditions when using PROC REPORT
> with several BY variables? We're running it interactively in Win 2K (SAS
> v8.2), and have managed to consistently hang PC's until they crash. There
> is nothing on the SAS Tech Support pages regarding this issue, but one of
> our programmers was told by SAS's UK tech support that this is a known
> problem in v8.2. One possible solution that was suggested was to include
> our BY variables using ORDER NOPRINT and break after them instead. I'm a
> PROC REPORT novice, and so have no idea what other problems that might
> introduce. Am hoping some of the PROC REPORT gurus out there can help us
> with this one. Please let me know if more information is necessary- I can
> get probably get hold of a log with the error messages, though the person
> running this code is in the UK, so that will take at least overnight.
> Thank you very much!
> Nancy