Hierarchy
⤷ BC-CST (Application Component) Client/Server Technology
⤷ STSK (Package) Task Handler, Number Range, Update, Gateway and so on
Basic Data
Data Element | SERVER_REASON |
Short Description | Description of Server Resources |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR64 | |
Data Type | CHAR | Character String |
Length | 64 | |
Decimal Places | 0 | |
Output Length | 64 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
Results of determining server resources.
The possible results are listed below:
0: Resources are available on the server. The text 'Resources ok
', appears in the view.
1: The resource check is deactivated (parameter rdisp/rfc_use_quotas is set to 0).
The other values indicate that the server has no resources currently available for aRFCs.
This could be for the following reasons:
- The server is not running
- The server is incorrectly configured
- An unexpected error has occurred
In these cases the text appears in red. You can find out the exact reason (why the configuration is incorrect) by briefly activating and deactivating the trace for the server. Goto -> Activate/Deactivate Trace). You can find the information in the dispatcher trace file, dev_disp, of the server.
The individual return values are described below. There is a short text for each in yellow.
2: The server does not have enough free dialog work processes.
3: The quota defined for the RFC communication channels is too small. Increase the value of parameter rdisp/rfc_max_comm_entries.
4: The quota defined for the RFC communication channels (rdisp/rfc_max_comm_entries) has been reached.
5: The local queue for asynchronous RFC calls is full.
6: The quota defined for dialog work processes occupied by one RFC user is too small. Increase the value of parameter rdisp/rfc_max_own_used_wp.
7: The quota defined for dialog processes occupied by one RFC user has been reached. (rdisp/rfc_max_own_used_wp).
8: The quota defined for the portion of RFC requests in the dialog queue is too small. Increase the value of parameter rdisp/rfc_max_queue.
9: The quota defined for the portion of RFC requests in the dialog queue (rdisp/rfc_max_queue) has been reached.
10: An error has occurred while determining the length of the request queue.
11: The quota defined for RFC logons to the server is too small. Increase the value of parameter rdisp/rfc_max_login.
12: The quota defined for RFC logons to the server (rdisp/rfc_max_login) has been reached.
13: The quota defined for your own RFC logons to the server is too small. Increase the value of parameter rdisp/rfc_max_own_login.
14: The quota defined for your own RFC logons to the server has been reached (rdisp/rfc_max_own_login).
15: The server is deactivated and cannto process any requests.
16: The server is just being stopped.
17: The server has been stopped.
18: The server is just being started.
19: The server has just been started and is being initialized.
20: The server has an unknown status.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 630 |