Use the putfile command to transfer a file from a local source to a remote managed system.
Transfer file sizes exceeding this limit can require additional response time and IBM Tivoli Monitoring environment consumption. If the getfile, putfile, executeaction and executecommand operations will be executed frequently, monitor the CPU utilization and network activity of the hub monitoring server and remote monitoring servers before and during these operations to ensure that resource consumption is acceptable. If resource consumption is too high, consider reducing the number of concurrent operations and the frequency of the operations.
The hub monitoring server, the targeted monitoring agents, and any remote monitoring servers to which the targeted agents are connected must be at IBM Tivoli Monitoring v6.2.2 Fix Pack 2 or later. If the Tivoli Enterprise Monitoring Agent component is at the IBM Tivoli Monitoring v6.2.2 Fix Pack 2 or later level, all the agents installed in the same CANDLEHOME directory at the endpoint are capable of handing this command. For this command, the specified system cannot be an i5/OS or z/OS monitoring agent.
Relative and absolute path support at the endpoint
When running this command between a UNIX or Linux system and targeting a Windows monitoring agent, you must replace the backslashes with forward slashes in the path definitions for the -d|--destination option. It is best to use forward slashes for tolerance with Windows systems. For example, if you want to run the command from a UNIX system to place the monitor agent's configuration file in the C:\IBM\ITM\tmaitm6 directory on a Windows system, use the following command:
./tacmd putfile -m Primary:WINDOWS:NT -s ./kntenv -d C:/IBM/ITM/tmaitm6/kntenv
-t text
File names
When either the remote file's directory or name and the destination file's directory or name contain spaces, you must include double quotation marks around the respective directory and filename. For example, run the following command from a UNIX system to place the monitoring agent's configuration file in the C:\Program Files\ITM\tmaitm6 directory
./tacmd putfile -m Primary:WINDOWS:NT -s /opt/IBM/ITM/kntenv
-d "C:/Program Files/ITM/tmaitm6/kntenv" -t text
When working with file and directory names that have nonalphanumeric characters (for example, ! @ #, etc), the path and file references for either the -s|--source or -d|--destination option must be surrounded by double quotation marks. However, paths that include an asterisk (@) sign must be escaped with the asterisk (@) sign. The path user@home@directory is escaped as follows:
user@@home@@directory
Variable substitution
Run this command using an environment variable for both the -d|--destination and the -s|--source options. If used for the -d|--destination option, it is for the specified monitoring agent’s managed system rather than the local environment where the command is issued. If used for the -s|--source option, it is for the local environment where the command is issued.
The environment variable format is @NAME@. The following characters are valid as the first character of any name, or any subsequent character:
The following characters are valid as any character in any name except the first:
In the following example, CANDLEHOME on the local computer is /opt/IBM/ITM and CANDLE_HOME on the managed system is c:\IBM\ITM:
./tacmd putfile -m Primary:WINDOWS:NT -s @CANDLEHOME@/kntenv
-d @CANDLE_HOME@/tmaitm6/kntenv -t text
where:
See the example in the description of this command.
See Table 6.
Return to Table 1.
[ Top of Page | Previous Page | Next Page ]