The component BC-CCM-MON-SLG is responsible for SAP system log function, but not responsible for specific system log message analysis.
Please refer following :
System log Messages and their Responsible Components.
AREA | SUBID | TXT | PS_POSID |
A0 | 0 | > Text &9&9&9&9&4 line &4 event &9&9 | BC-ABA-LA |
A0 | 1 | Message SY&4(&9&9&9&3) | BC-ABA-LA |
A0 | 2 | Program buffer re-initialized | BC-ABA-LA |
A0 | 3 | Breakpoint &9&9&9&9&4 reached | BC-ABA-LA |
A0 | 4 | Invalid load format for &9&9&9&9&4 | BC-ABA-LA |
A0 | 5 | No memory available | BC-ABA-LA |
A0 | 6 | Message SY&4(&9&9&9&3) | BC-ABA-LA |
A0 | 7 | Timeout | BC-ABA-LA |
A0 | 8 | Main memory destroyed | BC-ABA-LA |
A0 | 9 | Too many dependencies for &9&9&9&9&4. | BC-ABA-LA |
A1 | 0 | Initialization complete | BC-ABA-LA |
A1 | 1 | PXA recovery after reboot | BC-ABA-LA |
A1 | 2 | >>> Emergency installation <<< | BC-ABA-LA |
A1 | 3 | > Generation of program text &4&9&9&9&9 line &4 | BC-ABA-LA |
A1 | 4 | > in program &4&9&9&9&9, line &4, event &2&9&9 | BC-ABA-LA |
A1 | 5 | Run-time error &9&9&5 in program &4&9&9&9&9. | BC-ABA-LA |
A1 | 6 | Error &9&9&5 generating program &4&9&9&9&9. | BC-ABA-LA |
A1 | 7 | > &6&4&6&4&6&4&6&4&6&4&6&4&4 | BC-ABA-LA |
A1 | 8 | C debugging activated | BC-ABA-LA |
A1 | 9 | Field contents changed: &5&9&9&9&9&9 | BC-ABA-LA |
A2 | 0 | > Error code $$$$$$$$$$$$$$$$$$$$ | BC-ABA-LA |
A2 | 1 | Shared Memory for PXA buffer not available | BC-ABA-LA |
A2 | 2 | SORT ... AS TEXT error occurred in table line &4 | BC-ABA-LA |
A2 | 3 | Goto ABAP Debugger: &9&9&9&9 | BC-ABA-LA |
A2 | 4 | System time: Cannot go back (< 3 sec.). Wait &4 second(s) | BC-ABA-LA |
A2 | 5 | PXA Directory GC Triggered for Fragment &A: &B Entries Have Been Reclaimed | BC-ABA-LA |
A2 | 6 | A manually caught process was stopped from within the Debugger (&A) | BC-ABA-LA |
A2 | 7 | Database table &5&5&5&5&5&5 not found for READ TABLE | BC-ABA-LA |
A2 | 8 | DB &8 executed on explicit request from the debugger | BC-ABA-LA |
A2 | 9 | System time: Cannot go back (> 2 sec.). Use last "valid" time | BC-ABA-LA |
A3 | 0 | System time: Cannot be synchronized with the time of the database server. | BC-ABA-LA |
A3 | 1 | Problems detected in the prerequisites for AMDP (see following statements) | BC-ABA-LA |
A3 | 3 | Runtime Monitor deactivated itself due to an error. | BC-ABA-LA |
A3 | 4 | Problem state occurred in Runtime Monitor. | BC-ABA-LA |
AB | 0 | Runtime error "&a&b&c" occurred. | BC-ABA-LA |
AB | 1 | > Short dump "&6 &6 &8&8&8&8 &6&6" created. | BC-ABA-LA |
AB | 2 | > Include &8&8&8&8&8 line &4. | BC-ABA-LA |
AB | 3 | Error &8&8&7 in error handling. | BC-ABA-LA |
AB | 4 | Saving PXA statistics (&&&&& programs). | BC-ABA-LA |
AB | 5 | Open error for PXA statistics file (error no. &>E5). | BC-ABA-LA |
AB | 6 | User &6&6 forced regeneration of all ABAP programs. | BC-ABA-LA |
AB | 7 | Error when ending an internal mode. | BC-ABA-LA |
AB | 8 | A pipe was closed implicitly. | BC-ABA-LA |
AB | 9 | Invalid handler 0x&A for signal SIGCHLD. | BC-ABA-LA |
AB | D | Short dump deleted with default tool &A | BC-ABA-LA |
AC | 0 | Invalid Print Parameters | BC-ABA-LA |
AD | 0 | Checkpoint Group &A Activated for All Users and Servers (&B) | BC-ABA-LA |
AD | 1 | Checkpoint Group &A Activated for All Users and Servers &B (&C) | BC-ABA-LA |
AD | 2 | Checkpoint Group &A Activated for All Users &B and Servers (&C) | BC-ABA-LA |
AD | 3 | All Activations for Assertions and Breakpoints that Can Be Activated Deleted | BC-ABA-LA |
AD | 4 | Activatable Assertions: System Variant &A Activated for All Users | BC-ABA-LA |
AD | 5 | Activatable Assertions: System Variant &A Activated for User &B | BC-ABA-LA |
AD | 6 | Activatable Assertions: System Variant &A Activated for Server &B | BC-ABA-LA |
AL | 1 | ArchiveLink: &70 | BC-SRV-ARL |
AS | 0 | SYNC:&A->&B: &C &D &E | BC-CCM-MON-SLG |
AS | 1 | SYNC:&A->&B: &C &D &E | BC-CCM-MON-SLG |
AS | 2 | SYNC:&A->&B: &C &D &E | BC-CCM-MON-SLG |
AS | 3 | SYNC:&A:&B | BC-CCM-MON-SLG |
AS | 4 | SYNC:&A:&B | BC-CCM-MON-SLG |
AS | 5 | SYNC:&A:&B | BC-CCM-MON-SLG |
AS | 6 | SYNC:&A | BC-CCM-MON-SLG |
AV | 1 | Audit event recording was stopped (reason=&A) | BC-SEC |
AV | 2 | Error &A occurred when reading table &B key = '&C' (LOC = &D) | BC-SEC |
AV | 3 | Warning: Fill level of the Security Audit Log file exceeds &A percent | BC-SEC |
AV | 4 | Cannot open audit file: &A | BC-SEC |
AV | 5 | I/O error in audit file &A, operation &B | BC-SEC |
AV | 6 | Initialization SCSA for Security Audit completed, number of selections &A | BC-SEC |
AV | 7 | Despite system start, a shared memory for Security Audit Log was found | BC-SEC |
AV | 8 | Invalid Version (&A Not Equal to &B) of Audit Control Block in Shared Memory | BC-SEC |
AV | 9 | Existing shared memory for Security Audit Log is too small | BC-SEC |
AV | A | Profile parameter FN_AUDIT contains an invalid pattern &A, error = &B | BC-SEC |
AV | Z | SAL event definition &A in initial status | BC-SEC |
AW | 1 | Web Reporting: &A | BC-ABA-LA |
B6 | 3 | Data record from SAP table &9&9&9&3 missing for structure MCID &5&5 | BC-ABA |
B6 | 6 | Error reading runtime objects for $$$$$$$$$$ for synchronous MC maintenance | BC-ABA |
B6 | 7 | Analysis error in selection condition for MCID $$$$$$$ | BC-ABA |
B6 | 8 | BC-ABA | |
B6 | 9 | Record in MC table &5&5 already exists during a &6 operation | BC-ABA |
B6 | A | Record in MC table &5&5 not available during a &6 operation | BC-ABA |
B6 | B | Syn. MC maintenance deactivated fully from $$$$$$$$ by user $$$$$$$$$$$$ | BC-ABA |
B6 | C | Syn. MC maintenance deactivated partly from $$$$$$$$ by user $$$$$$$$$$$$ | BC-ABA |
BA | 0 | More than 10000 logical RSQL/RTAB operations completed | BC-ABA |
BA | 1 | More than 50000 logical RSQL/RTAB operations executed | BC-ABA |
BA | 2 | More than 100000 logical RSQL/RTAB operations executed | BC-ABA |
BA | 3 | More than 500000 logical RSQL/RTAB operations completed | BC-ABA |
BA | 4 | More than 1000000 logical RSQL/RTAB operations completed | BC-ABA |
BB | 0 | Buffer &5&5 started with &5&5 bytes | BC-ABA |
BB | 1 | Buffer &5&5 reset | BC-ABA |
BB | 2 | Inconsistent buffer &5&5 | BC-ABA |
BB | 3 | Inconsistency between buffer and nametab attributes for table &5&5 | BC-ABA |
BB | 4 | Buffer &5&5 is full: &5&5 bytes | BC-ABA |
BB | 5 | Processing of buffer &5&5 canceled due to a semaphore error | BC-ABA |
BB | 6 | Buffer &5&5 starts with displacement | BC-ABA |
BB | 7 | Sort sequence error loading table &5&5 | BC-ABA |
BB | 8 | Bufferoverflow loading table &5&5 | BC-ABA |
BB | 9 | Frame overflow loading table &5&5 | BC-ABA |
BB | A | Incorrect generic key loading table &5&5 | BC-ABA |
BB | B | ADM-Message TBX-Buffer: Function &5&5 returns value &5&5 | BC-ABA |
BB | C | Nametab-Inconsistency for Table &5&5 regarding buffering of database views | BC-ABA |
BB | D | Reset buffer &5&5; mode and status: &5&5 | BC-ABA |
BB | E | Reset the Export/Import buffers; work processes &5&5 &5&5 | BC-ABA |
BB | F | Internal Error in Export/Import Buffer: &5&5 &5&5 | BC-ABA |
BB | G | Error in synchronization function &5&5 | BC-ABA |
BB | H | Runtime object inconsistency in DB view &5&5 | BC-ABA |
BD | 0 | ALE: IDoc registry counter changed for object channel &A: &B set to &C | BC-MID-ALE |
BD | 1 | User has deleted entries from the IDoc queue (&A; Direction '&B') | BC-MID-ALE |
BG | 0 | bgRFC conversion failed for unit &A of destination &B. | BC-MID-RFC |
BG | 1 | bgRFC conversion for destination &A started. | BC-MID-RFC |
BG | 2 | bgRFC conversion for destination &A successfully completed. | BC-MID-RFC |
BG | 3 | Job for bgRFC conversion for destination &A failed to be released. | BC-MID-RFC |
BG | 4 | Temporary destination to obtain FM metadata successfully deleted. | BC-MID-RFC |
BG | 5 | Temporary destination to obtain FM metadata failed to be deleted. | BC-MID-RFC |
BG | 6 | bgRFC conversion failed for destination &A. | BC-MID-RFC |
BG | 7 | No bgRFC monitor API authorization for destination $A. | BC-MID-RFC |
BG | 8 | bgRFC conversion for destination &A failed. | BC-MID-RFC |
BI | 0 | X MESSAGE BRAIN 299: &A &B | BW-BEX-OT |
BS | 0 | Memory overflow in buffer synchronization | BC-ABA |
BS | 1 | Invalid synchronization class &5&5 | BC-ABA |
BS | 2 | The synchronization module cannot allocate temporary auxiliary memory | BC-ABA |
BS | 3 | Semaphore error in the buffer synchronization | BC-ABA |
BS | 4 | Invalid length in DDLOG-NOTEBOOK field: &5&5 | BC-ABA |
BS | 5 | The buffer synchronization has not been called for &5&5 seconds | BC-ABA |
BS | 6 | Synchronization record with number &5&5 could not be found in table DDLOG | BC-ABA |
BV | 0 | Record length of the table &5&5 exceeds the &5&5 bytes maximum. | BC-ABA |
BV | 1 | Inconsistent number of blocks in BLOB table &5&5 | BC-ABA |
BV | 2 | Return value &5 when reading a dynamic string | BC-ABA |
BV | 3 | SQL error &5 occurred (possible network problems?). Work process is stopped | BC-ABA |
BV | 4 | Work process is in reconnect status | BC-ABA |
BV | 5 | Conversion error during &3 database access for table &7&5&5 | BC-ABA |
BX | A | No logging information in TMCOL for table &9&9&9&3 | BC-ABA |
BX | B | Data record of table &9&9&9&3 already contained in log table &5&5 | BC-ABA |
BX | C | Data record of table &9&9&9&3 does not fit in log table &5&5 | BC-ABA |
BX | D | The log table &5&5 does not match the SAP kernel | BC-ABA |
BX | E | Log table &5&5 cannot be logged itself | BC-ABA |
BX | F | Table logging in program &5&5 disabled by user &5&5 | BC-ABA |
BX | G | Key length of matchcode root table exceeds the maximum length | BC-ABA |
BY | 0 | > &6&6&6&6&6&6&6&6&6&6 | BC-ABA |
BY | 1 | Database error &6 | BC-ABA |
BY | 2 | Database error &6 at &7 | BC-ABA |
BY | 3 | Database error &6 when accessing table &9&9&9&3 | BC-ABA |
BY | 4 | Database error &6 with &3 access to table &9&9&9&3 | BC-ABA |
BY | 5 | Parameter &5&5 missing when calling up database interface | BC-ABA |
BY | 6 | READ ONLY view &5&5 cannot be modified | BC-ABA |
BY | 7 | Database selection with invalid cursor &5&5 | BC-ABA |
BY | 8 | All cursors defined | BC-ABA |
BY | 9 | Physical table &5&5 for logical table &5&5 is not in the name table | BC-ABA |
BY | A | Details of database connection &9&9&9&3 could not be read | BC-ABA |
BY | B | Open SQL statement on structure &5&5 not allowed | BC-ABA |
BY | C | Field name discrepancy between projection view &5&5 and table &5&5 | BC-ABA |
BY | D | Primary key in view &5&5 and table &5&5 are different | BC-ABA |
BY | E | Invalid parameter &5&5 passed to database interface | BC-ABA |
BY | F | Internal error in cluster interface | BC-ABA |
BY | G | No shared library found for the database with ID &9&9&9&3 | BC-ABA |
BY | H | Invalid access mode &5&5 | BC-ABA |
BY | I | Connect to the database with ID &9&9&9&3 failed | BC-ABA |
BY | J | Function &5&5 on connection &5&5 failed | BC-ABA |
BY | K | SQL statement violates database system restriction | BC-ABA |
BY | L | Database error &6 requires database administrator to intervene | BC-ABA |
BY | M | SQL error &6 occurred; work process in reconnect status | BC-ABA |
BY | N | BC-ABA | |
BY | O | Deadlock occurred | BC-ABA |
BY | P | The long field &5&5 was converted into a SET or WHERE condition | BC-ABA |
BY | Q | Invalid parameter(s) passed to the database interface | BC-ABA |
BY | R | Maximum length of the long field of table &5&5 exceeded | BC-ABA |
BY | S | The work area passed is incorrectly set up | BC-ABA |
BY | T | The runtime element (nametab) of table &5&5 is invalid | BC-ABA |
BY | U | The length of complex object &5&5 (&5&5) is inconsistent | BC-ABA |
BY | V | The number of blocks of complex object &5&5 (&5&5) is inconsistent | BC-ABA |
BY | W | Occurred in table &5&5 | BC-ABA |
BY | X | Forbidden access to the user master table &5&5 by program &8 | BC-ABA |
BY | Y | Work process has left reconnect status | BC-ABA |
BY | Z | Cluster buffer commit unsuccessful | BC-ABA |
BZ | 0 | Invalid operation ID &5&5 | BC-ABA |
BZ | 1 | Invalid input buffer | BC-ABA |
BZ | 2 | Field &5&5 in table &5&5 must be specified in full | BC-ABA |
BZ | 3 | Return value &5 not expected | BC-ABA |
BZ | 4 | Synchronization of the queue buffer failed due to unsuccessful database commit | BC-ABA |
BZ | 5 | No. of columns in table &5&5 exceeds internal limit of &5&5 | BC-ABA |
BZ | 6 | Nametab of table &5&5 has fewer fields than expected | BC-ABA |
BZ | 7 | Storage request (&5&5 bytes) failed | BC-ABA |
BZ | 8 | Output buffer (&5&5 bytes) is too small for the record (&5&5 bytes) | BC-ABA |
BZ | 9 | Table &5&5 is not in the name table | BC-ABA |
BZ | A | Table &9&9&9&3 does not exist on the database with ID &9&9&9&3 | BC-ABA |
BZ | B | The specified access type requires the complete primary key | BC-ABA |
BZ | C | INSERT, UPDATE and MODIFY in work are mode require the complete record | BC-ABA |
BZ | D | Table &5&5 : Insertion of key &5&5&5&5&5&5&5&5 results in a duplicate | BC-ABA |
BZ | E | Type conversion for field &9&9&9&3 : &9 not permitted | BC-ABA |
BZ | F | Failed to read a record in table &5&5 in the buffer | BC-ABA |
BZ | G | Failed to load table &5&5 into the buffer | BC-ABA |
BZ | H | Incompletely buffered table &5&5 may not be loaded into buffer | BC-ABA |
BZ | I | Condition in an SQL statement returns the value 'FALSE' | BC-ABA |
BZ | J | A nametab restriction for cluster tables was violated (table &5&5) | BC-ABA |
BZ | K | UPDATE without SET list | BC-ABA |
BZ | L | Internal error in table buffer: &5&5 &5&5 | BC-ABA |
BZ | M | The maximum size allowed for cluster records was exceeded | BC-ABA |
BZ | N | UPDATE of key fields for table &5&5 not permitted | BC-ABA |
BZ | O | Invalid ORDER-BY clause | BC-ABA |
BZ | P | SELECT lists are presently not supported for this table type | BC-ABA |
BZ | Q | Invalid statement mode for &5&5: &5&5 | BC-ABA |
BZ | R | Operator &5&5 for field &5&5 not permitted | BC-ABA |
BZ | S | ABAP type &5&5 is unknown | BC-ABA |
BZ | T | Field no. in table &5&5 has no key field in the pool | BC-ABA |
BZ | U | Length info in database > data length in name table | BC-ABA |
BZ | V | Return value &5 when modifying a dynamic string | BC-ABA |
BZ | W | Error &5 during compression/decompression (&5&5) | BC-ABA |
BZ | X | Field &5&5 does not exist in table &5&5 | BC-ABA |
BZ | Y | Unexpected return value &5 when calling up &5&5 | BC-ABA |
BZ | Z | Statement type (&5&5) is only supported on the default database connection | BC-ABA |
C4 | 0 | Plausibility check was deactivated for view &A | BC-CCM-MON-SLG |
C4 | 1 | Application &A warns: &B &C &D &E | BC-CCM-MON-SLG |
CA | 1 | Unable to buffer factory calendar &A (exception &B, return code &C) | BC-SRV-ASF-CAL |
CA | 2 | Unable to buffer public holiday calendar &A (exception &B, return code &C) | BC-SRV-ASF-CAL |
CC | 1 | User SAP* in client &A deleted after cancellation of client copy | BC-CTS-CCO |
CP | 0 | &B records inserted in table &A: &C | BC-I18 |
CP | 1 | &B records changed in table &A: &C | BC-I18 |
CP | 2 | In table &A, there are &B entries | BC-I18 |
CP | 3 | Character set '&A' does not appear in table '&B' | BC-I18 |
CP | 4 | Table TCPDB has &A entries, but MNLS mechanism has status '&B' | BC-I18 |
CP | 5 | &B entries deleted from table &A: &C | BC-I18 |
CP | 6 | CCC initialization: &9&9&9&9&9&8 | BC-I18 |
CP | 7 | Length or address of a text is incorrect: &A | BC-I18 |
CP | 8 | Aux. memory of length &A (bytes) not available | BC-I18 |
CP | 9 | Invalid Parameters: &A &B &C &D &E &F: For Codepage Converter | BC-I18 |
CP | A | Load CCC (Codepage &A): Error Number &E>B for File &a&b&c&d&e&f&g&h&i | BC-I18 |
CP | B | The F4 Map from &A of Table TCP00 Does not Contain a Character Set | BC-I18 |
CP | C | CCC: Read TCP00: errno &E>A in File &a&b&c&d&e&f&g&h&i | BC-I18 |
CP | D | Character Set '&A' Is not in F4 Memory of &B | BC-I18 |
CP | E | Maximum Recursion Depth (&B) Exceeded After Loading Character Set '&A' | BC-I18 |
CP | F | h_rscp_use_db Is FALSE, but CCC Is Compiled with DB Interface Only | BC-I18 |
CP | G | Failed to Set Environment for Language &A Code Page &B Locale &C | BC-I18 |
CP | H | Failed to Get Environment for Language &A | BC-I18 |
CP | I | Failed to Reset Language Environment | BC-I18 |
CP | J | No GUI Code Page (Language &A, GUI Type &B; &C &D ) | BC-I18 |
CP | K | Shared Memory not Stabile: Lang=&A, Codepage=&B, &C <> &D : &a&b&c&d&e&f&g&h&i | BC-I18 |
CP | L | No Code Page Allowed. Wanted: &B for Language &A | BC-I18 |
CP | M | ABAP TEXTENV Initialization.&D Errors Already Suppressed (Lang.=&A, Cd.Pg.=&B) | BC-I18 |
CP | N | Invalid Value '&1' for Segment '&5' in TCPSEG-KIND | BC-I18 |
CP | O | Code page '&A' is contained in &B. This is not valid for the current converter | BC-I18 |
CP | P | In the character set &A the SAP character &B is not defined | BC-I18 |
CP | Q | Code Page '&A' is empty or incompletely defined: &B | BC-I18 |
CP | R | No Code Page Conversion '&A'->'&B' : &C->&D | BC-I18 |
CP | S | Active ICU Version &6; Compiled With ICU &6; Unicode Version &6 | BC-I18 |
CP | T | ICU shared libraries will not be used | BC-I18 |
CP | U | Table &A Field &B Key &C with Wrong Content "&D" | BC-I18 |
CP | V | Function &9&9&9&9&9&9&9&1 Not Yet Implemented | BC-I18 |
CP | W | Input Buffer Does Not Have Enough Bytes for a Single Character | BC-I18 |
CP | X | Not even the blank character is known of this code page | BC-I18 |
CP | Y | Table &A Missing in Control Table &B | BC-I18 |
CQ | 0 | -< Reserved for Packages SCP and NLS >- | BC-I18 |
CQ | 1 | Language cannot be identified | BC-I18 |
CQ | 2 | Language "&A" is not known | BC-I18 |
CQ | 3 | Table "&A" is missing in the database | BC-I18 |
CQ | 4 | Inconsistent software status: &A &B &C &D &E | BC-I18 |
CQ | 5 | Cannot read name tab type "&B" for "&C". rc=&A | BC-I18 |
CQ | 6 | Too many different code pages in env. control tables. Cp.=&A, Max.No.=&B | BC-I18 |
CQ | 7 | Table "&A" is empty | BC-I18 |
CQ | 8 | Table '&A' is empty or missing from the database | BC-I18 |
CQ | 9 | Problem with UMGCONTAINER: A=&A, B=&B, C=&C, D=&D | BC-I18 |
CQ | A | Reading for &B: Error number &>EA for file &a&b&c&d&e&f&g&h&i | BC-I18 |
CQ | B | No database is open; &A cannot be read | BC-I18 |
CQ | C | Function &A is not needed in a Unicode system | BC-I18 |
CQ | D | Code page converter has lost the database connection | BC-I18 |
CQ | E | Code page converter was reinitialized. | BC-I18 |
CQ | F | Alternative name tab entry for table/structure &A is too old: &B < &C | BC-I18 |
CQ | H | SAPPARAM(rsts/ccc/&A) = &B is too big. (Maximum=&C) | BC-I18 |
CQ | I | Inconsistent entry &C between tables &A and &B | BC-I18 |
CQ | J | Unicode conversion from &A to &C is not possible for database import | BC-I18 |
CQ | K | UMGCONTAINER specifies an unsuitable field "&A": &B , &C , &D | BC-I18 |
CQ | L | Character size is not known for container handling of &A | BC-I18 |
CQ | M | The &B name tab entry is missing for container field &C | BC-I18 |
CQ | N | Presently no access to database table &A | BC-I18 |
CQ | O | &B contains too many common characters: &A | BC-I18 |
CQ | P | There are no common characters for code pages &A | BC-I18 |
CQ | Q | Code pages to identify common characters are unknown | BC-I18 |
CQ | R | T1 in CCC cache is not formatted for ISO 2022 | BC-I18 |
CQ | S | Conflicting requirements of the code page converter | BC-I18 |
CR | 0 | -< CR1 .. CRZ to be used for I18n, code pages, NLS,... >-- | BC-I18 |
D0 | 1 | Transaction Canceled &9&9&5 ( &a &b &c &d &e &f &g &h &i ) | BC-ABA-SC |
D0 | 2 | DB error Mod:&8(&3) T100:&4 SQL-F:&1 Tab:&9&7 SQL-C:&5(&1) | BC-ABA-SC |
D0 | 3 | Unable to set parameter &A (length &B) | BC-ABA-SC |
D0 | 4 | Area for screen text generation is too small: &A | BC-ABA-SC |
D0 | 5 | > Screen &A &B, language &C | BC-ABA-SC |
D0 | 6 | INITIALIZATION COMPLETE | BC-ABA-SC |
D1 | 2 | Error creating batch input session $$$$$$$$$$$$ | BC-ABA-SC |
D1 | 3 | Error processing batch input session $$$$$$$$$$$$ | BC-ABA-SC |
D1 | 4 | > Queue ID: $$$$$$$$$$$$$$$$$$$$ | BC-ABA-SC |
D1 | 5 | > Transaction no. $$$$$, block no. $$$$$ | BC-ABA-SC |
D1 | 7 | > Queue error, function $$$$$$$, RC $$$, SQL-RC $$$$$ | BC-ABA-SC |
D1 | 9 | > Memory Area for Screen &9&9&9&9&4 &4 Is Too Small | BC-ABA-SC |
D2 | 0 | > Error in transaction data | BC-ABA-SC |
D2 | 1 | > Error in screen data | BC-ABA-SC |
D2 | 2 | > Length error in transaction data | BC-ABA-SC |
D2 | 3 | > Length error in screen data | BC-ABA-SC |
D2 | 4 | > Unable to create batch input log | BC-ABA-SC |
D2 | 5 | > Unable to create batch input log | BC-ABA-SC |
D2 | 6 | Processing Batch Input Folder Canceled | BC-ABA-SC |
D2 | 7 | Batch input log cannot be created | BC-ABA-SC |
D2 | 8 | Error creating batch input log | BC-ABA-SC |
D3 | 0 | Profile variable 'dbs/db2/hosttcp' not found | BC-DB-DB2 |
D3 | 1 | Open for file &a&b&c&d failed | BC-DB-DB2 |
D3 | 2 | Reason: &a&b&c&d | BC-DB-DB2 |
D3 | 3 | &a&b | BC-DB-DB2 |
D3 | 4 | JCL submission service: User &1 not found in table DB2JU | BC-DB-DB2 |
D3 | 5 | JCL submission service: Error $$$ occurred | BC-DB-DB2 |
D3 | 6 | JCL submission service: No connection to OS/390 host | BC-DB-DB2 |
D3 | 7 | JCL submission service: No valid host (IP address) | BC-DB-DB2 |
D3 | 8 | JCL submission service: No valid user | BC-DB-DB2 |
D3 | 9 | JCL submission service: No valid password | BC-DB-DB2 |
D3 | A | Database administration(XDB): Could not insert/update table &9 | BC-DB-DB2 |
D3 | B | DB02: LISTCAT job for HLQ &a ended with JCL condition code &b. Refresh aborted | BC-DB-DB2 |
D3 | C | Error &a in SlICLIGetTrace (trying to get directory) | BC-DB-DB2 |
D3 | D | Error &a in SlICLIGetTrace (trying to get file &b) | BC-DB-DB2 |
D3 | E | Failover to <&A> occurred. | BC-DB-DB2 |
D3 | F | &a&b | BC-DB-DB2 |
D3 | H | DB2 performance monitor: Error &a occurred | BC-DB-DB2 |
D3 | I | DB2/390: Exception &a in SALI function module | BC-DB-DB2 |
D3 | J | Database administration(XDB): Could not get the current DB2 system id. | BC-DB-DB2 |
D3 | S | &a&b | BC-DB-DB2 |
D4 | 0 | RSDB2MAS: conversion of table &A cancelled | BC-DB-DB2 |
D4 | 1 | DB2 version >= 7.1; RUNSTATS and other DB2 utilities may not be available! | BC-DB-DB2 |
D4 | 2 | DB2 version >= 7.1; the following DB2 utilities are available: | BC-DB-DB2 |
D4 | 3 | &A &B &C &D &E | BC-DB-DB2 |
D4 | 4 | DB2 utility &A is not available | BC-DB-DB2 |
D4 | 5 | Output of &A | BC-DB-DB2 |
D4 | 6 | DB2 version <= 6.1; all DB2 utilities on board! | BC-DB-DB2 |
D5 | 1 | The database monitor was not started (&A) | BC-DB-DB4 |
D6 | 0 | Reserved for DB6 | BC-DB-DB6 |
D6 | 1 | Function &a failed for &b . Reason: &c | BC-DB-DB6 |
D6 | 2 | Access to database &a via Command Line Processor (see DBA Cockpit Audit Log) | BC-DB-DB6 |
D6 | 3 | &a: &b (see SLG1 object DBACOCKPIT) | BC-DB-DB6 |
DA | 1 | &A '&B' has been deleted | BC-CCM-ADK |
DD | 1 | DICT SQL error during $$$$$$$$$$$ | BC-DWB-DIC-AC |
DD | 2 | DICT DDERR $$$$$$$$$$$ returned | BC-DWB-DIC-AC |
DD | 3 | DDIC function "Unlock table" executed for table &A. | BC-DWB-DIC-AC |
DG | 1 | Log Buffer Overflow (Screen &9&9&9&9&4 &4) | BC-ABA-SC |
E0 | 0 | New System Log File Started with Number &6 | BC-CCM-MON-SLG |
E0 | 1 | Program &8 Started: &8&8&8 | BC-CCM-MON-SLG |
E0 | 2 | Program &8 Ended: &8&8&8 | BC-CCM-MON-SLG |
E0 | 3 | Program &8 Reports &8&8&8 | BC-CCM-MON-SLG |
E0 | 5 | Program &8 Cannot Rename &8&8&8 | BC-CCM-MON-SLG |
E0 | 6 | Assertion &9&9&9&9&9&8 in program &8, location &3 not fulfilled | BC-CCM-MON-SLG |
E0 | 7 | Error &>E6 : &7&8&8&8&8&8 in Module &8(&3) | BC-CCM-MON-SLG |
E0 | 9 | &4-&2-&2 &2:&2:&2 ==> /&a/&b/&c/&d/&e/&f/&g/6h/&i/ | BC-CCM-MON-SLG |
E0 | A | < &2 &6&8&8&8&8&8&8&8 | BC-CCM-MON-SLG |
E0 | B | Central System Log was Changed: &A | BC-CCM-MON-SLG |
E0 | C | Local System Log was Changed: &A | BC-CCM-MON-SLG |
E0 | D | Not Used | BC-CCM-MON-SLG |
E0 | E | File name &a&b&c&d&e&f&g&h&i is invalid: &A | BC-CCM-MON-SLG |
E0 | F | File &a&b&c&d&e&f&g&h&i deleted | BC-CCM-MON-SLG |
E0 | G | File &a&b&c&d&e&f&g&h&i was not deleted: &A | BC-CCM-MON-SLG |
E1 | 0 | Buffer &8 Generated with Length &9 | BC-CCM-MON-SLG |
E1 | 1 | Buffer &8 Could Not be Generated | BC-CCM-MON-SLG |
E1 | 2 | Buffer &8 Deleted (Length=&9, Reason=&9&6&8&8&8&8) | BC-CCM-MON-SLG |
E1 | 3 | Test Entry a=&a A=&A 8=&8 | BC-CCM-MON-SLG |
E1 | 4 | Reorganized Buffer &8 with Length &9 (&9&9&9&9) | BC-CCM-MON-SLG |
E1 | 5 | Buffer &8 Already Exists. (Length=&9) | BC-CCM-MON-SLG |
E1 | 6 | During Initialization of &A : &B | BC-CCM-MON-SLG |
EA | 0 | Error processing the job log file | BC-CCM-BTC |
EA | 1 | Failed to open job log file with session $$ | BC-CCM-BTC |
EA | 2 | Job log file ID not found | BC-CCM-BTC |
EA | 3 | Error accessing buffer | BC-CCM-BTC |
EA | 4 | Occupancy vector too small | BC-CCM-BTC |
EA | 5 | Illegally created memory, address $$$$$$$$ | BC-CCM-BTC |
EA | 6 | Unknown exception, ID: $$$$ | BC-CCM-BTC |
EA | 7 | Directory entry too large ($$$$$$), maximum $$$$$$ | BC-CCM-BTC |
EA | 8 | Log partition already exists | BC-CCM-BTC |
EA | 9 | Data entry too large ($$$$$$), maximum $$$$$$ | BC-CCM-BTC |
EA | A | Failed to open log partition | BC-CCM-BTC |
EA | B | Log partition does not exist | BC-CCM-BTC |
EA | C | Failed to remove the scheduling of job &A/&B | BC-CCM-BTC |
EA | J | Widowed data block found, block index $$$$$$ | BC-CCM-BTC |
EA | K | Failed to access parameter $$$$ | BC-CCM-BTC |
EA | L | Character field too short for log file name | BC-CCM-BTC |
EA | M | Length of a job log directory entry <= 0 | BC-CCM-BTC |
EA | N | Failed to expand internal table &9&9&9&3 | BC-CCM-BTC |
EA | O | Job log consistency has been reestablished | BC-CCM-BTC |
EA | P | Job log was reorganized | BC-CCM-BTC |
EA | Q | Failed to update last execution time of the job scheduler | BC-CCM-BTC |
EA | R | No background jobs to start | BC-CCM-BTC |
EA | S | Failed to reschedule a periodic job | BC-CCM-BTC |
EA | T | Job start initiated, execution date $$$$$$$$ $$$$$$ | BC-CCM-BTC |
EA | U | Failed to remove scheduling of $$$ jobs | BC-CCM-BTC |
EA | V | Batch job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ started | BC-CCM-BTC |
EA | W | Failed to initiate start of job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EA | X | Failed to read successor no. $$$$$ of a job | BC-CCM-BTC |
EA | Y | Failed to read status entry for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EA | Z | Failed to maintain status entry for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EB | 0 | Failed to delete the internal report &9&9&9&9&4 | BC-CCM-BTC |
EB | 1 | Failed to delete the status entry for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EB | 2 | Failed to delete log for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EB | 3 | Failed to start a subsequent job for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EB | 4 | > Scheduling of job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ not released | BC-CCM-BTC |
EB | 5 | Batch scheduler: Unable to lock table TBTCS | BC-CCM-BTC |
EB | 6 | > Cause: Table was already locked | BC-CCM-BTC |
EB | 7 | > Cause: Error within the lock operation | BC-CCM-BTC |
EB | 8 | > Action: End the current scheduler run | BC-CCM-BTC |
EB | 9 | Batch scheduler: Unable to perform job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EB | A | > Cause: Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is being processed | BC-CCM-BTC |
EB | B | > Cause: ... and is therefore locked | BC-CCM-BTC |
EB | C | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EB | D | > Cause: Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ has been deleted | BC-CCM-BTC |
EB | E | Failed to read step $$$$$ of job (database error code: &B) | BC-CCM-BTC |
EB | F | Failed to activate authorization check for user $$$$$$$$$$$$ | BC-CCM-BTC |
EB | G | Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ was not started | BC-CCM-BTC |
EB | H | > Cause: Preceding job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ was cancelled | BC-CCM-BTC |
EB | I | Error scheduling a batch job | BC-CCM-BTC |
EB | J | > Program name not specified | BC-CCM-BTC |
EB | K | > Program &9&9&9&9&4 does not exist | BC-CCM-BTC |
EB | L | > Program &9&9&9&9&4 is not a schedulable program | BC-CCM-BTC |
EB | M | > Batch user name not specified | BC-CCM-BTC |
EB | N | > Unable to generate ID number for job | BC-CCM-BTC |
EB | O | > Internal reports are being processed, repeat $$$$$$$$$$$$ | BC-CCM-BTC |
EB | P | > Start date is in the past &9&9&2 | BC-CCM-BTC |
EB | Q | > The job is being processed, repeat $$$$$$$$$$$ | BC-CCM-BTC |
EB | R | > $$$$$$$$$$$$ for job failed, error in lock operation | BC-CCM-BTC |
EB | S | > No authorization for batch user name $$$$$$$$$$$$ | BC-CCM-BTC |
EB | T | > Batch user $$$$$$$$$$$$ does not exist | BC-CCM-BTC |
EB | U | > Batch user $$$$$$$$$$$$ has incorrect user type | BC-CCM-BTC |
EB | V | > Start date unclear | BC-CCM-BTC |
EB | W | > Job name not specified | BC-CCM-BTC |
EB | X | > The specified job does not exist | BC-CCM-BTC |
EB | Y | > Job group not specified | BC-CCM-BTC |
EB | Z | > No authorization for $$$$$$$$$$$$ of selected job | BC-CCM-BTC |
EC | 0 | > Parameter variant not specified | BC-CCM-BTC |
EC | 1 | > There are already several identical jobs | BC-CCM-BTC |
EC | 2 | > The internal report for the job has already been deleted | BC-CCM-BTC |
EC | 3 | > Unable to generate the name for an internal report | BC-CCM-BTC |
EC | 4 | > Program &9&9&9&9&4 is being processed, repeat $$$$$$$$$$$$ | BC-CCM-BTC |
EC | 5 | > Job ID number not specified | BC-CCM-BTC |
EC | 6 | > This job does not contain any steps | BC-CCM-BTC |
EC | 7 | System clean-up after unexpected batch job termination | BC-CCM-BTC |
EC | 8 | Failed to enter the spool list ID for step no. $$$$$ | BC-CCM-BTC |
EC | 9 | > Log file $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EC | A | > Function $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EC | B | > Op. system message: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EC | C | > Failed to position on block number $$$$$ | BC-CCM-BTC |
EC | D | > Failed to position at end of file | BC-CCM-BTC |
EC | E | > Failed to write to the log file | BC-CCM-BTC |
EC | F | Failed to create log for job &A/&B | BC-CCM-BTC |
EC | G | No batch request authorization for program &9&9&9&9&4 | BC-CCM-BTC |
EC | H | Batch scheduler: Failed to re-schedule a periodic job | BC-CCM-BTC |
EC | I | Unable to read name of job log file | BC-CCM-BTC |
EC | J | Failed to enter message $$$ (application area $$) in job log | BC-CCM-BTC |
EC | K | Batch scheduler: Unable to process a job | BC-CCM-BTC |
EC | L | > Cause: Planned start date too far in the past | BC-CCM-BTC |
EC | M | > Action: De-allocate batch job | BC-CCM-BTC |
EC | N | > Program &9&9&9&9&4 contains syntax errors | BC-CCM-BTC |
EC | O | > Failed to generate program &9&9&9&9&4 | BC-CCM-BTC |
EC | P | Background scheduler: $$$$$$$$$$. Error message with delay level $$$$$$$$$$ | BC-CCM-BTC |
EC | Q | Background scheduler table was locked | BC-CCM-BTC |
EC | R | The last background scheduler execution time was updated | BC-CCM-BTC |
EC | S | Periodic job was rescheduled | BC-CCM-BTC |
EC | T | Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ was started | BC-CCM-BTC |
EC | U | External program: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EC | V | Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ has been deleted | BC-CCM-BTC |
EC | W | Failed to receive log from external program | BC-CCM-BTC |
EC | X | Failed to determine the number of free batch work processes | BC-CCM-BTC |
EC | Y | $$$$$$$$-base job scheduler was deactivated | BC-CCM-BTC |
EC | Z | $$$$$$$$-based job scheduler was reactivated | BC-CCM-BTC |
ED | 0 | Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ has exceeded the latest start date | BC-CCM-BTC |
ED | 1 | > Variant &A is invalid | BC-CCM-BTC |
ED | 2 | > Program $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
ED | 3 | User $$$$$$$$$$$$ has started the BI-API test environment | BC-CCM-BTC |
ED | 4 | Unable to determine the name of the SAP system | BC-CCM-BTC |
ED | 5 | Unable to determine the name of the batch system | BC-CCM-BTC |
ED | 6 | No SAP system is currently active on computer $$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
ED | 7 | No SAP batch system is currently active on computer $$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
ED | 8 | Unalbe to check the name of target computer $$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
ED | 9 | > Latest start date was not specified fully | BC-CCM-BTC |
ED | A | > Latest start date is before the scheduled start date | BC-CCM-BTC |
ED | B | > Start date and latest start date are more than 1 year apart | BC-CCM-BTC |
ED | C | Event handler: Job cannot be processed | BC-CCM-BTC |
ED | D | > Reason: Failed to enter security mark | BC-CCM-BTC |
ED | E | Event handler: Security mark could be entered | BC-CCM-BTC |
ED | F | > Reason: Failed to remove event scheduling | BC-CCM-BTC |
ED | G | Event handler: Event scheduling was removed | BC-CCM-BTC |
ED | H | > Reason: Database Commit for central control tables failed | BC-CCM-BTC |
ED | I | Event handler: Database Commit was successful | BC-CCM-BTC |
ED | J | > Reason: Failed to update event scheduling | BC-CCM-BTC |
ED | K | Event handler: Event scheduling was updated | BC-CCM-BTC |
ED | L | Event handler: Event could not be processed | BC-CCM-BTC |
ED | M | > Reason: Unable to find ID os triggered event | BC-CCM-BTC |
ED | N | Program &9&9&9&9&4 has a syntax error | BC-CCM-BTC |
ED | O | Failed to generate program &9&9&9&9&4 | BC-CCM-BTC |
ED | P | Error reading variant catalog for program &9&9&9&9&4 | BC-CCM-BTC |
ED | Q | > Start date type = 'After predecessor job', but job name is missing | BC-CCM-BTC |
ED | R | > Predecessor job name $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is invalid | BC-CCM-BTC |
ED | S | > Predecessor job name $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not unique | BC-CCM-BTC |
ED | T | > Start date/time is not complete | BC-CCM-BTC |
ED | U | > Start date type = 'Event' Event ID is not specified | BC-CCM-BTC |
ED | V | > Event ID $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is invalid | BC-CCM-BTC |
ED | W | > Start date/time is missing | BC-CCM-BTC |
ED | X | BP_START_DATE_EDITOR: invalid start date detected. Reason: | BC-CCM-BTC |
ED | Y | > Periodic start date without period dates | BC-CCM-BTC |
ED | Z | > Period values are not unique | BC-CCM-BTC |
EE | 0 | Reserved for computer center control station | BC-CCM-BTC |
EE | 1 | PFL_PROFILE_EDITOR: Internal processing error. Reason: | BC-CCM-BTC |
EE | 2 | >the following status transition is unknown: $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EE | 3 | > Parameter switching (&9&9&7) triggered | BC-CCM-BTC |
EE | 4 | > Switching of profile parameters (&9&9&9&3) failed | BC-CCM-BTC |
EE | 5 | > Parameter switching (&9&9&7) successfully executed | BC-CCM-BTC |
EE | 6 | > Value for roll area switching (&9&3) is too large | BC-CCM-BTC |
EE | A | OPERATION MODES: Switch to operation mode &A triggered | BC-CCM-BTC |
EF | 0 | > Invalid system log ID ($$$) found during start date check | BC-CCM-BTC |
EF | 1 | > Start date 'Start after previous job' is not possible with period | BC-CCM-BTC |
EF | 2 | BP_STEPLIST_EDITOR: Invalid step values (step $$$$) found. Reason: | BC-CCM-BTC |
EF | 3 | > Unknown system log ID ($$$) found during step value check | BC-CCM-BTC |
EF | 4 | > Invalid step type ($) | BC-CCM-BTC |
EF | 5 | > Invalid step status ($) | BC-CCM-BTC |
EF | 6 | > Program name is missing | BC-CCM-BTC |
EF | 7 | > User name is missing | BC-CCM-BTC |
EF | 8 | > User name $$$$$$$$$$$$ is invalid | BC-CCM-BTC |
EF | 9 | > Program name &9&9&9&9&4 is invalid | BC-CCM-BTC |
EF | A | > No variants have been defined for &9&9&9&9&4 | BC-CCM-BTC |
EF | B | > Program &9&9&9&9&4 cannot be scheduled as a background job | BC-CCM-BTC |
EF | C | > Program &9&9&9&9&4 has no variants, but a variant was specified | BC-CCM-BTC |
EF | D | > Check of variant $$$$$$$$$$$$$$ failed | BC-CCM-BTC |
EF | E | > No variant was specified for program &9&9&9&9&4 | BC-CCM-BTC |
EF | F | > Name of external program is missing | BC-CCM-BTC |
EF | G | > Name of target computer is missing | BC-CCM-BTC |
EF | H | > Function module was called with an invalid dialog mode ($) | BC-CCM-BTC |
EF | I | > Invalid step number ($$$$) was specified in the step list | BC-CCM-BTC |
EF | J | > Step no. $$$$ could not be read from the step list | BC-CCM-BTC |
EF | K | BP_CHECK_REPORT_VALUES: invalid report values detected. Reason: | BC-CCM-BTC |
EF | L | > Invalid CHECK_TYPE ($) | BC-CCM-BTC |
EF | M | > Unknown system log ID ($$$) during program and variant check | BC-CCM-BTC |
EF | N | BP_JOB_EDITOR: Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is invalid. Reason: | BC-CCM-BTC |
EF | O | > Job name is missing | BC-CCM-BTC |
EF | P | > Function module was called with an invalid operation code ($$$$) | BC-CCM-BTC |
EF | Q | > Unknown system log ID ($$$) in job value check | BC-CCM-BTC |
EF | R | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ cannot be edited due to its status | BC-CCM-BTC |
EF | S | > No steps were specified for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EF | T | > Step $$$$ contains illegal values | BC-CCM-BTC |
EF | U | > Invalid job status ($) | BC-CCM-BTC |
EF | V | > User $$$$$$$$$$$$ cannot be scheduled due to its type | BC-CCM-BTC |
EF | W | Cannot generate a job count for job &A | BC-CCM-BTC |
EF | X | > No event count can be generated for event $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EF | Y | > Job has no job class ($) | BC-CCM-BTC |
EF | Z | > Failed to read print parameters for user $$$$$$$$$$$$ | BC-CCM-BTC |
EG | 0 | > You are not authorized to schedule user $$$$$$$$$$$$ | BC-CCM-BTC |
EG | 1 | > User &A is not authorized to schedule program &B in the background | BC-CCM-BTC |
EG | 2 | > You are not authorized to release background jobs | BC-CCM-BTC |
EG | 3 | > Target computer check failed | BC-CCM-BTC |
EG | 4 | > No free work process on target computer $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EG | 5 | > All servers for background processing are in use | BC-CCM-BTC |
EG | 6 | > No background processing active on $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EG | 7 | BP_JOB_CREATE: Job cannot be generated. Reason: | BC-CCM-BTC |
EG | 8 | > Unknown system log ID ($$$) within BP_JOB_CREATE | BC-CCM-BTC |
EG | 9 | > Generation of new job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ failed | BC-CCM-BTC |
EG | A | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ contains invalid data | BC-CCM-BTC |
EG | B | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is already in table TBTCO | BC-CCM-BTC |
EG | C | Job &A/&B is locked by user &C | BC-CCM-BTC |
EG | D | > Error locking table &9&9&9&3 | BC-CCM-BTC |
EG | E | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not in table TBTCO | BC-CCM-BTC |
EG | F | > Previous job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not in TBTCO | BC-CCM-BTC |
EG | G | > Error at INSERT job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ in table TBTCO | BC-CCM-BTC |
EG | H | > Error at UPDATE job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ in table TBTCO | BC-CCM-BTC |
EG | I | > Error deleting job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ from table TBTCO | BC-CCM-BTC |
EG | J | > Error at step INSERT (Job &A/&B in table TBTCP) | BC-CCM-BTC |
EG | K | > Error at step UPDATE (job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ in table TBTCP) | BC-CCM-BTC |
EG | L | > Error at step DELETE (job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ in table TBTCP) | BC-CCM-BTC |
EG | M | > Error: INSERT background sched. table (job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CCM-BTC |
EG | N | > Error at UPDATE background sched. table ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CCM-BTC |
EG | O | > Error deleting background scheduler table ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CCM-BTC |
EG | P | > Error inserting event control table ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CCM-BTC |
EG | Q | > Error updating event control table ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CCM-BTC |
EG | R | > Error deleting event control table ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CCM-BTC |
EG | S | > Event $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is currently locked | BC-CCM-BTC |
EG | T | > Event for previous/subsequent job control is currently locked | BC-CCM-BTC |
EG | U | > User $$$$$$$$$$$$ cannot release jobs for background processing | BC-CCM-BTC |
EG | V | > Unknown job log message ($$$) for a 'simulated' job | BC-CCM-BTC |
EG | W | > Failed to start 'simulated job' $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EG | X | > Target host $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not defined in an op.type | BC-CCM-BTC |
EG | Y | > Error at event $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EG | Z | BP_JOB_MODIFY: Cannot modify job &A; reason: | BC-CCM-BTC |
EH | 0 | Reserved for CC control station | BC-CCM-BTC |
EH | 1 | Event handler: Event $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not defined | BC-CCM-BTC |
EH | 2 | Event handler: Error in event $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EH | 3 | Event handler: Scheduling for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ was deleted | BC-CCM-BTC |
EH | 4 | Event 'End of job' could not be triggered | BC-CCM-BTC |
EH | 5 | Event handler: Pseudo start of job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ failed | BC-CCM-BTC |
EH | 6 | Event handler: Status of job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ unknown | BC-CCM-BTC |
EH | 7 | Event 'Start SAP system' could not be triggered | BC-CCM-BTC |
EH | 8 | Failed to delete op.type switch for op.type $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EH | 9 | Failed to insert op.type switch for op.type $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EH | A | Failed to trigger op.type switch for op.type $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EH | B | Failed to delete scheduling of exception op.type $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EH | C | Unable to determine name of operation type | BC-CCM-BTC |
EH | D | Failed to switch to operation type $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EH | E | > Name of external command missing | BC-CCM-BTC |
EH | F | > Operating system not specified | BC-CCM-BTC |
EH | G | > External command unknown | BC-CCM-BTC |
EH | H | > Parameter of external command too long | BC-CCM-BTC |
EH | I | > External command contains security risks (characters or check routine) | BC-CCM-BTC |
EH | J | > User-defined check routine has wrong interface | BC-CCM-BTC |
EH | K | > Internal error occurred when checking the external command | BC-CCM-BTC |
EH | L | > Too many parameters for external command | BC-CCM-BTC |
EH | M | > Expected parameters for external command | BC-CCM-BTC |
EH | N | > External command not modified by specified transaction | BC-CCM-BTC |
EH | O | > Internal communication error when checking external command | BC-CCM-BTC |
EH | P | Failed to trigger an event: server &A unknown | BC-CCM-BTC |
EH | Q | Failed to trigger event &A: &B/&C | BC-CCM-BTC |
EH | R | Event History: Access to criteria manager failed. Error: &9&9&9&9&9&9&9 | BC-CCM-BTC |
EH | S | Event History: Error when writing to DB table BTCEVTHISTORY | BC-CCM-BTC |
EH | T | Could not lock the &A entry of job &B/&C | BC-CCM-BTC |
EH | U | Could not unlock the &A entry of job &B/&C | BC-CCM-BTC |
EH | V | All jobs locked by consistency check | BC-CCM-BTC |
EH | W | All jobs unlocked after consistency check | BC-CCM-BTC |
EI | 0 | > Last workday before non-workday $$$$$$$$$$ is in past | BC-CCM-BTC |
EI | 1 | > Unknown system log ID ($$$) in module BP_JOB_MODIFY | BC-CCM-BTC |
EI | 2 | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ cannot be modified | BC-CCM-BTC |
EI | 3 | > No steps are available in the DB for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | 4 | > Unknown error reading job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | 5 | > No change authorization for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | 6 | > New ID for job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not compatible | BC-CCM-BTC |
EI | 7 | BP_JOB_COPY: Job copy failed. Reason: | BC-CCM-BTC |
EI | 8 | BP_JOB_MAINTENANCE: Job control/monitoring failed. Reason: | BC-CCM-BTC |
EI | 9 | > Unknown error at job selectin (BP_JOB_SELECT) | BC-CCM-BTC |
EI | A | > Job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ cannot be released without start date | BC-CCM-BTC |
EI | B | BP_JOBLOG_SHOW: Failed to display jobs. Reason: | BC-CCM-BTC |
EI | C | > Job count is missing | BC-CCM-BTC |
EI | D | > Error reading job log $$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | E | BP_JOBLIST_PROCESSOR: Failed to edit job list. Reason: | BC-CCM-BTC |
EI | F | > Definition of job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ is not complete | BC-CCM-BTC |
EI | G | BP_JOB_SELECT: Job selection from database failed. Reason: | BC-CCM-BTC |
EI | H | > Unknown system log ID ($$$) in function module BP_JOB_SELECT | BC-CCM-BTC |
EI | I | > No authorization to copy job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | J | OMS_OMSET_EDITOR has found invalid operation type set data. Reason: | BC-CCM-BTC |
EI | K | > Unknown system log ID ($$$) | BC-CCM-BTC |
EI | L | > Function module was called with an invalid mode parameter ($) | BC-CCM-BTC |
EI | M | BP_JOB_ABORT: Failed to cancel job. Reason: | BC-CCM-BTC |
EI | N | > No authorization to cancel job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | O | > Active check of job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ failed | BC-CCM-BTC |
EI | P | > Failed to cancel job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | Q | BP_JOB_CHECKSTAT: Failed to correct status of job. Reason: | BC-CCM-BTC |
EI | R | > No authorization to correct job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | S | > Failed to check job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EI | T | > Operation mode $$$$$$$$$$$$$$$$$$$$ is invalid | BC-CCM-BTC |
EI | U | > Failed to determine default calendar ID | BC-CCM-BTC |
EI | V | > Computer $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ only processes class A jobs | BC-CCM-BTC |
EI | W | > Date $$$$$$$$$$ is not in the range defined for the factory calendar | BC-CCM-BTC |
EI | X | > Factory calendar $$ is not defined | BC-CCM-BTC |
EI | Y | > Unknown error in factory calendar check ( ID = $$ ) | BC-CCM-BTC |
EI | Z | > Date $$$$$$$$$$ is a public holiday. Job cannot be executed. | BC-CCM-BTC |
EJ | 0 | Reserved for background processing | BC-CCM-BTC |
EJ | 1 | > Invalid start date restriction ( $ ) | BC-CCM-BTC |
EJ | 2 | > User $$$$$$$$$$$$ is not authorized to schedule jobs | BC-CCM-BTC |
EJ | 3 | > Period values < 1 week with restriction 'Bring forward' is not allowed | BC-CCM-BTC |
EJ | 4 | BP_JOB_MOVE: Error moving job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EJ | 5 | > No authorization to move job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EJ | 6 | > Target host is not specified to move job $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EJ | 7 | > Installed system languages could not be determined | BC-CCM-BTC |
EJ | 8 | > The language with the key $ is not installed | BC-CCM-BTC |
EJ | 9 | > invalid value for a work-day number: $$ | BC-CCM-BTC |
EJ | A | > invalid count direction for the start date type 'on work-day' | BC-CCM-BTC |
EJ | B | > Work-day not specified | BC-CCM-BTC |
EJ | C | > earliest start date for start date 'on work-day' missing | BC-CCM-BTC |
EJ | D | BP_CHECK_STARTDATE: Incorrect start date found. Reason: | BC-CCM-BTC |
EJ | E | > Cannot determine print parameters for report $$$$$$$$ | BC-CCM-BTC |
EJ | F | Could not find or load print parameters for step &C, job &A/&B | BC-CCM-BTC |
EJ | G | Print parameters for step &C, job &A/&B repaired | BC-CCM-BTC |
EJ | H | Status of job &A, number &B corrected (&C -> &D) | BC-CCM-BTC |
EJ | I | Error &A when reading the factory calendar &B (Job &C) | BC-CCM-BTC |
EJ | K | < Job Count $$$$$$$$ | BC-CCM-BTC |
EK | 0 | Reserved for background processing | BC-CCM-BTC |
EK | 1 | Error found in PBT environment, FM = $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EK | 2 | > Environment for parallel background tasks was already initialized | BC-CCM-BTC |
EK | 3 | > Invalid PBT server group name: $$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EK | 4 | > Failed to determine server information | BC-CCM-BTC |
EK | 5 | > Failure checking whether server is active/inactive | BC-CCM-BTC |
EK | 6 | Environment for parallel background tasks not yet initialized | BC-CCM-BTC |
EK | 7 | Failed to read resource table (index = $$$$$) | BC-CCM-BTC |
EK | 8 | > Invalid server name: $$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EK | 9 | > Invalid values: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EK | A | Internal error in XMI API | BC-CCM-BTC |
EK | B | Failed to save XMI log entry in database ( &9&9&9&3 ) | BC-CCM-BTC |
EK | C | Inconsistency detected in tables &A and &B | BC-CCM-BTC |
EK | D | > Job: &A &B | BC-CCM-BTC |
EK | F | > Cannot determine information on server &9&9&2 | BC-CCM-BTC |
EK | G | > Failed to read spool request &9&1 | BC-CCM-BTC |
EK | H | Cannot read overview of all servers (message server problem?) (XMB) | BC-CCM-BTC |
EK | I | 'List of work processes' external query could not be answered (XMB) | BC-CCM-BTC |
EK | J | 'Reset alert' external query could not be executed (XMB) | BC-CCM-BTC |
EK | K | Copying spool list recipient for job &A failed | BC-CCM-BTC |
EK | L | Bckgrnd def.srvr grp SAP_DEFAULT_BTC does not contain any active bckgrnd srvrs | BC-CCM-BTC |
EK | M | Background default server group SAP_DEFAULT_BTC also contains inactive servers | BC-CCM-BTC |
EK | N | BP_SOLMAN_JOBDEFINITON: Return Code $$$ | BC-CCM-BTC |
EM | 0 | > Predecessor job &A does not exist in status "planned" or "released" | BC-CCM-BTC |
EM | E | $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CCM-BTC |
EM | F | Logon of Jobstep User Failed | BC-CCM-BTC |
F0 | 0 | DB table $$$$$$$$$$ generated | BC-CCM-PRN |
F0 | 1 | $$$$$ system installed | BC-CCM-PRN |
F0 | 2 | DB table $$$$$$$$$$ could not be generated | BC-CCM-PRN |
F0 | 3 | $$$$$ system installed incorrectly | BC-CCM-PRN |
F0 | 4 | DB table $$$$$$$$$$ deleted | BC-CCM-PRN |
F0 | 5 | DB table $$$$$$$$$$ could not be deleted | BC-CCM-PRN |
F0 | 6 | $$$$$ system was deinstalled | BC-CCM-PRN |
F0 | 7 | Unknown status of $$$$$ system | BC-CCM-PRN |
F0 | 8 | $$$$$ system was already installed | BC-CCM-PRN |
F0 | 9 | $$$$$ system validated | BC-CCM-PRN |
F1 | 0 | $$$$$ system Validation Failed | BC-CCM-PRN |
F1 | 1 | $$$$$ system Is Not Installed | BC-CCM-PRN |
F1 | 2 | DB Table &9&7 Not Found | BC-CCM-PRN |
F1 | 3 | Invalid Data in Table &9&7, Line &9&9&5 | BC-CCM-PRN |
F1 | 4 | Table &A Does Not Have Enough Fields: &B | BC-CCM-PRN |
F1 | A | SAPPARAM(rsts/ccc/&A) = &B Is Small | BC-CCM-PRN |
F1 | B | INITIALIZATION COMPLETE | BC-CCM-PRN |
F2 | 0 | Calling program reports invalid handle for TemSe object (magic==X'&8') | BC-CCM-PRN |
F2 | 1 | Empty TemSe object handle | BC-CCM-PRN |
F2 | 2 | Field &5&5 in table &5 has an illegal value | BC-CCM-PRN |
F2 | 3 | Field &5&5 in table &5 is outside the permitted range | BC-CCM-PRN |
F2 | 4 | SAPPARAM(rsts/ccc/cache size) = &9 too small | BC-CCM-PRN |
F2 | 5 | TemSe object "&a" not found | BC-CCM-PRN |
F2 | 6 | Tried to ignore a rollback | BC-CCM-PRN |
F2 | 7 | Table TCP00 contains no character set | BC-CCM-PRN |
F2 | 8 | Character set converter cannot get semaphore (SemRq->&5) | BC-CCM-PRN |
F2 | 9 | Character set converter cannot release semaphore (SemRel->&5) | BC-CCM-PRN |
F2 | A | Invalid object kind | BC-CCM-PRN |
F2 | B | Invalid object cache permission | BC-CCM-PRN |
F2 | C | Illegal object status | BC-CCM-PRN |
F2 | D | Illegal append rule | BC-CCM-PRN |
F2 | E | Illegal delete rule | BC-CCM-PRN |
F2 | F | Illegal read rule | BC-CCM-PRN |
F2 | G | An illegal storage type was specified | BC-CCM-PRN |
F2 | H | Line length mismatch | BC-CCM-PRN |
F2 | I | Unable to convert type "&8&4" to "&8&4" | BC-CCM-PRN |
F2 | J | Unable to convert record format "&7" to "&7" | BC-CCM-PRN |
F2 | K | Unable to convert character set "&4" to "&4" | BC-CCM-PRN |
F2 | L | Data was already deleted | BC-CCM-PRN |
F2 | M | TemSe object "&8&8&4" is being processed | BC-CCM-PRN |
F2 | N | Invalid part number for TemSe object "&8&8&4" | BC-CCM-PRN |
F2 | P | Invalid parameter combination for TemSe object "&8&8&4" | BC-CCM-PRN |
F2 | Q | Attribute mismatch for TemSe object "&8&8&4" | BC-CCM-PRN |
F2 | R | Cannot delete parts of TemSe objects | BC-CCM-PRN |
F2 | S | Cannot change name | BC-CCM-PRN |
F2 | T | Cannot change part numbers | BC-CCM-PRN |
F2 | U | Cannot change client | BC-CCM-PRN |
F2 | V | Cannot change TemSe object type | BC-CCM-PRN |
F2 | W | Cannot change TemSe object kind | BC-CCM-PRN |
F2 | X | Cannot change TemSe object language | BC-CCM-PRN |
F2 | Y | Cannot change creation date/time | BC-CCM-PRN |
F2 | Z | Cannot change remaining lifetime | BC-CCM-PRN |
F3 | 0 | Char code converter cannot detach shared buffer (ShmDelete->$$$$$) | BC-CCM-PRN |
F3 | 1 | Char code converter cannot init semaphore mngt (SemInMgt->$$$$$) | BC-CCM-PRN |
F3 | 2 | Cannot create char code convert cache (ShmCreate->$$$$$) | BC-CCM-PRN |
F3 | 3 | Cannot attach char code convert cache (ShmCreate->$$$$$) | BC-CCM-PRN |
F3 | 4 | Char code convert cache not proper initialized | BC-CCM-PRN |
F3 | 5 | Char code convert table inconsistent | BC-CCM-PRN |
F3 | 6 | Char code converter damaged | BC-CCM-PRN |
F3 | 7 | Char code convert cache version should be $$$$$$$$$, but is $$$$$$$$$ | BC-CCM-PRN |
F3 | 8 | Missing char code parameter | BC-CCM-PRN |
F3 | 9 | Char code convert buffer overflow | BC-CCM-PRN |
F3 | A | Cannot change cache permission | BC-CCM-PRN |
F3 | B | Cannot change object state | BC-CCM-PRN |
F3 | C | Cannot change creator name | BC-CCM-PRN |
F3 | D | Cannot change CPU type | BC-CCM-PRN |
F3 | E | Cannot change TemSe attribute "Creation tool" | BC-CCM-PRN |
F3 | F | Cannot change size | BC-CCM-PRN |
F3 | G | Cannot change release number | BC-CCM-PRN |
F3 | H | Cannot change record format | BC-CCM-PRN |
F3 | I | Cannot change character code | BC-CCM-PRN |
F3 | J | May not change line length | BC-CCM-PRN |
F3 | K | May not change page length | BC-CCM-PRN |
F3 | L | Cannot change number of parts | BC-CCM-PRN |
F3 | M | Cannot change storage type | BC-CCM-PRN |
F3 | N | Cannot change storage location | BC-CCM-PRN |
F3 | O | 2 GB limit for TemSe object reached | BC-CCM-PRN |
F3 | P | Cannot change number of data base rows | BC-CCM-PRN |
F3 | Q | Cannot change begin point of object | BC-CCM-PRN |
F3 | R | Writers may not set position | BC-CCM-PRN |
F3 | S | May not position before begin | BC-CCM-PRN |
F3 | T | Invalid object name for TemSe object: "&8&8&4" | BC-CCM-PRN |
F3 | U | Database I/O error | BC-CCM-PRN |
F3 | V | Error &>E5 for write/read access to a file. File = &a&b&c&d&e&f | BC-CCM-PRN |
F3 | W | Unsupported media | BC-CCM-PRN |
F3 | X | No more data in this part of the TemSe object | BC-CCM-PRN |
F3 | Y | No read authorization for TemSe object "&8&8&4" | BC-CCM-PRN |
F3 | Z | No append authorization for TemSe object "&8&8&4" | BC-CCM-PRN |
F4 | 0 | Character is not convertible | BC-CCM-PRN |
F4 | 1 | In character set &4, SAP character &5 is not defined | BC-CCM-PRN |
F4 | 2 | Character presentation is larger than the output buffer | BC-CCM-PRN |
F4 | 3 | Character set &4 is unknown | BC-CCM-PRN |
F4 | 4 | The character set translation buffer (CCC) has an illegal status | BC-CCM-PRN |
F4 | 5 | Compression mode mismatch | BC-CCM-PRN |
F4 | 6 | 7-ASCII escapes or non-printables not acceptable here | BC-CCM-PRN |
F4 | 7 | 7-ASCII nation mismatch | BC-CCM-PRN |
F4 | 8 | "$$$$$$" to "$$$$$$" incompatible char code | BC-CCM-PRN |
F4 | 9 | "$$$$$$$" to "$$$$$$$" incompatible record format | BC-CCM-PRN |
F4 | A | No delete authorization TemSe object "&8&8&4" | BC-CCM-PRN |
F4 | B | Not enough $$$$$ memory for $$$$$ block | BC-CCM-PRN |
F4 | C | Procedure &1&9&2&8&3&7&4&6&5&5 Is Not Implemented | BC-CCM-PRN |
F4 | D | Fixed record size disallows substitution strings | BC-CCM-PRN |
F4 | E | Internal case selection confused | BC-CCM-PRN |
F4 | F | Illegal switch between line strategies | BC-CCM-PRN |
F4 | G | Record format "$$$$$$$" unknown | BC-CCM-PRN |
F4 | H | Partial line at EOD | BC-CCM-PRN |
F4 | I | Partial line header at EOD | BC-CCM-PRN |
F4 | J | Column0 with illegal char code | BC-CCM-PRN |
F4 | K | Wrong line length | BC-CCM-PRN |
F4 | L | Record not terminated | BC-CCM-PRN |
F4 | M | Record type has no lines | BC-CCM-PRN |
F4 | N | No space for byte of column0 | BC-CCM-PRN |
F4 | P | You are not a reader | BC-CCM-PRN |
F4 | Q | 1st stop byte, but no 2nd | BC-CCM-PRN |
F4 | S | Illegal state transition | BC-CCM-PRN |
F4 | T | Rule longer than rule buffer | BC-CCM-PRN |
F4 | U | Type unknown | BC-CCM-PRN |
F4 | V | Buffers freed during usage | BC-CCM-PRN |
F4 | W | Fetch with cursor error $$$$$ | BC-CCM-PRN |
F4 | X | Close cursor error $$$$$ | BC-CCM-PRN |
F4 | Y | DB_RSQL error &5 at table &5 | BC-CCM-PRN |
F4 | Z | Cannot prepare select for table $$$$$ | BC-CCM-PRN |
F5 | 0 | Type conversion from &8&4 to &8&4 is not possible | BC-CCM-PRN |
F5 | 1 | '0x1c' escape is not permitted here | BC-CCM-PRN |
F5 | 2 | No multiple client access | BC-CCM-PRN |
F5 | 3 | No match in the TemSe directory | BC-CCM-PRN |
F5 | 4 | Invalid handle for TemSe search | BC-CCM-PRN |
F5 | 5 | End of TemSe is already reached | BC-CCM-PRN |
F5 | 6 | No further objects in TemSe | BC-CCM-PRN |
F5 | 7 | Read buffer is too small | BC-CCM-PRN |
F5 | 8 | This TemSe object is not open for read | BC-CCM-PRN |
F5 | 9 | This TemSe object is not open for write | BC-CCM-PRN |
F5 | A | Database error &5 at RT_UPDATE for table &5 | BC-CCM-PRN |
F5 | B | Database error &5 at RT_SETB for table &5 | BC-CCM-PRN |
F5 | C | Database error &5 at RT_GET for table &5 | BC-CCM-PRN |
F5 | D | Database error: TemSe->RSQL(FETCH)->&5 | BC-CCM-PRN |
F5 | E | Database error &5 at RT_INSERT for table &5 | BC-CCM-PRN |
F5 | F | Database error &5 at RT_DELETE for table &5 | BC-CCM-PRN |
F5 | G | TemSe software is not compatible with DD: &8&8&4 | BC-CCM-PRN |
F5 | H | Illegal line length: &5&5 | BC-CCM-PRN |
F5 | I | Character set converter cannot initialize semaphore (SemInit->&5) | BC-CCM-PRN |
F5 | J | SAPPARAM(rsts/ccc/max_sapcode): Value is too small | BC-CCM-PRN |
F5 | K | CCC: Ambiguous byte coding for several characters | BC-CCM-PRN |
F5 | L | CCC: Ambiguous byte coding for several characters | BC-CCM-PRN |
F5 | M | Character set conversion buffer was not fully initialized | BC-CCM-PRN |
F5 | N | CCC: Buffer version changed from &9 to &9 | BC-CCM-PRN |
F5 | O | Unable to connect to database | BC-CCM-PRN |
F5 | P | Illegal TemSe processing mode | BC-CCM-PRN |
F5 | Q | TemSe callback: Invalid reason &8 or object &8 | BC-CCM-PRN |
F5 | R | Too many TemSe objects open per external mode | BC-CCM-PRN |
F5 | S | Double usage of buffer is not possible | BC-CCM-PRN |
F5 | T | This buffer cannot be released yet | BC-CCM-PRN |
F5 | U | Missing SAPPARAM parameter: &8&8&2 | BC-CCM-PRN |
F5 | V | Missing SAPPARAM parameter: &8&8&2 | BC-CCM-PRN |
F5 | W | Incorrect length in a SAPPARAM parameter rsts/file... | BC-CCM-PRN |
F5 | X | Incorrect length in a SAPPARAM parameter rsts/file name | BC-CCM-PRN |
F5 | Y | Incorrect characters in a SAPPARAM parameter rsts/file... | BC-CCM-PRN |
F5 | Z | TemSe callback: Invalid reason &8 for object &8 | BC-CCM-PRN |
F6 | 0 | TemSe object file name is too long | BC-CCM-PRN |
F6 | 1 | TemSe input/output to unopened file | BC-CCM-PRN |
F6 | 2 | Positioning error in a file for a TemSe object | BC-CCM-PRN |
F6 | 3 | Unable to access I/O buffer for TemSe object file | BC-CCM-PRN |
F6 | 4 | Cannot close the file of a TemSe object (error no &>E5) | BC-CCM-PRN |
F6 | 5 | No further data in TemSe object file | BC-CCM-PRN |
F6 | 6 | Path name does not contain a directory | BC-CCM-PRN |
F6 | 7 | Directory &a&b&c&d&e was created | BC-CCM-PRN |
F6 | 8 | Missing directory for path &a&b&c&d&e | BC-CCM-PRN |
F6 | 9 | Unable to create directory &a&b&c&d&e. Error no. &5 | BC-CCM-PRN |
F6 | A | Unable to find root for directory &a&b&c&d&e | BC-CCM-PRN |
F6 | B | File name is longer than &5 and does not fit in the data base table | BC-CCM-PRN |
F6 | C | Error deleting a TemSe object file. &a&b&c&d&e, error &5 | BC-CCM-PRN |
F6 | D | Objects stored in the data base cannot be rolled out after ROLLBACK | BC-CCM-PRN |
F6 | E | Error synchronizing file &a&b&c&d&e. Error &5 | BC-CCM-PRN |
F6 | F | TemSe object &8&8&4 was closed remotely | BC-CCM-PRN |
F6 | G | TemSe object file missing in delete operation. &a&b&c&d&e, error &5 | BC-CCM-PRN |
F6 | H | Database error: TemSe->&A(&B)->&C for table &D key &a | BC-CCM-PRN |
F6 | I | TemSe object '&8&8&4': Rollback is not allowed for public data | BC-CCM-PRN |
F6 | J | TemSe object '&8&8&4' for public file cannot contain a wildcard | BC-CCM-PRN |
F6 | K | TemSe object '&8&8&4' already exists | BC-CCM-PRN |
F6 | L | Character set '&4' can not be converted to '&4'. (NLS problem) | BC-CCM-PRN |
F6 | M | TemSe error repair: &8&8&5 (Module &8, location &3) | BC-CCM-PRN |
F6 | N | Repost table TST01 (TemSe->&B(&C)->&D; Flag: &A; Key &a) | BC-CCM-PRN |
F6 | O | No authorization for program &8 for operating system user &8&5. | BC-CCM-PRN |
F6 | P | Recursion while initializing the character set convertor (CCC) | BC-CCM-PRN |
F6 | Q | Can not read NameTab for &9&7 (rc=&5) | BC-CCM-PRN |
F6 | R | Table &9&7 has unknown buffering type "&1" | BC-CCM-PRN |
F6 | S | &1 error "&9&5&5" in TemSe software | BC-CCM-PRN |
F6 | T | Line not found in TemSe table &A | BC-CCM-PRN |
F6 | U | Line already exists or duplicated in TemSe table &A | BC-CCM-PRN |
F6 | V | Invalid address (NULL) specified | BC-CCM-PRN |
F7 | 0 | Spool: Attempt to Continue Processing After ROLLBACK was Rejected | BC-CCM-PRN |
F7 | 1 | Error in TemSe Management | BC-CCM-PRN |
F7 | 2 | No Authorization to Create | BC-CCM-PRN |
F7 | 3 | No Authorization to Delete | BC-CCM-PRN |
F7 | 4 | No Authorization | BC-CCM-PRN |
F7 | 5 | No Authorization to Change | BC-CCM-PRN |
F7 | 6 | Spool: Invalid Spool Request Name | BC-CCM-PRN |
F7 | 7 | Spool: Invalid Output Device | BC-CCM-PRN |
F7 | 8 | Spool: Invalid Disposition 1 | BC-CCM-PRN |
F7 | 9 | Spool: Invalid Disposition 2 | BC-CCM-PRN |
F7 | A | Spool: Invalid Disposition 3 | BC-CCM-PRN |
F7 | B | Spool: Invalid Owner | BC-CCM-PRN |
F7 | C | Spool: Invalid Spool Request Name (Suffix1) | BC-CCM-PRN |
F7 | D | Spool: Invalid Spool Request Name (Suffix2) | BC-CCM-PRN |
F7 | E | Spool: Invalid Create Authorization Protection | BC-CCM-PRN |
F7 | F | Spool: Invalid Delete Authorization Protection | BC-CCM-PRN |
F7 | G | Spool: Invalid Change Authorization Protection | BC-CCM-PRN |
F7 | H | Spool: Invalid Read Authorization Protection | BC-CCM-PRN |
F7 | I | Spool: RT_UPDATE Reports Error &5 for Table &9&9&7 | BC-CCM-PRN |
F7 | J | &1 &2 is Already Locked | BC-CCM-PRN |
F7 | K | Spool: RT_READ_FOR_UPDATE Reports Error &5 for Table &9&9&7 | BC-CCM-PRN |
F7 | L | Spool: RT_READ_... Reports Error &5 for Table &9&9&7 | BC-CCM-PRN |
F7 | M | Spool: RT_INSERT Reports Error &5 for Table &9&9&7 | BC-CCM-PRN |
F7 | N | Spool: RT_DELETE Reports Error &5 for Table &9&9&7 | BC-CCM-PRN |
F7 | O | Invalid Enqueue Arguments &1 &2 | BC-CCM-PRN |
F7 | P | Output Request Not Found in Output Request List | BC-CCM-PRN |
F7 | Q | Spool: Output Device Not Found | BC-CCM-PRN |
F7 | R | Spool: Multiple-Client Search is Not Permitted | BC-CCM-PRN |
F7 | S | Spool: Database Read Error: Get &5 | BC-CCM-PRN |
F7 | T | Spool: Database Read Error: Close Cursor &5 | BC-CCM-PRN |
F7 | U | Spool: Database Access Error: db_rsql &5 for Table &9&9&7 | BC-CCM-PRN |
F7 | V | Spool: Before Database Access: Prepare Select for Table &9&7 | BC-CCM-PRN |
F7 | W | End of Data in Directory of Spool Requests | BC-CCM-PRN |
F7 | X | End of Data in Directory of Output Requests | BC-CCM-PRN |
F7 | Y | Spool: Database is Inconsistent | BC-CCM-PRN |
F7 | Z | Invalid Handle for Reading Spool Catalog | BC-CCM-PRN |
F8 | 0 | Directory Scan Already at End | BC-CCM-PRN |
F8 | 1 | No Further Request(s) | BC-CCM-PRN |
F8 | 2 | Invalid Writer Count | BC-CCM-PRN |
F8 | 3 | BC-CCM-PRN | |
F8 | 4 | Spool request was not found | BC-CCM-PRN |
F8 | 5 | Special Character &5 Missing From Character Set &4 | BC-CCM-PRN |
F8 | 6 | No Normal Line Indicator Definition | BC-CCM-PRN |
F8 | 7 | No Page Break Definition | BC-CCM-PRN |
F8 | 8 | No Print Control Indicator Definition | BC-CCM-PRN |
F8 | 9 | End of Data in Directory of Printers | BC-CCM-PRN |
F8 | A | Get Next Print Job: Database Problem | BC-CCM-PRN |
F8 | B | Destination Already Installed | BC-CCM-PRN |
F8 | C | Procedure $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ Not Yet Implemented | BC-CCM-PRN |
F8 | D | No Spool Request to be Deleted | BC-CCM-PRN |
F8 | E | Spool Request is Currently Being Accessed | BC-CCM-PRN |
F8 | F | Spool request was not found | BC-CCM-PRN |
F8 | G | Print request was not found | BC-CCM-PRN |
F8 | H | Output Device &4 Not Found | BC-CCM-PRN |
F8 | I | BC-CCM-PRN | |
F8 | J | Indirect printer name was not found | BC-CCM-PRN |
F8 | K | Spool Request Attribute Block Missing | BC-CCM-PRN |
F8 | L | Cannot Connect to Printer | BC-CCM-PRN |
F8 | M | Cannot Send Data to Printer | BC-CCM-PRN |
F8 | N | Cannot Close Connection to Printer | BC-CCM-PRN |
F8 | P | Cannot Create Spool File. Error &A, File Name &B | BC-CCM-PRN |
F8 | Q | Cannot Spool Data to Host Spool | BC-CCM-PRN |
F8 | R | Cannot Query Host Spool | BC-CCM-PRN |
F8 | S | Error Accessing Spool Request | BC-CCM-PRN |
F8 | T | RSPO Versus DD Mismatch: $$$$$$$$$$$$$$$$$$$$$ | BC-CCM-PRN |
F8 | U | Unable to Log On to Database | BC-CCM-PRN |
F8 | V | Unable to Send Data to Printer (Disk Full?) | BC-CCM-PRN |
F8 | W | Unable to Log Off Database | BC-CCM-PRN |
F8 | X | Commit to Database Failed | BC-CCM-PRN |
F8 | Y | Bad TSP0A entry for printer or printer type | BC-CCM-PRN |
F8 | Z | Printer Type Not Found | BC-CCM-PRN |
F9 | 0 | Sequence Error in RSPO-ABAP Interface | BC-CCM-PRN |
F9 | 1 | There is no Format &8&8 for Printer Type &8 | BC-CCM-PRN |
F9 | 2 | Spool: "Do Not Process EOL" Indicator Missing from First Column | BC-CCM-PRN |
F9 | 3 | Error Writing Error Log $$$$$$, Spool ID = $$$$$ | BC-CCM-PRN |
F9 | 4 | Character Set &4, Character &5 is Very Long | BC-CCM-PRN |
FA | 0 | Computer $$$$$$$$: No Printer can be Used | BC-CCM-PRN |
FA | 1 | Computer $$$$$$$$: No Printer is Defined | BC-CCM-PRN |
FA | 2 | Failed to Create Socket. Error &>EA | BC-CCM-PRN |
FA | 3 | Operating System Call "bind(2)" Failed. Error &A, Port &B | BC-CCM-PRN |
FA | 4 | Are All Socket Ports from &A to &B occupied? | BC-CCM-PRN |
FA | 5 | Computer Name for Connection is Missing | BC-CCM-PRN |
FA | 6 | Computer &A is Unknown | BC-CCM-PRN |
FA | 7 | Service Printer/tcp is Unknown | BC-CCM-PRN |
FA | 8 | Connect(2) Failed. Error &A, Rport &B, Lport &C, Computer Name &D | BC-CCM-PRN |
FA | 9 | Unable to Establish Connection to SAPLPD or lpd | BC-CCM-PRN |
FA | A | Connection Closed by Remote SAPLPD/lpd | BC-CCM-PRN |
FA | B | Unable to Send Data to SAPLPD/lpd. Error &C, Target &A, Sent &B | BC-CCM-PRN |
FA | C | Connection to SAPLPD/lpd Broken. Error &A | BC-CCM-PRN |
FA | D | Connection Closed by SAPLPD/lpd. Code &A | BC-CCM-PRN |
FA | E | SAPLPD/lpd was Unable to Print. Code &A | BC-CCM-PRN |
FA | F | Invalid Print Destination: $$$$ | BC-CCM-PRN |
FA | G | Access Method &A to Printer &B is Not Supported for This Platform | BC-CCM-PRN |
FA | H | Error Writing to Microfiche File. Error &A | BC-CCM-PRN |
FA | I | Insufficient Main Memory | BC-CCM-PRN |
FA | J | Internal Error in Spool Work Process | BC-CCM-PRN |
FA | K | Error Creating Archive File &A. Error &B | BC-CCM-PRN |
FA | L | Extension Record for Archiving is Missing. Spool ID &A | BC-CCM-PRN |
FA | M | Error Opening Archive Queue &B (Eerror &A) | BC-CCM-PRN |
FA | N | Error Writing to Archive Queue &B. Error &A | BC-CCM-PRN |
FA | O | Error Closing Archive Queue &B. Error &A | BC-CCM-PRN |
FA | P | ***** Spool Inconsistency: Field &A Does Not Match Field &B ***** | BC-CCM-PRN |
FA | Q | Computer &A Cannot be Accessed | BC-CCM-PRN |
FA | S | Connection to SAPLPD Broken | BC-CCM-PRN |
FA | T | Error at 'Select'. Error &A | BC-CCM-PRN |
FA | U | Connection to SAPLPD Broken | BC-CCM-PRN |
FA | V | Archive ID was Not Found | BC-CCM-PRN |
FA | W | Format Error in Database Interface Found (&A) | BC-CCM-PRN |
FA | X | Dummy Function Called | BC-CCM-PRN |
FA | Y | Overflow in Internal Spool Data Structure &A | BC-CCM-PRN |
FA | Z | Error Writing to File &B, Error &>EA | BC-CCM-PRN |
FB | 0 | Spool: Shared Memory is Partly Initialized | BC-CCM-PRN |
FB | 1 | Spool: Init Cannot Initialize Semaphore Management: &A | BC-CCM-PRN |
FB | 2 | Spool: Cannot Initialize Semaphore: &A | BC-CCM-PRN |
FB | 3 | Spool: Error Waiting for Semaphore: &A | BC-CCM-PRN |
FB | 4 | Printer List is Set Too Small: &A (&B Min.) | BC-CCM-PRN |
FB | 5 | Spool: Request List is Too Small: &A (&B Min.) | BC-CCM-PRN |
FB | 6 | Cannot Create Shared Memory: Key &A, Size &B, Error &C | BC-CCM-PRN |
FB | 7 | Error Deleting Uninitialized Shared Memory, Key &A, Error &B | BC-CCM-PRN |
FB | 8 | Error Releasing From Uninitialized Shared Memory, Key &A. | BC-CCM-PRN |
FB | 9 | Semaphore Cannot be Released, Error &A | BC-CCM-PRN |
FB | A | Version of Shared Memory is Incorrect (Spool Administration) | BC-CCM-PRN |
FB | B | Spool Component is Not Ready | BC-CCM-PRN |
FB | C | Cannot Create Temporary Printer Entry, Name=&A | BC-CCM-PRN |
FB | D | Failed to Send to LPD on &D, rc=&C, &B of &A Bytes Sent | BC-CCM-PRN |
FB | E | Connection to SAPLPD or LPD Broken; Computer &A. | BC-CCM-PRN |
FB | F | Failed to Receive SAPLPD or LPD on &B; RC = &A. | BC-CCM-PRN |
FB | G | Internal Printer List Inconsistent | BC-CCM-PRN |
FB | H | Compressor CsCompr Reported Error, RC=&A, LEN=&B, Read=&C | BC-CCM-PRN |
FB | I | Internal Error in Spool, Code &A, Arg1=&B, Arg2=&C, Arg3=&D | BC-CCM-PRN |
FB | J | DB_RTAB_ERROR at Table &A, Error &B | BC-CCM-PRN |
FB | K | Parameter Validation Failed, Text=&A | BC-CCM-PRN |
FB | L | Print Request Query at Printer &A is Too Slow (&B Seconds) | BC-CCM-PRN |
FB | M | Printer &A Temporarily Locked Due to Connection Problem | BC-CCM-PRN |
FB | N | Spool is Full | BC-CCM-PRN |
FB | O | No Spool Request Number Obtained from Number Range Administrator. Code &A | BC-CCM-PRN |
FB | P | Network Error Transmitting Saved Data. NI Error &A | BC-CCM-PRN |
FB | Q | Error Transmitting Saved Data. SNC Error Code &A | BC-CCM-PRN |
FB | R | Initializing Saved Connection Failed RC= &A | BC-CCM-PRN |
FB | S | Profile Value "&A" is Not Allowed for "RSPO/STORE_LOCATION" | BC-CCM-PRN |
FB | T | Error Determining Own Identity, RC=&A, Time = &B | BC-CCM-PRN |
FB | U | Internal Job Queue Full for Synchronous Processing of Print Requests | BC-CCM-PRN |
FB | V | Error Message from Spool Error History | BC-CCM-PRN |
FC | 0 | Overflow loading the calendar buffer. Enlarge ZCSA/calendar_area. | BC-ABA |
FC | 1 | Temporary memory request for factory calendar failed | BC-ABA |
FC | 2 | Read error for factory or public holiday calendar | BC-ABA |
FC | A | Calender buffer shared memory (Key: 11) not available | BC-ABA |
FC | B | Semaphore request and release error (Semaphore: &5&5) | BC-ABA |
FC | C | Inconsistency found in calender buffer, buffer &5&5 reset | BC-ABA |
FC | D | Corrupt buffer entries found in calender buffer in function &5&5 | BC-ABA |
FC | E | Shared memory for calender buffer administration too small | BC-ABA |
FC | F | Directory overflow in calendar buffer CALE (Mode: &5&5 &5&5) | BC-ABA |
FC | G | Data buffer overflow in calender buffer CALE (Mode: &5&5 &5&5) | BC-ABA |
FC | H | Table &5&5 with inconsistent nametab | BC-ABA |
FC | I | Calender too big for calender buffer (calender: &3) | BC-ABA |
FC | J | Internal buffer too small for calender &3 | BC-ABA |
FC | K | Calender buffer &5&5 was reset (Mode: &5) | BC-ABA |
FC | L | Invalid year &5&5 found in table &5&5 | BC-ABA |
FD | 0 | Definition of Output Device &A Does Not Contain the External Device OMS Name | BC-CCM-PRN |
FD | 1 | Invalid Real Output Management System Selected (&A) | BC-CCM-PRN |
FD | 2 | Invalid Logical Output Management System Selected (&A) | BC-CCM-PRN |
FD | 3 | Operating System Recognition is Not Activated in the Work Process | BC-CCM-PRN |
FD | 4 | No Command Defined for Command &B of the Logical OMS &A | BC-CCM-PRN |
FD | 5 | Invalid OMS Command Line Parameters (&A) for Logical OMS &B | BC-CCM-PRN |
FD | 6 | Internal Error in OMS Polling Handling | BC-CCM-PRN |
FD | 7 | Missing Output of an OMS Command (&B) for Access Method "E" for Device &A | BC-CCM-PRN |
FD | 8 | Missing Memory for Requests Using Access Method "E" for Device &A | BC-CCM-PRN |
FD | 9 | Missing Answer to a Job Entry from External Command (&B) From LOMS &A | BC-CCM-PRN |
FD | A | Unable to Connect to Output Management System &A (Status &B) | BC-CCM-PRN |
FD | B | Format Error in Output &B (Device &A): &C Fields (&D Necessary, &E Possible) | BC-CCM-PRN |
FE | 0 | Test | BC-CCM-PRN |
FE | F | Error Flushing at End of Internal Session. Program: &A. Screen: &B. | BC-CCM-PRN |
FF | 0 | Test | BC-CCM-PRN |
FF | E | Test Message | BC-CCM-PRN |
FF | F | Test Message | BC-CCM-PRN |
FP | 0 | Repeat ADS Call: &a | BC-SRV-FP |
FP | 1 | Successful repetition of ADS call | BC-SRV-FP |
GC | 0 | GC0 ... GDZ reserved for CCMS | BC-CCM-CNF-PFL |
GC | 1 | &8 skipped: Timeout | BC-CCM-CNF-PFL |
GC | 2 | &8 canceled due to timeout | BC-CCM-CNF-PFL |
GC | 3 | The active profile was modified | BC-CCM-CNF-PFL |
GC | 4 | >>> Profile name = &a&b&c&d | BC-CCM-CNF-PFL |
GE | 0 | Enqueue: Invalid parameter length $$$$$$$$$$$$ | BC-CST-EQ |
GE | 1 | Enqueue: OpCode $, missing parameter $$$$$$$$$$$$ | BC-CST-EQ |
GE | 2 | Enqueue wildcard line: Missing parameter $$$$ | BC-CST-EQ |
GE | 3 | Enqueue: OpCode $, length exceeded for parameter $$$$$$$$$$$$ | BC-CST-EQ |
GE | 4 | Enqueue: Opcode $, max.number of elementary locks exceeds lock object $$$$$$$$ | BC-CST-EQ |
GE | 5 | Enqueue: Opcode $, missing elementary lock parameter, lock object $$$$$$$$ | BC-CST-EQ |
GE | 6 | Enqueue: Invalid op.code $ | BC-CST-EQ |
GE | 7 | Enqueue: Multiple elementary locks with the same name in one request | BC-CST-EQ |
GE | 8 | Enqueue: Elementary lock $$$ has invalid lock mode $; lock object $$$$$$$$ | BC-CST-EQ |
GE | 9 | Enqueue: Accumulated wait time for lock: $$$$$$$$$$$ seconds | BC-CST-EQ |
GE | A | Internal lock administration error | BC-CST-EQ |
GE | B | Enqueue: Length USER_SIZE and SAP_EN_KEY_LN do not match | BC-CST-EQ |
GE | C | Lock entries in the lock table are not compressed | BC-CST-EQ |
GE | D | Memory snapshot of lock table created | BC-CST-EQ |
GE | F | Error setting up the lock table | BC-CST-EQ |
GE | G | Lock table overflow | BC-CST-EQ |
GE | H | Enqueue: Transfer error while reading lock entries | BC-CST-EQ |
GE | I | Enqueue: Initialization error | BC-CST-EQ |
GE | J | Error opening a lock handler file | BC-CST-EQ |
GE | K | Error positioning on a lock handler file | BC-CST-EQ |
GE | L | Error occurred while reading a lock handler file | BC-CST-EQ |
GE | M | Error while writing to a lock handler file | BC-CST-EQ |
GE | N | Enqueue: SM12 test/diagnosis mode was activated | BC-CST-EQ |
GE | O | Lock entry deleted manually: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST-EQ |
GE | P | Enqueue logging was activated | BC-CST-EQ |
GE | Q | Enqueue logging was deactivated | BC-CST-EQ |
GE | R | Enqueue: Lock administration was activated manually | BC-CST-EQ |
GE | S | Enqueue: Lock administration was activated manually: Minimum operation | BC-CST-EQ |
GE | T | Dummy system log for error text module in long text | BC-CST-EQ |
GE | U | Enqueue: Report file $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST-EQ |
GE | V | Enqueue: Backup file $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST-EQ |
GE | W | Authorization check in transaction sm12 was deactivated | BC-CST-EQ |
GE | X | Lock entry deleted: $$$$$$$$$$ $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST-EQ |
GE | Y | Enqueue: &a | BC-CST-EQ |
GE | Z | Enqueue: &a | BC-CST-EQ |
GH | 0 | Error in Central Lock Handler | BC-CST-EQ |
GH | 1 | > Lock Request with Inconsistent Length | BC-CST-EQ |
GH | 2 | > Overlap Between Request and Response Area | BC-CST-EQ |
GH | 3 | > Length of Request Area Exceeds the Maximum Value | BC-CST-EQ |
GH | 4 | > Request Area Lost Due to Address Change | BC-CST-EQ |
GH | 5 | > Length of Response Area Exceeds the Maximum Value | BC-CST-EQ |
GH | 6 | > Error Response was Generated | BC-CST-EQ |
GH | A | Initialization of the Lock Table was Established | BC-CST-EQ |
GH | Z | > Previous Message was Suppressed &6 Times | BC-CST-EQ |
GI | 0 | Error calling the central lock handler | BC-CST-EQ |
GI | 1 | > Lock response with inconsistent length | BC-CST-EQ |
GI | 2 | > Unable to reach central lock handler | BC-CST-EQ |
GI | 3 | > Failed to clean up lock entries | BC-CST-EQ |
GI | 4 | > Dequeue All call failed | BC-CST-EQ |
GI | 5 | > Dequeue All call with invalid lock owner | BC-CST-EQ |
GI | 6 | Central lock handler can be accessed again | BC-CST-EQ |
GI | 7 | > Request to update the report file failed | BC-CST-EQ |
GJ | 0 | Incorrect lock handler configuration | BC-CST-EQ |
GJ | 1 | > No. of enqueue processes in the lock server must be greater than 0 | BC-CST-EQ |
GJ | 2 | > No. of enqueue processes in non-lock servers must be 0 | BC-CST-EQ |
GK | 0 | Incorrect call for central lock handler. Operation code = $ | BC-CST-EQ |
GK | 1 | Error accessing lock handler file | BC-CST-EQ |
GZ | Z | > $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST-EQ |
H0 | 1 | Enqueue for work item &A deleted by called application | BC-BMT-WFM |
H0 | 2 | Attempt to restore enqueue for work item &A failed | BC-BMT-WFM |
H1 | 1 | Event linkage was deactivated : &A.&B-&C -> &D | BC-BMT-WFM |
IC | 0 | ICF Recorder entry executed by user &A (activity: &B) | BC-MID-ICF |
IC | 1 | ICF Recorder entry executed by user &A (&B,&C) (activity: &D). | BC-MID-ICF |
IC | 2 | Administration settings for ICF Recorder changed by user | BC-MID-ICF |
IC | 3 | Administration settings for ICF Recorder deleted by user | BC-MID-ICF |
IC | 4 | Debugging of &A created for URL &B | BC-MID-ICF |
IC | 5 | Debugging of &A deleted for URL &B | BC-MID-ICF |
IC | 6 | Trace entry of USER &A created for USER &B and URL &C | BC-MID-ICF |
IC | 7 | Trace entry of USER &A created for URL &B | BC-MID-ICF |
IC | 8 | Trace entry of USER &A deleted for USER &B and URL &C | BC-MID-ICF |
IC | 9 | Trace entry of USER &A deleted for URL &B | BC-MID-ICF |
IC | A | ATRA entry of USER &A created for USER &B and URL &C | BC-MID-ICF |
IC | B | ATRA entry of USER &A created for URL &B | BC-MID-ICF |
IC | C | ATRA entry of USER &A deleted for USER &B and URL &C | BC-MID-ICF |
IC | D | ATRA entry of USER &A deleted for URL &B | BC-MID-ICF |
IC | F | RECORD entry of USER &A created for USER &B and URL &C | BC-MID-ICF |
IC | G | RECORD entry of USER &A created for URL &B | BC-MID-ICF |
IC | H | ATRA entry of USER &A deleted for USER &B and URL &C | BC-MID-ICF |
IC | I | ATRA entry of USER &A deleted for URL &B | BC-MID-ICF |
IC | J | DEBUGGING entry of USER &A created for USER &B and URL &C | BC-MID-ICF |
IC | K | DEBUGGING entry of USER &A deleted for USER &B and URL &C | BC-MID-ICF |
IM | 0 | &A | BC-CST-IC |
IM | 1 | &A started on host &B (PID: &C) | BC-CST-IC |
IM | 2 | &A terminated on host &B (PID: &C) | BC-CST-IC |
IM | 3 | &A is ready for operation (PID: &B) | BC-CST-IC |
IM | 4 | Port &A could not be started for protocol &B | BC-CST-IC |
IM | 5 | Network connection could not be accepted | BC-CST-IC |
IM | 6 | Deadlock detected in &A | BC-CST-IC |
IM | 7 | SAP Web Dispatcher could not connect to server &A | BC-CST-IC |
IM | 8 | Request from MPI memory failed | BC-CST-IC |
IM | 9 | Connection closed due to MPI memory bottleneck | BC-CST-IC |
LC | 0 | Logical command "&A" executed for "&B" on "&i": "&a&b&c&d&e&f&g&h" | BC-CCM-BTC |
LC | 1 | Illegal log. command "&A" rejected for "&B" on "&i": "&a&b&c&d&e&f&g&g&h" | BC-CCM-BTC |
LC | 2 | &C when executing external command &A on &B (&a&b&c&d&e&f&g&h&i) | BC-CCM-BTC |
LC | 3 | &B when executing external program on &A (&a&b&c&d&e&f&g&h&i) | BC-CCM-BTC |
LC | 4 | &B when calling internal RFC on &A in BP runtime system (&a&b&c&d&e&f&g&h&i) | BC-CCM-BTC |
LD | 0 | Could not send SLD data | BC-CCM-SLD-ABA |
LQ | 1 | Queue &A deleted from LDQ application &B | BC-MID-RFC |
O0 | 1 | Optical archiving: Error at &A | BC-SRV-ARL |
O0 | 2 | Optical archiving: Error at &A | BC-SRV-ARL |
P0 | 0 | Role file $$$$$$$$$$$$$$ could not be opened | BC-ABA |
P0 | 1 | Error in roll chain: Subsequent block to [$$$$$$,$$$$$$] missing | BC-ABA |
P0 | 2 | No block found for role area $ | BC-ABA |
P0 | 3 | Role File Overflow ($$$$$$ Blocks) | BC-ABA |
P0 | 4 | Invalid rrol_free call | BC-ABA |
P0 | 5 | Memory request (malloc) failed | BC-ABA |
P0 | 6 | Error in memory chain during roll out | BC-ABA |
P0 | 8 | Status: 80% of $$$$$$$$ is in use | BC-ABA |
P0 | 9 | Status: 90% of $$$$$$$$ is in use | BC-ABA |
P0 | A | Paging file $$$$$$$$$$$$$$ could not be opened | BC-ABA |
P0 | B | Overflow of Paging File ($$$$$$ Blocks) | BC-ABA |
P0 | C | Unpermitted paging access to block $$$$$$ | BC-ABA |
P0 | D | No free block in paging buffer ($$$$$$ blocks) | BC-ABA |
P0 | E | Unpermitted release of paging block $$$$$$,$$$$$$ | BC-ABA |
P0 | F | Inconsistent paging system administration | BC-ABA |
P0 | G | Incorrect call of pg_free_all | BC-ABA |
P0 | R | Failed to position on operating system file (error no. = &>E5) | BC-ABA |
P0 | S | Failed to read operating system file (error no. = &>E5) | BC-ABA |
P0 | T | Failed to write to operating system file (error no. &>E5) | BC-ABA |
PC | 1 | APC cross origin access has failed for origin &A | BC-MID-AC |
PC | 2 | APC cross origin entry with host "&A" port "&B" protocol "&C" has been deleted | BC-MID-AC |
PM | 1 | Validity of certificate with PSE type >&A< ends in &B days | BC-SEC-SSF |
PM | 2 | Certificate with PSE type >&A< has been invalid for &B days | BC-SEC-SSF |
PM | 3 | At least &A errors found when certificates checked | BC-SEC-SSF |
PM | 4 | Validity of certificate from list with PSE type >&A< ends in &B days | BC-SEC-SSF |
Q0 | 0 | Start SAP System, SAPSYSTEM $$, Dispatcher Pid $$$$$$$$ | BC-CST |
Q0 | 1 | Start $$$$$$$$$$, $$ times since system startup. PID $$$$$$$$ | BC-CST |
Q0 | 2 | Stop $$$$$$$$$$, PID $$$$$$$$ | BC-CST |
Q0 | 3 | No free block found in the WP communication area | BC-CST |
Q0 | 4 | Connection to user &5 (&9&3), terminal &4 (&9&3) lost | BC-CST |
Q0 | 5 | Stop SAP System, Dispatcher Pid $$$$$$ | BC-CST |
Q0 | 6 | Unable to read profile parameter $$$$$$$$$$$$$$$$$$$$ | BC-CST |
Q0 | 7 | Request has an error, invalid terminal ID ($$$$$$) | BC-CST |
Q0 | 8 | Request has an error, invalid session ($$$), terminal ID $$$$ ($$$$$$$$$$$$) | BC-CST |
Q0 | 9 | Host name $$$$$$$$$$$$$$$$$$$$ not known | BC-CST |
Q0 | A | Service $$$$$$$$$$$$$$$$$$$$ not known | BC-CST |
Q0 | B | Failed to establish connection to terminal $$$$$$$$$$$$$$$$$$$$ | BC-CST |
Q0 | C | Start of SAP gateway failed ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$) | BC-CST |
Q0 | D | New request for current session $, user $$$$$ ($$$$$$$$$$$$), work process $$ | BC-CST |
Q0 | E | Signal $$$ received by operating system | BC-CST |
Q0 | F | Message handling component is not activated | BC-CST |
Q0 | G | Request (type $$$$) cannot be processed | BC-CST |
Q0 | H | Error adding a request to the dispatcher queue ($$$$) | BC-CST |
Q0 | I | Operating system call &5&5&4 failed (error no. &>E5) | BC-CST |
Q0 | J | Work process type required for request handling does not exist | BC-CST |
Q0 | K | Connection to message server (on $$$$$$$$$$$$$$$$$$$$) established | BC-CST |
Q0 | L | Connection to message server failed | BC-CST |
Q0 | M | Message server disconnected | BC-CST |
Q0 | N | Failed to send a request to the message server | BC-CST |
Q0 | O | Multiple Client logon ($$$$$$$$$$$$$$$$$$$$) for message server | BC-CST |
Q0 | P | Maximum number of permitted terminal connections reached ($$$$$) | BC-CST |
Q0 | Q | Start $$$$$$$$$$, Pid $$$$$$$$ | BC-CST |
Q0 | R | Failed to call function $$$$$$$$$$$$; rc: $$$$ | BC-CST |
Q0 | S | Connection to SAP gateway closed | BC-CST |
Q0 | T | Connection to SAP gateway is disrupted | BC-CST |
Q0 | U | Client $$$$$$$$$$$$$$$$$$$$ is not known to the message server | BC-CST |
Q0 | V | Work process $$$ switched from request type $$$ to $$$ | BC-CST |
Q0 | W | &A deletes RFC destination &B | BC-CST |
Q0 | X | Connection to client &1 of message server closed due to timeout | BC-CST |
Q0 | Y | Unknown op. code &1 received | BC-CST |
Q0 | Z | Versions of dplib are different (sys_adm $$$$ / lib $$$$) | BC-CST |
Q1 | 0 | Alarm thread terminated | BC-CST |
Q1 | 1 | Host address $$$$$$$$$$$$$$$ is unknown | BC-CST |
Q1 | 2 | Buffer for host address is too small (required: $$$, available: $$$) | BC-CST |
Q1 | 3 | Connection request received by unknown SAP gateway | BC-CST |
Q1 | 4 | Maximum number of &6 SAP gateways that can be connected was reached | BC-CST |
Q1 | 5 | External partner (&A) tried to log on with a message type | BC-CST |
Q1 | 6 | Msg server hardware ID missing ($$$$$$$$$$$$) | BC-CST |
Q1 | 8 | Work process $$ exclusively locked by user $$$$$$$$$$$$ | BC-CST |
Q1 | 9 | The profile parameter &a&b&c&d was changed in productive operation | BC-CST |
Q1 | A | >>> Old/New value : &a&b&c&d | BC-CST |
Q1 | B | The dynamic changeability of the profile parameter &a&b&c&d was deactivated | BC-CST |
Q1 | C | MsgServer Hardware ID Was Determined | BC-CST |
Q1 | D | System startup procedure started | BC-CST |
Q1 | E | System startup procedure executed. | BC-CST |
Q1 | F | Server status changed to &A | BC-CST |
Q1 | G | Soft shutdown of ICM was started | BC-CST |
Q1 | H | Hard shutdown (kill) of ICM starting | BC-CST |
Q1 | I | &72 | BC-CST |
Q1 | J | Inactive terminal $$$$ is being logged off ($$$$$$$$$$$$$$$) | BC-CST |
Q1 | K | Kernel Version Incompatable with System | BC-CST |
Q1 | L | Soft shutdown of server started (reason is &a) | BC-CST |
Q1 | M | Soft Shutdown of Server &A | BC-CST |
Q1 | N | Shutdown of Server &A | BC-CST |
Q1 | O | The configuration of the work processes will be changed | BC-CST |
Q1 | P | An error has occurred when configuring the work processes | BC-CST |
Q1 | Q | > &a | BC-CST |
Q1 | R | Configuration of work processes was already changed (e.g. for process &a) | BC-CST |
Q1 | S | System startup procedure terminated; reason: &a | BC-CST |
Q1 | T | User &a in client &b (application: &c) could not be logged on | BC-CST |
Q1 | U | Current task of user &a / &b terminated because of a deadlock resolution | BC-CST |
Q1 | V | Server stopped (reason is &a) | BC-CST |
Q1 | W | Server is running again | BC-CST |
Q1 | X | Overflow in connection table (reason = &a) | BC-CST |
Q1 | Y | Tenant shutdown, user session &a (logon=&b, ID=&c) is closing | BC-CST |
Q1 | Z | Tenant &a is shutting down, open sessions are closing | BC-CST |
Q2 | 0 | User &A is deleting tRFC TID &B | BC-MID-RFC |
Q2 | 1 | User &A is reorganizing the outbound queue table | BC-MID-RFC |
Q2 | 2 | User &A is deleting outbound queue &B | BC-MID-RFC |
Q2 | 3 | User &A is deleting TID &B in outbound queue &C | BC-MID-RFC |
Q2 | 4 | User &A is reorganizing the inbound queue table | BC-MID-RFC |
Q2 | 5 | User &A is deleting inbound queue &B | BC-MID-RFC |
Q2 | 6 | User &A is deleting TID &B in inbound queue &C | BC-MID-RFC |
Q2 | 7 | User &A is reorganizing the table of the saved inbound queue | BC-MID-RFC |
Q2 | 8 | User &A is deleting the saved inbound queue &B | BC-MID-RFC |
Q2 | 9 | User &A is deleting TID &B in the saved inbound queue &C | BC-MID-RFC |
Q2 | A | User &A is deleting the first part of the saved inbound queue &B | BC-MID-RFC |
Q2 | B | User &A is reorganizing the tRFC tables | BC-MID-RFC |
Q2 | C | User &A is deleting the tRFC and qRFC tables (outbound queue) | BC-MID-RFC |
Q2 | D | User &A has deleted the tRFC/qRFC table for logs received | BC-MID-RFC |
Q2 | E | User &A is deleting TID &B in the tRFC-/qRFC confirmation table | BC-MID-RFC |
Q2 | F | User &A is reorganizing the table of tRFC and qRFC confirmations | BC-MID-RFC |
Q2 | G | User &A is deleting the qRFC tables (inbound queue) | BC-MID-RFC |
Q2 | H | User &A is reorganizing all GET tables | BC-MID-RFC |
Q2 | I | User &A deleted the queue &B of the GET table &C | BC-MID-RFC |
Q2 | J | User &A changed TID &B to tRFC TID &C | BC-MID-RFC |
Q2 | K | User &A deleted table &B with report &C | BC-MID-RFC |
Q2 | L | User &A reset &B &C in queue &D | BC-MID-RFC |
Q2 | X | &A &B &C | BC-MID-RFC |
Q3 | 0 | Incorrect value for profile parameter: &a | BC-CCM-CNF-PFL |
Q3 | 1 | > Value: &a | BC-CCM-CNF-PFL |
Q3 | 2 | > Cause: &a | BC-CCM-CNF-PFL |
Q4 | 0 | Server resources are exhausted | BC-CST |
Q4 | 1 | Snapshot &a created | BC-CST |
Q4 | 2 | Configured, secure, internal system communication is not supported | BC-CST |
Q4 | 3 | Configure secure internal system communication | BC-CST |
Q4 | 4 | Server startup procedure (session &a) canceled after timeout | BC-CST |
Q4 | 5 | Secure communication between internal systems was deactivated | BC-CST |
Q4 | 6 | Server is closing down (reason: &a) | BC-CST |
Q4 | 7 | &a connection errors have occurred in succession | BC-CST |
Q4 | 8 | Maximum number of AMC registrations reached (&a Registrations) | BC-CST |
R0 | 0 | Failed to lock semaphore $$$; RC=$$$ | BC-CST |
R0 | 1 | Failed to release semaphore $$$; ERR=$$$ | BC-CST |
R0 | 2 | Session $$$ is already active | BC-CST |
R0 | 3 | Invalid session $$$ | BC-CST |
R0 | 4 | Session $$$ is not active | BC-CST |
R0 | 5 | No active session exists | BC-CST |
R0 | 6 | Session chain $$$$ destroyed, incorrect session $$$ | BC-CST |
R0 | 7 | Mode chain $$$$ deleted, wrong predecessor: $$$ | BC-CST |
R0 | 8 | Unattained modes in mode chain $$$$ | BC-CST |
R0 | 9 | Mode chain $$$$ is not a circle | BC-CST |
R0 | A | Maximum number $$ of internal sessions reached | BC-CST |
R0 | B | Rollout failed; RC=$$$ | BC-CST |
R0 | C | Roll-in of UID/mode $$$$$$/$$$ failed; RC=$$$ | BC-CST |
R0 | D | Roll-free failed; RC=$$$ | BC-CST |
R0 | E | Page-free failed; RC=$$$ | BC-CST |
R0 | F | Error accessing $$$$$$$$ in table TXCOM | BC-CST |
R0 | G | Input with incorrect message type $$$ received | BC-CST |
R0 | H | Error handling canceled | BC-CST |
R0 | J | Work process with PID $$$$$$$$ is terminated manually | BC-CST |
R0 | K | Mode $$$ of user $$$$$$$$$$$$ manually terminated | BC-CST |
R0 | L | Program &9&9&9&9&4 set manually to debug mode by user &9&3 | BC-CST |
R0 | M | Program &9&9&9&9&4 manually terminated by user &9&3 | BC-CST |
R0 | N | HTTP session deleted after timeout | BC-CST |
R0 | O | No active update server exists (context = &a) | BC-CST |
R0 | P | Entries in the number range buffer were deleted (count: $$$$$$) | BC-CST |
R0 | Q | $$$-Eye-Catchers of the number range buffer were destroyed | BC-CST |
R0 | R | The update was deactivated following a system error | BC-CST |
R0 | S | The update was manually de-activated | BC-CST |
R0 | T | The update was activated | BC-CST |
R0 | U | Update requests were deleted (VBKEY = &A, VBUSR = &B) | BC-CST |
R0 | V | Updates were triggered manually | BC-CST |
R0 | W | Canceled update requests updated | BC-CST |
R0 | X | An update request was carried out in debugging mode | BC-CST |
R0 | Y | Update data was displayed | BC-CST |
R0 | Z | The update dispatch info was reset | BC-CST |
R1 | 0 | Writing to connection table failed | BC-CST |
R1 | 1 | No active connection found in connection table | BC-CST |
R1 | 2 | Connection closed | BC-CST |
R1 | 3 | Error in program flow | BC-CST |
R1 | 4 | Signal $$ received | BC-CST |
R1 | 5 | Function signal failed; errno=&>E5 | BC-CST |
R1 | 6 | open failed; ERR=$$$ | BC-CST |
R1 | 7 | Failed to read from a file; ERR=$$$$$ | BC-CST |
R1 | 8 | SAP commit failed | BC-CST |
R1 | 9 | Initialization $$$$$$$$$$$$$$$$$$$$ failed, return code $$$$$$$ | BC-CST |
R1 | A | $$$ logon failed | BC-CST |
R1 | B | SAP-DEXT loop, message key: &>M5 | BC-CST |
R1 | C | No terminal ID exists | BC-CST |
R1 | D | Eyecatcher in task handler destroyed | BC-CST |
R1 | E | Roll-Open failed | BC-CST |
R1 | F | Page-Open failed | BC-CST |
R1 | G | The update statistics were reset | BC-CST |
R1 | H | Internal error in $$$$$$$$$$ | BC-CST |
R1 | I | The session was canceled following loss of lock table. | BC-CST |
R1 | J | User/session &A/&B is being reset following loss of lock table | BC-CST |
R1 | K | Trace activated for user &A | BC-CST |
R1 | L | Trace deactivated for user &A | BC-CST |
R1 | M | Trace passed from remote client | BC-CST |
R1 | N | Session of user / client &A / &B cannot be passed | BC-CST |
R1 | O | Update request restarted after internal error | BC-CST |
R1 | P | Error in the enqueue configuration | BC-CST |
R1 | Q | SNC Active (&A) | BC-CST |
R1 | R | Update server &a activated | BC-CST |
R1 | S | Update server &a deactivated | BC-CST |
R1 | T | Update request (key = &A) was passed to server &B | BC-CST |
R1 | U | &A occurred in update task | BC-CST |
R1 | V | The tests were deactivated before post-updates | BC-CST |
R1 | W | Trace file(s) &A of user &B reset | BC-CST |
R1 | X | Debugging session of user/mode &A/&B reset | BC-CST |
R1 | Y | Update data was reorganized | BC-CST |
R2 | 0 | Insufficient shared memory | BC-CST |
R2 | 1 | Abnormal end of region $$ | BC-CST |
R2 | 2 | SAPASRV failed; OP=$$, RC=$$$ | BC-CST |
R2 | 3 | Process table overflow (wp_adm), max. size $$ processes | BC-CST |
R2 | 4 | malloc failed; errno=&>E3 | BC-CST |
R2 | 5 | Different $$$$ addresses | BC-CST |
R2 | 6 | ctdli failed; RC=$$$ | BC-CST |
R2 | 7 | Preceding error $$$ | BC-CST |
R2 | 8 | Different time stamps | BC-CST |
R2 | 9 | No shared memory exists | BC-CST |
R2 | A | > File: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
R2 | B | No memory for $$$$ | BC-CST |
R2 | C | Terminal $$$$$ in status $$$$ | BC-CST |
R2 | D | Session $$$ was already disconnected | BC-CST |
R2 | E | Session is waiting for APPC input | BC-CST |
R2 | F | Session is waiting for terminal input | BC-CST |
R2 | G | HTTP/RFC session was deleted following timeout | BC-CST |
R2 | H | Active &A file deleted | BC-CST |
R2 | I | &A files older than &B deleted | BC-CST |
R3 | 0 | Incorrect UID/mode $$$$$$/$$$ in SPA | BC-CST |
R3 | 1 | SemStat failed; RC=$$$ | BC-CST |
R3 | 2 | $$$ units of semaphore $$$ locked | BC-CST |
R3 | 3 | RSTG chain defective, return code $$$ | BC-CST |
R3 | 4 | Paging commit failed; RC=$$$ | BC-CST |
R3 | 5 | $$$$ block not released | BC-CST |
R3 | 6 | No $$$$ block received | BC-CST |
R3 | 7 | Error in T100, MSG: $$$$$ | BC-CST |
R3 | 8 | Error at DB commit, return code $$$$$$$ | BC-CST |
R3 | 9 | Error in DB rollback/SyFlush, return code $$$$$$$ | BC-CST |
R3 | A | Eyecatcher $$ destroyed | BC-CST |
R3 | B | RSTS: Failed to prepare for commit, return code $$$ | BC-CST |
R3 | C | Maximum no. users $$$$ reached | BC-CST |
R3 | D | tm_adm full ($$$$) | BC-CST |
R3 | E | DB function $$$$$$ failed; RC=$$$$$$$ | BC-CST |
R3 | F | No TTRAN entry for $$$$$$$$ | BC-CST |
R3 | G | Incomplete update request was deleted | BC-CST |
R4 | 0 | Incorrect transaction index $$ | BC-CST |
R4 | 1 | Illegal CPIC request $$ | BC-CST |
R4 | 2 | RSTS: Commit failed; RC=$$$ | BC-CST |
R4 | 3 | RSTS: Rollback failed; RC=$$$ | BC-CST |
R4 | 4 | RSTS: Rollout failed; RC=$$$ | BC-CST |
R4 | 5 | Shared memory destroyed | BC-CST |
R4 | 6 | Restart after IMS-ABEND | BC-CST |
R4 | 7 | Deletes session &a after error &b | BC-CST |
R4 | 8 | Invalid UID $$$$$$ | BC-CST |
R4 | 9 | Communication error, CPIC return code $$$, SAP return code $$$ | BC-CST |
R4 | A | Incorrect UID/session $$$$$$/$$$ in TM_ADM | BC-CST |
R4 | B | TM_ADM and SPA destroyed | BC-CST |
R4 | C | Static UID save destroyed | BC-CST |
R4 | D | Incorrect TID $$$$$$ in process table (wp_adm) | BC-CST |
R4 | E | Session is waiting for a message | BC-CST |
R4 | F | Failed to write to a file; ERR=$$$$$ | BC-CST |
R5 | 0 | Failed to delete file $$$$$$$$; ERR=$$$ | BC-CST |
R5 | 1 | Statistics: Buffer overflow | BC-CST |
R5 | 2 | > Table: &9&9&7 | BC-CST |
R5 | 3 | No work area for update screen | BC-CST |
R5 | 4 | Invalid APPC header version $$$ | BC-CST |
R5 | 5 | Invalid terminal ID $$$$$$ | BC-CST |
R5 | 6 | Enqueue: Rollback failed; RC=$$$ | BC-CST |
R5 | 7 | No output for background processing, task type $$$ | BC-CST |
R5 | 8 | Incorrect update mode $$ | BC-CST |
R5 | 9 | No update header in SPA | BC-CST |
R5 | A | > Conversation ID: $$$$$$$$ | BC-CST |
R5 | B | $$$$ Output Area Overflow | BC-CST |
R5 | C | Terminal type $$$: Incorrect output destination/message type $$$$$$ | BC-CST |
R5 | E | Incorrect parameter $$$$$$: $$$$$$ | BC-CST |
R5 | F | Incorrect task type $$$ | BC-CST |
R6 | 0 | Incorrect communications type $$$$ | BC-CST |
R6 | 1 | > TXCOM key: $$$$$$$$ | BC-CST |
R6 | 2 | > Request type: $$$$$$$$$$$$ | BC-CST |
R6 | 3 | Work process is being terminated | BC-CST |
R6 | 4 | > CPI-C function: $$$$$$$$$$$$ | BC-CST |
R6 | 5 | Update terminated | BC-CST |
R6 | 6 | > Update key: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
R6 | 7 | > Update module: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
R6 | 8 | Perform rollback | BC-CST |
R6 | 9 | VM container has been deactivated by the system | BC-CST |
R6 | A | VM container has been deactivated by the user | BC-CST |
R6 | B | VM container has been reset by the user | BC-CST |
R6 | C | VM &a has been terminated by the user | BC-CST |
R6 | D | Current processing of VM &a has been terminated by the user | BC-CST |
R6 | E | VM &a has terminated (exit/abort) | BC-CST |
R6 | F | Error occurred during execution of Java in VM &a | BC-CST |
R6 | G | > &a | BC-CST |
R6 | H | VM &a was moved to the debug mode | BC-CST |
R6 | I | Stack dump for VM &a has been triggered | BC-CST |
R6 | J | Trace flags for VM &a have been changed | BC-CST |
R6 | L | Java session error occurred: &a | BC-CST |
R6 | M | Maximum number of unsuccessful shared GCs exceeded | BC-CST |
R6 | N | VM Container activated by the user | BC-CST |
R6 | Q | &a | BC-CST |
R6 | R | &a | BC-CST |
R6 | S | &a | BC-CST |
R6 | T | &a | BC-CST |
RD | 0 | &A: Incorrect Parameter &B Value &C | BC-SEC-SSF |
RD | 1 | &A: RFC Error &B Occurred | BC-SEC-SSF |
RD | 2 | &A: Kernel Error &B Occurred | BC-SEC-SSF |
RD | 3 | &A: Function Returned &B | BC-SEC-SSF |
RD | 4 | &A: Sign Return Code &B | BC-SEC-SSF |
RO | Z | Runtime analysis in program &9&9&9&9&4 switched on by user &9&3 | BC-ABA-LA |
S0 | 0 | SAP gateway started (PID: $$$$$$$$$$) | BC-CST |
S0 | 1 | Maximum number $$$ of connections reached | BC-CST |
S0 | 2 | Receive failed; RC=$$$ | BC-CST |
S0 | 3 | Initialization of signal handling failed | BC-CST |
S0 | 4 | No PID received, return code $$$ | BC-CST |
S0 | 5 | Profile error, return code $$$ | BC-CST |
S0 | 6 | Semaphore Init failed; RC=$$$ | BC-CST |
S0 | 7 | Failed to create shared tables | BC-CST |
S0 | 8 | Event-Init failed; RC=$$$ | BC-CST |
S0 | 9 | Event-Open failed; EVT=$$$, RC=$$$ | BC-CST |
S0 | A | Timeout for function $$$$$$ | BC-CST |
S0 | B | Maximum number $$$$$ of requests per CPI-C connection reached | BC-CST |
S0 | C | Connection cannot be established, return code $$$ | BC-CST |
S0 | D | gethostname failed; ERR=$$$ | BC-CST |
S0 | E | Overflow block $$$ not found | BC-CST |
S0 | F | Signal $$ received | BC-CST |
S0 | G | Invalid session number $$$ received | BC-CST |
S0 | H | fwrite failed; ERR=$$$$ | BC-CST |
S0 | I | > Partner TP name: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
S0 | J | Failed to open side info file, ERR=$$$ | BC-CST |
S0 | K | > File: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
S0 | L | No entry found for destination $$$$$$$$ in side info file | BC-CST |
S0 | M | No value for $$$$$$$$ in side info entry of $$$$$$$$ | BC-CST |
S0 | N | Function LU62ATTCH failed; RC=$$$$$$$$ | BC-CST |
S0 | O | No free space in overflow area of gateway | BC-CST |
S0 | P | rexec failed; ERR=$$$ | BC-CST |
S0 | Q | > $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
S0 | R | > Host: &a&b&c&d&e | BC-CST |
S0 | S | > Service: $$$$$$$$ | BC-CST |
S0 | T | NiConnect failed; rc: $$$$$ | BC-CST |
S0 | U | Gateway SNA process (GWWP) started (number: $$$, PID: $$$$$$$$$$) | BC-CST |
S0 | V | Error, gateway closed | BC-CST |
S1 | 0 | Service-Init failed | BC-CST |
S1 | 1 | Storing GW-PID failed; RC=$$$ | BC-CST |
S1 | 2 | Select failed, error $$$ | BC-CST |
S1 | 3 | Gateway write process (gwwr) terminated | BC-CST |
S1 | 4 | No CPI-C request block received | BC-CST |
S1 | 5 | Failed to write a CPIC request | BC-CST |
S1 | 6 | Failed to enter CPI-C request in the process stack | BC-CST |
S1 | 7 | Event error, return code $$$ | BC-CST |
S1 | 8 | Failed to read datagramm; RC=$$$ | BC-CST |
S1 | 9 | Maximum no. $$$ of systems reached | BC-CST |
S1 | A | No system found for select flag | BC-CST |
S1 | B | Unknown APPC header version $$$ | BC-CST |
S1 | C | System and APPC header versions ($$$/$$$) are different | BC-CST |
S1 | D | Unknown APPC-DG version $$$ | BC-CST |
S1 | E | Incorrect APPC datagram length $$$$$$ | BC-CST |
S1 | F | Failed to initialize $$$$$$$$ | BC-CST |
S1 | G | Attempt to take over conversation Id $$$$$$$$ by computer $$$$$$$$$$$$$$$$ | BC-CST |
S1 | H | Simulation mode activated | BC-CST |
S1 | I | Simulation mode deactivated | BC-CST |
S2 | 0 | Connect failed | BC-CST |
S2 | 1 | Datagram with unknown type $$$ received | BC-CST |
S2 | 2 | Failed to read CPIC request; RC=$$$ | BC-CST |
S2 | 3 | Connection to CPI-C client $$$ was closed | BC-CST |
S2 | 4 | Error in datagram, return code $$$ | BC-CST |
S2 | 5 | Connection table full | BC-CST |
S2 | 6 | Unknown conversation ID $$$$$$$$ | BC-CST |
S2 | 7 | No free gateway work process | BC-CST |
S2 | 8 | Incorrect connection type $$$ | BC-CST |
S2 | 9 | Error starting the gateway work process (gwwp) | BC-CST |
S2 | A | Error in protocol value $$$ | BC-CST |
S3 | 0 | SAP gateway was closed | BC-CST |
S3 | 1 | bind failed; ERR=$$$ | BC-CST |
S3 | 2 | Start of gateway write processes (gwwr) failed | BC-CST |
S3 | 3 | fork failed; ERR=$$$ | BC-CST |
S3 | 4 | exec failed; ERR=$$$$, TP=$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
S3 | 5 | Opening of $$$$$$$$ failed; ERR=$$$ | BC-CST |
S3 | 6 | Failed to write GW-PID file; ERR=$$$ | BC-CST |
S3 | 7 | Failed to close GW-PID file; ERR=$$$ | BC-CST |
S3 | 8 | Failed to delete GW-PID file; ERR=$$$ | BC-CST |
S3 | 9 | Invalid output data | BC-CST |
S4 | 0 | Failed to create request pool | BC-CST |
S4 | 1 | Failed to create GW tables; RC=$$$ | BC-CST |
S4 | 2 | Semaphore error, return code $$$ | BC-CST |
S4 | 3 | No free request index block | BC-CST |
S4 | 4 | EvtCreate failed; RC=$$$ | BC-CST |
S4 | 5 | No event for gateway work process $$$ | BC-CST |
S4 | 6 | Invalid CPIC length $$$$$$$$$$ | BC-CST |
S4 | 7 | Error sending reply, return code $$$ | BC-CST |
S4 | 8 | Too few parameters | BC-CST |
S4 | 9 | gethostname failed; ERR=$$$ | BC-CST |
S5 | 0 | Initialization to send a data program failed | BC-CST |
S5 | 1 | sendto failed; ERR=$$$ | BC-CST |
S5 | 2 | getservbyname failed; Service=$$$$$$$$, ERR=$$$ | BC-CST |
S5 | 3 | gethostbyname failed; Host=$$$$$$$$, ERR=$$$ | BC-CST |
S5 | 4 | socket failed; ERR=$$$ | BC-CST |
S5 | 5 | Connection does not exist or was disconnected | BC-CST |
S5 | 6 | CPIC-Fkt $$$$$$ failed; RC=$$$ | BC-CST |
S5 | 7 | Error in $$$. Gateway request $$$ | BC-CST |
S5 | 8 | APPC blocks too large | BC-CST |
S5 | 9 | malloc failed; ERR=$$$ | BC-CST |
S6 | 0 | realloc failed; ERR=$$$ | BC-CST |
S6 | 1 | ShmCreate failed; KEY=$$$, RC=$$$ | BC-CST |
S6 | 2 | fread failed; RC=$$$$ | BC-CST |
S6 | 3 | rfopen failed; RC=$$$$, ERR=$$$ | BC-CST |
S6 | 4 | No segment key for SHM pool $$$, Seg=$$$ | BC-CST |
S6 | 5 | Unable to determine path name for the executable $$$$$$$$ | BC-CST |
S7 | 0 | Max. no. $$$ of links per gateway process reached | BC-CST |
S7 | 1 | malloc failed; ERR=$$$ | BC-CST |
S7 | 2 | No CMINIT/CMACCP performed before CPIC function $$$$$$ | BC-CST |
S7 | 3 | snaopen failed; ERR=$$$ | BC-CST |
S7 | 4 | > Partner LU Name: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
S7 | 5 | signal failed; ERR=$$$ | BC-CST |
S7 | 6 | Timeout at CMALLC | BC-CST |
S7 | 7 | snalloc failed; ERR=$$$ | BC-CST |
S7 | 8 | snawrit failed; ERR=$$$ | BC-CST |
S7 | 9 | snactl failed; ERR=$$$ | BC-CST |
S7 | A | flush is not supported in an IBM enironment | BC-CST |
S7 | B | snaread failed; ERR=$$$ | BC-CST |
S7 | C | snadel failed; ERR=$$$ | BC-CST |
S7 | D | snaclse failed; ERR=$$$ | BC-CST |
S7 | E | CPIC status error, function $$, status $$ | BC-CST |
S7 | F | Parameter $$$$$$$$ is missing | BC-CST |
S8 | 0 | Connection to conversation ID $$$$$$$$ not found | BC-CST |
S8 | 1 | tp_start failed; RC=$$$$$$$$ | BC-CST |
S8 | 2 | getlu failed; RC=$$$$ | BC-CST |
S8 | 3 | Allocate failed; RC=$$$$$$$$ | BC-CST |
S8 | 4 | Send failed; RC=$$$$$$$$ | BC-CST |
S8 | 5 | Prepare-To-Recceive failed; RC=$$$$$$$$ | BC-CST |
S8 | 6 | Flush failed; RC=$$$$$$$$ | BC-CST |
S8 | 7 | Receive failed; RC=$$$$$$$$ | BC-CST |
S8 | 8 | CMACCP: No argument -l | BC-CST |
S8 | 9 | get_allocate/receive_allocate/LU62CVCt failed, return code $$$$$$$$ | BC-CST |
S8 | A | Deallocate failed; RC=$$$$$$$$ | BC-CST |
S8 | B | freelu failed; RC=$$$$ | BC-CST |
S8 | C | Tp-End failed; RC=$$$$$$$$ | BC-CST |
S8 | D | Maximum number $$$ of connections reached | BC-CST |
S8 | E | Program name too long | BC-CST |
S8 | F | GwGetLocHost failed; ERR=$$$$ | BC-CST |
S9 | 0 | AsGwConnect failed; RC=$$$ | BC-CST |
S9 | 1 | AsSendToGw failed; RC=$$$ | BC-CST |
S9 | 2 | AsRcvFromGw failed; RC=$$$ | BC-CST |
S9 | 3 | No SAP_CMACCP before CMACCP | BC-CST |
S9 | 4 | NiRead failed; RC=$$$$$ | BC-CST |
S9 | 5 | tcp_read failed; ERR=$$$$ | BC-CST |
S9 | 6 | Parameter $$$$$$$$$$ too long | BC-CST |
S9 | 7 | Invalid value $$$ for parameter PROTOCOL | BC-CST |
S9 | 8 | Incorrect conversation ID $$$$$$$$ | BC-CST |
S9 | 9 | Incorrect CPIC send length $$$$$$$$$$$$ | BC-CST |
S9 | A | Incorrect requested length $$$$$$$$$$$$ | BC-CST |
S9 | B | Incorrect LU length $$$ | BC-CST |
S9 | C | Incorrect TP length $$$ | BC-CST |
S9 | D | Incorrect security password length $$$ | BC-CST |
S9 | E | Incorrect security ID length $$$ | BC-CST |
S9 | F | Incorrect security type $$$ | BC-CST |
S9 | G | Incorrect log mode length $$$ | BC-CST |
S9 | H | Incorrect LU length $$$ | BC-CST |
S9 | I | Incorrect TP length $$$ | BC-CST |
S9 | J | Incorrect log mode length $$$ | BC-CST |
S9 | K | Logical name SAPCPIC_SYMDEST is not defined | BC-CST |
S9 | L | Conversion failed $$$$$$$$ return code = $$$$$$$$ | BC-CST |
S9 | M | Synchronization type $$ does not match, type $$, value $$ | BC-CST |
S9 | N | Incorrect synchronization type $$$ | BC-CST |
S9 | O | Function $$$$$$ is not implemented | BC-CST |
S9 | P | LU6.2 call $$$$$$$$$$$$$$$$$$$$ failed. Return code $$$$$$$$ (hex) | BC-CST |
S9 | Q | > $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-CST |
S9 | R | Incorrect conversation type $$$$ | BC-CST |
S9 | S | Gateway shut down (soft) | BC-CST |
S9 | T | Gateway shut down (hard) | BC-CST |
SA | 0 | Confirmed failed, RC=$$$$$$$$ | BC-CST |
SA | 1 | No overflow block received | BC-CST |
SA | 2 | > Conversation ID: $$$$$$$$ | BC-CST |
SA | 3 | Time limit exceeded; connection closed | BC-CST |
SA | 4 | Session was disconnected by the administrator | BC-CST |
SA | 5 | Communication error, CPIC return code $$$, SAP return code $$$ | BC-CST |
SH | 0 | Shared Objects: DETACH for Area: &A | BC-DWB-TOO |
SH | 1 | Shared Objects: INVALIDATE for Area/Instance: &A &B &C | BC-DWB-TOO |
SH | 2 | Shared Objects: FREE for Area/Instance: &A &B &C | BC-DWB-TOO |
SH | 3 | Shared Objects: Deletion of a Lock: &A &B &C &D &E | BC-DWB-TOO |
SH | 4 | Shared Objects: PROPAGATE for Area/Instance: &A &B &C | BC-DWB-TOO |
SH | 5 | Shared Objects: System-Wide Deletion of Area: &A &B &C | BC-DWB-TOO |
SH | 6 | Shared Objects: FREE_ALL_AREAS_IN_CLIENT &A | BC-DWB-TOO |
SH | 7 | Shared Objects: INVALIDATE_ALL_AREAS_OF_USER &A | BC-DWB-TOO |
SK | 0 | SAPcomm: Error | BC-SRV-COM |
SK | 1 | SAPcomm: Transmission error | BC-SRV-COM |
SK | 2 | SAPcomm: Processing error | BC-SRV-COM |
SK | 3 | >Error( &A ) at status update (spool open &B &C &D &E). | BC-SRV-COM |
SK | 4 | >Error( &A ) at status update (Spool close &B &C ). | BC-SRV-COM |
SK | 5 | >Error( &A ) while printing a received message (open &B &C) | BC-SRV-COM |
SK | 6 | >Error( &A ) while printing a received message (close &B &C) | BC-SRV-COM |
SK | 7 | > SAP user &A is not an SAPoffice user! | BC-SRV-COM |
SK | 8 | > Error assigning SAP name &A to SAPoffice name. | BC-SRV-COM |
SK | 9 | > Message for &A / &B could not be sent: &C &D. | BC-SRV-COM |
SK | A | > Output task &A.&B could not be passed to the SAPcomm server. | BC-SRV-COM |
SK | B | > Incoming message could not be delivered, forwarded to &A by SAPmail. | BC-SRV-COM |
SK | C | SAP user &A has no &B authorization. | BC-SRV-COM |
SK | D | > CPI-C 'RECEIVE' error &A. | BC-SRV-COM |
SK | E | > Status message incomplete. (Error in status &A). | BC-SRV-COM |
SK | F | > Document is incomplete. (Error in status &A). | BC-SRV-COM |
SK | G | > Spool could not be read. | BC-SRV-COM |
SK | H | > Spool entry &A.&B is not a valid SAPcomm task. | BC-SRV-COM |
SK | I | > Message for &A / &B could not be sent by &C. | BC-SRV-COM |
SK | J | > Spool entry &A.&B could not be refreshed (&C). | BC-SRV-COM |
SL | 0 | System operation allowed with temporary license until $$$$$$$$ | BC-SEC-USR-ADM |
SL | 1 | Temporary license until $$$$$$$$ automatically generated | BC-SEC-USR-ADM |
SL | 2 | License check rejected for technical reasons | BC-SEC-USR-ADM |
SL | 3 | No license found for hardware ID $$$$$$$$$$$ | BC-SEC-USR-ADM |
SL | 4 | Error in network ID update => switch to local hardware ID | BC-SEC-USR-ADM |
SL | 5 | Network ID changed, new ID is '&11' | BC-SEC-USR-ADM |
SL | 6 | Update of the network ID failed | BC-SEC-USR-ADM |
SM | 0 | SAML: Path "&a", Code &b, Class &c, Number &d, Text: &e&f&g&h&i | BC-SEC |
SM | 1 | SAML Trace: &a&b&c&d&e&f&g&h | BC-SEC |
SN | 0 | SPNego Authenticator Expired (CreationTime=&A, CurrentTime=&B, UPN=&C) | BC-SEC-LGN |
SN | 1 | SPNego Authenticator NotYetValid (CreationTime=&A, CurrentTime=&B, UPN=&C) | BC-SEC-LGN |
SN | 2 | SPNego Authentication received unsupported NTLM Token | BC-SEC-LGN |
SN | 3 | SPNego Authentication Ticket Expired (UPN=&A) | BC-SEC-LGN |
SN | 4 | SPNego Authentication Ticket NotYetValid (UPN=&A) | BC-SEC-LGN |
SN | 5 | SPNego Authentication used unsupported algorithm (Algorithm Id=&A) | BC-SEC-LGN |
SN | 6 | SPNego Authentication failed due to missing Keytab entry | BC-SEC-LGN |
SN | 7 | SPNego Authentication failed since received token could not be decrypted | BC-SEC-LGN |
SN | 8 | SPNego Authentication failed (SPNego Library RC=&A) | BC-SEC-LGN |
SO | 1 | Send Error, Exception &A | BC-SRV-COM |
SO | 2 | Fax inbox: Error transmitting to &B &C. Exception &A. | BC-SRV-COM |
SO | 3 | Error deleting fax &A &B from server | BC-SRV-COM |
SQ | 1 | SQL Monitor - Defined limit of records exceeded | BC-DWB-TOO-RTA |
SQ | 2 | SQL Monitor - Defined limit of records exceeded - Error | BC-DWB-TOO-RTA |
SR | 0 | SOAP Runtime: &A &B &C &D &E &a &b &c &d &e &f &g &h &i | BC-ESI-WS-ABA-RT |
SR | 1 | SOAP Runtime: &A &B &C &D &E &a &b &c &d &e &f &g &h &i | BC-ESI-WS-ABA-RT |
SR | 2 | SOAP Runtime: &A &B &C &D &E &a &b &c &d &e &f &g &h &i | BC-ESI-WS-ABA-RT |
SR | 3 | SOAP Runtime: &A &B &C &D &E &a &b &c &d &e &f &g &h &i | BC-ESI-WS-ABA-RT |
ST | 0 | No free memory available in class &5. Memory block ID "&6", &9 bytes. | BC-ABA |
ST | 1 | > Memory requirement: $$$$$$$$ bytes | BC-ABA |
ST | 2 | > Memory block ID: $$$$$$ | BC-ABA |
TE | 0 | Non-reproducible error in INFORMIX: | BC-DB-INF |
TE | 1 | > $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ | BC-DB-INF |
TO | 0 | Function locked, update running in parallel. | BC-CTS |
TP | 0 | Tp call failed (RFC RC = &A: RFC message = &B...) | BC-CTS |
TP | 1 | Tp call failed (&B; RC= &A) | BC-CTS |
TR | 1 | &A | BC-TRX-API |
TR | 2 | &A | BC-TRX-API |
TR | 3 | &A | BC-TRX-API |
TT | 0 | Access granted to SECKEY for trusted system &A, installation number &B | BC-MID-RFC |
TT | 1 | Illegal access to SECKEY for trusted system &A, installation number &B | BC-MID-RFC |
TT | 2 | Access granted to SECKEY of dest=&A, ip=&B, whoami=&C | BC-MID-RFC |
TT | 3 | Illegal access: dest=&A, ip=&B, whoami=&C | BC-MID-RFC |
TZ | 0 | Time Zone &A is Set Automatically. Change Using STZAC. | BC-SRV-TIM-TZ |
TZ | 1 | The System's Time Zone Cannot be Determined. Enter it Using STZAC. | BC-SRV-TIM-TZ |
TZ | 2 | Suitable Time Zone was not Found. Contact SAP. | BC-SRV-TIM-TZ |
UF | 0 | liveCache Administration: LC Server "&A", LC Name "&B", CON Name "&C" | BC-DB-LVC |
UF | 1 | Application Server "&A": Action "Stop" performed for liveCache "&B" | BC-DB-LVC |
UF | 2 | Application Server "&A": Action "Initialize" performed for liveCache "&B" | BC-DB-LVC |
UF | 3 | Application Server "&A": Integration data for liveCache "&B" changed. | BC-DB-LVC |
UF | 4 | Application Server "&A": Action "Start" performed for liveCache "&B" | BC-DB-LVC |
UH | 0 | Wildcard for UCON-HTTP | BC-MID-ICF |
UR | A | &A;&B;&C;&D | BC-MID-ICF |
UR | D | Internal statistics memory limit reached | BC-MID-ICF |
UR | S | Stat file limit has been reached | BC-MID-ICF |
UR | T | Verification Test for Unified Connectivity | BC-MID-ICF |
US | 1 | User $$$$$$$$$$$$ locked due to incorrect logon | BC-SEC-USR-ADM |
US | 2 | User SAP* was deleted by user $$$$$$$$$$$$ | BC-SEC-USR-ADM |
US | 3 | Logon attempt for locked user $$$$$$$$$$$$ | BC-SEC-USR-ADM |
US | 4 | Maximum number of users reached | BC-SEC-USR-ADM |
US | 5 | Problems occurred building user buffer for user $$$$$$$$$$$$ | BC-SEC-USR-ADM |
US | 6 | User buffer is too small for user $$$$$$$$$$$$ | BC-SEC-USR-ADM |
US | 8 | Delete usr41 with: $$$ $$$$$$$$$$$$ $$$$$$$$$$$$$$$$$$$$ | BC-SEC-USR-ADM |
US | 9 | Licence check: Hardware ID of message server could not be read | BC-SEC-USR-ADM |
US | A | The SAP password encryption was called several times | BC-SEC-USR-ADM |
US | B | > Report: $$$$$$$$ | BC-SEC-USR-ADM |
US | C | The SAP password encryption was called from an external program | BC-SEC-USR-ADM |
US | D | Issuer &A of the Logon Ticket Could not Be Checked (rc=&>E2) | BC-SEC-USR-ADM |
US | E | Issuer &A of the Logon Ticket Is not in the ACL | BC-SEC-USR-ADM |
US | F | A Logon Ticket That Cannot Be Interpreted Was Received | BC-SEC-USR-ADM |
US | G | Password-based logon deactivated - Logon attempt rejected | BC-SEC-USR-ADM |
US | H | Password trunctated / converted: &a &b &c &d &e &f &g &h &i &j | BC-SEC-USR-ADM |
US | I | HTTP security context cache is full | BC-SEC-USR-ADM |
W0 | 0 | ITS, User session terminated | BC-FES-ITS |
W0 | 1 | ITS, User session terminated | BC-FES-ITS |
W0 | 2 | ITS, Service &A could not be found | BC-FES-ITS |
W0 | 3 | ITS, User session could not be created | BC-FES-ITS |
W0 | 4 | ITS, Required feature not available | BC-FES-ITS |
W0 | 6 | ITS, Requested memory not available | BC-FES-ITS |
W0 | 7 | ITS, Invalid Path &A | BC-FES-ITS |
W0 | 8 | ITS, Invalid Request Method &A | BC-FES-ITS |
W0 | 9 | ITS, Invalid Cookie | BC-FES-ITS |
W0 | A | ITS, &A Buffer too Small, Increase Profile Parameter &B | BC-FES-ITS |
W0 | B | ITS, Memory not Available, Increase Profile Parameter &B | BC-FES-ITS |
W0 | C | ITS, GUI Connection not Switched on. See Transaction SICF | BC-FES-ITS |
W0 | D | ITS, New user session denied due to memory bottleneck. | BC-FES-ITS |
W0 | E | ITS, Template generation due to memory bottleneck - Performance WARNING! | BC-FES-ITS |
W1 | 0 | &A | BC-FES-ITS |
W1 | 1 | Performance: template `%s', function `%s', parameter `%s' is undefined. | BC-FES-ITS |
W1 | 2 | ITS, Error during character conversion (internally), replaced character by # | BC-FES-ITS |
W1 | 3 | ITS, Error during character conversion (input), replaced character by # | BC-FES-ITS |
W1 | 4 | ITS, Error during character conversion (output), replaced character by # | BC-FES-ITS |
WA | 0 | Configuration error in SOAP Runtime: &A | BC-ESI-WS-ABA-RT |
WS | 0 | Error in processing queue of Web service configuration | BC-ESI-WS-ABA-CFG |
WS | 1 | Operation &A; assignment &B; type &C [see application log as well] | BC-ESI-WS-ABA-CFG |
WS | 2 | Operation &A; proxy: &B; LP: &C; task ID: &D | BC-ESI-WS-ABA-CFG |
WS | 3 | Operation &A; URL: &B&C&D | BC-ESI-WS-ABA-CFG |
WS | 4 | Error in technical configuration &A | BC-ESI-WS-ABA-CFG |
WS | 5 | SOAP Runtime Monitoring: &A &B &C &D &E &a &b &c &d &e &f &g &h &i | BC-ESI-WS-ABA-CFG |
WS | 6 | SOAP Runtime Protocol: &A &B &C &D &E &a &b &c &d &e &f &g &h &i | BC-ESI-WS-ABA-CFG |
WS | 7 | Error in asynchronous mass web service configuration. &A&B&C&D&E | BC-ESI-WS-ABA-CFG |
WS | 8 | DT-RT: &A | BC-ESI-WS-ABA-CFG |
WS | 9 | SRT persistence initialization. &A&B&C&D&E | BC-ESI-WS-ABA-CFG |
XI | 1 | Attempt by &A to access Integration Engine unauthorized | BC-XI-IS-IEN |
XI | 2 | Error when updating XI configuration cache. Category: &A, Id: &B | BC-XI-IS-IEN |
XI | 3 | A complete cache refresh was started in the background | BC-XI-IS-IEN |
XI | 4 | Error when creating licence data &A | BC-XI-IS-IEN |
XI | 5 | XI unable to access SLD: "&A" | BC-XI-IS-IEN |
XI | 6 | Attempt to access exchange profile failed: "&A" | BC-XI-IS-IEN |
XI | 7 | Lock against multiple-execution triggered: &A | BC-XI-IS-IEN |