Problem Note 50396: &SYSERR macro variable returns a value of 0 when a warning message occurs
The &SYSERR macro variable might return a value of 0 when a warning message occurs, as seen in the following example:
6 proc append base=spdslib.test data=spdslib.test;
7 run;
NOTE: Appending SPDSLIB.TEST to SPDSLIB.TEST.
NOTE: Appending the file SPDSLIB.TEST to itself.
NOTE: There were 1 observations read from the data set SPDSLIB.TEST.
NOTE: 0 observations added.
NOTE: The data set SPDSLIB.TEST has 1 observations and 1 variables.
WARNING: Duplicate values not allowed on index x for file SPDSLIB.TEST.
(Occurred 1 times.)
NOTE: PROCEDURE APPEND used (Total process time):
real time 0.03 seconds
cpu time 0.01 seconds
8 %put SYSERR=&SYSERR;
SYSERR=0
The &SYSERR macro variable is set to 0 incorrectly. A return code of 4 should be set because PROC APPEND produces a warning.
Select the Hot Fix tab in this Note to access the hot fix for this issue.
Operating System and Release Information
SPDS | Scalable Performance Data Client | Microsoft Windows Server 2003 Enterprise Edition | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2003 Datacenter Edition | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows XP 64-bit Edition | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2003 Standard Edition | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2003 for x64 | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2008 R2 for x64 | 4.52 HF7 | 4.52 HF8 | | |
Microsoft Windows Server 2008 for x64 | 4.52 HF7 | 4.52 HF8 | | |
64-bit Enabled AIX | 4.52 HF7 | 4.52 HF8 | | |
64-bit Enabled HP-UX | 4.52 HF7 | 4.52 HF8 | | |
64-bit Enabled Solaris | 4.52 HF7 | 4.52 HF8 | | |
HP-UX IPF | 4.52 HF7 | 4.52 HF8 | | |
Linux for x64 | 4.52 HF7 | 4.52 HF8 | | |
Solaris for x64 | 4.52 HF7 | 4.52 HF8 | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2013-08-06 18:28:07 |
Date Created: | 2013-07-14 14:58:43 |