Solution : https://service.sap.com/sap/support/notes/407663 (SAP Service marketplace login required)
Key words :
instance profile parameter dbs/db2/max_priqty, basis release 640 dbsl patch support pack 6, profile paramter dbs/db2/use_audit, note describes db2/390-specific corrections, range-partitioned tablespaces & growth-partitioned, dbs/db2/max_priqty reason, 40 dbsl library patch level, basis release support package 6, choose 'partitioned'-->'growth-partitioned', storage parameter member cluster
Related Notes :
| 905420 | DB2-z/OS: Upgrade to CRM4.0SR1 & R3E4.7x2SR1 |
| 792649 | DB2-z/OS: DB2 v8.1 functions in transaction SE14 |
| 686905 | DB2-z/OS: DDIC corrections (6.20 and higher) |
| 679694 | DB2/390: Fixing index names after CCSID switch |
| 661252 | DB2-z/OS: Additions upgrade to Basis 6.40 |
| 640516 | DB2/390: Additions upgrade to R/3 4.7 Ext.Set 2.00 |
| 635639 | DB2/390: PRIQTY too large -> conversion fails (SQLCODE -904) |
| 506339 | DB2/390: Additions upgrade to BW 3.0B |
| 505278 | DB2/390: GRANT ON DATABASE causes a core dump |
| 493577 | DB2/390: Transports and Support Packages for 6.20 |
| 417920 | DB2/390: Corrections for 6.10 and 6.20 |
| 399419 | DB2/390: MCOD installation |