BGRFC - qRFC - der neue Hintergrund RFC
The following messages are stored in message class BGRFC: qRFC - der neue Hintergrund RFC.
It is part of development package SQRFC2 in software component BC-MID-RFC-BG. This development package consists of objects that can be grouped under "ABAP Development for bgRFC".
It is part of development package SQRFC2 in software component BC-MID-RFC-BG. This development package consists of objects that can be grouped under "ABAP Development for bgRFC".
Message Nr ▲ | Message Text |
---|---|
000 | Scheduler (&1) &2 started |
001 | Average throughput: &1 unit(s)/h |
002 | Destination &1: Maximum number of connections reached |
003 | Destination &1: Called server system has reached its resource limit |
004 | Following parameter(s) (&1) of &2 &3 changed by &4 |
005 | Destination &1/queue &2: Unit &3 of user &4 deleted |
006 | Destination &1: Queue &2 of user &3 deleted |
007 | Destination &1: Lock set at start of queue &2 of user &3 |
008 | Destination &1: Lock set at end of queue &2 of user &3 |
009 | Destination &1/queue &2: Unit &3 (with errors) restarted by &4 |
010 | Destination &1/queue &2: Unit &3 unlocked by &4 |
011 | Destination &1 locked by &2 |
012 | Destination &1 unlocked by &2 |
013 | Destination &1: Queue &2 unlocked by &3 |
014 | Destination &1: Unit &2 |
015 | Instance &1: bgRFC Supervisor asynchronous deletion failed |
016 | Call for physical deletion of units failed |
017 | POSTMORTEM CLEANUP call failed |
018 | Call for deletion of table BGRFC_SRV_STATE failed |
019 | Instance &1: Could not start bgRFC supervisor |
020 | Instance &1: Could not start bgRFC scheduler (&2) &3 |
021 | Instance &1: bgRFC supervisor (&2) closed |
022 | &1 &2 &3 &4 |
023 | Reset by RUN_FAILED_UNIT in program context &1 of &2 |
024 | Deleted by DELETE_FAILED_UNIT in program context &1 of &2 |
025 | Destination &1 cannot be used due to inconsistent settings |
026 | Instance &1: &2 dialog work process(es) available |
027 | Instance &1: &2 inbound scheduler(s) and &3 outbound scheduler(s) started |
028 | Unit &1 started by &2 in debugger |
029 | Destination &1/queue &2: Unit &3 |
030 | Communication error: &1 &2 &3 &4 |
031 | Communication error in load balancing of destination &1 |
032 | System error in load balancing of destination &1 |
033 | RFC system error: &1 &2 &3 &4 |
034 | Unit is in manual retry mode: &1 &2 &3 &4 |
035 | Unspecified error: &1 &2 &3 &4 |
036 | Scheduler that executed unit has terminated: &1 &2 &3 &4 |
037 | Update error: &1 &2 &3 &4 |
038 | Context ID does not exist (target system): &1 &2 &3 &4 |
039 | Unit does not exist in database (target system): &1 &2 &3 &4 |
040 | Context ID does not exist in database (target system): &1 &2 &3 &4 |
041 | Unit has invalid status entry (target system): &1 &2 &3 &4 |
042 | Communication error when finding unit status (target system): &1 &2 &3 &4 |
043 | System error when finding unit status (target system): &1 &2 &3 &4 |
044 | Destination &1: Unit &2 of &3 deleted |
045 | Destination &1: Unit &2 (with errors) of &3 reset |
046 | Destination &1: Unit &2 of &3 unlocked |
047 | Supervisor destination for &1 &2 changed by &3 |
048 | Unit &1 started by &2 in debugger, using own user |
049 | Method &1 gets value &2 when called with following parameters: |
050 | No event information for server &1 and context &2 in database |
051 | Statement MODIFY BGRFC_EVENT_PARM gets the value &1: |
052 | Event information for server &1 and context &2 read from database |
053 | Transactional integrity check deactivated |
054 | Reset in program context &1 of &2 using FREE |
055 | Start time of bgRFC scheduler instance |
056 | Current size of program context of bgRFC scheduler instance in KB |
057 | Current throughput of a bgRFC Scheduler instance (units per hour) |
058 | Average throughput of a bgRFC Scheduler instance (units per hour) |
059 | Current number of parallel tasks for this bgRFC destination |
060 | Error rate (%) |
061 | Average data rate for this bgRFC destination (bytes per second) |
062 | Unit &1 executed by &2 for runtime analysis |
063 | Destination &1: Unit &2 locked by &3 for analysis |
064 | Destination &1/queue &2: Unit &3 locked by &4 for analysis |
065 | Unit &1 executed by &2 with trace |
066 | bgRFC needs more than two dialog WPs; only &1 WP(s) currently available |
067 | Destination &1 does not support configured protocol basXML |
068 | basXML conversion; error in metadata collection: &1 |
069 | basXML conversion; error in conversion: &1 |
070 | Instance &1: Supervisor call locked in Autoabap |
071 | due to resource problems in server group &1 |
072 | Ending scheduler(&1) &2 |
073 | Scheduler(&1) &2 is configuring &3 |
074 | Shutting down scheduler(&1) &2 server |
075 | Destination &1: Unit &2 server in shutdown &3 |
076 | Server &1 in graceful shutdown; execution stopped |
077 | Median execution time for this bgRFC destination in seconds |
078 | Maximum execution time for this bgRFC destination in seconds |
079 | Average time in runnable table in seconds |
080 | &1 converting basXML to classic RFC for destination &2 on server &3 |
081 | Destination configured for basXML but not implemented on target system |
082 | Maximum time in runnable table in seconds |
083 | Unit locked at runtime |
085 | Could not perform notification for unit: &1 &2 &3 &4 |
088 | Cannot create units in the upgrade system |
090 | Instance &1 cannot be reached; status check not possible |
093 | bgRFC Supervisor: Server group &1 does not exist |
100 | No lock found for queue &1 |
101 | No lock found for destination &1 |
102 | Invalid queue &1 |
103 | Invalid destination &1 |
104 | No lock found for unit &1 |
105 | No destination name found |
106 | Unit &1 deleted |
107 | Action canceled by user |
108 | Lock for unit &1 deleted |
109 | Queue &1 of destination &2 locked for further units |
110 | Queue &1 of destination &2 locked immediately |
111 | Lock for queue &1 of destination &2 deleted |
112 | No lock found for unit &1 |
113 | Queue &1 of destination &2 deleted |
114 | Unit &1 restarted |
115 | Internal error |
116 | Invalid unit ID |
117 | No errors in unit &1 |
118 | Lock for destination &1 deleted |
119 | Destination &1 locked |
120 | More than &3 units in queue &1 of destination &2 |
121 | No data for this selection |
122 | Locks exist for queue &1 of destination &2 |
123 | More than &1 unit(s) exist(s) for your selection |
124 | Unit &1 is being debugged |
125 | Resource problems with server group &1; local execution |
126 | System error with server group &1; message &2 |
127 | Communication error with server group &1; message &2 |
128 | Resource problem: &1 |
129 | Communication error: &1 |
130 | Do you want to unlock queues for destination &1 &2? |
131 | Do you want to delete queues for destination &1 &2? |
132 | Do you want to unlock type T units for destination &1 &2? |
133 | Do you want to delete type T units for destination &1 &2? |
134 | System error when determining resources: &1 |
135 | Communications error when determining resources: &1 |
136 | No resources in resource cache |
137 | No gateway resources exist |
138 | Incorrect group name in function call for determining resources |
139 | Server group does not get resources (may be incorrectly configured) |
140 | Incorrect information in function call for determining resources |
141 | Unit size is too big (see SAP Note 2772500) |
200 | Requested object &1 currently locked by user &2 |
201 | Requested object &1 currently locked by your own transaction |
203 | No destination selected; function not possible |
204 | Select at least one unit type |
205 | Select at least one procedure |
206 | Unit display not supported for chosen node |
207 | No authorization to display destination |
208 | No authorization for cross-client display |
209 | Select at least one scenario |
250 | Error in scheduler information query: &1 |
300 | bgRFC Supervisor: Logical destination &1 cannot have reference to &2 |
301 | Error when creating supervisor destination &1 |
302 | Supervisor destination &1 created |
303 | bgRFC Supervisor: No load balancing can be defined for destination &1 |
304 | bgRFC Supervisor: Destination &1 cannot have a system number |
305 | bgRFC Supervisor: No server can be entered for destination &1 |
306 | bgRFC Supervisor: No user entered for destination &1 |
307 | bgRFC Supervisor: No password entered for destination &1 |
308 | bgRFC Supervisor: No client entered for destination &1 |
309 | bgRFC Supervisor: System error when testing destination &1 |
310 | User &1 is unknown |
311 | bgRFC Supervisor: User &1 does not have sufficient authorization |
312 | Compression has incorrect value |
313 | Error when saving system-wide customizing settings |
314 | System-wide customizing settings saved |
315 | Cannot check RFC server name of application server &1 |
316 | Queue prefix contains invalid characters |
317 | Inbound destination name cannot be empty or 'NONE' |
318 | Queue prefix &1 is already used |
319 | Check class &1 returns the following for destination &2: &3 |
320 | Destination &1 already exists |
321 | Cannot lock configuration table &1 |
322 | Cannot delete queue prefix &1 |
323 | Configuration entries saved |
324 | Error when querying server groups |
325 | Error when querying servers |
326 | Error when querying dialog work processes for server &1 |
327 | bgRFC Supervisor: Authorization check for user &1 only in client &2 |
350 | Destination name can include syntactical characters only |
351 | Server group &1 is not defined |
352 | Destination &1 saved to database |
353 | Error when saving destination &1 to database |
354 | Server &1: Number of schedulers &2 is incorrect |
355 | Server &1: Number of possible connections &2 is incorrect |
356 | Server &1: Share of gateway resources &2 must be between 1 and 100 |
357 | Server &1: Idle time for scheduler &2 must be greater than 60 seconds |
358 | Server &1: Invalid number of destinations &2 (see long text) |
359 | Server &1: Expiration time for load balancing entries &2 is incorrect |
360 | Invalid application server &1 |
361 | Number of restarts must be greater than zero |
362 | Invalid wait time between restarts of unit (long text) |
363 | Invalid wait between restart attempts for destination (see long text) |
364 | Invalid processing time for destination (see long text) |
365 | Destination &1 not entered |
366 | Not authorized to edit destination &1 |
367 | Internal error in destination &1 |
368 | Incorrect bgRFC version for destination &1 |
369 | Invalid deletion time for processed units |
370 | Internal error on application server &1 |
371 | Application server &1 is not active |
372 | Logon group &1 not entered |
373 | Error when querying logon group &1 |
374 | Incorrect lifetime for logging |
375 | Incorrect compression |
376 | Incorrect number of message entries for each segment, at least 100 |
377 | Inbound destination &1 not entered |
378 | Too few dialog work processes configured on application server &1 |
379 | Configure a sufficient number of dialog work processes (see long text) |
380 | A check class must implement interface &1 |
381 | Cannot create user &1; user already exists |
382 | Cannot delete inbound destination &1; &2 units exist |
383 | Error when creating user &1 |
384 | bgRFC Supervisor: User &1 does not exist; this user must exist |
385 | &1: Enqueue not set; no changes possible |
386 | Server &1: Cannot reset configuration |
387 | Server &1: Configuration does not exist |
388 | Server &1: Configuration already exists; cannot be created again |
389 | bgRFC Supervisor: Could not clean up user: &1 |
390 | bgRFC Supervisor: Password too long |
391 | bgRFC Supervisor: Internal error in password check |
392 | bgRFC Supervisor: Password formally incorrect: &1 |
393 | bgRFC Supervisor: Error when saving destination &1. |
394 | bgRFC Inbound Destination &1: Queues with prefix &2 not empty |
395 | bgRFC Inbound Destination &1: Units still exist |
396 | bgRFC Inbound Destination: qRFC LUWs still exist for queue prefix &2 |
397 | bgRFC Inbound Destination &1: Queue prefix &2 contains invalid characters |
398 | bgRFC Inbound Destination &1: Queue prefix &2 does not exist |
399 | bgRFC Supervisor: System error occurred: &1 |
400 | Scheduler runs under user &3 and client &4, not &1 and &2 |
401 | Scheduler runs on a server other than &1 |
402 | Enqueue error (when scheduler debugging requested) |
403 | Scheduler number not found |
404 | Debug event sent to scheduler &1 |
405 | bgRFC Supervisor: Communication error occurred: &1 |
406 | bgRFC Supervisor: Miscellaneous error occurred |
450 | Cannot create connection to destination &1: &2 |
451 | &1: &2 units with errors |
452 | Destination &1 is locked |
453 | Number of units executed in the last five minutes: &2 (&1) |
454 | Number of executable units in the last five minutes: &2 (&1) |
455 | Max. and average time in executable state: &2 and &3 (&1) |
456 | &1 units exist with basXML to RFC protocol conversion errors |
457 | &1 inbound and &2 outbound schedulers are running |
458 | Server &1: Configured inbound schedulers &2, currently available &3 |
459 | Server &1: Configured outbound schedulers &2, currently available &3 |
460 | &1: Unexpected exception: &2 &3 &4 |
461 | Destination &1 does not have enough resources for a unit size of &2 bytes |
462 | Destination &1 is locked due to errors |
463 | No authorization to run health checks |
464 | User does not have authorization &1 for RFC destination &2 |
500 | Not authorized to edit bgRFC configuration (see long text) |
501 | Not authorized to display bgRFC configuration (see long text) |
502 | Not authorized to edit bgRFC configuration (see long text) |
503 | Not authorized to display bgRFC configuration (see long text) |
504 | Not authorized to edit bgRFC configuration (see long text) |
505 | Not authorized to display bgRFC configuration (see long text) |
506 | Not authorized to edit bgRFC configuration (see long text) |
507 | Not authorized to display bgRFC configuration (see long text) |
508 | Not authorized to edit bgRFC configuration (see long text) |
509 | Not authorized to display bgRFC configuration (see long text) |
510 | Not authorized to edit bgRFC configuration (see long text) |
511 | Not authorized to display bgRFC configuration (see long text) |
512 | Not authorized to edit inbound destinations (see long text) |
513 | No authorized to display inbound destinations (see long text) |
514 | Not authorized to edit supervisor destination of bgRFC (see long text) |
515 | No authorization to create entry in NW bgRFC configuration |
516 | No authorization to create entry in NW bgRFC configuration |
517 | No authorization to create entry in NW bgRFC configuration |
518 | No authorization to create entry in NW bgRFC configuration |
519 | No authorization to create an inbound destination |
520 | No authorization to create entry in NW bgRFC configuration |
521 | No authorization to edit scheduler settings for destination &1 |
522 | No authorization to delete entry in bgRFC configuration |
523 | No authorization to delete entry in bgRFC configuration |
524 | No authorization to delete entry in bgRFC configuration |
525 | No authorization to delete entry in bgRFC configuration |
526 | No authorization to delete inbound bgRFC destination |
527 | No authorization to display bgRFC system settings |
528 | No authorization to display bgRFC server configuration |
529 | No authorization to delete bgRFC server configuration |
530 | No authorization to change the bgRFC supervisor destination |
531 | No authorization for bgRFC configuration transaction &1 |
532 | bgRFC Supervisor: Destination &1 does not exist |
533 | bgRFC Supervisor: Destination &1 has an incorrect type |
534 | bgRFC Supervisor: Could not check user &1: &2 |
535 | bgRFC Supervisor: Could not create user &1 |
536 | bgRFC Inbound Destination &1: Cannot edit entry |
537 | bgRFC Inbound Destination &1 does not exist and cannot be edited |
538 | bgRFC Inbound Destination &1 already exists; it cannot be created again |
539 | bgRFC Inbound Destination &1: Name contains invalid characters |
540 | No authorization to change destination configurations |
541 | bgRFC dest. config. &1: Incorrect value for application check activation |
542 | bgRFC Dest. Config. &1: Incorrect value for automatic unit check &2 |
543 | bgRFC Dest. Config. &1: Incorrect value for max. processing time &2 |
544 | bgRFC Dest. Config. &1: Incorrect value for max. unit retries &2 |
545 | bgRFC Dest. Config. &1: Incorrect value for max. dest. wait time &2 |
546 | bgRFC Dest. Config. &1: Incorrect value for no. of schedulers &2. |
547 | bgRFC Dest. Config. &1: Incorrect value for max. no. of connections &2 |
548 | bgRFC Dest. Config. &1: Incorrect value for unit history activation &2 |
549 | bgRFC Dest. Config. &1: Incorrect time between two automatic retries &2 |
550 | bgRFC Dest. Config. &1: Check class &2 must implement interface &3 |
551 | bgRFC Dest. Config. &1: Entry is invalid and cannot be edited |
552 | bgRFC Dest. Config.: Destination name cannot be empty |
553 | bgRFC Dest. Config. &1: Destination does not exist |
554 | No authorization to display bgRFC destination configuration |
555 | bgRFC Dest. Config. &1: Error when creating configuration instance |
556 | bgRFC Dest. Config. &1: Incorrect qRFC version |
557 | bgRFC Dest. Config. &1: Destination has an incorrect type |
558 | bgRFC Dest. Config. &1: Error when reading destination: &2 |
559 | bgRFC Dest. Config. &1: Dest. config. does not exist and cannot be edited |
560 | bgRFC Dest. Config. &1: Dest. config. exists and cannot be created again |
561 | Server &1: Too few dialog WPs. &2 are required and &3 are available |
562 | bgRFC Supervisor Destination not created |
563 | bgRFC Dest. Config. &1: Appl. check and appl. check active wrong comb. |
564 | bgRFC System Config: No display authorization |
565 | bgRFC System Config: No change authorization |
566 | bgRFC Dest. Config. &1: Check class &3 registers errors: &2 |
567 | bgRFC dest. config. &1: Callback class &2 must implement interface &3 |
600 | No authorization to analyze bgRFC database |
601 | No authorization to repair bgRFC database |
650 | Error in bgRFC Scheduler Monitor |
651 | No scheduler with this ID found |
652 | Status of the user from the supervisor destination |
653 | Status of bgRFC schedulers |
654 | Number of running inbound schedulers |
655 | Number of running outbound schedulers |
656 | Time stamp of the oldest bgRFC units |
657 | Time stamp of the oldest bgRFC unit in the inbound scenario |
658 | Time stamp of the oldest bgRFC unit in the outbound scenario |
659 | Application Server |
660 | Number of dumps in the inbound scenario |
661 | Number of dumps in the outbound scenario |
662 | User name from the supervisor destination |
663 | Status of bgRFC authorization check from supervisor destination |
664 | Lock status of user from supervisor destination |
665 | Last five bgRFC dumps |
666 | bgRFC destination |
667 | Number of bgRFC units in runnable table |
668 | Average time of a bgRFC unit in the runnable table |
669 | Maximum time of a bgRFC unit in the runnable table |
670 | Average execution time of a bgRFC unit |
671 | Maximum execution time of a bgRFC unit |
672 | Ratio between inbound and processed bgRFC units |
700 | BGRFC_DEST_SHIP called without unit ID |
701 | bgRFC UCON RFC rejected |
800 | Destination &1 already has an enqueue lock |
801 | System error when creating enqueue lock for destination &1 |
802 | Conversion job is already running |
899 | Central user administration is active; create user &1 manually |