:SET_UC_SETTING
Script Statement: Changes the system settings while the system is running.
Syntax
:SET_UC_SETTING Setting, Component, Value
Syntax |
Description/Format |
---|---|
Setting |
The system setting to be changed. Format: AE name, script literal or script variable Allowed values:
|
Component |
The system setting component to be changed. Format: script literal, script variable, AE name or script function For WORKLOAD_MAX, WORKLOAD_MAX_FT and WORKLOAD_MAX_JOB:
For SET_TRACE:
For SERVER_MODE:
|
Value |
New value assignment for the system setting. Format: script literal, script variable or script function For WORKLOAD_MAX, WORKLOAD_MAX_FT and WORKLOAD_MAX_JOB:
For SET_TRACE:
For SERVER_MODE:
|
Trace Target |
Target traces are written into. Format: AE name, script literal or script variable For SET_TRACE:
|
Memory Buffer Size |
Size of memory provided to be written. Format: AE name, script literal or script variable For SET_TRACE:
|
Search Text |
Text to be searched for within the traces. Format: AE name, script literal or script variable For SET_TRACE:
|
Currently, you can use the script statement :SET_UC_SETTING in order to change three system settings. Your modifications are valid until a new value is assigned or until the server processes or the agent are terminated.
To change the system settings, you need the authorization "Modify at runtime" and the privilege "Create diagnostic information".
Note: The script statement causes all open transactions of the script to be written to the AE database. For more information, see Script Processing.
Warning! If you change trace options for WPs, you may change them only for all of them together. It is not possible to change them for individual WPs.
Warning! You should change the trace options for CPs one at a time.
Changing Trace Options
By setting trace options, you can use a script to log the behavior of work processes and agents in exceptional cases. Neither the work processes nor the agents need to be terminated for this purpose but setting trace options can result in a lot of data that is accumulated and performance losses can be a result thereof.
Note: Set trace options only in close cooperation with the Support team.
To modify the trace options, you can use the Setting SET_TRACE. The Value is a 16-digit string. Each digit corresponds to a particular trace flag (such as the first position in a TCP/IP trace).
The order of
the trace flags complies with the order that is used in the properties dialog in the Administration perspective for server
processes and agents.
Note: If you reboot only one work process, it will use the trace options that are specified in the INI file. All other work processes use the values that are specified by using the script statement :SET_UC_SETTING until they are rebooted.
Examples
The first example sets the number of resources provided by the agent WIN01 for jobs and file transfers to 1000. The result is written to the activation report.
:SET_UC_SETTING WORKLOAD_MAX, WIN01, 1000
:SET &RET# = GET_UC_SETTING(WORKLOAD_MAX_JOB,
WIN01)
:PRINT &RET#
The second example retrieves the name of the AE system and then activates the TCP/IP trace for its work processes.
:SET &TRC# = GET_UC_SYSTEM_NAME()
:SET_UC_SETTING
SET_TRACE, &TRC#,
"1000000000000000"
The following example changes the server process AE#WP003 to a dialog process provided that it is active.
:IF SYS_SERVER_ALIVE("AE#WP003") = "Y"
: SET_UC_SETTING "SERVER_MODE", "AE#WP003", "D"
:ELSE
: SEND_MSG "ADMIN","AE","Work process AE#WP003
is not active!"
:ENDIF
In this example, the trace options for the AE system are set with noted values to look for the first Job that ended abnormally (error message 11003).
Note: If such message is found on a trace, the trace is written into a file , and not into the memory.
:SET_UC_SETTING SET_TRACE, &$SYSTEM#,"2400000000000000", "MEMORY", "128", "U00011003"
For more information, see the agent's properties dialog in the Administration perspective. For more information, see Agents (HOST).
In this last example the trace options for the agent WINAGENT01 are set with noted values to look for the first File Transfer that ended abnormally.
Note: If such message is found on a trace, the trace is written into a file , and not into the memory.
:SET_UC_SETTING SET_TRACE, "WINAGENT01", "2400000000000000", "MEMORY", "128", "File Transfer * ended abnormally."
For more information, view the agent's properties from in the Administration perspective.
See also: