Universal Command Server for IBM i - Configuration
Overview
UCMD Server configuration consists of defining runtime and default values. This section describes the Server configuration options.
Manager Override
A UCMD Manager can specify certain UCMD Server configuration options when it makes its request for command execution to the UCMD Server. The UCMD Manager command line option -server is used to specify UCMD Server options.
Which options are available for UCMD Manager override depend on the UCMD Server platform and release. The configuration options listed below describe the UCMD Manager override option only if applicable. If the option is not listed, than no UCMD Manager override is available.
The UCMD Manager is not notified of override errors. The UCMD Server logs the error and continues processing the request.
Configuration File
The configuration file provides the simplest method of specifying configuration options whose values you do not want changed with each command invocation.
Configuration options are specified in the UCMD Server configuration file. The configuration file name is specified in the UCMD Server component definition. The default file name is UNVPRD511/UNVCONF(UCMDS). This file can be edited manually with any text editor (for example, Notepad or Source Edit Utility (SEU)).
Configuration Options
The following table identifies all UCMD Server for IBM i configuration options. Each Option Name is a link to detailed information about that option.
Option Name | Description |
Specification for whether or not product activity monitoring events are generated. | |
Specification for whether or not spooling is permitted. | |
Code page used for text translation. | |
Default command type. | |
Specification for whether or not data integrity checks are performed on all standard I/O files. | |
Specification for whether or not data is compressed on all standard I/O files. | |
Specification for whether or not data is encrypted on all standard I/O files. | |
SSL/TLS cipher list for the control sessions. | |
Message severity that terminates the initiator. | |
Events to be generated and processed as persistent events. | |
Job log processing. | |
Specification for whether or not copies of the joblog from the UCMSINIT job and (optionally) from the job started with USBMJOB are written to a spool file. | |
Number of seconds that a disconnected server remains active after user process completes. | |
Frequency of how often a keepalive message is sent. | |
Specification for whether or not to set up a login environment. | |
Level of messages written. | |
Minimum SSL/TLS protocol level that will be negotiated and used for communications channels. Note This option was introduced to IBM i in version 5.1.1.0. | |
Specification for whether or not the server accepts the network fault tolerant protocol. | |
Script type of the user job being run. | |
Length of time to wait for standard I/O to close before the server process exits. | |
Maximum number of lines to write to a trace file. | |
Memory trace table specification. | |
Specification for whether or not the IBM i user profile under which a process is run is to be used as the source for the job accounting code | |
Specification for whether or not user authentication is active. |