Date:         Sat, 23 Jun 2007 08:56:08 +0200
Reply-To:     Robert Bardos <bardos2@ANSYS.CH>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Robert Bardos <bardos2@ANSYS.CH>
Subject:      Re: z/OS heads up: SAS hotfix E9BB25 breaks FILEEXIST behaviour
              (9.1.3 sp4)
Comments: To: MICS List <MICS-L@NIC.SURFNET.NL>
In-Reply-To:  <78012A2589634E4390C73636F270CCDD02E42144@mercmbx02.na.sas.com>
Content-Type: text/plain; charset="us-ascii"

A little birdie [*1] replied on MXG-L:

>
> I have updated this SAS note, and wanted to tell the
> list as well, that the variable contents are only
> altered when you are running SAS with the
> NONLSCOMPATMODE option is also set.
> Since NLSCOMPATMODE is the default, that means (hopefully!)
> that this will affect fewer customers than it might appear.
>

 [*1] As per the (mutual?) policy of SAS-L I removed the name.
 /rb

>
>> -----Original Message-----
>>
>> (Cross-posted to SAS-L, MXG-L, MICS-L)
>>
>> A heads up to the z/OS community.
>>
>> http://support.sas.com/techsup/unotes/SN/020/020327.html
>>
>>
>> Quoted from the SAS Note:
>>
>> If you apply hot fix E9BB25 and then pass a variable to
>> the FILEEXIST function in a DATA step, the contents of
>> the variable will change after the function executes.
>> Specifically, a null value (hex '00') will appear after
>> the last non-blank character in the variable.
>>
>>
>> Robert Bardos
>> Ansys AG, Zurich, Switzerland