On the z/OS side the 10.1.0.4 ++ PTF (UI59016) includes the following:
****************************************************************
* USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1 *
* customers *
****************************************************************
* PROBLEM DESCRIPTION: 1. Rollup Multiplatform 10.1.0.4 *
* fixpack. *
* *
* 2.Message ARS0013E ARSTTT DB Error: *
* {DB2 FOR OS/390}{ODBC DRIVER}{DSN11015} *
* DSNT408I SQLCODE = -104, ERROR: *
* ILLEGAL SYMBOL ";". *
* SOME SYMBOLS THAT MIGHT BE LEGAL *
* ARE: AT MICROSECONDS MICROSECOND *
* SECONDS SECOND MINUTES MINUTE HOURS *
* DSNT418I SQLSTATE = 42601 SQLSTATE *
* RETURN CODE DSNT415I SQLERRP = *
* DSNHPARS SQL PROCEDURE DETECTING ERROR *
* DSNT416I SQLERRD = 3 0 0 -1 71 502 *
* SQL DIAGNOSTIC INFORMATION DSNT416I *
* SQLERRD = X'00000003' X'00000000' *
* X'00000000' X'FFFFFFFF' X'00000047' *
* X'000001F6' SQL DIAGNOSTIC INFORMATION *
* ERRLOC=5:10:1 -- SQLSTATE=37000, *
* SQLCODE=-104, File=arsdoc.c, Line=3079 *
* can occur when using *
* arsuperm for action 4 - SQL query *
* string - in 31-bit mode. *
* *
* 3. Message ARS1109E Unable to allocate *
* enough memory. *
* File=SYS18109.T101342.RA000.ARGL390C.SR *
* Line=671 occurs when using the 390 *
* indexer for a large-object load with *
* greater than 10,000 pages. *
* *
* *
* 4. Message ARS0013E ARSSOCKD DB Error: *
* {DB2 FOR OS/390}{ODBC DRIVER}{DSN11015} *
* DSNT408I SQLCODE = -302, ERROR: THE *
* VALUE OF INPUT *
* VARIABLE OR PARAMETER NUMBER 13 IS *
* INVALID OR TOO LARGE FOR THE TARGET *
* COLUMN OR THE TARGET VALUE DSNT418I *
* SQLSTATE = 22003 *
* SQLSTATE RETURN CODE DSNT415I SQLERRP = *
* DSNXRIHB SQL PROCEDURE DETECTING ERROR *
* DSNT416I SQLERRD = -385 0 0 -1 0 *
* 0 SQL *
* DIAGNOSTIC INFORMATION DSNT416I SQLERRD *
* = X'FFFFFE7F' X'00000000' *
* X'00000000' X'FFFFFFFF X'00000000' *
* X'00000000' SQL *
* DIAGNOSTIC INFORMATION ERRLOC=5:10:2 -- *
* SQLSTATE=22003, SQLCODE=-302, *
* File=arsdoc.c, Line=5026 is received *
* when retrieving a V2 large object. *
* Note that the retrieve is successful, *
* but the logging of the retrieve is what *
* fails. *
* *
* 5. When using the 390 indexer with *
* INDEXSTYLE=AFP, excessive CPU *
* consumption may be noticed. *
* *
* 6. When using the 390 indexer with *
* INDEXSTYLE=AFP and the INDEXnnn *
* statements do not specify sequentially *
* increasing nnn can receive *
* ARS5432I Match not found for value in *
* TLE record, record number 281. Input *
* DDNAME //DD:SYS00004 *
* ARS1129E Row 1: The string "07022017" *
* could not be converted to a date from *
* the format of %m/%d/%y *
* *
* 7.arsdb -u without an *
* ARS_ORIGINAL_CODEPAGE in the ars.cfg *
* issues ARS4012E with *
* ARS_ORIGINAL_CODEPAGE=0 like *
* ARS4012E Unable to initialize *
* environment. The return code is -1. If *
* this is a new (created in version 8.5 *
* or later) instance, then define *
* ARS_ORIGINAL_CODEPAGE=0 in ars.cfg. *
* Otherwise, if this is an existing *
* instance (created prior to 8.5), then *
* define ARS_ORIGINAL_CODEPAGE=1047 in *
* ars.cfg. Once set, *
* ARS_ORIGINAL_CODEPAGE must never *
* change. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
-PROBLEM SUMMARY-
1. Rollup Multiplatform 10.1.0.4 fixpack.
2. When using the 31-bit arsuperm, for action 4 and if the exit
returns updated sql, ARSZ31OS was updating the wrong pointer
causing corruption of the SQL.
3. ARGL390C was using the wrong variable tor a realloc.
4. V2 LO processing may result in a comp_off > 2G. ARNDOC did
not allow for that possibility, resulting in a too big value
being passed to ODBC.
5. ARGL390A was excessively zeroing storage.
6. ARGL390A was not properly dealing with 'missing' INDEXnnn
statements.
7. ARGDB was formatting the text for ARS4012E before getting the
actual codepage resulting in a '0' for the codepage.