Documentation View

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

00124 - Slow TPs on AS/400 with latest (308) 4.6D kernel

00124 - Slow TPs on AS/400 with latest (308) 4.6D kernel

BAL Application Log Documentation   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Slow TPs on AS/400 with latest (308) 4.6D kernel

Hi Doreen,

unfortunately the patch is not available by now. The patch is developed and
runs fine. I tested it with an complete upgrade.
Do you have by any chance an old version of the tp (the correct pgm is
TPOS4) ? You could use this in the meantime.
I expect the patch to be ready by tomorrow now. When it is really urgent, I
could put a "pre-compiled" version to sapserv to dist.

I will let you all know, when the official tp fix is available on sapserv.

Regards

Volker Gueldenpfennig

> -----Original Message-----
> From: Anderson, Doreen [mailto:DAndersoZb...]
> Sent: Donnerstag, 21. Dezember 2000 00:44
> To: 'SAP AS/400 Discussion Group'
> Subject: FW: Slow TPs on AS/400 with latest (308) 4.6D kernel
>
>
>
> Has anyone heard if there has been any changes with this issue?
> We are a couple of days away from tp all DEV change requests
> to build TST.
>
> Thanks
> Doreen Anderson
>
>
> -----Original Message-----
> From: Gueldenpfennig, Volker [mailto:volker.gueldenpfennigZs...]
> Sent: Monday, December 11, 2000 11:25 AM
> To: 'sap400Zm...'
> Subject: Slow TPs on AS/400 with latest (308) 4.6D kernel
>
>
> Hello all,
>
> there is a problem that seems to effect a lot customers that
> the TPs are
> getiing very slow on AS/400 with the latest 4.6D kernel,
> because the events
> doesn't seem to come through, even when the command SAPEVT
> runs fine and
> works immediately.
>
> We were able to reproduce your problem today on our systems as well.
>
> It seems to have delays in the area when SAPEVT is started from the
> TP to start the trigger for the RDDIMPDP. Then there seems to be a
> delay of 2 or 3 minutes. So every phase that needs R3 access gets
> longer by this. When only 1 R3-phase is necessary then it may take
> 3 minutes otherwise it may take up to 10 or even 15 minutes!
>
> We will let you know as soon as we do have a fix for this
> strange issue.
>
> Regards
>
> Volker Gueldenpfennig
>

Durban Tours - Südafrika Safari

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3066 Date: 20230205 Time: 123940     sap01-206 ( 2 ms )