If a SAS file containing a conversion of a numeric macro variable into
a character variable is submitted from within Risk Dimensions, SAS may
terminate abnormally, possibly issueing a Segmentation Violation.

A SAS file may be submitted for processing from Risk Dimensions in a
number of ways, any of which may trigger this problem.  The file may be
submitted via the RUNSASFILE statement, for example.  Or, a SAS file may
be submitted when a running a project for which a REPORT statement
refers to a SAS file.

Most macro variables are character variables, but some may be numeric.
The automatic macro variables SYSERR, SYSINFO, SYSINDEX and SYSRC, for
example, are numeric.  Conversion from numeric to character may occur
when an attempt is made to display such a variable using CALL SYMGET,
for example.

If a SAS file containing such a conversion is executed within Risk
Dimensions, then a Segmentation Violation or other abnormal termination
may occur at any time during subsequent processing within the same SAS
session.

To circumvent the problem, do not call a SAS file which contains such
a numeric to character conversion from within Risk Dimensions.
Instead, submit the statements outside of Risk Dimensions, perhaps using
%INCLUDE to refer to the SAS file, if possible.  Or, eliminate any code
from the SAS file which attempts to display any numeric macro variables.


A Technical Support hot fix for Release 8.2 TSLEVEL TS2M0 for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#008902

For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#008902

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at: