Job Management Partner 1/Software Distribution Setup Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
(1) Tag specification rules
The following describes the rules for specifying the tags:
- Express tags as upper case letters, symbols, and space.
- A tag and a value cannot consist of multiple lines.
- A tag and a comment cannot be on the same line.
- Neither comment nor tag can be on the same line as <POLICY> or </POLICY>.
- A value for a tag cannot be omitted.
- Tags between <POLICY> and </POLICY> can be specified in any order.
(2) Descriptive notations for tags
This manual uses the following format to describe each tag in the automatic maintenance policy files:
- Format
- Indicates the format of the tag.
- Description
- Describes how to specify the tag.
- Note
- Describes notes about specifying the tag.
- Example
- Presents a coding example when the value of a tag is not a number.
(3) <DEST> (sets the type of automatic maintenance)
This tag sets the type of automatic maintenance. Make sure that you always set this tag.
- Format
- <DEST>automatic-maintenance-type
- Description
- Specify 0 or 1 as the type of automatic maintenance.
| Automatic maintenance type |
Value |
| Host group |
0 |
| ID group |
1 |
- Notes
- No value other than 0 or 1 can be specified.
- Any space or tab is ignored before and after the value.
(4) <KIND> (sets a policy type)
This tag specifies the policy type. Make sure that you always set this tag.
- Format
- <KIND>policy-type
- Description
- Specify a value in the range from 0 to 3 as the policy type. The value permitted for policy type depends on the value of <DEST>.
| Value of <DEST> |
Policy type |
Value |
| 0 (host group) |
IP address |
0 |
| New host |
1 |
| OS type |
2 |
| User inventory item |
3 |
| 1 (ID group) |
New host |
1 |
| User inventory item |
3 |
- Notes
- No combination other than the above is permitted.
- Any space or tab is ignored before and after the value.
(5) <COND> (sets a condition)
This tag sets the condition for the policy type specified in <KIND>.
The tag to be specified depends on the values of <DEST> and <KIND>.
The following table shows the tags to be specified according to the combination of <DEST> and <KIND>:
| Value of <DEST> |
Value of <KIND> |
Tag to be specified |
| 0 (host group) |
0 (IP address) |
<COND IP_ADRESS> |
| 2 (OS type) |
<COND OS> |
| 3 (User inventory item) |
<COND USER> |
| 1 (ID group) |
3 (User inventory item) |
<COND USER_VALUE> |
The following describes how to specify each tag.
(a) <COND IP_ADRESS> (sets an IP address)
If an IP address is set as the condition of automatic maintenance for host groups, this tag specifies the range of IP addresses that are to be the target of automatic maintenance.
- Format
- <COND IP_ADRESS>IP-address-range
- Description
- Specify a range of IP addresses using a hyphen (-).
- The permitted range of IP addresses is from 0.0.0.0 to 255.255.255.254.
- A single-digit or two-digit value may not require leading zeros.
- Notes
- Make sure that the specified range begins with a smaller IP address, followed by a hyphen (-), then a larger IP address.
- Neither space nor tab may be placed before or after the hyphen (-).
- Any space or tab is ignored before and after the value.
- Example
- <COND IP_ADRESS>172.16.10.0-172.16.10.255
(b) <COND OS> (sets an OS type)
If an OS type is set as the condition of automatic maintenance for host groups, this tag specifies the OS type that is to be the target of automatic maintenance.
- Format
- <COND OS>OS-type
- Description
- Specify the OS type as a value in the range from 0 to 22. Only one value can be specified at a time.
| OS type |
Value |
| Windows 95 |
0 |
| Windows 98 |
1 |
| Windows Me |
2 |
| Windows NT |
3 |
| Windows 2000 |
4 |
| Windows XP |
5 |
| Windows Server 2003 |
6 |
| MS-DOS+Windows |
7 |
| Windows CE |
8 |
| Windows CE .NET |
9 |
| HP-UX |
10 |
| Solaris |
11 |
| AIX |
12 |
| HP Tru64 UNIX |
13 |
| HI-UX/WE2 |
14 |
| Linux |
15 |
| Windows Vista |
19 |
| Windows Server 2008 |
20 |
| Windows 7 |
21 |
| Windows Server 2008 R2 |
22 |
| Windows 8 |
23 |
| Windows Server 2012 |
24 |
- Notes
- To set multiple OS types in policies, create multiple different policies.
- Any space or tab is ignored before and after the value.
(c) <COND USER> (sets a user inventory item (host group))
If a user inventory item is set as the condition of automatic maintenance for host groups, this tag specifies the user inventory item that is to be the target of automatic maintenance.
- Format
- <COND USER>user-inventory-item-(hierarchy-1),..., user-inventory-item-(hierarchy-6)
- Description
- Specify a user inventory item for each hierarchy separated by a comma (,). You can specify a maximum of six hierarchies of user inventory items.
- Notes
- The value for a user inventory item cannot be a space or tab alone.
- There must be no comma (,) after the last hierarchy.
- An error results if nothing is specified between two commas.
- All trailing spaces are ignored.
- Example
- <COND USER>headquarters-name,department-name,employee-number
(d) <COND USER_VALUE> (sets a user inventory item (ID group))
If a user inventory item is set as the condition of automatic maintenance for host groups, this tag specifies the user inventory item to be registered to the ID group and the selection item for the user inventory item.
- Format
- <COND USER_VALUE>user-inventory-item, selection-item-for-user-inventory-item
- Description
- Specify a user inventory item and a selection item for user inventory item separated by a comma (,). You can set a maximum of 10 tags in a single policy.
- Notes
- The value for a user inventory item cannot be a space or tab alone.
- All trailing spaces are ignored.
- Example
- <COND USER_VALUE>headquarters,software-development-department
- <COND USER_VALUE>department,public-affairs-department
- <COND USER_VALUE>section,section-1
(6) <PATH> (sets a path)
This tag sets a path where the host group is to be created.
- Format
- <PATH>path
- Description
- Specify the path where the group is to be created.
- You can specify multiple paths separated by a \. Each path must be no longer than 32 bytes. If multiple paths are specified, the permitted maximum length is 190 bytes including the host group name and delimiters (\).
- The path names cannot include \, /, *, ", ', :, !, |, ., <, >, ?, @, %, or a space.
- Notes
- If <DEST>1 is specified, <PATH> is ignored, if specified.
- The same name cannot be specified for each path.
- When a new path is specified, that path is created during execution of automatic maintenance.
- Any space or tab is ignored before and after the value.
- Example
- <PATH>\group1\group2\group
(7) <NAME> (sets a host group name or an ID group name)
This tag specifies the host group name or ID group name that is to be the target of automatic maintenance.
- Format
- <NAME>host-group-name-or-ID-group-name
- Description
- Specify a host group name or ID group name in a maximum of 32 bytes. It cannot contain \, /, *, ", ', :, !, |, ., <, >, ?, @, %, or a space.
- Notes
- If you have specified the <DEST>0 tag and 0, 1 or 2 as the value of <KIND>, make sure that you specify a host group name.
- If you have specified the <DEST>1 tag, make sure that you specify an ID group name.
- The specified name cannot be the same as the host group name that was specified in path.
- Any space or tab is ignored before and after the value.
(8) <TARGET> (sets a host type)
This tag sets the host type that is to be the target of automatic maintenance. Specification of this tag is optional.
- Format
- <TARGET>host-type
- Description
- Specify 0 or 1 as the host type.
| Host type |
Value |
| All hosts |
0 |
| Clients only |
1 |
- Notes
- If the value of <KIND> is 0 or 2, make sure that the values of <TARGET> are the same.
- If this tag is omitted and <DEST>0 is specified, 0 is automatically set; if <DEST>1 is specified, 1 is automatically set.
- Any space or tab is ignored before and after the value.
(9) <SUBVER> (sets whether or not there is an OS sub-version)
If OS type is specified as the policy type, this tag sets whether or not there is an OS sub-version. Specification of this tag is optional.
<SUBVER> can be specified only when OS type is specified as the policy type.
- Format
- <SUBVER>whether-or-not-there-is-an-OS-sub-version
- Description
- Specify 0 or 1 to indicate whether or not there is an OS sub-version.
| Whether or not there is an OS sub-version |
Value |
| No |
0 |
| Yes |
1 |
- Notes
- If this tag is omitted, 0 is automatically specified.
- If the specified policy type is not OS type, this tag is ignored, if specified.
- Any space or tab is ignored before and after the value.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.