Release Notes

4Information Catalog Center log file not generated when importing tag language files

4If an Information Catalog Center log file is not generated when you import 4tag language files to the Information Catalog Center, perform the following 4troubleshooting steps: 4

4When running db2icmimport from a command line:

4

• 4If output files were not generated (.xml, .out, .err, 4.log), there is probably an error on the command line. Verify 4that the first five arguments, which are UserId, Password, Database, Catalog, 4and Tagfile, are correct. View the syntax by entering the 4db2icmimport command. If this does not solve the problem, 4modify db2icmimport to capture the output of the 4db2javit command by using the -g option to save the output to a 4file. For example:

  4db2javit -j:com.ibm.db2.common.icm.tag.IcmImport -w: -i: 
  4   -o:"-Xmx128m -Xms32m" -g:"d:\temp\myimport.trc" ...

• 4If a log file was not generated, there is usually a parsing error. 4Look at the .xml file and the .out file. If you can, 4insert a ":COMMIT.CHKPID(DEBUG)" command at the beginning of the 4tag language file. This command generates debug report messages and 4checks the .xml and .out files for parsing errors.
• 4After parsing, errors should appear in the .log file. When 4the debug report is being generated, look at the .log file and the 4.out file for information.
• 4Always check the .err file to see if there is a run-time 4error. 4

4

4When importing tag language files using the Information Catalog Center 4GUI:

4

• 4When you import tag language files using the GUI interface, no .out 4or 4.err files are generated.
• 4If a .log or .xml file is generated, try to debug by using 4those files.
• 4If a .log or .xml file is not generated or does not help, 4run the import process from a command line to get more information. 4

4