Ansicht
Dokumentation
01722 - Poll about changing the kernel-patches or not
rdisp/max_wprun_time - Maximum work process run time BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Poll about changing the kernel-patches or not
Thanks for the clarification, Volker. If I don't get the "TP" and "R3TRANS" andsuch patches, then I guess I don't care. That was my biggest complaint: at one
point, there were about 15 non-KERNEL patches to keep track of.
For that matter: (I don't claim to understand the entire kernel maintenance
strategy--I know WHAT works, but not necessary WHY) It it seems like the
periodic kernel CD was the only thing that eventually got rid of all the TP-type
patches. The CD was a "checkpoint" or a "level-set" that included everything.
If we no longer get a CD, it seems like the TP-type patch list would grow and
grow until a CD *was* finally issued, for 4.6E, for example.
Would this be true?
Jim Doll, Perrigo BASIS
>>> "Gueldenpfennig, Volker" <volker.gueldenpfennigZs...> 04/12 1:00 PM >>>
Hi Jim,
"everything" would stay the same. This means that we would still deliver
r3trans, tp, kernel, r3up and every other executable on it's own, as this is
standard at SAP.
The only thing that becomes changed is that the file KERNEL does contain all
the *SRVPGMs (about 90) for the DW and so just can be restored in once. As
we remove the observabilities and compress it, it is possible to become
reduced from about 250 MB down to 40 MB.
Then a new Kernel CD wouldn't be necessary any more all few months, because
everything is updated in one step.
So we would be once more on the main-track of SAP.
Regards
Volker
Durban Tours - Südafrika Safari
BAL Application Log Documentation SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 2095 Date: 20240603 Time: 043049 sap01-206 ( 3 ms )
