not able to understand log

vimal — Mon, 31 May 2010 09:24:51 GMT

Hi

This is my code:::::
OPTION MISSING =0;

PROC REPORT DATA=sh_SEG_SALES_MIS2;
TITLE "MTD PRODUCT WISE SOURCE WISE LEAD STATUS SUMMARY AT &firstday1";
footnote;
footnote2;
footnote3;
footnote4;

COLUMNS SOURCE PRODUCTDESC,(ENTERED CLOSED);

DEFINE SOURCE/GROUP ;
DEFINE PRODUCTDESC/ACROSS '' ;
DEFINE ENTERED/ANALYSIS STYLE(COLUMN) = {just=center} ;
DEFINE CLOSED/ANALYSIS STYLE(COLUMN) = {just=center} ;

RBREAK AFTER/SUMMARIZE;
COMPUTE SOURCE;
IF _BREAK_ EQ '_RBREAK_' THEN SOURCE = 'TOTAL';
ENDCOMP;
RUN;

/*************************************************/

When i am running it once, it gives no error, evrything goes fine...But when i run it second time, it gives me this log..which i am not able to understand ,and why is it happening so..please help me out:::::::::::::::::::::

/*******************************************************/
1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 %LET _CLIENTTASKLABEL=%NRBQUOTE(Code);
4 %LET _EGTASKLABEL=%NRBQUOTE(Code);
5 %LET _CLIENTPROJECTNAME=%NRBQUOTE();
6 %LET _SASPROGRAMFILE=;
7
8 ODS _ALL_ CLOSE;
NOTE: Some of your options or statements may not be supported with the Activex or Java series of devices. Graph defaults for these
drivers may be different from other SAS/GRAPH device drivers. For further information, please contact Technical Support.
9 OPTIONS DEV=ACTIVEX;
10 FILENAME EGHTML TEMP;
NOTE: Writing HTML(EGHTML) Body file: EGHTML
11 ODS HTML(ID=EGHTML) FILE=EGHTML ENCODING='utf-8' STYLE=EGDefault
11 ! STYLESHEET=(URL="file:///C:/Program%20Files/SAS/Shared%20Files/BIClientStyles/EGDefault.css")
11 ! ATTRIBUTES=("CODEBASE"="http://www2.sas.com/codebase/graph/v91/sasgraph.exe") NOGTITLE NOGFOOTNOTE GPATH=&sasworklocation
11 ! ;
12
13 %gaccessible;
MPRINT(GACCESSIBLE): GOPTIONS ACCESSIBLE;
14 OPTION MISSING =0;
15
16 PROC REPORT DATA=sh_SEG_SALES_MIS2;
17 TITLE "MTD PRODUCT WISE SOURCE WISE LEAD STATUS SUMMARY AT &firstday1";
18 footnote;
19 footnote2;
20 footnote3;
21 footnote4;
22
23 COLUMNS SOURCE PRODUCTDESC,(ENTERED CLOSED);
24
25 DEFINE SOURCE/GROUP ;
26 DEFINE PRODUCTDESC/ACROSS '' ;
27 DEFINE ENTERED/ANALYSIS STYLE(COLUMN) = {just=center} ;
28 DEFINE CLOSED/ANALYSIS STYLE(COLUMN) = {just=center} ;
29
30 RBREAK AFTER/SUMMARIZE;
31 COMPUTE SOURCE;
32 IF _BREAK_ EQ '_RBREAK_' THEN SOURCE = 'TOTAL';
33 ENDCOMP;
34 RUN;

Segmentation Violation In Task [ REPORT ( ]
Fault Occurred at [/sas1/sasinst/SAS_9.1/hotfix/sasexe/sas.e9ba69:vvmcput+0x124]

Task Traceback

/sas1/sasinst/SAS_9.1/hotfix/sasexe/sas.e9ba69:vvmcput+0x124
/sas1/sasinst/SAS_9.1/hotfix/sasexe/sas.e9ba69:hgfrmem+0xc8
/sas1/sasinst/SAS_9.1/hotfix/sasexe/sas.e9ba69:vgclose+0x8
/sas1/sasinst/SAS_9.1/sasexe/saswgp:wgclose+0x334
/sas1/sasinst/SAS_9.1/sasexe/sasrepmn:zdsterm+0xb8
/sas1/sasinst/SAS_9.1/sasexe/sasrep7:getCellStyle+0x48dc
/sas1/sasinst/SAS_9.1/sasexe/sasrep7:getCellStyle+0x4c34
/sas1/sasinst/SAS_9.1/sasexe/sasxml:xmlprtv+0x178
/sas1/sasinst/SAS_9.1/sasexe/sasoda:odstrev+0x424
/sas1/sasinst/SAS_9.1/sasexe/sasoda:sasoda+0xc2c
2 The SAS System 14:44 Monday, May 31, 2010

/sas1/sasinst/SAS_9.1/sasexe/sasxml:sasxml+0x3170
/sas1/sasinst/SAS_9.1/sasexe/sasods:odssm+0x368
/sas1/sasinst/SAS_9.1/sasexe/sasods:odsfact+0x39d0
/sas1/sasinst/SAS_9.1/sasexe/sasrepmn:repmain+0x2c30
/sas1/sasinst/SAS_9.1/sasexe/sasrepor:sasrepor+0x94
/sas1/sasinst/SAS_9.1/hotfix/sasexe/sas.e9ba69:vvtentr+0x120
NOTE: The SAS System stopped processing this step because of errors.
NOTE: There were 17 observations read from the data set WORK.SH_SEG_SALES_MIS2.
NOTE: PROCEDURE REPORT used (Total process time):
real time 0.15 seconds
user cpu time 0.08 seconds
system cpu time 0.08 seconds
Memory 7814k
Page Faults 0
Page Reclaims 0
Page Swaps 0
Voluntary Context Switches 21
Involuntary Context Switches 10
Block Input Operations 0
Block Output Operations 0

35
36 %LET _CLIENTTASKLABEL=;
37 %LET _EGTASKLABEL=;
38 %LET _CLIENTPROJECTNAME=;
39 %LET _SASPROGRAMFILE=;
40
41 ;*';*";*/;quit;run;
42 ODS _ALL_ CLOSE;
ERROR: Event Stack Underflow. This is probably caused by mis-matched begin and end event calls.
43
44
45 QUIT; RUN;
46
/*****************************
thanks

Re: not able to understand log

sbb — Mon, 31 May 2010 11:48:46 GMT

Suggest you contact SAS technical support for assistance, with this type of SAS operational error.

Scott Barry
SBBWorks, Inc.

topic not able to understand log in ODS and Base Reporting

not able to understand log

Re: not able to understand log