When I want to search for ERRORs in my SASLOG, I can of course do a
search for the test string ERROR in the SASLOG, however sometimes this
turns up _ERROR_, which really isn't an error, it is written to the
LOG by a data step (for example, if you divide by zero). In this
instance, and many similar instances, I'm not really interested in
finding _ERROR_, but there could be a bazillion of them.

So, next, trying to find actual code ERRORs, I  search for
'ERROR:' (without the quotes, but with that colon on the end) which
helps me find normal code errors, but I also have to search for "ERROR
' (without the quotes, but with a space after the last R), which helps
me find MACRO errors.

Is there a better way to find ERRORs in the SASLOG, skipping the data
step _ERROR_, and finding both MACRO errors and normal code errors?

"Paige Miller" <paige.miller@kodak.com> wrote in message 
news:0447a200-788d-44eb-9bb6-a9a271dc8f5b@c16g2000yqd.googlegroups.com...
> When I want to search for ERRORs in my SASLOG, I can of course do a
> search for the test string ERROR in the SASLOG, however sometimes this
> turns up _ERROR_, which really isn't an error, it is written to the
> LOG by a data step (for example, if you divide by zero). In this
> instance, and many similar instances, I'm not really interested in
> finding _ERROR_, but there could be a bazillion of them.
>
> So, next, trying to find actual code ERRORs, I  search for
> 'ERROR:' (without the quotes, but with that colon on the end) which
> helps me find normal code errors, but I also have to search for "ERROR
> ' (without the quotes, but with a space after the last R), which helps
> me find MACRO errors.
>
> Is there a better way to find ERRORs in the SASLOG, skipping the data
> step _ERROR_, and finding both MACRO errors and normal code errors?

Yeah - don't make _ERROR_'s in the first place.  In my business, if a log 
shows those kinds of messages, the program is not finished.  Tighten up your 
code - for example,

if y ^= 0 then z = x / y;

will mean that you don't get _ERROR_ messages due to attempted division by 
zero

If that's really too much trouble, you could use additional operands of the 
find command.  For instance

find ERROR word

will find the words "ERROR" and "ERROR:" but not find the word "_ERROR_". 

Speaking of regular expressions I use the following when searching for
errors in SAS log files on unix:

grep '^ERROR.*:'

So that only ERROR message that start in column 1 and also have a semi-
colon will be found.
In a SAS data step I would code this as:
  if _infile_=3D:'ERROR' and index(_infile_,':') then ....


On Mar 18, 12:56=A0pm, "Lou" <lpog...@hotmail.com> wrote:
> "Paige Miller" <paige.mil...@kodak.com> wrote in message
>
> news:0447a200-788d-44eb-9bb6-a9a271dc8f5b@c16g2000yqd.googlegroups.com...
>
> > When I want to search for ERRORs in my SASLOG, I can of course do a
> > search for the test string ERROR in the SASLOG, however sometimes this
> > turns up _ERROR_, which really isn't an error, it is written to the
> > LOG by a data step (for example, if you divide by zero). In this
> > instance, and many similar instances, I'm not really interested in
> > finding _ERROR_, but there could be a bazillion of them.
>
> > So, next, trying to find actual code ERRORs, I =A0search for
> > 'ERROR:' (without the quotes, but with that colon on the end) which
> > helps me find normal code errors, but I also have to search for "ERROR
> > ' (without the quotes, but with a space after the last R), which helps
> > me find MACRO errors.
>
> > Is there a better way to find ERRORs in the SASLOG, skipping the data
> > step _ERROR_, and finding both MACRO errors and normal code errors?
>
> Yeah - don't make _ERROR_'s in the first place. =A0In my business, if a l=
og
> shows those kinds of messages, the program is not finished. =A0Tighten up=
 your
> code - for example,
>
> if y ^=3D 0 then z =3D x / y;
>
> will mean that you don't get _ERROR_ messages due to attempted division b=
y
> zero
>
> If that's really too much trouble, you could use additional operands of t=
he
> find command. =A0For instance
>
> find ERROR word
>
> will find the words "ERROR" and "ERROR:" but not find the word "_ERROR_".

Try the %checklog. It only identifies the ERRORs you are interested.
However, I agree with Lou that any type of error should be treated
with caution.
http://www.listserv.uga.edu/cgi-bin/wa?A2=ind0411E&L=sas-l&P=16645

In SAS EG or PC SAS (9.2, not sure for previous) "find" using a
regular expression is possible. This RegEx should to the job:
^ERROR[: ]
I believe the same expression could also be used under Unix with
"egrep".

On Mar 18, 1:51=A0pm, Patrick <patrick.mat...@gmx.ch> wrote:
> In SAS EG or PC SAS (9.2, not sure for previous) "find" using a
> regular expression is possible. This RegEx should to the job:
> ^ERROR[: ]
> I believe the same expression could also be used under Unix with
> "egrep".

Unfortunately, I do not understand what it means to use a RegEx
expression on the SASLOG. Pasting your ^ERROR[: ] exactly into the
Find dialog box (Ctrl-F) in the SASLOG does not find any ERRORs, even
though I know they exist.

Exactly where do you issue this regular expression?

--
Paige Miller
paige\dot\miller \at\ kodak\dot\com

Paige

Seems that SAS has to resolve some small inconsistencies.

The find window in PC SAS 9.2 differs between a code and a log window.
In the code window there is an option "Regular expression search"
where the RegEx works. Looks to me as if the PC SAS log window is
still using the old find version.

Interestingly in SAS EG 4.2 the new find window with RegEx option also
works for the Log window.

Cheers
Patrick

On Mar 18, 12:41=A0pm, Patrick <patrick.mat...@gmx.ch> wrote:
> Paige
>
> Seems that SAS has to resolve some small inconsistencies.
>
> The find window in PC SAS 9.2 differs between a code and a log window.
> In the code window there is an option "Regular expression search"
> where the RegEx works. Looks to me as if the PC SAS log window is
> still using the old find version.
>
> Interestingly in SAS EG 4.2 the new find window with RegEx option also
> works for the Log window.
>
> Cheers
> Patrick

Hi SAS-Lers,

  Quite a few ERROR messages do not have the ':', I have a list
somewhere. Note TRACEBACK does not have the ':' or the ERROR string.
  There are other serious ERRORs that have ERROR and not the  ':' and
I don't think ERROR always begins in column 1.

  SAS does seem to always capitilaize ERROR, so use lower case ERROR
on your put string. User put "ERR" "OR". if you want the scrub to pick
up the error.

  I have a more complete list of what I consider potential issues in
the log, however it does have false positive issues.
  I also have a perl script somewhere, I will look for it

see
http://homepage.mac.com/magdelina/.Public/utl.html
utl_tipweb.txt
/* T002550 CHECK LOG */
also around line 17235

Here is a list of strings I look for - you need to lower case the log
statements
I have built this string over the years and add to it each time I find
a issue in my log I want to trap on.

I also tried to oder them from most to least serious, howver you
should always eyeball your log.

 "0 observations rewritten, 0 observations added and 0 observations
deleted"
" 0 lines"
" 0 observations"
" 0 records"
" 0 rows"
" 0 obs"
"%to value of"
"traceback"
"not currently in"
"abnormally terminated"
"access denied"
"allowed"
"already been defined"
"ambiguous"
"apparent invocation"
"apparent symbolic"
"appears as text"
"are not allowed"
"argument 1"
"argument 2"
"argument 3"
"assumed"
"assuming"
"at least"
"but appears on"
"but is not"
"but no"
"by-group"
"cannot be accessed"
"cannot be deleted"
"cannot be found"
"cannot be loaded"
"cannot be"
"cannot open"
"cartesian"
"central parameter"
"character in one"
"clause has been augmented"
"clause references"
"cli error"
"closing"
"columns were too wide"
"condition in the"
"conflicting attributes"
"contain no data in common"
"contain unequal"
"contains 1 variable"
"convert"
"converted to"
"converted"
"could not be fit"
"could not be found"
"could not be loaded"
"could not be written"
"could not be"
"could not"
"creates a common"
"default estimation"
"default style will be used instead"
"defined as both"
"did not satisfy"
"differ"
"different data types"
"division by zero"
"denied"
"does not exist"
"does not have enough arguments"
"does not match"
"doesn't appear"
"doesn't have"
"double-dash"
"due to a"
"due to errors"
"due to looping"
"dummy macro"
"ellipsoid centered"
"end of macro"
"end-of-record"
"ending execution"
"enter run"
"error"
"errorabend"
"errorcheck=3Dstrict"
"errors noted"
"estimated autoregression parameter"
"examine fields"
"exceeds 8 characters"
"exceed"
"execution terminated"
"execution terminating"
"expected"
"expecting"
"experimental release"
"export cancelled"
"expression has no"
"extraneous information"
"extraneous"
"failed to converge"
"failed to load"
"failed to"
"fatal"
"firstobs option >"
"firstobs option"
"generic critical"
"groups are not created"
"hanging"
"has 0 observations"
"has _type_"
"has a null"
"has already been defined"
"has already been set"
"has already been"
"has already"
"has become more"
"has been reduced"
"has been transformed"
"has been discarded"
"has changed"
"has different lengths"
"has exceeded"
"has multiple"
"has never been"
"has no condition"
"has not been dropped"
"has not been"
"has too few"
"have been detected"
"ignored"
"ignoring"
"illegal"
"included in the"
"incomplete"
"incorrect"
"input data set is empty"
"input distances have been squared"
"input data set is already sorted"
"input empty"
"insufficient"
"invalid"
"is already on the"
"is already sorted"
"is also a dataset"
"is ambiguous"
"is before the starting"
"is included"
"is invalid"
"is less than or equal"
"is less than"
"is not a valid"
"is not allowed"
"is not assigned"
"is not greater than"
"is not in effect"
"is not in"
"is not on file"
"is not recognized"
"is not sorted"
"is not valid"
"is obsolete"
"is sequential"
"it is used out"
"is obsolete"
"labels differ"
"length of numeric"
"limit set by"
"list empty"
"lost card"
"mathematical operations"
"mathemat"
"may be incomplete"
"may be longer"
"may not be as expected"
"merge statement has more than"
"merge statement"
"missing close parentheses"
"missing equals sign"
"missing on every"
"missing semicolon"
"missing values"
"missing"
"misspelled"
"mixed engine types"
"model contains"
"more positional"
"multiple lengths"
"multiple optimal"
"multiple vertical"
"multiple"
"must be character"
"must be entered"
"must be followed"
"must be given"
"must be invoked"
"must have appeared"
"must precede"
"no body file"
"no body"
"no by"
"no cards"
"no data set"
"no data sets qualify"
"no data"
"no effect"
"no expression"
"no file"
"no formats found"
"no keep"
"no libraries"
"suppress"
"no logical"
"no longer exists"
"no matching"
"no non-missing"
"no observations"
"no output destinations active"
"no output produced"
"no output"
"no rows were selected"
"no rows"
"no shape"
"no variables found"
"no variables specified"
"no variables"
"none of the options"
"not a valid"
"not acceptable"
"not adjusted"
"not all"
"not allow character"
"not be included"
"not be performed"
"not currently licensed"
"not found"
"not in a valid"
"not in effect"
"not licensed"
"not on input data set"
"not processed"
"not recognized"
"not replaced because"
"not resolved"
"not valid for import"
"not valid"
"not written"
"null where"
"numeric in one"
"obs=3D0"
"observations not"
"obsolete"
" omitted due to"
"occurred on module"
"offline"
"one or more lines may be longer"
"operand was found in"
"option value"
"outside the axis"
"parenthesis for"
"previous errors"
"proc sql statements are executed immediately"
"product not found"
"product with which"
"partial initialization"
"quoted string"
"recursion"
"recursive"
"reference"
"references the data set being updated"
"refers to the same"
"refers to"
"repeat"
"request ignored"
"required operator not found"
"requires a numeric"
"requires compatible"
"right-hand"
"sas set option obs=3D0"
"sas went"
"scale parameter was held fixed"
"shifted"
"starting variable"
"statement has been deleted"
"statement needs"
"statement syntax"
"statement transforms"
"statistics are mean corrected"
"statistics requested"
"stop"
"stopped"
"subroutine"
"syntax for this"
"the chi-square is small"
"too long"
"too many array subscripts"
"too small"
"too wide"
"trying to use"
"unable to initialize"
"unable to"
"unable"
"unbalanced"
"unclosed"
"undeclared"
"undetermined"
"uninitialized"
"unknown"
"unrecognized"
"unref"
"unresolved"
"unsatisfied"
"violation"
"was disabled"
"was stopped"
"was misspelled as"
"was not created"
"was not defined"
"was not found"
"was not replaced"
"went to a new line"
"were excluded"
"will be assumed"
"will be used"
"will not be"
"will not load"
"will stop executing"
"within the range"
"you can only"
"your request"
"zero elements"

On Mar 19, 12:42=A0am, xlr82sas <xlr82...@aol.com> wrote:
> On Mar 18, 12:41=A0pm, Patrick <patrick.mat...@gmx.ch> wrote:
>
> > Paige
>
> > Seems that SAS has to resolve some small inconsistencies.
>
> > The find window in PC SAS 9.2 differs between a code and a log window.
> > In the code window there is an option "Regular expression search"
> > where the RegEx works. Looks to me as if the PC SAS log window is
> > still using the old find version.
>
> > Interestingly in SAS EG 4.2 the new find window with RegEx option also
> > works for the Log window.
>
> > Cheers
> > Patrick
>
> Hi SAS-Lers,
>
> =A0 Quite a few ERROR messages do not have the ':', I have a list
> somewhere. Note TRACEBACK does not have the ':' or the ERROR string.
> =A0 There are other serious ERRORs that have ERROR and not the =A0':' and
> I don't think ERROR always begins in column 1.
>
> =A0 SAS does seem to always capitilaize ERROR, so use lower case ERROR
> on your put string. User put "ERR" "OR". if you want the scrub to pick
> up the error.
>
> =A0 I have a more complete list of what I consider potential issues in
> the log, however it does have false positive issues.
> =A0 I also have a perl script somewhere, I will look for it
>
> seehttp://homepage.mac.com/magdelina/.Public/utl.html
> utl_tipweb.txt
> /* T002550 CHECK LOG */
> also around line 17235
>
> Here is a list of strings I look for - you need to lower case the log
> statements
> I have built this string over the years and add to it each time I find
> a issue in my log I want to trap on.
>
> I also tried to oder them from most to least serious, howver you
> should always eyeball your log.
>
> =A0"0 observations rewritten, 0 observations added and 0 observations
> deleted"
> " 0 lines"
> " 0 observations"
> " 0 records"
> " 0 rows"
> " 0 obs"
> "%to value of"
> "traceback"
> "not currently in"
> "abnormally terminated"
> "access denied"
> "allowed"
> "already been defined"
> "ambiguous"
> "apparent invocation"
> "apparent symbolic"
> "appears as text"
> "are not allowed"
> "argument 1"
> "argument 2"
> "argument 3"
> "assumed"
> "assuming"
> "at least"
> "but appears on"
> "but is not"
> "but no"
> "by-group"
> "cannot be accessed"
> "cannot be deleted"
> "cannot be found"
> "cannot be loaded"
> "cannot be"
> "cannot open"
> "cartesian"
> "central parameter"
> "character in one"
> "clause has been augmented"
> "clause references"
> "cli error"
> "closing"
> "columns were too wide"
> "condition in the"
> "conflicting attributes"
> "contain no data in common"
> "contain unequal"
> "contains 1 variable"
> "convert"
> "converted to"
> "converted"
> "could not be fit"
> "could not be found"
> "could not be loaded"
> "could not be written"
> "could not be"
> "could not"
> "creates a common"
> "default estimation"
> "default style will be used instead"
> "defined as both"
> "did not satisfy"
> "differ"
> "different data types"
> "division by zero"
> "denied"
> "does not exist"
> "does not have enough arguments"
> "does not match"
> "doesn't appear"
> "doesn't have"
> "double-dash"
> "due to a"
> "due to errors"
> "due to looping"
> "dummy macro"
> "ellipsoid centered"
> "end of macro"
> "end-of-record"
> "ending execution"
> "enter run"
> "error"
> "errorabend"
> "errorcheck=3Dstrict"
> "errors noted"
> "estimated autoregression parameter"
> "examine fields"
> "exceeds 8 characters"
> "exceed"
> "execution terminated"
> "execution terminating"
> "expected"
> "expecting"
> "experimental release"
> "export cancelled"
> "expression has no"
> "extraneous information"
> "extraneous"
> "failed to converge"
> "failed to load"
> "failed to"
> "fatal"
> "firstobs option >"
> "firstobs option"
> "generic critical"
> "groups are not created"
> "hanging"
> "has 0 observations"
> "has _type_"
> "has a null"
> "has already been defined"
> "has already been set"
> "has already been"
> "has already"
> "has become more"
> "has been reduced"
> "has been transformed"
> "has been discarded"
> "has changed"
> "has different lengths"
> "has exceeded"
> "has multiple"
> "has never been"
> "has no condition"
> "has not been dropped"
> "has not been"
> "has too few"
> "have been detected"
> "ignored"
> "ignoring"
> "illegal"
> "included in the"
> "incomplete"
> "incorrect"
> "input data set is empty"
> "input distances have been squared"
> "input data set is already sorted"
> "input empty"
> "insufficient"
> "invalid"
> "is already on the"
> "is already sorted"
> "is also a dataset"
> "is ambiguous"
> "is before the starting"
> "is included"
> "is invalid"
> "is less than or equal"
> "is less than"
> "is not a valid"
> "is not allowed"
> "is not assigned"
> "is not greater than"
> "is not in effect"
> "is not in"
> "is not on file"
> "is not recognized"
> "is not sorted"
> "is not valid"
> "is obsolete"
> "is sequential"
> "it is used out"
> "is obsolete"
> "labels differ"
> "length of numeric"
> "limit set by"
> "list empty"
> "lost card"
> "mathematical operations"
> "mathemat"
> "may be incomplete"
> "may be longer"
> "may not be as expected"
> "merge statement has more than"
> "merge statement"
> "missing close parentheses"
> "missing equals sign"
> "missing on every"
> "missing semicolon"
> "missing values"
> "missing"
> "misspelled"
> "mixed engine types"
> "model contains"
> "more positional"
> "multiple lengths"
> "multiple optimal"
> "multiple vertical"
> "multiple"
> "must be character"
> "must be entered"
> "must be followed"
> "must be given"
> "must be invoked"
> "must have appeared"
> "must precede"
> "no body file"
> "no body"
> "no by"
> "no cards"
> "no data set"
> "no data sets qualify"
> "no data"
> "no effect"
> "no expression"
> "no file"
> "no formats found"
> "no keep"
> "no libraries"
> "suppress"
> "no logical"
> "no longer exists"
> "no matching"
> "no non-missing"
> "no observations"
> "no output destinations active"
> "no output produced"
> "no output"
> "no rows were selected"
> "no rows"
> "no shape"
> "no variables found"
> "no variables specified"
> "no variables"
> "none of the options"
> "not a valid"
> "not acceptable"
> "not adjusted"
> "not all"
> "not allow character"
> "not be included"
> "not be performed"
> "not currently licensed"
> "not found"
> "not in a valid"
> "not in effect"
> "not licensed"
> "not on input data set"
> "not processed"
> "not recognized"
> "not replaced because"
> "not resolved"
> "not valid for import"
> "not valid"
> "not written"
> "null where"
> "numeric in one"
> "obs=3D0"
> "observations not"
> "obsolete"
> " omitted due to"
> "occurred on module"
> "offline"
> "one or more lines may be longer"
> "operand was found in"
> "option value"
> "outside the axis"
> "parenthesis for"
> "previous errors"
> "proc sql statements are executed immediately"
> "product not found"
> "product with which"
> "partial initialization"
> "quoted string"
> "recursion"
> "recursive"
> "reference"
> "references the data set being updated"
> "refers to the same"
> "refers to"
> "repeat"
> "request ignored"
> "required operator not found"
> "requires a numeric"
> "requires compatible"
> "right-hand"
> "sas set option obs=3D0"
> "sas went"
> "scale parameter was held fixed"
> "shifted"
> "starting variable"
> "statement has been deleted"
> "statement needs"
> "statement syntax"
> "statement transforms"
> "statistics are mean corrected"
> "statistics requested"
> "stop"
> "stopped"
> "subroutine"
> "syntax for this"
> "the chi-square is small"
> "too long"
> "too many array subscripts"
> "too small"
> "too wide"
> "trying to use"
> "unable to initialize"
> "unable to"
> "unable"
> "unbalanced"
> "unclosed"
> "undeclared"
> "undetermined"
> "uninitialized"
> "unknown"
> "unrecognized"
> "unref"
> "unresolved"
> "unsatisfied"
> "violation"
> "was disabled"
> "was stopped"
> "was misspelled as"
> "was not created"
> "was not defined"
> "was not found"
> "was not replaced"
> "went to a new line"
> "were excluded"
> "will be assumed"
> "will be used"
> "will not be"
> "will not load"
> "will stop executing"
> "within the range"
> "you can only"
> "your request"
> "zero elements"

Hi SAS-Lers,

As a side note, If I hit CTL T,  a logscrub on the log scrub of the
log window will be palced in  in note h,h

CTL T      log;file "./&pgm..log";note zx;notesubmit '%utl_logcurchk(./
&pgm..log);';

Also 'ctl h' changes focus to the log scrub output

CTL H      note h.h

Not sure this works in the enhanced editor and it certainly does not
work in the super enhanced EG, Enterprise Guide.

On Mar 19, 12:52=A0pm, xlr82sas <xlr82...@aol.com> wrote:
> On Mar 19, 12:42=A0am, xlr82sas <xlr82...@aol.com> wrote:
>
>
>
>
>
> > On Mar 18, 12:41=A0pm, Patrick <patrick.mat...@gmx.ch> wrote:
>
> > > Paige
>
> > > Seems that SAS has to resolve some small inconsistencies.
>
> > > The find window in PC SAS 9.2 differs between a code and a log window=
..
> > > In the code window there is an option "Regular expression search"
> > > where the RegEx works. Looks to me as if the PC SAS log window is
> > > still using the old find version.
>
> > > Interestingly in SAS EG 4.2 the new find window with RegEx option als=
o
> > > works for the Log window.
>
> > > Cheers
> > > Patrick
>
> > Hi SAS-Lers,
>
> > =A0 Quite a few ERROR messages do not have the ':', I have a list
> > somewhere. Note TRACEBACK does not have the ':' or the ERROR string.
> > =A0 There are other serious ERRORs that have ERROR and not the =A0':' a=
nd
> > I don't think ERROR always begins in column 1.
>
> > =A0 SAS does seem to always capitilaize ERROR, so use lower case ERROR
> > on your put string. User put "ERR" "OR". if you want the scrub to pick
> > up the error.
>
> > =A0 I have a more complete list of what I consider potential issues in
> > the log, however it does have false positive issues.
> > =A0 I also have a perl script somewhere, I will look for it
>
> > seehttp://homepage.mac.com/magdelina/.Public/utl.html
> > utl_tipweb.txt
> > /* T002550 CHECK LOG */
> > also around line 17235
>
> > Here is a list of strings I look for - you need to lower case the log
> > statements
> > I have built this string over the years and add to it each time I find
> > a issue in my log I want to trap on.
>
> > I also tried to oder them from most to least serious, howver you
> > should always eyeball your log.
>
> > =A0"0 observations rewritten, 0 observations added and 0 observations
> > deleted"
> > " 0 lines"
> > " 0 observations"
> > " 0 records"
> > " 0 rows"
> > " 0 obs"
> > "%to value of"
> > "traceback"
> > "not currently in"
> > "abnormally terminated"
> > "access denied"
> > "allowed"
> > "already been defined"
> > "ambiguous"
> > "apparent invocation"
> > "apparent symbolic"
> > "appears as text"
> > "are not allowed"
> > "argument 1"
> > "argument 2"
> > "argument 3"
> > "assumed"
> > "assuming"
> > "at least"
> > "but appears on"
> > "but is not"
> > "but no"
> > "by-group"
> > "cannot be accessed"
> > "cannot be deleted"
> > "cannot be found"
> > "cannot be loaded"
> > "cannot be"
> > "cannot open"
> > "cartesian"
> > "central parameter"
> > "character in one"
> > "clause has been augmented"
> > "clause references"
> > "cli error"
> > "closing"
> > "columns were too wide"
> > "condition in the"
> > "conflicting attributes"
> > "contain no data in common"
> > "contain unequal"
> > "contains 1 variable"
> > "convert"
> > "converted to"
> > "converted"
> > "could not be fit"
> > "could not be found"
> > "could not be loaded"
> > "could not be written"
> > "could not be"
> > "could not"
> > "creates a common"
> > "default estimation"
> > "default style will be used instead"
> > "defined as both"
> > "did not satisfy"
> > "differ"
> > "different data types"
> > "division by zero"
> > "denied"
> > "does not exist"
> > "does not have enough arguments"
> > "does not match"
> > "doesn't appear"
> > "doesn't have"
> > "double-dash"
> > "due to a"
> > "due to errors"
> > "due to looping"
> > "dummy macro"
> > "ellipsoid centered"
> > "end of macro"
> > "end-of-record"
> > "ending execution"
> > "enter run"
> > "error"
> > "errorabend"
> > "errorcheck=3Dstrict"
> > "errors noted"
> > "estimated autoregression parameter"
> > "examine fields"
> > "exceeds 8 characters"
> > "exceed"
> > "execution terminated"
> > "execution terminating"
> > "expected"
> > "expecting"
> > "experimental release"
> > "export cancelled"
> > "expression has no"
> > "extraneous information"
> > "extraneous"
> > "failed to converge"
> > "failed to load"
> > "failed to"
> > "fatal"
> > "firstobs option >"
> > "firstobs option"
> > "generic critical"
> > "groups are not created"
> > "hanging"
> > "has 0 observations"
> > "has _type_"
> > "has a null"
> > "has already been defined"
> > "has already been set"
> > "has already been"
> > "has already"
> > "has become more"
> > "has been reduced"
> > "has been transformed"
> > "has been discarded"
> > "has changed"
> > "has different lengths"
> > "has exceeded"
> > "has multiple"
> > "has never been"
> > "has no condition"
> > "has not been dropped"
> > "has not been"
> > "has too few"
> > "have been detected"
> > "ignored"
> > "ignoring"
> > "illegal"
> > "included in the"
> > "incomplete"
> > "incorrect"
> > "input data set is empty"
> > "input distances have been squared"
> > "input data set is already sorted"
> > "input empty"
> > "insufficient"
> > "invalid"
> > "is already on the"
> > "is already sorted"
> > "is also a dataset"
> > "is ambiguous"
> > "is before the starting"
> > "is included"
> > "is invalid"
> > "is less than or equal"
> > "is less than"
> > "is not a valid"
> > "is not allowed"
> > "is not assigned"
> > "is not greater than"
> > "is not in effect"
> > "is not in"
> > "is not on file"
> > "is not recognized"
> > "is not sorted"
> > "is not valid"
> > "is obsolete"
> > "is sequential"
> > "it is used out"
> > "is obsolete"
> > "labels differ"
> > "length of numeric"
> > "limit set by"
> > "list empty"
> > "lost card"
> > "mathematical operations"
> > "mathemat"
> > "may be incomplete"
> > "may be longer"
> > "may not be as expected"
> > "merge statement has more than"
> > "merge statement"
> > "missing close parentheses"
> > "missing equals sign"
> > "missing on every"
> > "missing semicolon"
> > "missing values"
> > "missing"
> > "misspelled"
> > "mixed engine types"
> > "model contains"
> > "more positional"
> > "multiple lengths"
> > "multiple optimal"
> > "multiple vertical"
> > "multiple"
> > "must be character"
> > "must be entered"
> > "must be followed"
> > "must be given"
> > "must be invoked"
> > "must have appeared"
> > "must precede"
> > "no body file"
> > "no body"
> > "no by"
> > "no cards"
> > "no data set"
> > "no data sets qualify"
> > "no data"
> > "no effect"
> > "no expression"
> > "no file"
> > "no formats found"
> > "no keep"
> > "no libraries"
> > "suppress"
> > "no logical"
> > "no longer exists"
> > "no matching"
> > "no non-missing"
> > "no observations"
> > "no output destinations active"
> > "no output produced"
> > "no output"
> > "no rows were selected"
> > "no rows"
> > "no shape"
> > "no variables found"
> > "no variables specified"
> > "no variables"
> > "none of the options"
> > "not a valid"
> > "not acceptable"
> > "not adjusted"
> > "not all"
> > "not allow character"
> > "not be included"
> > "not be performed"
> > "not currently licensed"
> > "not found"
> > "not in a valid"
> > "not in effect"
> > "not licensed"
> > "not on input data set"
> > "not processed"
> > "not recognized"
> > "not replaced because"
> > "not resolved"
> > "not valid for import"
> > "not valid"
> > "not written"
> > "null where"
> > "numeric in one"
> > "obs=3D0"
> > "observations not"
> > "obsolete"
> > " omitted due to"
> > "occurred on module"
> > "offline"
> > "one or more lines may be longer"
> > "operand was found in"
> > "option value"
> > "outside the axis"
> > "parenthesis for"
> > "previous errors"
> > "proc sql statements are executed immediately"
> > "product not found"
> > "product with which"
> > "partial initialization"
> > "quoted string"
> > "recursion"
> > "recursive"
> > "reference"
> > "references the data set being updated"
> > "refers to the same"
> > "refers to"
> > "repeat"
> > "request ignored"
> > "required operator not found"
> > "requires a numeric"
> > "requires compatible"
> > "right-hand"
> > "sas set option obs=3D0"
> > "sas went"
> > "scale parameter was held fixed"
> > "shifted"
> > "starting variable"
> > "statement has been deleted"
> > "statement needs"
> > "statement syntax"
> > "statement transforms"
> > "statistics are mean corrected"
> > "statistics requested"
> > "stop"
> > "stopped"
> > "subroutine"
> > "syntax for this"
> > "the chi-square is small"
> > "too long"
> > "too many array subscripts"
> > "too small"
> > "too wide"
> > "trying to use"
> > "unable to initialize"
> > "unable to"
> > "unable"
> > "unbalanced"
> > "unclosed"
> > "undeclared"
> > "undetermined"
> > "uninitialized"
> > "unknown"
> > "unrecognized"
> > "unref"
> > "unresolved"
> > "unsatisfied"
> > "violation"
> > "was disabled"
> > "was stopped"
> > "was misspelled as"
> > "was not created"
> > "was not defined"
> > "was not found"
> > "was not replaced"
> > "went to a new line"
> > "were excluded"
> > "will be assumed"
> > "will be used"
> > "will not be"
> > "will not load"
> > "will stop executing"
> > "within the range"
> > "you can only"
> > "your request"
> > "zero elements"
>
> Hi SAS-Lers,
>
> As a side note, If I hit CTL T, =A0a logscrub on the log scrub of the
> log window will be palced in =A0in note h,h
>
> CTL T =A0 =A0 =A0log;file "./&pgm..log";note zx;notesubmit '%utl_logcurch=
k(./
> &pgm..log);';
>
> Also 'ctl h' changes focus to the log scrub output
>
> CTL H =A0 =A0 =A0note h.h
>
> Not sure this works in the enhanced editor and it certainly does not
> work in the super enhanced EG, Enterprise Guide.- Hide quoted text -
>
> - Show quoted text -


You can identify ERRORS/WARNING messages in Log files using the SAS
Tool bar.
What you need to do is=85.Create a list of shortcut keys inside your SAS
Toolbar for the LOG window. This is quick and saves lot of time.

You  can customize toolbar settings using the Customize tools dialog
box.

Here is how you can do that....

1) Enter TOOLEDIT (one word) in the command bar or
2) Go to, TOOLS ________ CUSTOMIZE or
3) Right click on the Toolbar and select CUSTOMIZE.

More details available at
http://studysas.blogspot.com/2010/02/check-how-easy-to-find.html

sarath