Ansicht
Dokumentation

03535 - DBSL patch level vs. Kernel patch level - stup id question

03535 - DBSL patch level vs. Kernel patch level - stup id question

CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

DBSL patch level vs. Kernel patch level - stup id question

Doreen,

Currently, we have the policy of checking the patch level of the files on
SAPSERV4 and compare them to the levels of the files on the AS400. If there
is a major difference in levels, we normally go ahead and apply them ob a
quarterly basis. So far, no problems encountered with this strategy.

Chris

-----Original Message-----
From: Anderson, Doreen [mailto:dandersoZb...]
Sent: Thursday, October 18, 2001 12:54 PM
To: 'Gueldenpfennig, Volker'
Cc: Sap400 (E-mail)
Subject: RE: DBSL patch level vs. Kernel patch level -
stup id question



Our DBSL is at 485 (behind 3 patches); BIG ARGH!
Are all the additional patches on sapservx in the kernel directory
considered "shared library" SRVPGM?

Can you point me to a Note and/or documentation which lists the different
types of patches
We have always had pride in our patching strategies & our DBSL being so far
behind is a BIG issue when we've had many failed attempts to cleanly "DB
Switch"

Having started working with SAP on the AS/400 at release 3.0F on O/S
V3R1....
there are changes with technically managing the product which have occurred
along the way (like this one) that are getting past us.

Thank you so much for your help!

-----Original Message-----
From: Gueldenpfennig, Volker [mailto:volker.gueldenpfennigZs...]
Sent: Thursday, October 18, 2001 11:14 AM
To: 'dandersoZb...'
Cc: Sap400 (E-mail)
Subject: RE: DBSL patch level vs. Kernel patch level -
stup id question


Hi Doreen,

since 4.5A LIB_DBSL is no longer part of the KERNEL. It is a "shared
library" which is a *SRVPGM on AS/400. You always have to patch it yourself.


When you did this you'd see at the end(!) not in the gaps(!) the patches of
the LIB_DBSL.

One example of the 4.6D kernel with patch 804 and DBSL-Patch 638 looks as
follows (SM51->Release info):
...
( 0.800) Spool: DBC archivelist conversion bug (note 435080)
( 0.802) Keep scrollposition (note 391871)
( 0.803) Check sapgui version (note 121619)
( 0.804) UPDATE: inconsistent update data (note 434811)
( 0.026) Create library for explain packages failed (note 314181)
( 0.061) Explain failed for PACKED Hostvariables (note 314181)
( 0.167) SQL0204 in 3-tier with 46D kernel (note 330456)
( 0.216) DBSL Hints & Options (note 129385)
( 0.217) SINGLE_EXECUTION hint in EXEC SQL statements (note 336175)
( 0.437) Prepare: several mySAP.com components in one DB (note 379572)
( 0.485) BW: Database error 9998 (note 387507)
( 0.546) iSeries: SQL0913 for report tables and screen table (note 395490)
( 0.558) iSeries: DB Switchover (note 397906)
( 0.638) Copy input variables; add mod_cnt (note 411982)

The patch-numbers are increasing up to 804 and then are dropping doen to 26
which indicates clearly(!) (sorry for that crazy display!!!) that now the
DBSL-Patches will start. When you never applied them the last 3 lines should
miss as the CD had the patch 543 and there ALL patches are always inlcuded.

Regards

Volker

The group has decided in January 2000
to be free of recruiting and other SPAM!
Violaters will be banned from the group.

SAP on System i-unsubscribeZegroups.com



Your use of consolut is subject to http://www.consolut.net


Durban Tours - Südafrika Safari

BAL Application Log Documentation   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4441 Date: 20240510 Time: 162526     sap01-206 ( 3 ms )