Support Forums > z/OS Server
Recommended DB2 on z/OS Service, V12
Ed_Arnold:
Just FYI - here's the level of Db2 V12 we're currently running:
DSNG007I -DSNC DB2 CATALOG LEVEL (V12R1M500 )
CODE LEVEL (V12R1M502 )
CURRENT FUNCTION LEVEL (V12R1M501 )
HIGHEST ACTIVATED FUNCTION LEVEL (V12R1M501 )
DSNR002I -DSNC RESTART COMPLETED
Ed
Ed_Arnold:
Just noting that there's nothing new under the sun, haven't exposed any Db2 defects lately.
Still at:
DSNG007I -DSNC DB2 CATALOG LEVEL (V12R1M500 )
CODE LEVEL (V12R1M502 )
CURRENT FUNCTION LEVEL (V12R1M501 )
HIGHEST ACTIVATED FUNCTION LEVEL (V12R1M501 )
DSNR002I -DSNC RESTART COMPLETED
Ed
Ed_Arnold:
It's now 2020 and still no new Db2 defects have been exposed.
Ed
Ed_Arnold:
Had a report during an upgrade to Db2 V12:
--- Quote ---... in the ARSSOC startup : ARS0013E ARSSOCKD DB Error: Warning: Unexpected sql_rc -- SQLSTATE=
Not Defined, SQLCODE=-805, File=arssys.c, Line=935
--- End quote ---
Note the -805, bind issue.
I t turns out there was a variation of DSNACLI that was put in by IBM CMOD Services team when they implemented. It includes CMODPROD_MIGTOOLS and CMODPROD_USEREXIT, CMODTEST_MIGTOOLS and CMODTEST_USEREXIT in the package list.
Their DSNACLI variation was called ARSACLI.
Once that was rebound all was well.
Please note that this could also occur if you have an ODSCRT table in your system, which is also from the IBM CMOD Services team.
Ed
Ed_Arnold:
Symptom: S0C1 in ARSSOCKD after upgrade of Db2 to V12
Also could show up as Fault Analyzer IDI0002I Abend U3000 along with a SA03
Resolution: Db2 ODBC APAR PH11103:
ODBC WORKAROUND TO RETAIN TRAILING PERIOD IN THE CHAR REPRESENTATION OF DECIMAL COLUMNS
PTF UI63117 resolved the issue.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version