Ansicht
Dokumentation

03831 - Problem with writing to trace file

03831 - Problem with writing to trace file

PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Problem with writing to trace file

Hi Gerd,

sorry for the delay, but I'm really having to do a lot at the moment.

First of all: All you did was OK and the note 25099 (even when old) ist OK
as well!
As soon as some new new functions are inserted in SRVPGMs or a few
parameters change (even when not used by the program) the signature changes,
because SAP exports ALL functions, even the only internal ones, because we
don't use explicit export lists.
So, when a signature violation occurs, you have to "re-bind" as follows:
UPDPGM PGM(SAPMSCSA) MODULE(*NONE) BNDSRVPGM(RSLGLIB)
Unfortunately the program mostly has to stay in the original library which
is in your case GEN40BOPT. So it might be easiest, to rename the kernel-lib
temporary to this or do a save and restore, do the UPDPGM in your kernel lib
and delete the one GEN40BOPT afterwards. Be sure, NOT to have such a lib on
your system after the changes, because otherwise the next APYR3FIX will
fail.

Normally the programs should be updated during APYR3FIX. I checked this in
our reference system and it was fine. But at least, you can always do this
on your own now!

Regards

Volker

Durban Tours - Südafrika Safari

CPI1466 during Backup   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 1587 Date: 20240328 Time: 191748     sap01-206 ( 2 ms )