Ansicht
Dokumentation

03516 - DB2 Locking

03516 - DB2 Locking

rdisp/max_wprun_time - Maximum work process run time   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

DB2 Locking

--- In SAP on System iZy..., "Mike Martin, IS, Sousa" <MMartinZa...>
wrote:

>
> First, the memory of the 400 will be used for the ODBC queries
outside of
> SAP's memory management which could force swapping and invalidations
of SAP
> memory objects.

Assuming U use *BASE pool for R/3 subsystem, ODBC server jobs run in
QSERVER subsystem which, by default, also uses *BASE pool. U can
change the subsystem description of QSERVER to use another pool (like
*SHRPOOL1) instead to aviod interfering with R/3's objects in *BASE
pool.

> Second, I've heard that while long reads are occurring on
> these tables, data cannot be updated (if the read is using an index,
for example).

If the table is very large, creating an EVI (Encoded Vector Index with
CREATE ENCODED VECTOR INDEX ON ...) will help reduce index scanning
time. EVI is in OS/400 V4R3 onwards. Please look in OS/400 SQL
Reference manual for EVI details.

> Lastly, almost all system monitoring, etc,
> currently occurs in SAP, whereas this proposal would force more
monitoring on AS/400 server level.

U can use real-time performance monitor (in Management Central part of
Operations Navigator) for monitoring through GUI instead of using 5250
session. This is also in V4R3 onwards.

Satid S.
IBM Thailand




Durban Tours - Südafrika Safari

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 1785 Date: 20240426 Time: 200052     sap01-206 ( 3 ms )