| J41008 |
| SAS/ACCESS Interface to DB2 9.3_M2 |
| Issue(s) Addressed: | Introduced: |
| 49134 | Trying to share a LIBNAME connection when accessing DB2 on a z/OS system might result in "System abend 0C4" |
J41001 |
| 47285 | ALERT - Null values might be appended to the end of VARCHAR variables when data is retrieved from DB2 in the z/OS operating environment |
J41002 |
| 48272 | ALERT - An arithmetic exception in an explicit pass-through query to DB2 on a z/OS system might result in incorrect results |
J41002 |
| 50803 | The occurrence of a -913 error from DB2 might not stop subsequent steps from processing |
J41002 |
| 51505 | Trying to associate a client's z/OS authorization identifier with a connection to DB2 might not work |
J41002 |
| 9308 | SAS/ACCESS® Interface to DB2 does not support DB2 large objects |
J41003 |
| 11460 | ALERT - Incorrect results or an abend might occur when bulk loading to an existing DB2 table |
J41004 |
| 51025 | ALERT - Incorrect results might occur when you use the system options DIRECT_SQL= and READBUFF= |
J41005 |
| 53825 | A DB2 -804 error or a "column does not exist" error might occur when you join two DB2 tables in the z/OS operating environment |
J41005 |
| 53828 | Reading a DB2 table that contains a BLOB or CLOB data type might result in errors |
J41005 |
| 53989 | Calling a DB2 stored procedure might result in a DB2 -804 error |
J41005 |
| 54613 | Accessing DB2 tables might result in an "insufficient memory" error |
J41006 |
| 54616 | ALERT - Incorrect results might occur when you read a DB2 table using the DBSASTYPE= data set option |
J41006 |
| 56387 | Attempting to use the bulk-load utility to load data into a DB2 table might result in an error |
J41007 |
| 56448 | An incorrect query might be passed to DB2 if you use the SASTRACE= system option and batch submitting in a z/OS operating environment |
J41007 |
| 59257 | The SYSDBRC macro variable does not contain the return code from the last step against a database |
J41008 |
|
|
General Information about Hot Fixes