Job Management Partner 1/Software Distribution Administrator's Guide Volume 1
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
9.1.5 Notes on outputting to a CSV file
You should note the following about outputting information to a CSV file:
- If the contents of a package are being output to a CSV file, do not reference the package contents in the Package window. If package contents are referenced while the package is being output to a CSV file, output processing may fail.
- In order to output to a CSV file with the CSV output utility, at least one data item must be registered. If no data is registered, you cannot output to a CSV file. However, if you are using the basic database, an output item title only is output even if no data is registered.
- If the number of specified host-output ranges 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-output ranges that can be specified.
DBMS type |
Version |
Maximum value of host-output ranges 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
- In order for data to be output to a CSV file, all the following conditions must be satisfied:
- Output operation is performed from JP1/Software Distribution Manager.
- The registry settings required for output of CSV files in Unicode have been specified.
- The CSV output utility is started from JP1/Software Distribution Manager.
- JP1/Software Distribution is using a relational database for Microsoft SQL Server 2005 or later.
- One of the following templates has been specified:
System information
Installed package information
Registry collection item
Microsoft Office products
Anti-virus products
- If there are multiple different language data items in a single client (host), Unicode CSV files cannot be output. An example would be when both Japanese-language and Chinese-language software programs have been installed on a client (host) and both programs are used by switching Windows system locales between Japanese and Chinese.
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.