CSL_TOKENMGMT - CSL: Nachrichtenklasse f�r Nachrichten des Token-Management
The following messages are stored in message class CSL_TOKENMGMT: CSL: Nachrichtenklasse f�r Nachrichten des Token-Management.
It is part of development package SCSL in software component BC-SRV-CSL. This development package consists of objects that can be grouped under "CSL: Cross-System Cross-LUW Lock".
It is part of development package SCSL in software component BC-SRV-CSL. This development package consists of objects that can be grouped under "CSL: Cross-System Cross-LUW Lock".
Message Nr ▲ | Message Text |
---|---|
000 | CSL: Unexpected Error |
001 | CSL: Calling &1 with initialized token management not possible |
002 | CSL: Execution of &1 only possible during update |
003 | CSL: No "real" locking possible in update task (&1 with scope &2) |
004 | CSL: Add.ref.: No lock exists (&1) |
005 | CSL: Add.ref.: Scope of lock not sufficient (&1 with scope &2) |
006 | CSL: Not yet implemented |
007 | CSL: Unexpected error during database access (&1) |
008 | CSL: No RFC destination is assigned to the logical system &1 (table &2) |
009 | CSL: TokMgr communication channel {&1, &2}->{&3, &4} is interrupted |
010 | CSL: Your own logical system is not maintained |
011 | CSL: Token manager {&1, &2} is not maintained |
012 | CSL: Token &1 cannot be created in token manager {&2, &3} |
013 | CSL: Condition in &1: no internal lock for &2 exists (TokMgr: &3, &4) |
014 | CSL: Reference &1 for token &2 already created (tok.mgr: &3, &4) |
015 | CSL: Reference &1 for token &2 already used (TokMgr: &3, &4) |
016 | CSL: Reference &1 for Token &2 already released (TokMgr: &3, &4) |
017 | CSL: Inconsistency: &1 is thought to be in &3 based on &2 - was not there |
018 | CSL: Inconsistency: Cycle for &1, based on &2, found in &3 |
019 | CSL: &1: No entry but parameter pactual_scope is not initial |
020 | CSL: &2 is currently bein processed locally by &1 |
021 | CSL: &2 is currently being removed by &1 |
022 | CSL: &2 is locked by &1 (lock time: &3, reference counter: &4) |
023 | CSL: &1: User ref. lock is not compatible with existing lock (&2) |
024 | CSL: Lock for tok. &1 cannot be released because of references |
025 | CSL: Dequeue A11 cannot be executed because of existing references |
026 | CSL: Phys.comm.channel not maintained({CIR, CPP} = {{&1, &2}, {&3, &4}}) |
027 | CSL: Port for phys.c.c. not maintained({CIR, CPP} = {{&1, &2}, {&3, &4}}) |
028 | CSL: Inconsistency with &1: Reference counter is negative (&2) |
029 | CSL: Inconsistency with &1: Used reference is no longer valid |
030 | CSL: Token &1 is not assigned to token manager {&2, &3} |
031 | CSL: Token &1 is not in state &4 in token manager {&2, &3} |
032 | CSL: Token &1 does not have version &4 in token manager {&2, &3} |
033 | CSK: Mass function module &1: Exception &2 was raised at least once |
034 | CSL: Selection criteria have errors or are missing |
035 | CSL: Missing communication channel or channel has error |
036 | CSL: Inconsistent status of function group buffer |
037 | CSL: No authorization to change application log |
038 | CSL: Inconsistency with &1: Missing DB record in system &2 |
039 | CSL: No hit in token manager &1 &2 |
040 | CSL: Application log object &1 not maintained in system &2 |
041 | CSL: Internal error during write of application log in system &1 |
042 | CSL: Missing value &1 for field &2 in authorization object &3 |
043 | CSL: No entry found |
044 | CSL: Error occurred when fetching token &1 from &2: &3 (&4) |
045 | CSL: Error occurred (first time) when fetching token &1 from &2: &3 (&4) |