![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains problems and corrections for the following manuals of the IBM Tivoli Configuration Manager, Version 4.2 library:
The following information changes apply to the Planning and installation manual.
Uninstalling Tivoli Software Distribution endpoints
After you remove the endpoints using the procedure described in the Tivoli Enterprise: Installation Guide, perform the following steps manually:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.
In "Chapter 2. Planning a Configuration Manager Environment", section "Using Configuration Management in Connected Tivoli Regions", replace the introductory sentence with the following:
This section discusses the requirements for running inventory scans, distributing software, and managing devices and users in connected Tivoli regions. If you plan to use IBM Tivoli Configuration Manager among Tivoli regions, the following conditions must be met:
The following information changes apply to the User's Guide for Deployment Services.
Part 2. "Modelling the Enterprise Configuration", Chapter 5, "Using the Command Line", wccmgui command, add the following note after the first sentence:
Enabling the IBM Voice Kit to Function with the Activity Planner and Configuration Change Manager GUIs.
To enable the IBM Voice Kit to Function with the Activity Planner and Configuration Change Manager GUIs, you must add in the system the system path variable the JRE path installed with the Tivoli_JRE_$INTERP.spb package. For example, if you are working in a Windows environment, add the following path in the system variables drop-down list of the System Properties->Environment Variables dialog box:
C:\Program Files\Tivoli\JavaTools\JRE\1.3.0\jre
wlstpln [-Qoption_to_query=value]
Also, add the following text to the description of the options for the wlstpln command:
-Qoption_to_query=value
Specifies filters to be applied to the query. The query returns all submitted plans, templates, and drafts, based on their recursion settings. The option and its possible values are:
Also, add the following line to the Syntax description:
wmonpln -f [FilterName] [-w]
Also, add the following text in the Options section for the wmonpln command:
Also add the following example to the wlstpln command:
5. To display a list of all plans with recursion type set to days of week, enter the following command:
wlstpln -Qrecursion_type=dow
The following output is displayed:
Plan | Status | Recursion |
test | Template | 1 |
test_plan@06/10/03 09:19:34 | Submitted | 1,2,4 |
submission | Draft | 4,5 |
jupiter | Submitted | st |
juno | Template | 2,3 |
venus | Draft | 3,5 |
The st symbol indicates that the recursion for the specified plan was stopped.
In "Chapter 2. Performing Activity Planner Operations", section "Using Variables", the text in the note at the end of the section should read as follows:
When performing Software Distribution operations, you can use Activity Planner internal variables or Software Distribution variables. To distinguish between these variables, precede the Software Distribution variables with a double $ sign, for example $$(ep_label).
The following information changes apply to the User's Guide for Software Distribution.
Enabling the IBM Voice Kit to Function with the Software Package Editor
To enable the IBM Voice Kit to Function with the Software Package Editor, you must add in the system the system path variable the JRE path installed with the Tivoli_JRE_$INTERP.spb package. For example, if you are working in a Windows environment, add the following path in the system variables drop-down list of the System Properties->Environment Variables dialog box:
C:\Program Files\Tivoli\JavaTools\JRE\1.3.0\jre
If you are removing a software package that has already been installed, you can define or override only those variables that were not solved during the previous install operation.
9. In the sharing control drop-down list, select the appropriate value:
If either auto or only_shared is specified, the version of the objects distributed with the software package is left on the target when a remove operation is performed.
The PackGen.htm help file was changed to reflect the change.
The restart action is executed in relation to four change management operations: install, remove, undo and commit.
The Restart.htm help file was changed to reflect the same change.
Any operation launched from the Software Package Editor hangs the process if the software package being processed is too large. To avoid this problem, tune the "mx100m" value parameters in the appropriate .bat file:
Raise the value in small increments until you find the optimal value for your environment. For example, replace "mx100m" with "-mx150m" and then continue to increase this value until the machine performance improves.
In the Timeout text box, enter the time, expressed in seconds, to wait for the program to complete. See "Setting Timeout Values for a Distribution" on page 315 for more details.
Specify the Execution Timeout. The default is 300 seconds (five minutes). The Execute Timeout refers to the length of time a repeater will wait for Software Distribution to return the result of a distribution after all the data has been sent. This timeout is used to detect network, endpoint, or script failures, for example, a script that is running in an infinite loop. The value specified here overrides the value previously set using the wmdist -s command.
send_timeout | If the software package contains at least one program with a timeout setting, this value is used to extend either the repeater execute_timeout or the repeater send_timeout, depending on where the program action is positioned in the package. See "User Program Timeout" on page 316 for more information. |
By default, Software Distribution overwrites the log file for each distribution of the software package. For more information about logs, see "Software DistributionLogs" on page 307.
with the following new sentence:
By default, Tivoli Software Distribution appends at the end of the log file the information related to the last operation performed on the software package. For more information about logs, see "Software Distribution Logs" on page 307.Operation | Context | Required Role |
---|---|---|
View a software package profile (using the Software Package Editor) | Software package | admin, senior, or super |
Operation | Context | Required Role |
---|---|---|
Modify a software package profile (using the Software Package Editor) | Software package | senior, or super |
Also, by specifying the from_depot attribute of the winstsp command, you can request that a software package be installed directly from the depot, rather than from the source host.
to the following:You can specify the from_depot attribute of the winstsp command, to request that a software package be installed directly from the depot connected to the endpoint, rather than from the source host. The depot must be previously loaded with the software package or the install operation fails.
In Chapter 2. "Creating a Software Package", section "Launching the Software Package Editor", add the following note after the first note:
2. To use the Software Package Editor on Windows XP systems, you must be a member of the Administrators or Power Users group.
The verify operation checks whether files contained in the package are also present on the target system. The operation is successful if the date of the file on the target is equal to or greater than the date of the same file in the package. If the date of the file is older than the date of the same file in the package, the operation fails.
The verify operation does not check whether a file has been changed since it was installed. To perform this check, run a repair operation.
The following information changes apply to the Reference Manual for Software Distribution.
Authorization:
Section "Other SPD File Actions", Sub-section "execute_user_program", Subsection "Format of the execute_user_program Stanza", change the text below:
The value of this attribute can be set to either a number of seconds or to -1. Setting the timeout to -1 indicates that the user program timeout should be set to the highest value between the send_timeout attribute of the swdis.ini file on the endpoint and the repeater timeout setting.
with the following:
The value of this attribute can be set to either a number of seconds or to -1. If the timeout is set to -1, Software Distribution does not perform any action on the program. The distribution waits for the execute_timeout (the highest value between the execute_timeout of the gateway and the send_timeout of the swdis.ini file).
If the execute_timeout is reached and the program did not complete, the distribution interrupts. At the next retry if the program did not complete, the distribution ends in changing (C) status. If you set the timeout to a number of seconds and the program does not complete before the timeout expires, Software Distribution interrupts the program and the distribution ends in an error status.
Table 35, 36, 37, and 38. Change the text contained in the Comments column for the timeout attribute as follows:
Time expressed in seconds to wait for the program's completion. Use this value only if you are certain that your program will complete. See "Format of the execute_user_program Stanza" for detailed information.
Defines the value of a variable used in the software package to add or override existing variables. If you are removing a software package that has already been installed, you can define or override only those variables that were not solved during the previous install operation. When specifying multiple variables, repeat the -D argument before each variable=value.
fatal_failure | Stop running. If some corequisite files are specified in the software package, they are not removed. |
Change the sentence "The following examples show how to use wildcards when specifying directories" to:
"The following example shows how to use wildcards to add directories and files"
Add the following paragraph before the Note:
The following example shows how to use wildcards to remove directories and files.
remove directory destination =" c:\target\new*" descend_dirs = y name = "new*" remove= y remove_empty_dirs = y rename_if_locked = n stop_on_failure = y end
In this example, directories and files that match the pattern in the name are removed from the target. For example, if the following directory and files are present on the target they are removed:
c:\target\newfile.txt c:\target\newdoc.doc c:\target\newweb.txt c:\target\newdir\*.*
If the descend_dirs = n attribute is specified, only files at the top level of the specified directory structure are removed.
For the example above, the following files are removed from the target:
c:\target\newfile.txt c:\target\newdoc.doc c:\target\newweb.txt
The s and r options cannot be used if you are performing a transactional installation (t transactional).
In the format of the restart stanza, add the following line after the during_undo = <none, after, immediately> line:
during_commit = <none, after, immediately>
At the bottom of Table 22. SPD file attributes of the restart stanza, add the following row:
during_commit | Specifies when a restart must be performed during the commit of the package. If set to immediately, the restart takes place when the restart statement is encountered. | |||
none, after, immediately | No | after | restart |
After the description of the -p tp:dest_path option, add the following note:
endpointname_distributionID_timestamp
In the Examples section add the following example after example Number 2:
3. The following command runs a pre-processing script called export_file.sh on the pi003-ept, pi006-ept endpoints to extract data. The extracted data is saved in a file called trans. The trans file is stored in the /sales directory on each endpoint. Afterwards the trans files are retrieved from the endpoints and stored on the source host system, in a sub-directory within the /data/sales destination directory:
wspmvdata -s @pi003-ept,@pi006-ept -t @centoff -r tpost:/tmp/import_file.sh -r spre:/tmp/export_file.sh -P sp:/sales -P tp:/data/sales trans
When the operation is completed the trans file is stored on the source host system under the following paths:
data/sales/pi003-ept_14614660071043934511_20030130144803/trans data/sales/pi006-ept_14614660071043934511_20030130144803/trans
The value of this attribute can be set to either a number of seconds or to -1. Setting the timeout to -1 indicates that the user program timeout should be set to the highest value between the send_timeout attribute of the swdis.ini file on the endpoint and the repeater timeout setting.
with the following text:The value of this attribute can be set to either a number of seconds or to -1. If the timeout is set to -1, Software Distribution does not perform any action on the program. The distribution waits for the execute_timeout (The highest value between the execute_timeout of the gateway and the send_timeout of the swdis.ini.). If the execute_timeout is reached and the program did not complete the distribution interrupts. At the next retry if the program did not complete, the distribution ends in changing (C) status. If you set the timeout to a number of seconds and the program does not complete before the timeout expires, Software Distribution interrupts the program and the distribution ends in error status.
Time expressed in seconds to wait for the program's completion. Use this value only if you are certain that your program will complete. See "Format of the execute_user_program Stanza" for detailed information.
Attribute | Comments | |||
---|---|---|---|---|
Values | Required | Default | Stanzas | |
group_name | Specifies the group name necessary to obtain the specific GID under which the program is executed on a UNIX machine. Use this attribute in case the user name is present in several groups and you want to use a specific GID. This value overrides the GID value set at the package level. If no GID value is set, that is neither unix_group_id nor group_name are specified, the program is executed with root group privileges. This feature is supported for all UNIX endpoints excepting OS/400(R). If you do not specify this attribute the value specified for the unix_group_id attribute is taken. | |||
String | No | None | execute_user_
program |
|
y: yes n: no |
No | n | execute_user_
program |
Attribute | Comments | |||
---|---|---|---|---|
Values | Required | Default | Stanzas | |
user_name | The OS/2(R) user required to execute the program. | |||
String | No | None | execute_user_
program |
In Chapter 2. "Performing Change Management Operations", section "Types of Change Management Operations", sub-section "Verify Operation", add the following second paragraph before the note:
The verify operation checks whether files contained in the package are also present on the target system. The operation is successful if the date of the file on the target is equal to or greater than the date of the same file in the package. If the date of the file is older than the date of the same file in the package, the operation fails.
The verify operation does not check whether a file has been changed since it was installed. To perform this check, run a repair operation.
The following information change applies to the IBM Tivoli Configuration Manager: Release Notes:
Table 1, "Supported Tier 1 operating systems by components and services," shows that the Tivoli Web Gateway component is supported on IBM AIX Versions 5.1 and 5.2. This component is supported only on AIX Version 5.1.
The following information changes apply to the Activity Planner Online Help documentation.
You can use Activity Planner internal variables and data moving or Software Distribution variables. To distinguish between these variables, precede the Software Distribution variables entered in this dialog with a $ sign, for example $$(ep_label).
with the following:
When performing Software Distribution operations, you can use Activity Planner internal variables or Software Distribution variables. To distinguish between these variables, precede the Software Distribution variables with a double $ sign, for example $$(ep_label).
The same text should be added in the help files for all Software Distribution operations performed using Activity Planner.
[ Top of Page | Previous Page | Next Page | Contents ]