Date:         Tue, 13 Feb 2007 09:19:41 -0500
Reply-To:     Peter Crawford <peter.crawford@BLUEYONDER.CO.UK>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Peter Crawford <peter.crawford@BLUEYONDER.CO.UK>
Subject:      Re: PROC REPORT and the Document Destination

On Tue, 13 Feb 2007 08:52:14 -0500, Ken Borowiak
<EvilPettingZoo97@AOL.COM> wrote:

>On Thu, 8 Feb 2007 18:34:39 -0800, David L Cassell <davidlcassell@MSN.COM>
>wrote:
>
>>EvilPettingZoo97@AOL.COM wrote:
>>>
>>>Peeps of the 'L,
>>>
>>>I was wondering if anyone else has experienced this vexing phenomenon.
When
>>>executing a PROC REPORT I am receiving a warning in my log stating "PROC
>>>REPORT does not support the ODS Document in this release." (btw, I am
>>>running SAS V9.1.3 SP4 on Windows). However, I do not have the Document
>>>destination open (executed  ods document close; before, just to be
sure). A
>>>few weeks ago, though, I did dump something to the Document destination.
>>>Then when I try to execute another PROC step (MEANS, TABULATE, REPORT
>>>etc.),
>>>I get the following error:
>>>
>>>ERROR:  Read Access Violation In Task [ REPORT {or some other PROC}  )
>>>Exception occurred at (676C1D77)
>>>Task Traceback
>>>Address   Frame     (DBGHELP API Version 4.0 rev 5)
>>>676C1D77  050CE664  sasyys:mcn_main+0xD77
>>>60ECA6DD  050CEB48  sasdoc:mcn_main+0x196DD
>>>60ED6AF9  050CEF58  sasdoc:mcn_main+0x25AF9
>>>67141955  050CF050  sasoda:mcn_main+0x955
>>>60ED843C  050CF0A4  sasdoc:mcn_main+0x2743C
>>>674DE11C  050CF140  sasods:mcn_main+0x4D11C
>>>674A27DA  050CF294  sasods:mcn_main+0x117DA
>>>663A4066  050CFB54  sasrepmn:mcn_main+0x3066
>>>663910B5  050CFF88  sasrepor:mcn_main+0xB5
>>>01232B02  050CFFA0  sashost:Main+0xBE72
>>>01236C20  050CFFB4  sashost:Main+0xFF90
>>>7C80B683  050CFFEC  kernel32:GetModuleFileNameA+0x1B4
>>>
>>>Any thoughts?
>>>
>>>Thanks!
>>>Ken
>>
>>Peeps, am I?  I was aiming for at least a 'homey'.  :-)
>>
>>Is it possible that the material you dumped off to the ODS DOCUMENT
>>destination has filled up an itemstore and never freed it?  Can you check
>>to see if the stuff you dumped off a few weeks ago is still there?  If
so,
>>try emptying it and see if that helps.
>>
>>HTH,
>>David
>>--
>
>
>Davids,
>
>Thank you both for your suggestions. There is only one (small) entry in
the
>item store and my problem still occurs when the troublesome PROC REPORT is
>the first thing run in a fresh interactive SAS session. I think I'll have
to
>take this up with Technical Support.
>
>Ciao!
>Ken


Ok, it is a sas proprietary format "item store". Will the management
of this sas file type be better than sas catalogs?    There, they
just seem to keep on growing. Does anyone know if we can "repair"
an itemstore like we can repair a sas dataset?
It might be worth trying a new itemstore for a large document, rather
than repeatedly write into the same one, even if all entries are
cleared.

good luck

Peter Crawford