cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
BookmarkSubscribeRSS Feed
SafetySal1
Calcite | Level 5 SafetySal1
Calcite | Level 5

proc lifetest errors

Posted 03-07-2018 11:51 AM (2062 views)

Hello,

SAS enterprise guide will not run this code:


data rat;
length treatment $8;
input time event treatment;
datalines;

18 1 lowdose
23 1 lowdose
25 1 lowdose
26 1 lowdose
29 0 lowdose
30 1 lowdose
30 1 lowdose
31 1 lowdose
31 0 lowdose
32 0 lowdose
13 1 moderate
13 1 moderate
15 1 moderate
17 1 moderate
17 0 moderate
18 1 moderate
18 1 moderate
21 1 moderate
23 1 moderate
23 0 moderate
24 1 moderate
25 1 moderate
25 1 moderate
;

proc freq data=rat;
tables treatment;
run;

ods graphics on;
proc lifetest data=rat atrisk conftype=asinsqrt
  plots=(survival(cb=ep atrisk) loglogs logsurv);
 time time*event(0);
 strata treatment;
run;
ods graphics off;

 

 

 

I'm getting this error message:


 
ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [LIFETEST]
Segmentation Violation
 
Traceback of the Exception:
 
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x1666ce) [0x55bcbdd476ce]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x4e7df) [0x55bcbdc2f7df]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f9474b2ba44]
/lib64/libpthread.so.0(+0xf5e0) [0x7f94761495e0]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saslifet(+0x77eb8) [0x7f9415dd2eb8]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saslifet(saslifet+0x713) [0x7f9415d99083]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x55bcbdc2f33a]
/lib64/libpthread.so.0(+0x7e25) [0x7f9476141e25]
/lib64/libc.so.6(clone+0x6d) [0x7f947573234d]

 
4                                                          The SAS System                      Wednesday, March  7, 2018 04:34:00 PM

ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [LIFETEST]
Segmentation Violation

 

Please help.

 

0 Likes
Reply
6 REPLIES 6
ballardw
Super User ballardw
Super User

Re: proc lifetest errors

Posted 03-07-2018 12:30 PM (2053 views)  |   In reply to SafetySal1

I ran your code without errors or message which indicates there may be something off about your install.

 

I would suggest 1) save the program, 2) shut down and restart SAS and 3) resubmit just this program. If the program executes then something you had done in the previous session caused a problem. If the same or similar error occurs then contact tech support.

Reply
SafetySal1
Calcite | Level 5 SafetySal1
Calcite | Level 5

Re: proc lifetest errors

Posted 03-07-2018 01:12 PM (2040 views)  |   In reply to ballardw

Thank you Ballard!  I appreciate it.  I just restarted the enterprise guide and reran the program and received the same problem.  I'll contact support.  I also had a friend run it and she said it worked perfectly without a problem. This is what my output data looks like:

 

"25 1 low" . .
"30 1 low" . .
"31 0 low" . .
"13 1 mod" . .
"17 0 mod" . .
"21 1 mod" . .
"24 1 mod" . .

 

something is off...

Thanks again!!

0 Likes
Reply
ballardw
Super User ballardw
Super User

Re: proc lifetest errors

Posted 03-07-2018 03:51 PM (2026 views)  |   In reply to SafetySal1
@SafetySal1 wrote:

Thank you Ballard!  I appreciate it.  I just restarted the enterprise guide and reran the program and received the same problem.  I'll contact support.  I also had a friend run it and she said it worked perfectly without a problem. This is what my output data looks like:

 

"25 1 low" . .
"30 1 low" . .
"31 0 low" . .
"13 1 mod" . .
"17 0 mod" . .
"21 1 mod" . .
"24 1 mod" . .

 

something is off...

Thanks again!!

That data looks like what I would expect  you ran:

data rat;
length treatment $8;
input treatment $8. time event ;
datalines;

18 1 lowdose
23 1 lowdose
25 1 lowdose

;

 

or similar. You don't show WHICH variable isn't missing though.

If you are actually reading an external file instead of the datalines example you provided you might post the code used to read the external file. Or rerun the code and look closely at the log for any warning or notes about invalid data and such. If so post the code and log, preferably into a code box opened with the forum's {I} icon to preserve any warning or error formatting.

 

0 Likes
Reply
SafetySal1
Calcite | Level 5 SafetySal1
Calcite | Level 5

Re: proc lifetest errors

Posted 03-07-2018 04:24 PM (2023 views)  |   In reply to ballardw 
26         data rat;
27         length treatment $8;
28         input time event treatment;
29         datalines;

NOTE: Invalid data for time in line 31 1-12.
NOTE: Invalid data for event in line 32 1-12.
RULE:      ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                     

33  CHAR   25.1.lowdose                                                                    
    ZONE   33030667667622222222222222222222222222222222222222222222222222222222222222222222
    NUMR   25919CF74F3500000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=25	1	low time=. event=. _ERROR_=1 _N_=1
NOTE: Invalid data for time in line 34 1-12.
NOTE: Invalid data for event in line 35 1-12.

36  CHAR   30.1.lowdose                                                                    
    ZONE   33030667667622222222222222222222222222222222222222222222222222222222222222222222
    NUMR   30919CF74F3500000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=30	1	low time=. event=. _ERROR_=1 _N_=2
NOTE: Invalid data for time in line 37 1-12.
NOTE: Invalid data for event in line 38 1-12.

39  CHAR   31.0.lowdose                                                                    
    ZONE   33030667667622222222222222222222222222222222222222222222222222222222222222222222
    NUMR   31909CF74F3500000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
2                                                          The SAS System                      Wednesday, March  7, 2018 09:20:00 PM

treatment=31	0	low time=. event=. _ERROR_=1 _N_=3
NOTE: Invalid data for time in line 40 1-12.
NOTE: Invalid data for event in line 41 1-13.
RULE:      ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0                     

42  CHAR   13.1.moderate                                                                   
    ZONE   33030666676762222222222222222222222222222222222222222222222222222222222222222222
    NUMR   13919DF4521450000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=13	1	mod time=. event=. _ERROR_=1 _N_=4
NOTE: Invalid data for time in line 43 1-13.
NOTE: Invalid data for event in line 44 1-13.

45  CHAR   17.0.moderate                                                                   
    ZONE   33030666676762222222222222222222222222222222222222222222222222222222222222222222
    NUMR   17909DF4521450000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=17	0	mod time=. event=. _ERROR_=1 _N_=5
NOTE: Invalid data for time in line 46 1-13.
NOTE: Invalid data for event in line 47 1-13.

48  CHAR   21.1.moderate                                                                   
    ZONE   33030666676762222222222222222222222222222222222222222222222222222222222222222222
    NUMR   21919DF4521450000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=21	1	mod time=. event=. _ERROR_=1 _N_=6
NOTE: Invalid data for time in line 49 1-13.
NOTE: Invalid data for event in line 50 1-13.

51  CHAR   24.1.moderate                                                                   
    ZONE   33030666676762222222222222222222222222222222222222222222222222222222222222222222
    NUMR   24919DF4521450000000000000000000000000000000000000000000000000000000000000000000
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=24	1	mod time=. event=. _ERROR_=1 _N_=7
NOTE: Invalid data for time in line 52 1-13.
NOTE: Invalid data for event in line 53 1-13.
NOTE: LOST CARD.
54         ;
NOTE: Invalid data errors for file CARDS occurred outside the printed range.
NOTE: Increase available buffer lines with the INFILE n= option.
treatment=  time=. event=. _ERROR_=1 _N_=8
NOTE: SAS went to a new line when INPUT statement reached past the end of a line.
NOTE: The data set WORK.RAT has 7 observations and 3 variables.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      user cpu time       0.00 seconds
      system cpu time     0.00 seconds
      memory              563.00k
      OS Memory           18860.00k
      Timestamp           03/07/2018 09:20:59 PM
      Step Count                        2  Switch Count  1
      Page Faults                       0
      Page Reclaims                     164
      Page Swaps                        0
3                                                          The SAS System                      Wednesday, March  7, 2018 09:20:00 PM

      Voluntary Context Switches        5
      Involuntary Context Switches      0
      Block Input Operations            0
      Block Output Operations           264
      
54         ;

55         
56         proc freq data=rat;
57         tables treatment;
58         run;

NOTE: There were 7 observations read from the data set WORK.RAT.
NOTE: PROCEDURE FREQ used (Total process time):
      real time           0.00 seconds
      user cpu time       0.01 seconds
      system cpu time     0.00 seconds
      memory              1321.00k
      OS Memory           19632.00k
      Timestamp           03/07/2018 09:20:59 PM
      Step Count                        3  Switch Count  1
      Page Faults                       0
      Page Reclaims                     617
      Page Swaps                        0
      Voluntary Context Switches        5
      Involuntary Context Switches      0
      Block Input Operations            0
      Block Output Operations           272
      

59         
60         ods graphics on;
61         proc lifetest data=rat atrisk conftype=asinsqrt
62         		plots=(survival(cb=ep atrisk) loglogs logsurv);
63         	time time*event(0);
64         	strata treatment;
65         run;

 
ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [LIFETEST]
Segmentation Violation
 
Traceback of the Exception:
 
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x1666ce) [0x5571c81e46ce]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x4e7df) [0x5571c80cc7df]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7fadbc81aa44]
/lib64/libpthread.so.0(+0xf5e0) [0x7fadbde385e0]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saslifet(+0x77eb8) [0x7fad59ad5eb8]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saslifet(saslifet+0x713) [0x7fad59a9c083]
/pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x5571c80cc33a]
/lib64/libpthread.so.0(+0x7e25) [0x7fadbde30e25]
/lib64/libc.so.6(clone+0x6d) [0x7fadbd42134d]

 
4                                                          The SAS System                      Wednesday, March  7, 2018 09:20:00 PM

ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [LIFETEST]
Segmentation Violation
 
NOTE: PROCEDURE LIFETEST used (Total process time):
      real time           0.00 seconds
      user cpu time       0.00 seconds
      system cpu time     0.00 seconds
      memory              1055.62k
      OS Memory           20148.00k
      Timestamp           03/07/2018 09:20:59 PM
      Step Count                        4  Switch Count  0
      Page Faults                       0
      Page Reclaims                     526
      Page Swaps                        0
      Voluntary Context Switches        0
      Involuntary Context Switches      0
      Block Input Operations            0
      Block Output Operations           16
      

66         ods graphics off;
67         
68         
69         GOPTIONS NOACCESSIBLE;
70         %LET _CLIENTTASKLABEL=;
71         %LET _CLIENTPROCESSFLOWNAME=;
72         %LET _CLIENTPROJECTPATH=;
73         %LET _CLIENTPROJECTNAME=;
74         %LET _SASPROGRAMFILE=;
75         
76         ;*';*";*/;quit;run;
77         ODS _ALL_ CLOSE;
78         
79         
80         QUIT; RUN;
81

Sal Capture.PNG

0 Likes
Reply
SafetySal1
Calcite | Level 5 SafetySal1
Calcite | Level 5

Re: proc lifetest errors

Posted 03-07-2018 04:25 PM (2022 views)  |   In reply to SafetySal1

Any assistance is appreciated.

Thanks,

Sal

0 Likes
Reply
TomKari
Onyx | Level 15 TomKari
Onyx | Level 15

Re: proc lifetest errors

Posted 03-07-2018 05:21 PM (2017 views)  |   In reply to SafetySal1

I believe that the '09' hex characters between your values are tabs. Either convert them to spaces, or use dlm='09'x on an infile statement to set the delimiters to tab characters.

 

Tom

0 Likes
Reply

SAS Innovate 2025: Save the Date

 SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!

Save the date!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Watch SAS Enterprise Guide vs. SAS Studio on YouTube

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 6 replies
  • ‎03-07-2018 11:51 AM
  • 2063 views
  • 2 likes
  • 3 in conversation