1.16.1 Setting up a command execution environment for executing commands on managed hosts
This subsection describes how to set up a command execution environment for performing automated actions and for executing commands on managed hosts from the Execute Command window of JP1/IM - View.
In the following procedure, step 7 is performed only once for an upgrade of JP1/Base from a version earlier than version 8. Step 7 is not necessary for a new installation.
-
Setting up a command execution environment
Execute the jcocmddef command to set up a command execution environment.
We recommend that you adjust the number of commands that can be executed concurrently. To do this, execute the command as follows:
- Example: Set the number of commands that can be executed concurrently to 3
-
jcocmddef -execnum 3
-
Creating an environment variable file
If you will use an environment variable file during command execution, create it.
-
Defining host groups
If necessary, define host groups (groups of hosts at which a command can be executed simultaneously).
-
Settings for enabling command buttons
If you want to execute a command from a command button, execute the jcoimdef command to enable command buttons.
- Example: Enabling command buttons
-
jcoimdef -i -cmdbtn ON
-
Creating a command button definition file
If you want to execute a command from a command button, create a command button definition file.
To pass event information, set true in the inev parameter.
-
Creating a configuration file for converting information
When you pass event information for automated actions and command execution, if you want to convert specific ASCII characters in the event information to be passed to other types of characters, create a configuration file for converting information.
-
Settings for upgrading a command execution history file for version 9 or later
Execute the jcocmdconv command to migrate the command execution history of version 8 or earlier to the command execution history file for version 9 or later. The cautionary notes on upgrading the command execution history file for version 6, version 7, and version 8 are the same as the cautionary notes on upgrading JP1/Base from version 8. For details about the cautionary notes, see 12.2.5 Upgrading from JP1/Base version 8 in the Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide.
For details about when the settings of a command execution environment are enabled or how to create definition files, see the information in the locations described below.
- About command execution environments
-
-
jcocmdconv command
See the chapter that describes commands in the Job Management Partner 1/Base User's Guide.
-
jcocmddef command
See the chapter that describes commands in the Job Management Partner 1/Base User's Guide.
-
jcoimdef command
see jcoimdef in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
-
Creation of an environment variable file
See Environment variable file in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
-
Host group definition
See Host group definition file in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
-
Creation of a command button definition file
See Command button definition file (cmdbtn.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
-
Creation of a configuration file for converting information
See Configuration file for converting information (event_info_replace.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
-