| 82D226 |
| Issue(s) Addressed: | Introduced: |
| SN-006004 |
"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2 |
82D203 |
| SN-005708 |
ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state |
82D203 |
| SN-006276 |
New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo |
82D203 |
| SN-005997 |
Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected. |
82D203 |
| SN-005996 |
Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations |
82D203 |
| SN-005330 |
PROC APPEND to SQL Server using BCP option will insert data incorrectly |
82D203 |
| SN-004053 |
CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver |
82D203 |
| SN-006323 |
Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest |
82D204 |
| SN-006293 |
Read Isolation Level defaults to CR when using SAS/Access Interface toDB2 |
82D203 |
| SN-006312 |
CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows |
82D208 |
| SN-007694* |
NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows |
82D210 |
| SN-008603 |
"No data found" error occurs when trying to update or delete from a DB2table with SQL |
82D216 |
| SN-009478 |
SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table |
82D220 |
| SN-009773 |
Incorrect data when KEEP= contains a field with a binary data type |
82D220 |
| SN-009914 |
/UNIQUE option does not work with ODBC engine for character typedvariables |
82D220 |
| SN-011355* |
WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS |
82D220 |
| SN-012061 |
"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220 |
82D222 |
| SN-013571 |
Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1 |
82D225 |
| SN-013504 |
SQL3061N received bulkloading to a DB2 table in a DBCS database |
82D225 |
| SN-013980 |
DB2 bulk loader does not run with ALLOW READ ACCESS enabled |
82D226 |
| SN-008941 |
Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2 |
82D226 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| PC: |
Windows |
| UNIX: |
HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Linux |
ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied.
ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x. |
| 82OD09 |
| Issue(s) Addressed: | Introduced: |
| SN-006004 |
"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2 |
82OD01 |
| SN-005708 |
ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state |
82OD01 |
| SN-006276 |
New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo |
82OD02 |
| SN-005997 |
Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected. |
82OD01 |
| SN-005996 |
Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations |
82OD01 |
| SN-005330 |
PROC APPEND to SQL Server using BCP option will insert data incorrectly |
82OD01 |
| SN-004053 |
CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver |
82OD01 |
| SN-006323 |
Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest |
82OD02 |
| SN-006293 |
Read Isolation Level defaults to CR when using SAS/Access Interface toDB2 |
82OD02 |
| SN-006312 |
CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows |
82OD03 |
| SN-007694* |
NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows |
82OD04 |
| SN-008603 |
"No data found" error occurs when trying to update or delete from a DB2table with SQL |
82OD05 |
| SN-009478 |
SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table |
82OD06 |
| SN-009773 |
Incorrect data when KEEP= contains a field with a binary data type |
82OD06 |
| SN-009914 |
/UNIQUE option does not work with ODBC engine for character typedvariables |
82OD06 |
| SN-011355* |
WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS |
82OD06 |
| SN-012061 |
"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220 |
82OD07 |
| SN-013571 |
Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1 |
82OD08 |
| SN-013504 |
SQL3061N received bulkloading to a DB2 table in a DBCS database |
82OD08 |
| SN-013980 |
DB2 bulk loader does not run with ALLOW READ ACCESS enabled |
82OD09 |
| SN-008941 |
Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2 |
82OD09 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| PC: |
Windows |
| UNIX: |
HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Linux |
ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied.
ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x. |
| 82OL05 |
| Issue(s) Addressed: | Introduced: |
| SN-004249 |
PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file |
82OL01 |
| SN-005811 |
Syntax error when using WGDB option with PROC IMPORT procedure |
82OL01 |
| SN-005812 |
PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine |
82OL01 |
| SN-004195 |
PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly |
82OL01 |
| SN-005506 |
Importing from Excel 97 or 2000 where the sheet name contains an &fails. |
82OL01 |
| SN-006001 |
Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared' |
82OL01 |
| SN-000494 |
Can SAS access Microsoft SQL Server OLAP cubes? |
82OL01 |
| SN-007399 |
ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed |
82OL01 |
| SN-006709 |
PROC IMPORT of Excel 2000 data containing double byte characters aretruncated in SAS |
82OL02 |
| SN-007477 |
Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390 |
82OL03 |
| SN-007806 |
Accessing OLAP cube that contains a currency type will return $0 |
82OL04 |
| SN-005809 |
ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table |
82OL05 |
| SN-010553 |
Unable to list tables or retrieve data using the Ihistorian OLE DBprovider |
82OL05 |
| Select an Available Operating System: |
| PC: |
Windows |
| 82PF05 |
| Issue(s) Addressed: | Introduced: |
| SN-004249 |
PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file |
82PF01 |
| SN-005811 |
Syntax error when using WGDB option with PROC IMPORT procedure |
82PF01 |
| SN-005812 |
PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine |
82PF01 |
| SN-004195 |
PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly |
82PF01 |
| SN-005506 |
Importing from Excel 97 or 2000 where the sheet name contains an &fails. |
82PF01 |
| SN-006001 |
Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared' |
82PF01 |
| SN-000494 |
Can SAS access Microsoft SQL Server OLAP cubes? |
82PF01 |
| SN-007399 |
ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed |
82PF01 |
| SN-006709 |
PROC IMPORT of Excel 2000 data containing double byte characters aretruncated in SAS |
82PF02 |
| SN-007477 |
Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390 |
82PF03 |
| SN-007806 |
Accessing OLAP cube that contains a currency type will return $0 |
82PF04 |
| SN-005809 |
ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table |
82PF05 |
| SN-010553 |
Unable to list tables or retrieve data using the Ihistorian OLE DBprovider |
82PF05 |
| Select an Available Operating System: |
| PC: |
Windows |
| 82BW03 |
| Issue(s) Addressed: | Introduced: |
| SN-006764 |
Runtime error when extracting or displaying InfoCube with 0DATEattribute from InfoObject |
82BW01 |
| SN-006766 |
Cannot extract InfoCubes from SAS/ACCESS to SAP BW which have compoundcharacteristics where reference character of compound in SID table doesnot match InfoObject name |
82BW01 |
| SN-006765 |
SQL star view requires excessive space for temporary files in SAS/ACCESSto SAP BW |
82BW01 |
| SN-007682 |
Error creating formats for class variables during InfoCube dataextraction within SAS/ACCESS Interface to SAP BW |
82BW02 |
| SN-007675 |
Full extraction versus change data capture for InfoCubes and ODS inSAS/ACCESS Interface to SAP BW |
82BW02 |
| SN-007719 |
SAS/ACCESS Interface to SAP BW extraction does not recognize certainerror conditions |
82BW02 |
| SN-007674 |
Metadata extractions with FIELDS and TABLES selected from SAS/ACCESSInterface to SAP BW returns metadata about non-relevant tables |
82BW02 |
| SN-010160 |
Extractions of InfoCubes or ODS tables within SAS/ACCESS Interface toSAP BW using remote host metadata fails |
82BW03 |
| SN-008892 |
Misleading error message written when extracting ODS tables that containInfoObjects with compound keys from SAS/ACCESS Interface to SAP BW |
82BW03 |
| SN-010159 |
Change Data Capture feature in SAS/ACCESS Interface to SAP BW mayproduce incorrect InfoCube data for compressed InfoCubes in SAP BW |
82BW03 |
| SN-010158 |
Format names created for infocubes in SAS/ACCESS to SAP BW are notdescriptive |
82BW03 |
| Select an Available Operating System: |
| PC: |
Windows |
| UNIX: |
HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64 |
| ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82R302 for your operating system. Customers running in a DBCS environment should download 82R302. This hot fix will NOT be fully functional without both 82BW02 and 82R302 applied. |
| 82SB12 |
| Issue(s) Addressed: | Introduced: |
| SN-004321 |
Unable to execute multiple SELECT statements with Access to Sybase inVersion 7 and Version 8 of the SAS System |
82SB01 |
| SN-005897 |
BULKLOAD of DOLLAR 12.2 format using SAS/ACCESS Interface to SYBASEproduces an OVERFLOW error |
82SB01 |
| SN-005909 |
Unable to append to a SYBASE table with BULKCOPY if an identity columnexists on the table |
82SB01 |
| SN-006327 |
SQL Pass-Through to Sybase EXECUTE statement allows only one statement |
82SB02 |
| SN-006335 |
Using PROC DBLOAD APPEND with BULKCOPY may cause data corruption |
82SB02 |
| SN-008034* |
Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris |
82SB03 |
| SN-008355 |
PROC DBLOAD password is not X'd-out in the SAS log when using SAS/ACCESSInterface to Sybase |
82SB04 |
| SN-008473 |
"Error in results set for update" when updating a Sybase view with DATAstep MODIFY |
82SB04 |
| SN-008967 |
SAS/ACCESS Interface to Sybase incorrectly reads the Sybase value'JUN 21 2001 2:03:46:793AM' and generates a warning message |
82SB05 |
| SN-009796* |
Sybase Open Client 12.5 will not connect with Sybase 11.1 image on AIX |
82SB06 |
| SN-009951* |
New image for Sybase 12.5 on HPUX |
82SB07 |
| SN-010317 |
Access to Sybase V8.2 is not honoring the database= option for updates |
82SB08 |
| SN-010867 |
Unable to update a Sybase table with an Identity field with SAS V8.2 |
82SB09 |
| SN-012997 |
With SAS 8.2 ACCESS TO SYBASE, Notes, warning or errors are not beingissued when attempting to insertinto a Sybase table with triggers using RAISERROR with PROC APPEND |
82SB10 |
| SN-001373 |
ALERT - SAS/ACCESS Version 6 incompatibility issues with SAS Version 7 andVersion 8 |
82SB10 |
| SN-010795 |
Wrong Sybase table accessed when using the SCHEMA LIBNAME option |
82SB10 |
| SN-015017 |
Segmentation Violation error issued intermittently when accessing aSybase server that is not available |
82SB12 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| PC: |
Windows |
| UNIX: |
Solaris_32bit_SAS |
| 82BB12 |
| Issue(s) Addressed: | Introduced: |
| SN-004619 |
Risk Dimensions documentation will not display after SAS System Helphas been invoked |
82BA32 |
| SN-005042 |
Margin settings are ignored in Release 8.2. |
82BA32 |
| SN-005201 |
Read-access violation submitting a simple data step on Windows ME |
82BA32 |
| SN-005938 |
The SAS system abends after you select File from the menu bar |
82BA56 |
| SN-004882 |
FIND and REPEAT FIND (RFIND) keys do not work in the Enhanced Editor inRelease 8.2 |
82BA56 |
| SN-007046 |
ALERT - Enterprise Guide may crash when using RTF result format type |
82BA74 |
| SN-006943 |
ALERT - Combo Box may not display blank value using Dropdown List |
82BA74 |
| SN-007007 |
Abnormal SAS termination entering a long string in a Text Pad Control |
82BA74 |
| SN-007766 |
ALERT - When opening SAS System Help 8.2, browser opens and "The page cannot befound" error message appears |
82BB04 |
| SN-008335 |
Scrolling the wheel of an Intelli Mouse while the END command is issuedcrashes SAS |
82BB12 |
| SN-008755 |
Webhound child processes may hang during the reporting phase |
82BB12 |
| Select an Available Operating System: |
| PC: |
Windows |
| 82BB21 |
| Issue(s) Addressed: | Introduced: |
| SN-004555* |
Subsequent records not read after invalid VBS segment detected |
82BA39 |
| SN-004078* |
FILENAME statement requests three tape mounts for a single tape |
82BA52 |
| SN-004439* |
BY variable position may cause errors |
82BA52 |
| SN-004435* |
Abend S0C1 received in PROC SORT step |
82BA52 |
| SN-004629* |
RC=0 incorrectly issued when running out of directory space writingto PDS |
82BA52 |
| SN-004465* |
LIBNAME statement WAIT= option may causeincorrect engine assignment |
82BA52 |
| SN-007318* |
DIALOG WINDOW of PMENU may issue message indicating an incorrectcommand |
82BA08 |
| SN-005862* |
SASXAL module has increased in size from 300K to 730K from Release 8.1to 8.2 |
82BA52 |
| SN-005121* |
U315, U317, U319, S0C4 and Page Validation Errors when creating ordeleting catalog entries |
82BA52 |
| SN-005971* |
Cannot connect to OS/390 Spawner with MAXASSIZE=2G in BPXPRM** |
82BA57 |
| SN-005642* |
SAS Notes referring to Version 8 multivolume SASIO problems |
82BA57 |
| SN-006100 |
Invalid package files (*.spk) are generated when running with AsianLanguage Support (DBCS) installed |
82BA57 |
| SN-006320 |
PROC PRINT does not honor SPLIT= option (DBCS compliant version only) |
82BA57 |
| SN-006321 |
Japanese version of SAS 8.2 cannot read a back slash correctly from adirectory server |
82BA57 |
| SN-006322 |
Byte order of UCS2 character is wrong with the KCVT function (DBCScompliant version only) |
82BA57 |
| SN-006609* |
PROC SOURCE abends when processing many members |
82BA77 |
| SN-007032* |
ZDVw.d informat incorrectly rejects a value of '9' |
82BA77 |
| SN-006754* |
Performance degradation due to support for long character stringvariables |
82BA77 |
| SN-007394* |
Experimental SECPROFILE SAS System option along with a new SVC routine,allows use of the RACF Secured Signon function |
82BA77 |
| SN-007000* |
When attempting to connect to SAS/SHARE server, an @ sign in the useridreceives "Invalid value" message |
82BA77 |
| SN-007065* |
Loop in SAS/SHARE during termination of server task |
82BA77 |
| SN-007066* |
Abend SEC6 in BPXAS address space using FTP with MP-Connect for OS/390 |
82BA77 |
| SN-007513* |
System abend S0C1 due to bad call from YN1NDMS at +x'166' after applying82BA77 hot fix |
82BA97 |
| SN-007455* |
Small numeric values causing problems on OS/390 in Release 8.2 |
82BA97 |
| SN-007722* |
Publish fails when the French-encoded EBCDIC version is used |
82BB05 |
| SN-007220* |
S400 abend, S0C9 abend, or Insufficient Space messages |
82BB05 |
| SN-007210* |
OS/390 sites may receive S282-048 abend |
82BB05 |
| SN-007952* |
Blank lines written to terminal when SAS CLIST is called from a CLIST |
82BB05 |
| SN-008252* |
When using SAS/SECURE with Spawner script signon, -noinheritance must bespecified |
82BB15 |
| SN-008432* |
Insufficient USS capability causes authorization messages with certainhot fixes applied |
82BB15 |
| SN-008831* |
OC1 and OC4 abends when executing SAS on Fujitsu mainframe MSP-EX |
82BB21 |
| SN-006517* |
B37 abend may cause looping when building an index |
82BB21 |
| SN-008820* |
SAS failing due to not enough buffers available |
82BB21 |
| SN-008435* |
System abend S0C1 in function VSPRNTF |
82BB21 |
| * Indicates that the fix for the issue described in this |
