SERVER_OPTIONS

Systemwide variable that contain various server settings for performance improvement and trace outputs.

• Format: 16 digit strings

  Activate the particular settings by inserting the respective letters in the relevant positions. The character N is used to deactivate a server option.

  Example

  Options 1, 2, 6 and 8 are activated:

  SERVER_OPTIONS SPNNNUNENNNNNNNN

  Each digit represent a particular server setting. These values can be read using the script function GET_UC_SETTING.

  Digits:

  1. (DB2) Avoids deadlocks especially when starting workflows.

     Character: S

  2. (DB2) Avoids deadlocks especially when deactivating workflows.

     This setting is ignored, the behavior always corresponds to the value P.

     Character: P

  3. With this setting, the statistical records are not checked when a server cold start is performed. This improves the booting performance of large Automation Engine systems (especially in combination with Oracle databases) because in most cases, the statistical records remain unchanged.

     This is an update statement against the database and using a NULL value column and as far we know in Oracle databases null values are not within the index.

     This update will set the timestamp4 for all records within AH where we do not have any EH anymore and the timestamp4 is null.

     In large systems, this simple update could take up to 10 minutes on start-up. To avoid this, it can be turned off. There is no hard and fast definition for a large system. A large system could consist of tens of thousand sof activities, but it depends on many factors such as database speed and IO.

     Character: S

  4. Extends traces so that memory leaks are found more easily.

     Character: M

  5. XML messages (such as OS messages) can contain invalid characters. With this setting, an additional message and the relevant XML message (memory dump) are written to the server log file.

     Character: X

  6. (DB2) An additional way to avoid deadlocks.

     Character: U

  7. Configuration for the restart behavior of tasks.
     In manual restarts, Generate Task at: Runtime is ignored. Therefore, the processing in Script objects and Sync objects that use this setting is swapped over. This option prevents the setting Generate Task at: Runtime from being deactivated.

     Character: G

  8. (DB2) Avoids database problems especially when activating file transfers.

     Character: E

  9. If you activate this option, agents are no longer disconnected. Instead, a warning is printed to the log in the frequency of KEEP_ALIVE as long as this connection is inactive. The value KEEP_ALIVE is taken from UC_HOSTCHAR_*.

     Character: D

  10. Configuration for report lengths in Sync object reports.
      
      Checks, accesses, and modifications of Sync objects are described in detail in the task's reports. Exact logging can negatively affect performance when many Sync objects are in use. Use this server option to handle report lengths, thereby improving performance. It is used to reduce the amount of LOGGING=IO for the database to increase the speed of the Automation Engine.

      S: The Automation Engine does not create Sync object reports.

      N: Only Sync object modifications are logged.

      A: The Automation Engine logs Sync object modifications and unsuccessful Sync object checks in the report.

      Character: S or A

  11. Extended output of time-critical database accesses in the log file.

      The Automation Engine logs the bind parameters of all time-critical database accesses whose select statements take more seconds than specified in this server option. Any number between 1 and 9 can be specified.

      Regardless of this setting, bind parameters will not be logged in insert statements.

      Tip: We recommend using 3 when you use this option. This means that the bind parameter of all selects that take more than 3 seconds will be logged. Therefore, the Automation Engine logs the BIND VARIABLES for long running SQL statements within the LOG file without the need for a trace.

      Character: Number

  12. Used to determine whether report messages for import/export processes are written to the client report.

      N - Report messages for import/export processes are written to the client report.

      Y - Report messages for import/export processes are skipped.

      If the value is set to something different than N, the value Y is used.

      Character: Y or N

  13. (Oracle) Alternative method to read server messages from the queue. This method is slower than the default method.

      Character: S

  14. This option has the effect that the output of the script statement :PRINT is also written to the Automation Engine log if you activate the tasks

      • using Generate Task at: Runtime
      • via the script function ACTIVATE_UC_OBJECT
      • as an alarm object.

      Doing so can result in extensive reports and log files. Deactivate this server option in order to increase the performance of your AE system.

      Character: P

  15. Affects the naming of wildcard file transfers from or to z/OS if the source file name includes several wildcard characters.

      Example

      Source is UC4*A.AAA.AA.AAA.A????.A????.A??????

      Target is UC4*

      Y: The target file name is correctly built according to the wildcard characters. After the transfer, the file UC4ZZA.AAA.AA.AAA.A1111.A1111.A111111 is given exactly the same name.

      N: The characters that start with the first wildcard until the last character minus one are ignored. After the transfer, the file UC4ZZA.AAA.AA.AAA.A1111.A1111.A111111 is given the name UC41.

      This option is ignored in the new file transfer protocol. Wildcards are always correctly resolved.

      Character: Y

  16. Not used.

      Character: N

• Default: All Server options are deactivated (NNNNNNNNNNNNNNNN)

• Restart required: No

See also:

UC_SYSTEM_SETTINGS - Systemwide Settings