Job Management Partner 1/Software Distribution Administrator's Guide Volume 2

[Contents][Glossary][Index][Back][Next]

4.26.14 OUTPUT_CONSTRAINTS (specifying the output information)

In the OUTPUT_CONSTRAINTS tag, you can specify the kinds and comparison condition for the information you want to output. You can use this tag in the dcmcsvu command only.

The following shows the contents of specifiable parameters and the correspondence between parameters and command arguments:

Parameter Description Command argument
template Template used for exporting template-key
format Format of the output file csv or par
row Item (row) to be output --
group_membership Group to which the targets belongs --
condition Comparison condition --
unicode Whether a CSV file in Unicode is to be output /uniY or /uniN

Legend:
--: Cannot be specified in a command argument.

Use a template provided by JP1/Software Distribution to specify the items you want to output. This template is the same as the template that the CSV output utility uses. Information is output for the items included in the specified template (the columns in the template). For some templates, you can also perform the following operations:

Organization of this subsection
(1) Format
(2) Explanation
(3) Notes

(1) Format

OUTPUT_CONSTRAINTS{
template = template-key
format = export-file-format (csv or par)
row = items-to-be-output (row)
group_membership = group-of-the-host
condition = condition
unicode = Y-or-N-indicating-whether-a-CSV-file-in-Unicode-is-to-be-output
}

(2) Explanation

#
In YYYY (year), specify a value in the range from 1970 to 2038. If you do not specify a value within this range, an error occurs and the return code 2 is returned. You can omit the portions other than YYYY. The omitted portions are set to their minimum values. If you specify a single-digit value, prefix a 0 to align the digits. If you do not align the digits, an error occurs. The following examples show you how to use date representation correctly:
200
Error
2004
0:00 on January 1, 2004
2003101
Error
20031010
0:00 on October 10, 2003
200401010101
1:01 on January 1, 2004
200312312359
23:59 on December 31, 2003
If you use a date/time representation in the following comparison conditions, an error occurs: A=X, A<>X, A:X1,X2,... Xn, A=[*]X*, A<>X1,X2,... Xn, or A<>[*]X*.

Table 4-37 Items that can be specified in the condition parameter with the J_STAT (job status) template when exporting to a file in CSV format

Item Explanation Setting the values and conditions
jname Job name Inclusion of , or > causes a syntax error.
execdate Execution date/time at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
execsch Scheduled execution date/time at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
sduedate Execution time limit at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
sregdate Scheduled registration date/time at the server. Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
dstname Job destination name Inclusion of , or > causes a syntax error. Use ! or \ for hierarchical representation.
dexecdate ob execution date/time by destination Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
pname Package name Inclusion of , or > causes a syntax error.
pid Package ID Inclusion of , or > causes a syntax error.
cabid Cabinet ID Inclusion of , or > causes a syntax error.
pver Version Inclusion of , or > causes a syntax error.
pgen Generation Inclusion of , or > causes a syntax error.
status Status You can specify the first 1 to 6 characters of the maintenance code for Remote Installation Manager. You can use * or ? in the condition.
If you include , or >, a syntax error occurs. The following comparison conditions cannot be specified: A:X1-X2, A:X1,X2,... Xn, A<>X1-X2, and A<>X1,X2,... Xn.

#
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

Table 4-38 Items that can be specified in the condition parameter during output to a CSV-formatted file (VIRUS (anti-virus product) template)

Item Explanation Setting the values and conditions
host Host name Inclusion of , or > causes a syntax error.
ipaddr IP address Inclusion of , or > causes a syntax error. The number of periods is not checked.
hid Host ID Inclusion of , or > causes a syntax error.
sname Software name Inclusion of , or > causes a syntax error.
sver Software version Inclusion of , or > causes a syntax error.
org Company name Inclusion of , or > causes a syntax error.
lang Language Specify a numeric-only code.
Comparison conditions can be specified in the following formats: A=X, A<>X, A:X1, X2, ... Xn, and A<>X1, X2, ... Xn.
path Path Inclusion of , or > causes a syntax error.
size Size Specify size in numeric only (in bytes). The unit is not required.
A condition containing * or ? cannot be coded; if specified, such a code can cause an error.
sdate Search date/time Specify year, month, day, hour, minute in the YYYYMMDDhhmm format, using numeric only.#1
idate Installation date Specify year, month, day in the YYYYMMDD format, using numeric only.#2
regorg Registered company name Inclusion of , or > causes a syntax error.
reguser Name of registered owner Inclusion of, or > causes a syntax error.
virusver Virus detection engine version Inclusion of , or > causes a syntax error.
vfilever Virus detection file version Inclusion of , or > causes a syntax error.
vstation Virus detection resident/non-resident Specify in the following code:
0: non-resident
1: resident

#1
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

#2
The date format to be used is YYYYMMDD. Although dates require the same specification method as the YYYYMMDDhhmm format, entering hh and mm parts can cause an error. For details about how to represent the date/time, see Table 4-36.

Table 4-39 Items that can be specified in the condition parameter during output to a CSV-formatted file (NO_CLIENT (information on a host on which JP1/Software Distribution is not installed) template)

Item Explanation Setting the values and conditions
ipaddr IP address Inclusion of , or > causes a syntax error. The number of periods is not checked.
type Node type#1 Specify a numeric-only code.
Comparison conditions can be specified in the following formats: A=X, A<>X, A:X1, X2, ... Xn, and A<>X1, X2, ... Xn.
host Node name Inclusion of , or > causes a syntax error.
macaddr MAC address No limit; the number of spaces is not checked.
subnet Subnet mask Inclusion of , or > causes a syntax error.
netaddr Network address Inclusion of , or > causes a syntax error. The number of periods is not checked.
datetime Detection date/time Specify year, month, day, hour, minute in the YYYYMMDDhhmm format, using numeric only.#2
lastupdate Explanation Specify year, month, day, hour, minute in the YYYYMMDDhhmm format, using numeric only.#2
cmnt Comment on node Inclusion of, or > causes a syntax error.

#1
For details about the codes that can be specified, see the dm_nodetype values in C.18 netmdm_host_withoutdm in the manual Description and Planning Guide.

#2
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

Table 4-40 Items that can be specified in the condition parameter during output to a CSV-formatted file (DISCOVERY_INFO (host search results) template)

Item Explanation Setting the values and conditions
ipaddr IP address Inclusion of , or > causes a syntax error. The number of periods is not checked.
type Node ID#1 Specify a numeric-only code.
Comparison conditions can be specified in the following formats: A=X, A<>X, A:X1, X2, ... Xn, and A<>X1, X2, ... Xn.
host Node name Inclusion of , or > causes a syntax error.
macaddr MAC address No limit; the number of spaces is not checked.
subnet Subnet mask Inclusion of , or > causes a syntax error.
netaddr Network address Inclusion of , or > causes a syntax error. The number of periods is not checked.
lastupdate Last update date/time Specify year, month, day, hour, minute in the YYYYMMDDhhmm format, using numeric only.#2
cmnt Comment on node Inclusion of, or > causes a syntax error.

#1
For details about the codes that can be specified, see the dm_nodetype values in C.12 netmdm_discovery_info in the manual Description and Planning Guide.

#2
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

Tables 4-41 to 4-44 list the items you can specify in the condition expression of a condition parameter when exporting to a file in the parameter file format. Unlike when the CSV output utility is used, when you use a command to output a file in parameter file format, you can use the Host attributes and Package attributes template to narrow the conditions.

Table 4-41 Items that can be specified in the condition parameter with the HOST_ATTR (host attribute) template when exporting to a file in the parameter file format

Item Explanation Setting the values and conditions
host Host name Inclusion of , or > causes a syntax error.
ipaddr IP address Inclusion of , or > causes a syntax error.
The number of periods is not checked.
cmnt Comment Inclusion of , or > causes a syntax error.
cdate Creation date/time Use only numbers to represent the date/time in the YYYYMMDDhhmm format.#
date Update date/time Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
pkgupdate Installed package information last update date Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
syupdate System information last update date Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
uupdate User inventory information last update date Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
rupdate Registry information last update date Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
sfupdate Software inventory information last update date Use only numbers to represent the date/time in the YYYYMMDDhhmm format.#

#
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

Table 4-42 Items that can be specified in the condition parameter with the PKG_INFO (package attribute) template when exporting to a file in the parameter file format

Item Explanation Setting the values and conditions
pname Package name Inclusion of , or > causes a syntax error.
pid Package ID Inclusion of , or > causes a syntax error.
cabid Cabinet ID Inclusion of , or > causes a syntax error.
dmcode DM ID code Specify PC or WS. Any other specification causes an error.
pver Version Inclusion of , or > causes a syntax error.
pgen Generation Inclusion of , or > causes a syntax error.
cabname Cabinet name Inclusion of , or > causes a syntax error.

#
The template does not include this item, but it can be specified in the condition parameter.

Table 4-43 Items that can be specified in the condition parameter with the INSTLD_PKG (installed package information) template when exporting to a file in the parameter file format

Item Explanation Setting the values and conditions
host Name of the host where the package is installed Inclusion of , or > causes a syntax error.
ipaddr IP address of the host where the package is installed Inclusion of , or > causes a syntax error. The number of periods is not checked.
pname Package name Inclusion of , or > causes a syntax error.
pid Package ID Inclusion of , or > causes a syntax error.
install Installation Inclusion of , or > causes a syntax error.
newver New version Inclusion of , or > causes a syntax error.
newgen New generation Inclusion of , or > causes a syntax error.
oldver Old version Inclusion of , or > causes a syntax error.
oldgen Old generation Inclusion of , or > causes a syntax error.
date Installation or software search date/time Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#

#
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

Table 4-44 Items that can be specified in the condition parameter with the J_STAT (job status) template when exporting to a file in the parameter file format

Item Explanation Setting the values and conditions
folder Folder name Inclusion of , or > causes a syntax error.
jname Job name Inclusion of , or > causes a syntax error.
jattr Job attribute Inclusion of , or > causes a syntax error.
execdate Execution date/time at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
execsch Scheduled execution date/time at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
sduedate Execution time limit at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
sregdate Scheduled registration date/time at the server Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
dstname Job destination name There are no restrictions. Use ! or \ for hierarchical representation.
jtype Job type Inclusion of , or > causes a syntax error.
dexecdate Job execution date/time by destination Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
pname Package name Inclusion of , or > causes a syntax error.
pid Package ID Inclusion of , or > causes a syntax error.
cabid Cabinet ID Inclusion of , or > causes a syntax error.
dmcode DM ID code Specify PC or WS. Any other specification causes an error.
pver Version Inclusion of , or > causes a syntax error.
pgen Generation Inclusion of , or > causes a syntax error.
cexecdate Installation date/time at the client Use numbers only to represent the date/time in the YYYYMMDDhhmm format.#
result Result Inclusion of , or > causes a syntax error.
status Status You can specify the first 1 to 6 characters of the maintenance code for Remote Installation Manager. You can use * or ? in the condition.
If you include , or >, a syntax error occurs. The following comparison conditions cannot be specified: A:X1-X2, A:X1,X2,... Xn, A<>X1-X2, and A<>X1,X2,... Xn

#
For details about how to represent the date/time and examples of date/time representation, see Table 4-36.

Specify Y or N to indicate whether a CSV file in Unicode is to be output.

Y
Outputs a CSV file in Unicode. Note that only UTF-8 encoding is supported for output of CSV files in Unicode.
This parameter is effective only when the following conditions are satisfied:
[Figure] JP1/Software Distribution Manager is used for command execution
[Figure] The following relational database is used in JP1/Software Distribution:
[Figure] Microsoft SQL Server 2005 or later
[Figure] One of the following output templates is specified:
[Figure] System information
[Figure] Installed package information
[Figure] Registry collection item
[Figure] Microsoft Office products
[Figure] Anti-Virus products
If you have specified par in the format parameter, Y is ignored, if specified.

N
Outputs a CSV file that has not been converted to Unicode.

Note that an error results if you make the specification for output of a CSV file in Unicode both as a command argument and in the parameter file. If you omit this specification from both the command argument and the parameter file, the registry setting for output of CSV files in Unicode becomes effective. For details about the registry setting, see 4.6 Registry settings (JP1/Software Distribution Manager) in the manual Setup Guide.

When a CSV file is output in Unicode, the conversion rules are applied. The conversion rules are the same as for the CSV output utility. For details, see 9.1.4 Conversion rules for outputting CSV files in Unicode in the manual Administrator's Guide Volume 1.

(3) Notes

If the number of specified comparison conditions or groups to which the targets belongs increases, an RDB access error might occur depending on the limitations of DBMS. In case of the error, reduce the number of them.

For your reference, see the following sample maximum values of "Host name" conditions that can be specified.

DBMS type Version Maximum value of "Host name" conditions that can be specified
Embedded RDB 08-51# 255
Microsoft SQL Server 7.0 2,041
Oracle 9i 1,000

#
Version of Job Management Partner 1/Software Distribution Manager