Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

00022 - Kernel patches

00022 - Kernel patches

rdisp/max_wprun_time - Maximum work process run time   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Kernel patches

Hi Charlie,

as the patches on sapserv for AS/400 are ALWAYS cumulative patches in
opposite to the other platforms you'd have to install both of them. The
first one lifts you to 275 and the second one to 308. 280 is no longer
available because 308 superseeded it. So please take 308 and apply the other
EXEs and last but not least the LIB_DBSL as well!
The question "to upgrade" to 4.6D is not easy. Is the customer already
running 4.6x ? Yes => Install 4.6D Kernel and apply all patches because only
this one will be maintained. When the customer is running e.g. 4.5B it would
be a real upgrade and then you should consider the timeschedule of the


Volker Gueldenpfennig

> -----Original Message-----
> From: Charles Richardson [mailto:cericharZu...]
> Sent: Montag, 11. Dezember 2000 19:21
> To: sap400Zm...
> Subject: Kernel patches
> I have some questions for applying the latest kernel patches. We are
> planning to apply the latest patches to our 46D kernel and
> are slightly
> confused. I have seen several emails concerning problems with
> patch 275 for
> 46D, and recommendations of going to patch 280. What I find
> on SAPSERV4 on
> SAPnet are patches 275 and 308. If 275 is "bad", do I still
> need to apply
> it in order toget to 308? Is there a patch 280 that I should also be
> applying before going to 308?
> Also, it certainly would be helpful if SAP would keep SAPnet
> and SAPSERV4
> consistent.
> Thanks,
> Charlie Richardson
> IBM AS/400 Basis

Durban Tours - Südafrika Safari

TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 2336 Date: 20230206 Time: 232006     sap01-206 ( 3 ms )