Universal Command Manager for IBM i
Currently, IBM i runs Workload Automation 5.1.1. These pages provide information for that version.
Overview
This page provides information on Universal Command (UCMD) Manager specific to the IBM i operating system.
UCMD Manager for IBM i provides an IBM i command interface to remote computers running the UCMD Server component. UCMD Manager executes remote commands as they would be if you entered the command directly on the remote command line.
On the command line, you must specify a command to execute and a remote Universal Broker. Additional input to each execution of the UCMD Manager command is made via configuration options, which control product behavior and resource allocation for that execution.
Remote standard input and output files are redirected to the UCMD Manager's standard input and output files.
Usage
UCMD Manager for IBM i executes as a CL command. This section describes the command environment, configuration and configuration options, and command line syntax.
Workload Automation 5 for IBM i Commands
The names of the Workload Automation 5 for IBM i commands that are installed in the IBM i QSYS library are tagged with the Workload Automation 5 for IBM i version / release / modification number, 511. The names of the commands installed in the Workload Automation 5 for IBM i product library, UNVPRD511, are untagged.
To maintain consistency across releases, you may prefer to use the untagged names in your production environment. The UCHGRLS (Change Release Tag) program lets you change the tagged command names in QSYS to the untagged command names in UNVPRD511.
(See UCHGRLS (Change Release Tag) Program for detailed information on UCHGRLS.)
These pages references the IBM i commands by their untagged names. If you are using commands with tagged names to run UCMD, substitute the tagged names for the untagged names in these references.
Command Execution Environment
The command is valid in all environments:
- Batch input streams
- CL programs
- REXX procedures
- CL ILE modules
- Interactive processing
- Passed to the system program QCMDEXC (or QCAEXEC) for processing
Configuration
Configuration consists of:
- Setting default options and preferences for all executions of UCMD Manager.
- Setting options and preferences for a single execution of UCMD Manager.
UCMD Manager for IBM i configuration options are read from the following sources:
- STRUCM parameters
- Environment variables
- Configuration file
The order of precedence is the same as the list above; STRUCM parameters being the highest, and configuration file being the lowest. That is, options specified via STRUCM parameters override options specified via environment variables, and so on.
For detailed information on these methods of configuration, see Configuration Management.
Configuration File
The configuration file, UNVPRD511/UNVCONF(UCMD), provides the simplest method of specifying configuration options whose values you do not want changed with each command invocation. These default values are used if the options are not read from one or more other sources.
Some options only can be specified in the configuration file; they have no corresponding command line equivalent. Other options cannot be specified in the configuration file; they must be specified via one or more other sources for a single execution of UCMD Manager.
Configuration Options
This section describes the configuration options used to execute UCMD Manager for IBM i.
Configuration Options Categories
The following table categorizes the configuration options into logical areas of application. Each Category name is a link to a table of options in that category. Each Option Name in those tables is a link to detailed information about that option.
Category | Description |
X.509 certificate related options. | |
Command or script to execute on the remote system. If a script is being executed, the script may reside on the local host on which the Manager is running or the remote host on which the Server is running. It also includes options to control the process environment in which the command executes. | |
Options used to define event generation. | |
Options required for local broker registration. | |
Universal Command message options. | |
Options use to display command help and program versions. | |
Processing options for all the data transferred between the remote and local systems. | |
Alternative methods to specify command options. | |
Network address of the remote system and connection options. | |
Processing options for the standard files transferred between the remote and local systems. At the program interface level, the STDFILE options are specified differently then the other options. There are three types of standard files: stdin, stdout, and stderr. Each standard file can have a different set of options applied. In order to distinguish between the standard files, the options must start with a standard file specification option (STDERR_FILE_SPEC, STDIN_FILE_SPEC, or STDOUT_FILE_SPEC). The standard file options (see #Standard File Category Options) follow the standard file specification option. The STRUCM command interface hides this difference from the user. | |
User account the command executes with on the remote system. |
Certificate Category Options
Option Name | Description |
Location of the PEM formatted trusted CA X.509 certificates | |
Location of Manager's PEM formatted X.509 certificate. | |
Location of Manager's PEM-formatted CRL. | |
Location of Manager's PEM formatted RSA private key. | |
Password for the Manager's PRIVATE_KEY. | |
Specification for whether or not the Broker's X.509 certificate host name field must be verified. | |
Specification for whether or not the Broker's X.509 certificate serial number field must be verified. |
Command Category Options
Option Name | Description |
Remote command to execute. | |
Unique command ID associated the unit of work. | |
Type of command specified with option COMMAND. | |
Allows exit codes from the user process executed by UCMD Server to be translated (mapped) to a corresponding exit code for UCMD Manager. | |
Specification for whether or not the command runs in a login environment. | |
Specification for whether or not manager fault tolerance is used. | |
Local script file to execute on the remote system. | |
Command line options passed to the script file. | |
Type of script file specified by option SCRIPT_FILE. |
Events Category Options
Option Name | Description |
Specification for whether or not product activity monitoring events are generated. | |
Events to be generated as persistent events. |
Local Category Options
Option Name | Description |
Program Lock File (PLF) directory where the program lock files are located. |
Messages Category Options
Option Name | Description |
Language of messages written. | |
Level of messages written. | |
Maximum number of lines written to a trace file before it wraps around. | |
Memory trace table specification. |
Miscellaneous Category Options
Network Category Options
Option Name | Description |
Code page used for text translation. | |
SSL/TLS cipher list for the control session. | |
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 data sessions. | |
Default SSL/TLS cipher used for data sessions. | |
Forces a manager fault tolerant server in a PENDING communication state to COMPLETED state without retrieving the spooled data. | |
Length of time that a Server waits for a reconnect after the user process completes. | |
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. | |
Maximum number of seconds considered acceptable to wait for data communications. | |
Specification for whether or not the network fault tolerant protocol is used. | |
Maximum number of network fault tolerant reconnect attempts. | |
Number of seconds between network fault tolerant reconnect attempts. | |
Specification for whether or not the manager is requesting restart. |
Options Category Options
Option Name | Description |
Specification for whether or not UCMD Server assigns child processes to a single Windows job object. | |
Encrypted command file. | |
Plain text command file. | |
Encryption key used to decrypt an encrypted command file specified by option COMMAND_FILE_ENCRYPTED. | |
UCMD Server options that can be overridden by UCMD Managers. | |
Character code page that Universal Command Manager uses to translate characters within a command file that has been encrypted with the Universal Encrypt utility. |
Remote Category Options
Option Name | Description |
Amount of time that a UCMD Manager will wait for a connection to a remote Universal Broker to complete. | |
Number of IP addresses returned to UCMD Manager following a DNS query issued to resolve a host name. | |
Host in the REMOTE_HOST list that the UCMD Manager will choose to begin its attempts to connect to a remote Universal Broker. | |
Number of times that Universal Command will attempt to resolve the host name of a specified Universal Broker before it ends with a connect error. | |
Situations in which more than one host may be specified in the REMOTE_HOST list when manager fault tolerance (MFT) is enabled. | |
Host or IP address to use for all outgoing IP connections. | |
TCP/IP host name of the remote Broker. | |
TCP/IP port number of the remote Broker. |
Standard File Category Options
Option Name | Description |
Code page used for local text translation on a standard file. | |
Local file used for a standard file instead of the default. | |
Translation mode of a standard file. | |
Code page used for remote text translation on a standard file. |
User Category Options
Option Name | Description |
User ID or account with which to execute the remote command. | |
Password associated with USER_ID. |
Command Line Syntax
The following figure illustrates the command line syntax — using the STRUCM parameter form of the configuration options — of UCMD Manager for IBM i.
After the positional options, which appear immediately after the STRUCM command, the options are organized by category.
STRUCM { CMD(command) [CMDTYPE({cmd|cmdref|rexx})] | SCRFILE(file) [SCRMBR(member)] [OPTIONS(options)] [SCRTYPE(type)] } HOST(hostaddress) [PORT(port)] [USERID(user) [PWD(pwd)] ] REMOTE CATEGORY: [CONNECTTO(seconds)] [DNSEXPAND(*option)] [HOSTSELECT(*option)] [HSTNMRTYCT(count)] [MFTSAFMODE(*option)] [OUTBOUNDIP(host)] OPTIONS CATEGORY: [ASSIGNPROC(*options)] [CMDFILE(file) [CMDMBR(member)] ] | [ECMFILE(file) [ECMMBR(member)] [KEY(key)] ] [ECMFILECP(codepage)] [SERVER(options)] COMMAND CATEGORY: [CMDID(id)] [EXITCDMAP(option)] [LOGIN({yes|no})] [MANAGERFT({yes|no})] MESSAGES CATEGORY: [MSGLANG(language)] [MSGLEVEL(*{trace|audit|info|warn|error})] NOTE: Value *trace* turns trace on. [TRCLINES(lines)] [TRCTBL(size,{error|always|never}) ] [CACERTS(file [lib] ) [CACERTSMBR(member)] [VFYHSTNM({yes|no|hostname})] [VFYSERNUM(number)] ] [CERT(file [lib] ) [CERTMBR(member)] PVTKEYF(file [lib] ) [PVTKEYFMBR(member)] [PVTKEYPWD(password)] ] [CRLFILE(file [lib]) [CRLMBR(member)] ] NETWORK CATEGORY: [AUTH(*{yes|no})] [CODEPAGE(codepage)] [COMPRESS(*{yes|no}[CMPRSMTH*{zlib|hasp}] ) ] [CTLCPHRLST(cipherlist)] [DELAY(seconds)] [DFTCPHR(cipher)] [DTACPHRLST(cipherlist)] [ENCRYPT(*{yes|no})] [FRCCMPLT({yes|no})] [JOBRTN(seconds)]
[MINSSLPROTOCOL(option)] [NETWORKFT({yes|no})] [RESTART({yes|no|auto}) [MANAGERFT({yes|no}) [CMDID(id)] ] ] [RETRYCNT(number)] [RETRYINT(seconds)] [SERFILE(output_file)] [SERMBR(member)] [SERMODE(*{text|binary})] [SERCPG(codepage)] [SERRCP(codepage)] [SINFILE(input_file)] [SINMBR(member)] [SINMODE(*{text|binary})] [SINCPG(codepage)] [SINRCP(codepage)] [SOTCPG(codepage)] [SOTFILE(output_file)] [SOTMBR(member)] [SOTMODE(*{text|binary})] [SOTRCP(codepage)] LOCAL CATEGORY: [PLFDIR(directory)] MISCELLANEOUS CATEGORY: [COMMENT(user-defined string)] STRUCM VERSION(*{yes|no})
* The command file (CMDFILE or ECMFILE) can contain some or all required and/or optional configuration options, including CMD (or SCRFILE) and HOST. If a command file is specified on the command line, and it contains the required CMD (or SCRFILE) and HOST options, those options do not have to be specified additionally on the command line.