Solution : https://service.sap.com/sap/support/notes/170271 (SAP Service marketplace login required)
Summary :
SAP Note addresses the issue where the initial screen data of Transaction DB12 is needlessly redetermined each time a user navigates back from detail screens, causing unnecessary database access, especially when SYSIBM.SYSCOPY is overloaded. To resolve this, ensure that transports from Note 101217 are imported for your specific R/3 release in the recommended sequence. Regularly revisit the note for updates to maintain system efficiency. Additionally, import the appropriate transport as detailed in Note 13719 for specific releases to mitigate the issue.
Key words :
additional key words db2, unnecessary database access, newest maintenance level, transport kd2k000136 releases 3, transport belonging, initial screen, transaction db12, detail screens, generally change, table sysibm
Related Notes :
| 170319 | DB2/390: Poor error handling in DB02 Refresh |
| 151394 | DB2/390: Transports for 4.5B |
| 101303 | DB2/390: Transports for 3.1I |
| 101217 | DB2 z/OS: Overview of transports and corrections |
| 13719 | Preliminary transports to customers (note for customers) |