Date: Sun, 30 Apr 2006 19:49:41 -0400
Reply-To: Arthur Tabachneck <art297@NETSCAPE.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Arthur Tabachneck <art297@NETSCAPE.NET>
Subject: Re: Q: v6 to v9
Without seeing some examples from the log it is, of course, difficult to
guess. However, the worst problem I confronted in switching from V6 to V9
was the fact that SAS changed which error codes would get trapped.
Specifically, we had to change every instance of:
%IF &SYSERR ne 0 %THEN %GOTO ERRSTEP;
%IF &SYSERR ne 0 and &SYSERR NE 4 %THEN %GOTO ERRSTEP;
If the macro tries to control for errors, that might be a reasonable place
On Fri, 28 Apr 2006 16:44:34 -0400, Fehd, Ronald J. (CDC/CCHIS/NCHM)
>I am (attempting) testing some user v6 programs.
>The user supplied a v6 format catalog:
>which prompts SAS to conclude the
>libname statement to use the v6 engine.
>NOTE: SAS (r) 9.1 (TS1M3)
>8 LIBNAME LIBRARY "!ProjRoot\sas7b";
>NOTE: Libref LIBRARY was successfully assigned as follows:
> Engine: V6
> Physical Name: L:\Temp\sas7b
>The test program writes a Library.DataSet
>with ~200 vars and (eventually) ~4000 rows.
>The user complains that SAS hangs and never completes the data step.
>I've just aborted a run with 500,000 lines in the log
>and got it to run with just the data structure
>so I could see the Proc Contents:
>there are no numerics with length of 4, 6 and 7
>but methinks too many with lengths 3 and 5
>... oh! several $200.
>I suppose this is just my mumbling
>while trying to figure out
>why a macro with an %Include doesn't run in v9
>Ron Fehd the macro maven