crash

[deleted_user]

The sas system crashes/disappears when I am running the job.
What is the reason for this crash? and how can I check it?
Thanks in advance.

[Andre]

Without any other information about the program
how can we guess?

Andre

[sbb]

1) Suggest you begin with some self-diagnosis by converting pieces of your code into SAS comments, as a technique for weeding out what is causing the error.

2) It would also be useful to COPY/PASTE your code directly into your forum post, so that others can provide meaningful feedback - without your code any comments received would be just suggestions based on others' situations and experiences, not your particular situation.

So, first suggestion - try number 1 above and then provide number 2 above if you are still unclear about the error cause. If you re-post, be sure to explain your complete SAS environment (version, OS, remote or local SAS system running, has the code ever worked?, do you otherwise have a working SAS environment?, does the code work on another SAS environment/platform).

Scott Barry
SBBWorks, Inc.

[data_null__]

I would run the program in BATCH mode so that you will have SASLOG file, that will remain to be examined after your program crashes.

[deleted_user]

The output of log file is attached as below:
========================================================
ERROR: Permanent copy of file WORK.DATA1.DATA was deleted.
ERROR: Cannot create data set WORK.DATA1. [Permanent copy of file WORK.DATA1.DATA was deleted.]
NOTE: The data set WORK.data1 has 0 observations and 1 variables.


Invalid free() attempt to deleted pool
Traceback
SASTBTraceBackCtx has been called with a
string ("vacrash") instead of a CONTEXT pointer.
Address Frame (DBGHELP API Version 4.0 rev 5)
5CB31C3D 05D0F8E0 tkmk:tkBoot+0x20C19
5CB31A3F 05D0F8EC tkmk:tkBoot+0x20A1B
5CB27EF2 05D0F90C tkmk:tkBoot+0x16ECE
67EE2F03 05D0F92C sashost:Main+0xCC483
67E1D6C8 05D0F94C sashost:Main+0x6C48
67E11A33 05D0F9A4 sashost:rtmdoit+0x1DF
67E2CC26 05D0F9B8 sashost:Main+0x161A6
67E2A12A 05D0F9D4 sashost:Main+0x136AA
678F2589 05D0FA18 sasyh:mcn_main+0x1589
671A1A25 05D0FD40 sasyoio:mcn_main+0xA25
57883014 05D0FD70 sasimi:mcn_main+0x2014
57882758 05D0FEC8 sasimi:mcn_main+0x1758
578426F2 05D0FF58 sasiml:mcn_main+0x16F2
578412AE 05D0FF88 sasiml:mcn_main+0x2AE
67E227E2 05D0FFA0 sashost:Main+0xBD62
67E26800 05D0FFB4 sashost:Main+0xFD80
7C80B699 05D0FFEC kernel32:GetModuleFileNameA+0x1BA

[sbb]

You still provided very limited information about the items mentioned in a prior post-reply.

Suggest you contact SAS technical support - see link at the bottom of the SAS Discussion Forum page or here's the link:

http://support.sas.com/techsup/contact/submit_emits2.html


Scott Barry
SBBWorks, Inc.

[deleted_user]

Thank you for your suggestion.
I identified the problem and find the solution in the SAS/support page.
http://support.sas.com/kb/12/564.html
I run IML numerous times on window XP. I follow the suggested solution provided by the above link and defragmented the C drive. However, I still encounter this problem. Does it have any alternative to solve this problem? Thanks.

[sbb]

No mention is made otherwise in the tech-note, which would be the place if SAS had an alternative. Suggest you try invoking SAS (not an OPTIONS command override though - see DOC references below) with -MEMSIZE 0 and/or -REALMEMSIZE 0 and observe any different behavior.

Again, the most expedient resolution would be to contact SAS support.

Scott Barry
SBBWorks, Inc.


SAS Companion for Windows: Starting SAS
http://support.sas.com/documentation/cdl/en/hostwin/61924/HTML/default/startsas.htm

SAS Companion for Windows: MEMSIZE System Option
http://support.sas.com/documentation/cdl/en/hostwin/61924/HTML/default/win-sysop-memsize.htm

SAS Companion for Windows: REALMEMSIZE System Option
http://support.sas.com/documentation/cdl/en/hostwin/61924/HTML/default/win-sysop-realmemsize.htm