analytics/msgsdk/rspecupgrademsgs_en.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed Materials - Property of IBM

IBM Cognos Products: rspecupgrade

(C) Copyright IBM Corp. 2005, 2017

US Government Users Restricted Rights - Use, duplication or disclosure 
restricted by GSA ADP Schedule Contract with IBM Corp.
-->
<!-- COPYRIGHT_DATA { 'YEAR':[2005, 2014], 'RELEASE':['danube', 'caspian_rp1', 'colorado_rp1'], 'VISIBLE':'YES', 'COMPONENT':'rspecupgrade' }-->
<!--All lines above the COPYRIGHT_DATA  line will be replaced when copyright notices are generated. -->

<stringTable xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" localization="Product Locale" usage="Message source for CCLMessageFramework"  xsi:noNamespaceSchemaLocation="..\..\..\cclcore/prod/Resources/CCLMessageFile.xsd">
	<component name="RSU">
		<section name="UPG" usage="This section contains messages used by the RSUpgrade component of the Report Server.  These messages should be related to confguration, infrastructure, bad parameters, etc.  Not directly related to the report specifcation being upgraded.  Because of historical code there are messages present that do relate to the report specification but they should be migrated to the SPC section.">
			<string name="INVALID_REPORT_SPEC" usage="The report spec that is to be upgraded is not valid." errorCode="0026">The report specification to be upgraded is not valid.</string>
			<string name="MIGRATION_SUCCESS" usage="Migration completed sucessfully" errorCode="0030">Migration successful.\nThe result is in "<param index="1" name="filepath" type="string" usage="file path"/>".
			</string>
			<string name="MASTER_DETAIL_INFO_USAGE" usage="Help Information when running MasterDetailInfo directly.  This is not supported usage by customers." errorCode="0031">com.cognos.rsvp.rsupgrade.wrapper.MasterDetailInfo &lt;ReportNetSpecification&gt; &lt;mdInfo&gt;\n\nRead in the ReportNet version of the report specification from &lt;ReportNetSpecification&gt;.\nWrite out the master detail data to &lt;mdInfo&gt;."</string>
			<string name="WRONG_NB_IDENTIFIERS" usage="Internal error, number of identifiers in equality expression is correct. " errorCode="0032">The amount of identifiers in the equality expression is incorrect.</string>
			<string name="NO_MASTER_QUERY" usage="Internal error, the master query of a master/detail relationship was not found. " errorCode="0033">Cannot find the master query of a master-detail relationship.</string>
			<string name="NO_DETAIL_QUERY" usage="Internal error, the detail query of a master/detail relationship was not found. " errorCode="0034">Cannot find the detail query of a master-detail relationship.</string>
			<string name="ERROR_REFITEM_NULL" usage="Internal Error when creating master/detail links." errorCode="0037">The refItem cannot be null for the linkParameter.</string>
			<string name="ERROR_PARAMETER_NULL" usage="Internal Error when creating master/detail links." errorCode="0038">The parameter cannot be null for the linkParameter.</string>
			<string name="ERROR_CANNOT_FIND_XSLT_FILE" usage="Upgrade error, file not found" errorCode="0042">Cannot find the following XSLT file: "<param index="1" name="filename" type="string" usage="XSLT file name"/>".
			</string>
			<string name="ERROR_BINDIR_NOT_DIRECTORY" usage="Path where binaries are supposed to be located is not a directory" errorCode="0044">Cannot find the following directory: "<param index="1" name="dir" type="string" usage="directory path"/>".
			</string>
			<string name="UPGRADE_REPORT_SPEC_USAGE" usage="Instructions on how to use com.cognos.rsvp.rsupgrade.cm_plugin.UpgradeReportSpec from command line.  This usage is not supported" errorCode="0045">UpgradeReportSpec &lt;ReportNet report specification&gt; &lt;new report specification&gt;\n\nUpgrades a ReportNet version of the report from a file to the latest verision of an IBM Cognos report specification in another output file.</string>
			<!-- 0046 was previously used. -->
			<string name="BATCH_UPGRADER_USAGE" usage="Usage for a test tool.  Tool is not supported." errorCode="0047">\n\ncom.cognos.rsvp.rsupgrade.wrapper.BatchUpgrader [--NovRTM=true|false] --outdir=&lt;dir&gt; [&lt;reports&gt;]... \nUpgrade one or more ReportNet report specs\n\n--NovRTM Treat 2.0 reports as November release.\n&lt;dir&gt; Directory where upgraded report specifications will be placed.  Upgraded reports will have the same base name, as the report that was upgraded.\n\n&lt;reports&gt; Path to file containing the report to upgrade. </string>
			<string name="ERROR_UNABLE_TO_CREATE_DIRECTORY" usage="Attempt to create a directory failed.  Check path and see if it is correct, and if permissions on the file system are correct." errorCode="0048">Cannot create the following directory: <param index="1" name="dir" type="string" usage="directory path"/>.
			</string>
			<string name="ERROR_UPGRADE_FAILED" usage="Failure during an upgrade of a report from baltic to bering.  Look in the logs for further information." errorCode="0052">Report upgrade failed. Check the logs for more information.</string>
			<string name="ELEMENT_NOT_FOUND" usage="XML element was not found in the report being upgraded.  Check that the report being upgraded is valid against the schema." errorCode="0055">Cannot find the element "<param index="1" name="element" type="string" usage="Xml element local name that is missing."/>" in the report being upgraded. Make sure that the report validates.</string>
			<string name="UNEXPECTED_EXCEPTION" usage="An unexpected exception was caught.  Examine the error message for further actions." errorCode="0056">The following error occurred: "<param index="1" name="msg" type="string" usage="Message from exception caught."/>".
			</string>
			<string name="QUERY_NOT_FOUND_FOR_DATAITEM" usage="Query was not able to be determined for a data item.  Check the report being upgraded, that all instances of the data item are assigned to a query." errorCode="0057">Cannot find the query for the following data item: "<param index="1" name="dataitem" type="string" usage="Name of the data item."/>".
			</string>
			<string name="CRX_PARSER_ERROR" usage="Expression in report could not be parsed.  Verify the syntax." errorCode="0059">Unable to parse the expression:\n<param index="1" name="expression" type="string" usage="Expression that could not be parsed."/>
			</string>
			<string name="CRX_PARSER_ERROR_2" usage="Expression in report could not be parsed.  Verify the syntax." errorCode="0060">Unable to parse the expression:\n<param index="1" name="expression" type="string" usage="Expression that could not be parsed."/>\n\nExpression error:\n<param index="2" name="msg" type="string" usage="Text from exception caught indicating what the error is."/>
			</string>
			<string name="CQE_PARSER_ERROR" usage="Expression in report could not be parsed.  Verify the syntax." errorCode="0061">Unable to parse the expression:\n<param index="1" name="expression" type="string" usage="Expression that could not be parsed."/>
			</string>
			<string name="CQE_PARSER_ERROR_2" usage="Expression in report could not be parsed.  Verify the syntax." errorCode="0062">Unable to parse the expression:\n<param index="1" name="expression" type="string" usage="Expression that could not be parsed."/>\n\nExpression error:\n<param index="2" name="msg" type="string" usage="Text from exception caught indicating what the error is."/>
			</string>
			<string name="QUERY_NOT_FOUND_FOR_DATAITEM_EXPRESSION" usage="Query was not able to be determined for a data item used in an expression.  Check the report being upgraded, that the data item are assigned to a query." errorCode="0063">Cannot find te query for the following data item: "<param index="1" name="dataitem" type="string" usage="Name of the data item."/>" in the expression "<param index="2" name="expression" type="string" usage="Expression where data item is used."/>". Make sure that the data item is assigned to a query in the report being upgraded.</string>
			<string name="UPGRADE_REPORT_SPECIFICATION_USAGE" usage="Usage on running UpgradeReportSpecification directly." errorCode="0064" translate="changed">com.cognos.rsvp.rsupgrade.wrapper.UpgradeReportSpecification [-h|--help] [--NovRtm]  -i|--input &lt;OriginalSpecification&gt; -o|--output &lt;UpgradedSpecification&gt;\n\n-h|--help\n Display help message and exit. \n\n--NovRtm\nTreat 2.0 reports as November release.\n\n-i|--input &lt;OriginalSpecification&gt;\n The original version of the report specification to upgrade.\n\n-o|--output &lt;UpgradedSpecification&gt;\n Upgraded IBM Cognos report specification.</string>
			<string name="ORIGINAL_REPORT_FILE_NOT_READABLE" errorCode="0065">Cannot read the original report specification file: "<param index="1" name="path" type="string" usage="The pathname to the file."/>".</string>
			<string name="UPGRADE_CMD" usage="Command that was being executed when an error was discovered." errorCode="0066">The following command was running when an error occurred: "<param index="1" name="cmd" type="string" usage="Command that was being executed."/>".
			</string>
			<string name="INVALID_STREAM" usage="Invalid character detected while processing a stream." errorCode="0067">Error detected near line:<param index="1" name="linenumber" type="string" usage="line number in source file where error was detected"/> column: <param index="2" name="colnumber" type="string" usage="column number in source file where error was detected."/> character: <param index="3" name="pos" type="string" usage="Position in source file where error was detected."/> (<param index="4" name="err" type="string" usage="Original exception"/>)</string>
			<string name="INVALID_FILE" usage="Input file was unable to be parsed." errorCode="0068">Invalid input file "<param type="string" index="1" name="path" usage="Path of file that failed"/>" line:<param index="2" name="linenumber" type="string" usage="line number in source file where error was detected"/> column: <param index="3" name="colnumber" type="string" usage="column number in source file where error was detected."/> character: <param index="4" name="pos" type="string" usage="Position in source file where error was detected."/> (<param index="5" name="err" type="string" usage="Original error message"/>)</string>
			<string name="CONFIG_FILE_NOT_READABLE" usage="configuration file is not readable" errorCode="0069">Unable to read the configuration file: "<param type="string" name="path" index="1" usage="Path of file that failed"/>"</string>
			<!-- 0075 was previously used -->
			<string name="LIGHTWEIGHT_CONFIGURATION_FILE_INVALID" usage="The lightweight upgrade configuration file shared between RSPECUPGRADE and RSVP is not well formed as described by the schema." errorCode="0076">
The lightweight upgrade configuration is not valid: <param index="1" name="path" type="string" usage="Path of the configuration file."/>
			</string>
			<!--
			<string name="LIGHTWEIGHT_SCRIPT_MISSING" usage="The lightweight upgrade XSL script cannot be read.  " errorCode="0077">
Unable to read upgrade script <param index="2" type="string" usage="Path of the upgrade script file."/> defined by lightweight upgrade configuration file <param index="1" type="string" usage="Path of the configuration file."/>
			</string>
-->
			<string name="LOCALIZED_FORMAT_PATTERNS_FILE_INVALID" errorCode="0078" usage="The document that describes the localized format pattern characters is invalid.">The localized pattern characters file is invalid: "<param index="1" name="path" type="string" usage="Path of the localized pattern characters file."/>".</string>
			<string name="UNABLE_TO_LOAD_RESOURCE" usage="Due to an installation or configuration error, a resource was unable to be retrieved." errorCode="0079">Unable to load resource:<param index="1" name="id" type="string" usage="Identifier for the resource."/>
			</string>
			<string name="URL_TO_URI_CONVERSION_FAILED" usage="Converting a URI to a URL failed unexpectedly.  This is an internal error." errorCode="0079">
			URL to URI conversion failed. URL was '<param index="1" name="url" type="string" usage="the URL we were converting."/>', URI was '<param index="2" name="result" type="string" usage="The result of the conversion."/>. 
			</string>
			<string name="URL_TO_URI_CONVERSION_FAILED_BAD_URI" usage="Converting a URI to a URL failed unexpectedly.  This is an internal error." errorCode="0080">
			URL to URI conversion failed. URL was '<param index="1" name="url" type="string" usage="the URL we were converting."/>'. 
			</string>
			<string name="TAINTED_UNSAFE_PROPERTY" usage="A configruation property which came from an unsafe source is not recognized as being safe.  The whole request is being rejected as a possible secureity risk." errorCode="0081">
			Possibly unsafe configuration option is being used, the request is being rejected. Parameter in question is:<param index="1" name="property" type="string" usage="the name of the property."/>.</string>
			<string name="UPGRADE_EXCEPTION" usage="An exception has occurred during the upgrade process." errorCode="0082">Exception occurred during upgrade: <param index="1" name="exp" type="string" usage="Untranslated details of the exception."/></string>
		</section>
		<section name="SPC" usage="Messages inserted into the upgraded report specifications">
			<string name="QUERYSET_UPGRADE_FAILED" usage="There was an error reported during the querySet upgrade.  Because of this, no queries were generated.  The parameter is the error text returned by the querySet upgrade." errorCode="0003">No queries were generated.  The querySet could not be upgraded for the following reason: "<param index="1" name="err" type="string" usage="Error text from the query upgrade."/>".</string>
			<string name="DATA_ITEM_NOT_IN_SCOPE" usage="During an upgrade from baltic to bering the query was unable to be determined for the refDataItem.  Validate the usage of the refDataItem in the batic report specification to ensure that it is scoped by a query." errorCode="0006">Cannot determine the query for the following referenced data item: "<param index="1" name="refitem" type="string" usage="refItem that needed a query."/>".
			</string>
			<string name="INVALID_XML_REPORT_SPEC" usage="The v4 report spec that is to be upgraded is not valid, look at the error message for further details." errorCode="0007">The report specification to be upgraded is not a valid XML document because: "<param index="1" name="err" type="string" usage="Error message from Java libraries."/>".
			</string>
			<string name="NO_LISTGROUP_FOR_DATAITEM" usage="A list group is needed for a data item." errorCode="0008">Cannot find the list group for the following data item: "<param index="1" name="dataitem" type="string" usage="name of data item."/>".
			</string>
			<string name="NO_PROPERTY_ITEM_ADDED_FOR_CROSSTABFACTCELL_0" usage="A property item should have been added for a crosstab fact cell, but the upgrade algorithms failed.  User intervention may be necessary for the report to run correctly." errorCode="0010">The upgrade algorithm did not add the property item to the crosstab fact cell.</string>
			<string name="NO_PROPERTY_ITEM_ADDED_FOR_CROSSTABFACTCELL_1" usage="A property item should have been added for a crosstab fact cell, but the upgrade algorithms failed.  User intervention may be necessary for the report to run correctly." errorCode="0011">The upgrade algorithm did not add the data item "<param index="1" name="dataitem" type="string" usage="name of data item that should have been added to property list"/>" to the crosstab fact cell.</string>
			<string name="DANGLING_DATA_ITEM" usage="An upgraded report uses a data item that is not in the scope of an enclosing query.  The upgraded report needs to be manaully fixed up." errorCode="0014">The following data item  is not in the scope of an enclosing query: "<param index="1" name="dataitem" type="string" usage="The data item being used"/>". You must manually fix the upgraded report.
			</string>
			<string name="VARIABLE_NOT_DEFINED" usage="A refVariable is being used but is not defined.  The upgraded report needs to be manaully fixed up." errorCode="0015">The variable "<param index="1" name="var" type="string" usage="The name of the variable being used"/>" is not defined. You must manually fix the upgraded report.
			</string>
			<string name="V4_VALIDATION_ERROR" usage="A report to be upgraded did not validate correctly.  The Baltic report needs to be fixed before upgrading will succeeed." errorCode="0016">The report to be upgraded had the following validation error: "<param index="1" name="err" type="string" usage="Error message from the dtd validator, which may not be localized."/>".
			</string>
			<string name="V4_VALIDATION_WARNING" usage="A report to be upgraded had a warning during validation.  The Baltic report should be fixed before upgrading." errorCode="0017">The report to be upgraded had the following validation warning: "<param index="1" name="warning" type="string" usage="Warning message from the dtd validator, which may not be localized."/>".
			</string>
			<string name="INVALID_REPORT_TO_UPGRADE" usage="The report specification was not recognized as one that can be upgraded.  Verify that the report is supposed to be upgraded." errorCode="0019">Cannot upgrade this report. Verify that the report is supposed to be upgraded.</string>
			<string name="ATTRIBUTE_NOT_FOUND" usage="XML attribute was not found in the report being upgraded.  Check that the report being upgraded is valid against the schema." errorCode="0021">Cannot find the attribute "<param index="1" name="xmlattr" type="string" usage="Xml attribute name that is missing."/>". Make sure that the report validates.</string>
			<string name="LOCALE_INVALID" usage="The locale is not recognized as being valid.  Check the locale against the list of valid locales." errorCode="0022">The locale "<param index="1" name="locale" type="string" usage="Unrecognized locale."/>" is not valid. Make sure the locale appears in the list of valid locales.</string>
			<string name="INVALID_BURST_SPECIFICATION" usage="The burst specification is invalid and was removed." errorCode="0067">The burst specification is invalid and was removed.</string>
			<string name="EXTRA_ELEMENTS_IGNORED" usage="The upgrade has found more than one instance of an element in a context where only one is allowed.  Only the first instance is upgraded and the others are ignored." errorCode="0068">You can specify only one "<param index="1" name="extraelement" type="string" usage="Name of the extra element found"/>" in a "<param index="2" name="parent" type="string" usage="Name of the parent element"/>" element. The extra elements are ignored by the upgrade.</string>
			<string name="VARIABLE_EXPRESSION_CHANGED" usage="A variable expression had an invalid value and was changed to a legal value.  The report author should verify that the change was correct. " errorCode="0069">Cannot process the expression for the report variable "<param index="1" name="var" type="string" usage="Name of the report variable"/>". The original expression "<param index="2" name="expression" type="string" usage="original expression"/>" was replaced with "<param index="3" name="newexp" type="string" usage="new expression"/>".  The parser error was "<param index="4" name="msg" type="string" usage="Text from exception caught indicating what the error is."/>".
			</string>
			<string name="REPORT_EXPRESSION_CHANGED" usage="A report expression had an invalid value and was changed to a legal value.  The report author should verify that the change was correct. " errorCode="0070">Cannot process the report expression. The original expression "<param index="1" name="expression" type="string" usage="original expression"/>" was replaced with "<param index="2" name="newexp" type="string" usage="new expression"/>".  The parser error was "<param index="3" name="err" type="string" usage="Text from exception caught indicating what the error is."/>".
			</string>
			<string name="SCHEMA_FIXUP_NODE_REMOVED" usage="The upgraded report has found an XML node that will stop the upgraded report from validating.  The erronous node has been removed." errorCode="0071">The upgraded report has found an XML node that will prevent it from validating. The node has been deleted.</string>
			<string name="SCHEMA_FIXUP_ELEMENT_CREATED" usage="The upgraded report would stop from validating against the schema.  A new element has been created to allow the report to validate." errorCode="0072">The element "<param index="1" name="element" type="string" usage="Element name"/>" was created because it is required to validate the upgraded report.</string>
			<string name="SCHEMA_FIXUP_ATTRIBUTE_REMOVED" usage="The upgraded report has found an attribute that will stop the upgraded report from validating.  The erronous attribute has been removed." errorCode="0073">The attribute "<param index="1" name="attribute" type="string" usage="Attribute name"/>" will prevent the upgraded report from validating and has been deleted from the element "<param index="2" name="element" type="string" usage="Name of element containing the attribute."/>".
			</string>
			<string name="SCHEMA_FIXUP_ATTRIBUTE_CREATED" usage="The upgraded report would stop from validating against the schema.  A new attribute has been created to allow the report to validate." errorCode="0074">The attribute "<param index="1" name="attribute" type="string" usage="Attribute name"/>" was created because it is required to validate the upgraded report.</string>
			<string name="SCHEMA_FIXUP_ATTRIBUTE_VALUE_CHANGED" usage="The upgraded report would stop from validating against the schema.  The attribute value has been changed to allow the report to validate." errorCode="0075">The attribute "<param index="1" name="attribute" type="string" usage="Attribute name"/>" was changed to "<param index="2" name="value" type="string" usage="new attribute value"/>" from "<param index="3" name="originalvalue" type="string" usage="original value of attribute"/>" to allow the upgraded report to validate.</string>
			<string name="SCHEMA_FIXUP_TEXT_CREATED" usage="The upgraded report would stop from validating against the schema.  A new text node has been created to allow the report to validate." errorCode="0076">The text node "<param index="1" name="content" type="string" usage="Contents of new text node"/>" was created because it is required to validate the upgraded report. </string>
			<string name="SCHEMA_FIXUP_TEXT_CHANGED" usage="The upgraded report would stop from validating against the schema.  A text node has been changed to allow the report to validate." errorCode="0077">The text node was changed to "<param index="1" name="newvalue" type="string" usage="new value"/>" from "<param index="2" name="originalvalue" type="string" usage="original value"/>" to allow the upgraded report to validate.</string>
			<string name="SCHEMA_FIXUP_ABORTED_TOO_MANY_ERRORS" usage="The fixing of a broken report specification has been aborted becuase of too many errors." errorCode="0078">The repair of the broken report specification was cancelled after <param index="1" name="numerrors" type="string" usage="how many detected errors"/> errors.</string>
			<string name="DUPLICATE_ELEMENT_RENAMED" usage="An element with a duplicate name was detected and renamed to be unique within its scope." errorCode="0079">The value of attribute "<param index="1" name="attribute" type="string" usage="The attribute name"/>" must be unique for all "<param index="2" name="element" type="string" usage="The element name"/>" elements within a "<param index="3" name="ancestor" type="string" usage="The ancestor element which defines the scope"/>" element. The duplicate value "<param index="4" name="oldvalue" type="string" usage="The old attribute value"/>" was changed to "<param index="5" name="newvalue" type="string" usage="The new attribute value"/>".</string>
			<string name="QUERY_NOT_FOUND" usage="An referenced query was not found in the report spec." errorCode="0080">Cannot find the query "<param index="1" name="query" type="string" usage="The query name"/>".</string>
			<string name="DATA_ITEM_NOT_DEFINED_FOR_DRILL_SOURCE_CONTEXT" usage="In baltic a drill through parameter that used a data item that was not in context was ignored.  The upgrader removes such elements, since the make the report erronous.  The report author should reintroduce the data items if they were suposed to be present and working. That is an embeded XML path in the message. See trakker 529699.4 and 541337" errorCode="0081">The data item "<param index="1" name="dataitem" type="string" usage="The data item name"/>" is not defined in the context for the drill through parameter.</string>
			<string name="XML_NODE_REMOVED_0" usage="XML text has been removed from the report specification.  Used to embed a comment in the report specification that will contain the removed node.  The removed node will follow in the comment.  I realize building of messages is generally frowned on, but consider this message to be a title." errorCode="0082">An XML node has been removed.</string>
			<string name="XSL_PLUGIN_EXECUTED" usage="Comment that will be added to a report specification if a user defined XSL plugin is executed." errorCode="0083">The plugin "<param index="1" name="xslscript" type="string" usage="The path for the XSL script."/>" has run on this report specification.</string>
			<string name="ERROR_XSL_PLUGIN_MISSING" usage="Error message for XSL plugin missing" errorCode="0084">The plugin <param index="1" name="xslscript" type="string" usage="The path for the XSL script."/> cannot be read.</string>
			<string name="ERROR_XSL_PLUGIN_FAILED" usage="Error message for XSL plugin execution failing." errorCode="0085">The plugin failed.</string>
			<string name="ERROR_XSL_PLUGIN_FAILED_1" usage="Error message for XSL plugin execution failing." errorCode="0086">The XSL plugin failed: <param index="1" name="error" type="string" usage="Error message describing the cause of the failure.  The message may not be localized. "/>
			</string>
			<string name="ERROR_NO_REPORT_GENERATED" usage="Internal error upgrade failed to generated a report." errorCode="0087">The upgrade did not generate a report. </string>
			<string name="UNUSED_REPORTVARIABLE_REMOVED" usage="An unused report variable that would have caused a validation error has been removed." errorCode="0088">The following unused report variable has been removed: "<param index="1" name="reportvar" type="string" usage="Name of the reportVariable."/>".
			</string>
			<string name="INVALID_LAYOUT_COMPONENT_REF_REMOVED" usage="Attribute href points to an element that does not exist in the report specification.  Because Baltic allows and just ignores them, but Bering does not, we just remove them from the v5 spec." errorCode="0089">Removed the reference to the following non-existent layout component: "<param index="1" name="value" type="string" usage="The value of the href"/>".</string>
			<string name="INTERNAL_ERROR_CROSSTAB_PROPERTY_LIST_BAD_ELEMENT" usage="An internal error has occurred.  The wrong element is being used while generating a property list for a crosstab." errorCode="0090">The following incorrect element is being used while generating a property list for a crosstab report: "<param index="1" name="element" type="string" usage="Element name"/>".
			</string>
			<string name="INTERNAL_ERROR_MISSING_ATTRIBUTE_ORIGINAL_REFQUERY" usage="An internal error has occurred.  The artificially generate attribute 'originalRefQuery' cannot be found." errorCode="0091">The attribute originalRefQuery cannot be found.</string>
			<string name="REPORT_EXPRESSIONS_CANNOT_BE_EMPTY" usage="In Baltic an empty report expression that was empty was treated as false.  Empty report expression are now invalid." errorCode="0092">A report expression cannot be empty or consist entirely of whitespace.</string>
			<string name="INFO_UPGRADE_PERFORMED" usage="Informational message indicating an upgrade has been performed." errorCode="0093">The report specification was upgraded from "<param index="1" name="originalNS" type="string" usage="Namespace of the original report."/>" to "<param index="2" name="destNS" type="string" usage="Namespace of the report after upgrade."/>" at <param index="3" name="year" type="string" usage="numeric representation of year"/>-<param index="4" name="month" type="string" usage="numeric representation of month"/>-<param index="5" name="day" type="string" usage="numeric representation of day"/>.
				<param index="6" name="hour" type="string" usage="hour"/>:<param index="7" name="minute" type="string" usage="minute"/>:<param index="8" name="second" type="string" usage="second"/>
			</string>
			<string name="INFO_VALIDATE_REPORT" usage="Reminder that reports should validate before being upgraded." errorCode="0095">Problems were detected while upgrading.  Please ensure that the original report validates in the original environment.</string>
			<string name="INFO_OLD" usage="Old INFO level message in report that was being upgraded." errorCode="0096">The upgraded report contained the following message: "<param index="1" name="msg" type="string" usage="Message that was in the upgraded report."/>".
			</string>
			<string name="WARNING_OLD" usage="Old WARNING level message in report that was being upgraded." errorCode="0097">The upgraded report contained the following message: "<param index="1" name="msg" type="string" usage="Message that was in the upgraded report."/>".
			</string>
			<string name="ERROR_OLD" usage="Old ERROR level message in report that was being upgraded." errorCode="0098">The upgraded report contained the following message: "<param index="1" name="msg" type="string" usage="Message that was in the upgraded report."/>".
			</string>
			<string name="CONDITIONAL_STYLE_REMOVED" usage="CRN allows conditional styles to reference invalid, even undefined  report variables.  When rendering the report it simply ignores the style altogether.  In order to reproduce the same results in C8, the upgrade removes the conditional style." errorCode="0099">Removed the conditional style because it referenced the following report variable "<param index="1" name="reportvar" type="string" usage="Name of the report variable."/>", which is not valid.</string>
			<string name="INTERNAL_ERROR_UNKNOWN_UPGRADE_NOTE_ID" usage="An internal error has occurred.  The specified upgrade note id does not exist." errorCode="0100">No upgrade note with an ID of "<param index="1" name="noteid" type="string" usage="The upgrade note id that does not exist."/>" exists.</string>
			<string name="SCHEMA_FIXUP_KEY_CONSTRAINT_NON_UNIQUE" usage="Two elements having the same key value were produced.. " errorCode="0101">
			The key "<param index="1" name="key" type="string" usage="name of the key in the schema"/>"  value of "<param index="2" name="value" type="string" usage="Code produced representation of the key value."/>" is used for more than one element.</string>
			<string name="SCHEMA_FIXUP_KEY_CONSTRAINT_FIELD_MISSING" usage="A mandatory field is missing. " errorCode="0102">
			The key "<param index="1" name="key" type="string" usage="name of the key in the schema"/>" is missing the following field: "<param index="2" name="id" type="string" usage="id of the field as defined in the schema,."/>". </string>
			<string name="SCHEMA_FIXUP_KEYREF_CONSTRAINT_KEY_NOT_FOUND" usage="Reference to a key not  found." errorCode="0103">
			The reference restriction "<param index="1" name="keyref" type="string" usage="Name of keyref in schema"/>" could not be completed because the following key was not found: "<param index="2" name="field" type="string" usage="Code generated representation of the fields that make up the key for an element."/>".
			</string>
			<string name="SCHEMA_FIXUP_KEYREF_CONSTRAINT_MISSING_FIELD" usage="Keyref was missing a field" errorCode="0104">
			The reference restriction <param index="1" name="keyref" type="string" usage="Name of keyref in schema"/> could not be completed because the following field is missing: "<param index="2" name="attribute" type="string" usage="Name of missing attribute."/>". </string>
			<string name="CUBE_NOT_FOUND" usage="cube element was not found in Baltic report specification for a query." errorCode="0105">Cube not found for query "<param index="1" name="query" type="string" usage="Name of the baltic query."/>".</string>
			<string name="CONDITIONAL_LAYOUTS_REMOVED" usage="CRN allows conditional layouts to reference invalid, even undefined  report variables.   When rendering the report it simply ignores the conditional layout altogether.  In order to reproduce the same results in C8, the upgrade removes the conditional layout element." errorCode="0106">Removed a conditional layouts element because it referenced the following report variable "<param index="1" name="reportvar" type="string" usage="Name of the report variable."/>", which is not valid.</string>
			<string name="DEPTH_OVERRIDES_MARKER" usage="See trakker 544100 and 540948.  In Baltic a bug prevented markers from showing on charts when the chart was three dimensional." errorCode="0107">Markers are removed from three-dimensional charts during an upgrade.</string>
			<string name="OBSOLETE_MARKER" usage="See WO1194.  Marker for chart is obsolete." errorCode="0108">Obsolete marker "<param index="1" name="oldname" type="string" usage="old marker name"/>" changed to "<param index="2" name="newname" type="string" usage="new marker name"/>".</string>
			<string name="DUPLICATE_REFVARIABLEVALUE" usage="See trakker 546826.  You are not allowed to have the same condition more than once.  Baltic let the error through, but C8 will catch it.  The duplicate condition value is removed during upgrade." errorCode="0109">The duplicate variable value "<param index="1" name="dupvalue" type="string" usage="The duplicated value"/>" is not allowed and has been removed.</string>
			<string name="RECURSIVE_LAYOUT_COMPONENT_REF" usage="An element with attribute refLayoutElement refrenced an element that also had a reference, possibly through many layers of expansions, to the same name." errorCode="0110">The recursive layout component reference  "<param index="1" name="refvalue" type="string" usage="Value of the reference."/>" is not allowed and has been removed.</string>
			<string name="LAYOUT_COMPONENT_REF_EXPANDED" usage="An element with attribute layoutComponentRef had to be expanded during upgrade, removing the reference." errorCode="0111">An element with the referenced layout component "<param index="1" name="refname" type="string" usage="name of the reference."/>" was expanded during upgrade, and the reference was removed.</string>
			<string name="INTERNAL_ERROR_LAYOUT_COMPONENT_REF_HAS_UNEXPECTED_CHILDREN" usage="The children of layoutComponentRef element were not expected in a report upgraded from Baltic." errorCode="0112">The child elements of the referenced layout component "<param index="1" name="layout" type="string" usage="Name of the layoutComponent."/>" were not expected in this upgraded report.</string>
			<string name="LAYOUT_COMPONENT_REF_OVERRIDE_NOT_FOUND" usage="The layoutComponentOverride element attribute refLayoutElement 's value could not be found in the referenced layout component." errorCode="0113">Cannot find the override element attribute "<param type="string" name="refLayoutElement" index="1" usage="Value of the refLayoutElement attribute for the layoutComponentRef"/>" for the referenced layout component "<param type="string" name="value" index="2" usage="Value of the refLayoutElement attribute for the layoutComponentOverride element"/>".</string>
			<string name="LAYOUT_COMPONENT_REF_NOT_FOUND" usage="The layoutComponentRef element attribute refLayoutElement 's value could not be found." errorCode="0114">Cannot find the referenced layout component "<param type="string" name="value" index="1" usage="Value of the attribute refLayoutelement"/>".</string>
			<string name="INTERNAL_ERROR_UNEXPECTED_ELEMENT" usage="Internal error.  An unexpected element was found." errorCode="0115">Found the unexpected element "<param type="string" name="element" index="1" usage="name of the element"/>".</string>
			<string name="DANGLING_DATA_ITEM_MASTER_DETAIL" usage="A dangling data item, a data item outside of the scope of a defining refQuery, could not be fixed because another element has a master-detail relationship which could possibly have been broken if the refQuery attribute was defined." errorCode="0116">Unable to fix dangling data item for query "<param index="1" name="query" type="string" usage="Name of the query that  refQuery attribute needs."/>" because of the master-detail relationship between "<param index="2" name="master" type="string" usage="Name of the master query"/>" and "<param index="3" name="detail" type="string" usage="Name of the detail query"/>".</string>
			<string name="CONDITIONALSTYLE_REMOVED_VARIABLE_EXPRESSION_MISSING" usage="In Baltic conditionalStyle elements were ignored if the refered to a variable that was missing.  During upgrade we detect the condition and remove the conditionalStyle element, issuing this diagnostic. 'conditionalStyle' is the name of an element and should not be translated." errorCode="0117">A conditionalStyle refers to a variable "<param index="1" name="var" type="string" usage="name of the variable used"/>" whose expression could not be retrieved.</string>
			<string name="CONDITIONALSTYLE_REMOVED_VARIABLE_EXPRESSION_PARSE_FAILURE" usage="In Baltic conditionalStyle elements used the default value if the refered to a variables expression could not be parsed.  During upgrade we detect the error and remove the conditionalStyle element, issuing this diagnostic. 'conditionaStyle' is the name of an element and should not be translated." errorCode="0118">A conditionalStyle refers to a variable "<param index="1" name="var" type="string" usage="name of the variable used"/>" whose expression could not be parsed. The conditionalStyle has been removed.\n\nExpression:\n<param index="2" name="expression" type="string" usage="Expression that could not be parsed."/>\n\ncaused by:\n<param index="3" name="msg" type="string" usage="Already translated message indicating what is wrong with the expression"/>
			</string>
			<string name="CONDITIONALSTYLECASES_REMOVED_DANGLING_DATAITEM" usage="In Baltic conditionalStyle elements used the default value if the refered to a variables expression could not be executed due to a dangling data item..  During upgrade we detect the error and remove the Bering conditionalStyleCases element, issuing this diagnostic. 'conditionalStyleCases' is the name of an element and should not be translated." errorCode="0119">A conditionalStyleCases element refers to a variable "<param index="1" name="var" type="string" usage="name of the variable used"/>" whose expression contains a data item "<param index="2" name="dataitem" type="string" usage="Name of the data item"/>" which could not be resolved to a query. The conditionalStyleCases element has been removed.</string>
			<string name="TEXTITEM_REFVARIABLE_REMOVED_NO_SUCH_VARIABLE" usage="The Baltic report specification had a textItem element with a refVariable attribute, where the variable was not defined.  The attribute has been removed, and text elements that used refVariableValue have been removed.  'textItem', 'text', 'refVariable', and 'refVariableValue' are names from the schema and should not be translated." errorCode="0120">A textItem element referred to a non-defined variable "<param index="1" name="var" type="string" usage="name of the variable used"/>". The condition and any conditional child elements have been removed.</string>
			<string name="FACTCELL_AND_FACTCELLSTYLE_PRESENT" usage="A crosstab had both a factCell and factCellStyle element.  factCellStyle has been deprecated but the upgrade could not be performed because of the factCell.  See WO 1752.  factCell and factCellStyle are element names and should not be translated" errorCode="0121">Unable to upgrade factCellStyle element to factCell because a factCell was already present. The factCellStyle element has been removed.</string>
			<string name="INDENTATION_ELEMENT_ALREADY_HAS_ATTRIBUTE" usage="An attribute was supposed to be moved from a crosstabNodeMember to an indentation element, however the element already had the attribute.  'crosstabNodeMember', and 'indentation' are names of elements and should not be translated. " errorCode="0122">The attribute <param index="1" name="attribute" type="string" usage="Name of the attribute"/> with value "<param index="2" name="value" type="string" usage="Value we wanted to set on indentation element"/>" from crosstabNodeMember was unable to be set on an indentation element because it already had the value "<param index="3" name="preValue" type="string" usage="pre-existing attribute value"/>".</string>
			<string name="BLARING_INDENTATION_LENGTH_NOT_PARSED" usage="Blaring attribute 'indentationLenth' had a value that could not be parsed, and was ignored.  indentationLength should not be translated" errorCode="0123">Unable to parse indentationLength attribute value "<param index="1" name="value" type="string" usage="value of the attribute"/>". The value was ignored.</string>
			<string name="BLARING_XMLATTRIBUTE_HAS_RENDER_AND_OUTPUT" usage="Blaring report specification had element XMLAttribute with both attributtes render and output.  The render attribute has been removed.  XMLAttribute, render, and output should not be translated." errorCode="0124">The XMLAttribute element had attribute output and attribute render. Attribute render has been removed.</string>
			<string name="BLARING_SCOPE_ELEMENT_DEPRECATED" usage="Blaring report sepecification lement scope deprecated with no upgrade strategy.  See WO 1752.  'scope' should not be tranlated." errorCode="0125">Scope elements have been removed from the upgrade report specification because their use is deprecated.</string>
			<string name="BLARING_ALLOWISMISSING_REMOVED" usage="Blaring report sepecification had attribute allowIsMissing which has been deprecated.  The attribute has been removed.  Do not translate 'allowIsMissing'." errorCode="0126">Attribute allowIsMissing has been removed because its use is deprecated.</string>
			<string name="SCHEMA_FIXUP_UNIQUE_CONSTRAINT_VIOLATED" usage="The upgraded report has found an XML node that will stop the upgraded report from validating against the schema, due to a uniqe constraint violation.  The erronous node has been removed." errorCode="0129">A node has been removed that would prevent schema validation due to unique constraint "<param index="1" name="constraint" type="string" usage="Name of the constraint in the schema"/>" being violated.</string>
			<string name="REFQUERY_CREATE_QUERY" usage="There was a refQuery attribute referencing an query that did not exist.  A query element has been created to bypass the problem, but the report author still needs to fix it.  query and refQuery should not be translated." errorCode="0131">The refQuery value "<param index="1" name="query" type="string" usage="The name of the query"/>" referenced a non-existant query element. A new element has been created with that name.</string>
			<string name="QUERY_EXPRESSION_NAME_MAPPED" usage="Info level message indicating that a name in query expression has been changed." errorCode="0132">The query expression name has been changed from "<param index="1" name="oldname" type="string" usage="old name"/>" to "<param index="2" name="newname" type="string" usage="new name"/>".</string>
			<string name="LIST_COLUMN_ROW_SPAN_NOT_GROUPED" usage="Warning level message indicating that a listColumnRowSpan element has been removed because the data item was not grouped.  It was an error that was allowed in Bering.  'listColumnRowSpan', 'listGroup' and 'refDataItem' should not be translated." errorCode="0133">A listColumnRowSpan element for refDataItem "<param index="1" name="value" type="string" usage="value of the refDataItem attribute on the element."/>"  was removed because the data item was not grouped with a listGroup element.</string>
			<string name="CONDITIONALSTYLE_REMOVED_ITEM_NOT_DEFINED_IN_QUERY" usage="In Baltic, conditionalStyle elements used the default value if the variable referred to an item not defined in the queries available in its context.  During upgrade we detect the error and remove the conditionalStyle element, issuing this diagnostic. The word 'conditionaStyle' is the name of an XML element and should not be translated." errorCode="0134">A conditionalStyle refers to the variable "<param index="1" name="var" type="string" usage="name of the variable used"/>" whose expression contains references to data item "<param index="2" name="dataitem" type="string" usage="name of the dataItem"/>" This data item is not defined in the queries available in its context. The conditionalStyle has been replaced with its default style.</string>
			<string name="CHART_BODY_STYLE_IGNORED_FOR_NON_FIRST_MEASURE" usage="Info level message. A bug in baltic (554842) did not apply the chartBody style to the second series.  this behaviour has been reproduced in the upgraded report." errorCode="0135">The chart body style was used for the first measure only.</string>
			<string name="DECIMAL_SIZE_REMOVED_FROM_CURRENCY_FORMAT" usage="Info level message. See trakkers 564673 and  569493.  currencyFormat and decimalSize are identifiers and should not be translated.  Baltic did not handle the decimalSize attribute correctly.  We are removing it from the upgraded report to reproduce the Baltic behaviour." errorCode="0136">The decimalSize attribute has been removed from the currencyFormat element to match the IBM Cognos ReportNet behaviour.</string>
			<string name="DUPLICATE_DATA_ITEM_REMOVED" usage="Until Blacksea two data items with the same name were allowed.  In this case two data items are identical and one has been removed, but the upgrade is considered good.." errorCode="0137">The duplicate data item <param index="1" name="dataitem" type="string"/> has been removed from the query <param index="2" name="query" type="string" usage="name of query that contains the data item."/>.</string>
			<string name="CONFLICTING_DATA_ITEM_REMOVED" usage="Until Blacksea two data items with the same name were allowed.  In this case two data items are differed and one has been removed.  The upgrade is considered to have failed, since the choice of which data item to remove is arbitrary." errorCode="0138">The data item <param index="1" name="dataitem" type="string"/> had multiple definitions in the query <param index="2" name="query" type="string" usage="name of query that contained data item"/>. The extra definitions have been removed.</string>
			<string name="BALTIC_ATTR_EMPTY" usage="An attribute in the CRN report specification was empty that should not have been. See trakker 571526.2" errorCode="0139">The IBM Cognos ReportNet report has element <param index="1" name="element" type="string" usage="Name of element that contains the attribute"/> with attribute <param index="2" name="attribute" type="string" usage="name of the attribute"/> that has an empty value.</string>
			<string name="SECTIONING_NOT_IMPLEMENTED_WITH_PARAMETERS" errorCode="0140" usage="See trakker 571917 and trakker 520911.2.  A sectioning would talke place in Baltic for a report that had nested queries Q1, Q2, Q1 where Q1 and Q2 had a master detail relationship.  This sectioning cannot be replicated in BSE due to the detailContext using a parameterContext element.">
			Sectioning between layout frames: 
			<param index="1" name="outterelement" type="string" usage="outter most element name"/> 
			refQuery="<param index="2" name="outterrefquery" type="string" usage="outter most refQuery attribute value."/> "
			name="<param index="3" name="outtername" type="string" usage="outter most name attribute value, may be empty."/> ",
			<param index="4" name="midelement" type="string" usage="middle element name"/> 
			refQuery="<param index="5" name="midrefquery" type="string" usage="middle refQuery attribute value."/> "
			name="<param index="6" name="midname" type="string" usage="middle name attribute value, may be empty."/> ",
			and
			<param index="7" name="innerelement" type="string" usage="inner element name"/> 
			refQuery="<param index="8" name="innerrefquery" type="string" usage="inner refQuery attribute value."/> "
			name="<param index="9" name="innername" type="string" usage="inner name attribute value, may be empty."/> "
			could not be upgraded due to the use of a parameter 
			(<param index="10" name="paramenter" type="string" usage="name of the parameter"/>) in the master-detail relationship.
			</string>
			<string name="BALTIC_DANGLING_REFERENCE_IN_EXPRESSION" errorCode="0141" usage="Info level message, that indicates the possible cause of an upgrade failure due to a badly formed Baltic report, that could validate and run in Baltic.  Even with this messge, uprade may succeed.">The IBM Cognos ReportNet report specification refers to a data item that is not in the scope of a query.  Data item "<param index="2" name="dataitem" type="string" usage="Name of data item"/>" is refered to in the expression "<param index="1" name="expression" type="string" usage="Expression that had the data item"/>" at location "<param index="3" name="xpath" type="string" usage="xpath to the expression"/>".</string>
			<string name="DATA_ITEM_NOT_DEFINED_IN_ANY_QUERY" errorCode="0142" usage="A data item is refered to, but not defined by any query. Issued to make clear why a BALTIC_DANGLING_REFERENCE_IN_EXPRESSION message output occurred. ">Data item "<param index="1" name="dataitem" type="string" usage="data item name"/>" is not defined by any query.</string>
			<string name="DATA_ITEM_DEFINED_IN_QUERY" errorCode="0143" usage="Info level message indicating where a data item is defined.  Issued to make clear why a BALTIC_DANGLING_REFERENCE_IN_EXPRESSION message output occurred.  ">Data item "<param index="1" name="dataitem" type="string" usage="data item name"/>" is defined by the query "<param index="2" name="query" type="string" usage="name of the query"/>".</string>
			<string name="BALTIC_NO_CHARTMEMBERS" errorCode="0144" usage="Info level message, that indicates that a chart has no chartMember nodes.  In Baltic such a chart might sometomes render data, while after upgrade the chart will be empty.  See trakker 571471.  chartMember should not be translated" translate="new">The IBM Cognos ReportNet report specification has an element <param index="1" name="element" type="string" usage="Element name as defined in the schema."/> at location "<param index="2" name="xpath" type="string" usage="XPath to the charting node"/>" that has no chartMember child elements.  The chart will not render any data after upgrade.</string>
			<string name="TEST_EXPRESSION_REWRITING_FAILED" errorCode="0145" usage="A debugging option has been turned on to perform expression parsing tests.  The extra tests have failed." translate="new">Expression rewriting test has failed for the expression\n<param index="1" name="expression" type="string" usage="Expression that failed."/>
			</string>
			<string name="DUPLICATE_BALTIC_QUERY_REMOVED" errorCode="0146" usage="In Baltic if more than one query had the same name, then the last one was used.  See trakker 574751.1. Do not translate BIQuery and name." translate="new">More than one BIQuery element had name attributes with value "<param index="1" name="value" type="string" usage="Value of the name attribute"/>".  Earlier definitions of the query have been removed.</string>
			<string name="BALTIC_BURST_KEY_QUERY_UNDEFINED" errorCode="0147" usage="Baltic report has an invalid refQuery in the burst key element. refQuery, burst, and key should not be translated." translate="new">IBM Cognos ReportNet report specification being upgraded had an invalid value for attribute refQuery (<param index="1" name="value" type="string" usage="Value of the refQuery attribute"/>) in a 'key' element. Verify that the report bursted as expected in the source environment.</string>
			<string name="BALTIC_BURST_KEY_LEVEL_UNDEFINED" errorCode="0148" usage="Baltic report has an invalid refLevel in the burst key element. refQuery, refLevel, burst, and key should not be translated." translate="new">IBM Cognos ReportNet report specification being upgraded had an invalid value for attribute refLevel (<param index="2" name="value" type="string" usage="Value of the refLevel attribute"/>) in a 'key' element, with attribute refQuery (<param index="1" name="refQuery" type="string" usage="Value of the refQuery attribute"/>).  Verify that the report bursted as expected in the source environment.</string>
			<string name="BALTIC_BURST_KEY_ITEM_UNDEFINED" errorCode="0149" usage="Baltic report has an invalid refItem in the burst key element. However it is an optional attribute and Baltic ignores it if it is invalid.  refQuery, refLevel, refItem, burst, and key should not be translated." translate="new">IBM Cognos ReportNet report specification being upgraded had an invalid value for attribute refItem (<param index="3" name="refItem" type="string" usage="Value of the refItem attribute"/>) in a 'key' element, with attribute refQuery (<param index="1" name="refQuery" type="string" usage="Value of the refQuery attribute"/>) and refLevel (<param index="2" name="refLevel" type="string" usage="Value of the refLevel attribute"/>).  This is an optional attribute and ReportNet ignores it when it refers to an invalid item.  The attribute has been deleted to ensure the burst key upgrades correctly.  Verify that the report bursted as expected in the source environment.</string>
			<string name="BALTIC_BURST_RECIPIENT_QUERY_UNDEFINED" errorCode="0150" usage="Baltic report has an invalid refQuery in the burst recipient element. refQuery, burst, and recipient should not be translated." translate="new">IBM Cognos ReportNet report specification being upgraded had an invalid value for attribute refQuery (<param index="1" name="refQuery" type="string" usage="Value of the refQuery attribute"/>) in a 'recipient' element.  Verify that the report bursted as expected in the source environment.</string>
			<string name="BALTIC_BURST_RECIPIENT_ITEM_UNDEFINED" errorCode="0151" usage="Baltic report has an invalid refItem in the burst recipient element. refQuery, refItem, burst, and recipient should not be translated." translate="new">IBM Cognos ReportNet report specification being upgraded had an invalid value for attribute refItem (<param index="2" name="refItem" type="string" usage="Value of the refItem attribute"/>) in a 'recipient' element, with attribute refQuery (<param index="1" name="refQuery" type="string" usage="Value of the refQuery attribute"/>).  Verify that the report bursted as expected in the source environment.</string>
			<string name="BALTIC_BURST_RECIPIENT_TYPE_UNDEFINED" errorCode="0152" usage="Baltic report has an invalid type attribute value in the burst recipient element. type, refQuery, refItem, burst, and recipient should not be translated." translate="new">IBM Cognos ReportNet report specification being upgraded had an invalid value for attribute type (<param index="1" name="attribute" type="string" usage="Value of the type attribute"/>) in a 'recipient' element.  Verify that the report bursted as expected in the source environment.</string>
			<string name="DANGLING_DATA_ITEM_MASTER_DETAIL_NON_LIST" usage="A dangling data item, a data item outside of the scope of a defining refQuery, could not be fixed because another element has a master-detail relationship which could possibly have been broken if the refQuery attribute was defined." errorCode="0153">Unable to fix dangling data item for query "<param index="1" name="query" type="string" usage="Name of the query that  refQuery attribute needs."/>" because of the master-detail relationship between "<param index="2" name="master" type="string" usage="Name of the master query"/>" and <param index="4" name="element" type="string" usage="Element name of the detail frame, e.g. crostab"/> "<param index="3" name="detail" type="string" usage="Name of the detail query"/>".</string>
			<string name="INTERNAL_ERROR_SEE_ADMIN" usage="An internal error has occurred, which caused the upgrade to fail.  The details of the error are in the system logs." errorCode="0154" translate="new">An internal error has occurred that caused the upgrading of a report specification to fail.</string>
			<string name="DUPLICATE_ELEMENT_REMOVED" usage="An element with a duplicate name was detected and removed to be unique within its scope." errorCode="0155">The value of attribute "<param index="1" name="attribute" type="string" usage="The attribute name"/>" must be unique for all "<param index="2" name="element" type="string" usage="The element name"/>" elements within a "<param index="3" name="ancestor" type="string" usage="The ancestor element which defines the scope"/>" element. The duplicate value "<param index="4" name="oldvalue" type="string" usage="The old attribute value"/>" was defined more than once.  The element has been removed.</string>
			<string name="DANGLING_DATA_ITEM_AMBIGUOUS_REFQUERY_USED" errorCode="0156" translate="new" usage="A dangling data item was solved by assigning a query to a layout element, however the choice could not be correctly determined.  The report author has to verify if the choice was correct and if not manually fix the report. After this  message one or more DANGLING_DATA_ITEM_AMBIGUOUS_REFQUERY_ALTERNATIVE message will follow.">Dangling data item &quot;<param index="2" name="dataitem" type="string" usage="Data item that needs to be assigned to a query."/>&quot; was not able to be resolved unambiguously, the query &quot;<param index="1" name="query" type="string" usage="Name of the query that was used"/>&quot; has been used.  The report must be  examined to see if the correct choice was made.</string>
			<string name="DANGLING_DATA_ITEM_AMBIGUOUS_REFQUERY_ALTERNATIVE" errorCode="0157" translate="new" usage="Alternative query that could have been used for solving a dangling date item. See DANGLING_DATA_ITEM_AMBIGUOUS_REFQUERY_USED">Query &quot;<param index="1" name="query" type="string" usage="Query name that could have been used"/>&quot; defines the dangling data item &quot;<param index="2" name="dataitem" type="string" usage="Data item that needs to be assigned to a query."/>&quot;.</string>
			<string name="DANGLING_DATA_ITEM_REFQUERY_LOCATION_NOT_FOUND" errorCode="0158" usage="An upgraded report uses a data item that is not in the scope of an enclosing query.  The scope was unable to be set even though the defining query was found. The upgraded report needs to be manaully fixed up.">The following data item &quot;<param index="2" name="dataitem" type="string" usage="The data item being used"/>&quot;, defined by query &quot;<param index="1" name="query" type="string" usage="Query that defines the data item"/>, is not in scope.</string>
			<string name="LEVEL_KEYITEM_MISSING" errorCode="0159" usage="The baltic report spec had a level without a key.  The upgraded report will fail.">CRN report spec had level &quot;<param index="2" name="level" type="string" usage="name of the level"/>&quot; without a key, the <param index="1" name="type" type="string" usage="type of element that was being generated when the error was discovered"/> element was unable to be generated in the upgraded report specification.</string>
			<string name="CQE_PARSER_MACRO_PARSE_ERROR" usage="Expression in report could not be parsed.  Verify the syntax. Expressions with macros may be correct, but RSPECUPGRADE is unable to check." errorCode="0160">Unable to parse expression with a macro.  The expression may be correct, however it cannot be upgraded. The expression was:\n<param index="1" name="expression" type="string" usage="Expression that could not be parsed."/>\n\nExpression error:\n<param index="2" name="msg" type="string" usage="Text from exception caught indicating what the error is."/>
			</string>
			<string name="QUERY_NOT_FOUND_IN_EXPRESSION" usage="The query of a data item referenced in an expression was not found in the report specification." errorCode="0161">Cannot find the data item "<param index="1" name="query" type="string" usage="The query name"/>" in the expression: <param index="2" name="expression" type="string" usage="The expression that had the undefined data item."/>
			</string>
			<string name="DATA_ITEM_NOT_IN_QUERY_FOR_EXPRESSION" usage="The query does not contain a data item referenced in an expression" errorCode="0162">Data item "<param index="1" name="query" type="string" usage="The query name and data item name"/>" is not defined for the query.  Referenced in expression: <param index="2" name="expression" type="string" usage="The expression that had the undefined data item."/>
			</string>
			<string name="DATA_ITEM_NOT_IN_ANY_QUERY_FOR_EXPRESSION" usage="No query contains a data item referenced in an expression" errorCode="0163">Data item "<param index="1" name="query" type="string" usage="The query name and data item name"/>" is not defined by any query.  Referenced in expression: <param index="2" name="expression" type="string" usage="The expression that had the undefined data item."/>
			</string>
			<string name="CSS_DECLARATION_BAD_PARSE" usage="Cascading Style Sheet declaration could not be parsed" errorCode="0164">CSS style was removed. Unable to parse CSS declaration: <param index="1" name="decl" type="string" usage="The declaration that could not be parsed"/>
			</string>
			<string name="QUERY_SCOPE_NOT_FOUND_FOR_ELEMENT" usage="An element that needs to be defined within an element containing a refQuery attribute, had no enclosing element with the refQuery attribute." errorCode="0165">' <param index="1" name="tag" type="string" usage="The tag name of the element, e.g. threeDComboBaseline"/>' element was not defined in the scope of any query.</string>
			<string name="NON_SEMANTIC_ELEMENT_REMOVED" usage="An element that had no semantic meaning, and that has been removed from the report specification schema has been removed from the report specification.  This is an info level message." errorCode="0166"><param index="1" name="tag" type="string" usage="The tag name of the element, e.g. generatedText"/> element had no semantic meaning and has been removed from the report specification.</string>
			<string name="NON_SEMANTIC_ATTRIBUTE_REMOVED" usage="An attribute that had no semantic meaning, and that has been removed from the report specification schema has been removed from the report specification.  This is an info level message." errorCode="0167"><param index="1" name="tag" type="string" usage="The tag name of the element, e.g. allowsIsMissing"/> attribute had no semantic meaning and has been removed from the report specification.</string>
			<string name="NON_IMPLEMENTED_ATTRIBUTE_CHANGED" usage="An attribute that had a semantic meaning, but was not implemented, has been changed.  The runtime behaviour of the new attribute value is the same as the old value.  This is an info level message." errorCode="0168">The attribute <param index="1" name="attribute" type="string" usage="The name of the attribute, e.g. pointChartDataPointShape"/> has been changed from <param index="2" name="oldvalue" type="string" usage="Old value of the attribute."/> to <param index="3" name="newvalue" type="string" usage="New value of the attribute"/>.  The report outputs should remain the same.</string>
			<string name="ATTRIBUTE_CHANGED_TO_MEET_NEW_CONSTRAINTS" usage="An attribute that had a semantic meaning, but has had new constraints added has been changed..  The runtime behaviour of the new attribute value is approximately the same as the old value.  This is an info level message." errorCode="0169">The attribute "<param index="1" name="attribute" type="string" usage="The name of the attribute, e.g. pointChartDataPointShape"/>" has been changed from "<param index="2" name="oldvalue" type="string" usage="Old value of the attribute."/>" to "<param index="3" name="newvalue" type="string" usage="New value of the attribute"/>" to meet new report specification restrictions.  The report outputs should remain consistent to previous versions.</string>
			<string name="CLASS_ATTRIBUTE_MOVED_TO_EXISTING_DEFAULT_STYLE" usage="The attribute 'class' has been removed from the schema, and its contents are moved to the defaultStyle element.  However, the report being ugpraded already had a defaultStyle element, which is being deleted, to preserve runtime behaviour." errorCode="0170">Attribute 'class' was found on an <param index="1" name="element" type="string" usage="name of the element"/> element, which already had a defaultStyle.  The existing default style '<param index="2" name="prestyle" type="string" usage="The previous default style"/>'is being replaced with '<param index="3" name="content" type="string" usage="The contents that the class attribute had"/>'.</string>
			<string name="APPLYSINGLEDEFAULTSTYLE_OVERRIDDEN" usage="The attribute applySingleDefaultStyle had to be set to true to support the moving of the class attribute to the defaultStyle element for a crosstabFactCell.  However, the attribute was already set to false." errorCode="0171">Attribute applySingleDefaultValue was overriden to 'true' from 'false' during the creation of defaultStyles from class attributes.</string>
			<string name="RANGE_CANNOT_PARSE" usage="The contents of the defaultSelections element could not be parse." errorCode="0172">Unable to parse default selections: <param index="1" name="text" type="string" usage="The text that did not parse."/></string>
			<string name="OBSOLETE_OUTPUT_FORMAT_CHANGED" usage="The output format is no longer supported and has been changed" errorCode="0173">The output format <param index="1" name="oldformat" type="string" usage="old format."/> is obsolete and has been changed to <param index="2" name="newformat" type="string" usage="new format"/>.</string>
			<string name="REFQUERY_REMOVED_QUERY_NONEXISTENT" usage="There was a refQuery attribute referencing a query that did not exist.  The refQuery attribute has been removed.  The report author should verify that the report behaviour is still correct.  See COGCQ00246824." errorCode="0174">The refQuery value "<param index="1" name="query" type="string" usage="The name of the query"/>" referenced a non-existent query element and has been removed.</string>
			<string name="CROSSTABCOLUMN_REPEATEVERYPAGE_REMOVED" usage="The attribute repeatEveryPage on a crosstabNode has no effect for crosstab columns.  The attribute has been removed.  If the attribute is not removed then RSVP will report a runtime diagnostic.  See COGCQ00275651." errorCode="0176">The attribute "repeatEveryPage" has been removed from a crosstab node for a column, as it has no effect on the generated report.</string>
			<string name="DEPRECATED_ATTRIBUTE_REMOVED" usage="IBM Cognos report sepecification had attribute which has been deprecated.  The attribute has been removed." errorCode="0177">Attribute "<param index="1" name="deprecatedattribute" type="string" usage="The revision attribute"/>" has been removed because its use is deprecated.</string>
			<string name="COGNOS_STATS_DEPRECATED" usage="Diagnostic message for replacing Cognos Stats with an image." errorCode="0178">The statistical object was removed because IBM Cognos Statistics is no longer available.</string>
			<string name="COGNOS_STATS_DEPRECATED_ALTTEXT" usage="Alternate text used for the image for replacing customContent." errorCode="0179">The statistical object was removed because IBM Cognos Statistics is no longer available.</string>
			<string name="VIZ_OUTPUTTYPE_CREATED" usage="outputType attribute has been created for viz chart for active reports." errorCode="0180">The attribute "<param index="1" name="attribute" type="string" usage="Attribute name"/>" was created for viz elements.</string>
			<string name="VIZ_VIZPROPERTYVALUES_NOLONGER_ASCHILD" usage="vizPropertyValues is no longer supported as a child of a vizCategoryField or vizValue." errorCode="0181">vizPropertyValues is no longer supported as a child of a vizCategoryField or vizValue.</string>
			<string name="VIZ_VIZPROPERTYVALUE_UPGRADED_TO_NEWTYPES" usage="Specific types have been added to the report spec for visualization properties. The old visualization property values are upgraded to the new types." errorCode="0182">Specific types have been added to the report spec for visualization properties. The old visualization property values are upgraded to the new types.</string>  			
			<string name="GROUPROLLUP_IGNORED" usage="Certain values of groupRollupattribute are not supported in V5 queries.  They are ignored." errorCode="0183">The groupRollup <param index="1" name="groupRollup" type="string" usage="Attribute value"/> was ignored.</string>
			<string name="MODSORTBY_IGNORED" usage="modSort items that have modSortBy as a child are not supported." errorCode="0184">The modDataItem <param index="1" name="name" type="string" usage="Attribute value"/> has a modSort with a modSortBy child.  The modDataItem was ignored.</string>
			<string name="MODDATAITEM_IGNORED" usage="modDataItem that can't be converted to a v5 query item is ignored." errorCode="0185">The element <param index="1" name="tag" type="string" usage="Element name"/> can't be converted to a V5 query data item.  It was ignored.</string>
			<string name="MODFILTER_IGNORED" usage="modFilterDefinition that can't be converted to a v5 filterDefinition is ignored." errorCode="0186">The element <param index="1" name="tag" type="string" usage="Element name"/> can't be converted to a V5 query filter definition.  It was ignored.</string>
			<string name="SHOW_IGNORED" usage="modAttribute attribute &quot;show&quot; is ignored." errorCode="0187">The attribute &quot;show&quot; on the modAttribute element under the modDataItem named <param index="1" name="name" type="string" usage="name attribute value"/> is ignored.</string>
			<string name="NULLPOSITION_IGNORED" usage="modSort attribute &quot;nullPosition&quot; is ignored." errorCode="0188">The attribute &quot;nullPosition&quot; on the modSort element under the modDataItem named <param index="1" name="name" type="string" usage="name attribute value"/> is ignored.</string>
			<string name="DETAIL_NULLPOSITION_IGNORED" usage="modDetailSort attribute &quot;nullPosition&quot; is ignored." errorCode="0189">The attribute &quot;nullPosition&quot; on the modDetailSort element under the modQuery named <param index="1" name="name" type="string" usage="name attribute value"/> is ignored.</string>
			<string name="SORT_SKIPPED" usage="A modSort or modDetailSort was not upgraded into a sortList." errorCode="0190">A modSort or modDetailSort on the modQuery <param index="1" name="query" type="string" usage="name attribute value"/> for data item <param index="2" name="dataItem" type="string" usage="name attribute value"/> was not upgraded.</string>
			<string name="DATATYPE_ATTRIBUTE_CREATED" usage="Could not determine the value of the dataType attribute so used string." errorCode="0191">The data type of the filter item could not be determined so a default type of "string" was used. If this is incorrect, the filter should be deleted and re-created.  Validating the report will clear the errors.</string>
		</section>
		<section name="NM" usage="This section contains labels for the name attribute values generated by the report specification upgrade (see work order 2015 for details)">
			<string name="list">List</string>
			<string name="crosstab">Crosstab</string>
			<string name="repeater">Repeater</string>
			<string name="repeaterTable">Repeater Table</string>
			<string name="paretoChart">Pareto Chart</string>
			<string name="pieChart">Pie Chart</string>
			<string name="gaugeChart">Gauge Chart</string>
			<string name="mapChart">Map</string>
			<string name="bubbleChart">Bubble Chart</string>
			<string name="polarChart">Polar Chart</string>
			<string name="radarChart">Radar Chart</string>
			<string name="scatterChart">Scatter Chart</string>
			<string name="combinationChart">Combination Chart</string>
			<string name="metricsChart">Metrics Range Chart</string>
			<string name="threeDCombinationChart">3-D Combination Chart</string>
			<string name="threeDScatterChart">3-D Scatter Chart</string>
			<string name="progressiveChart">Progressive Chart</string>
		</section>
		<section name="MAP" usage="Messages used in name mapping.">
			<string name="NAMEMAPPING_RULES_INVALID" usage="The name mapping rules could not be parsed as XML, or could not be interpreted propery.  Do not give the rules as it could be a security leak. See trakker 599871." errorCode="0001">
Configuration error. The name mapping rules are invalid. Check the rules against the schema.</string>
			<string name="ONLY_ONE_OF_NAMEMAPPING" usage="Configuration error only one of com.cognos.rspecupgrade.rsupgrade.nameMappingRules or com.cognos.rspecupgrade.rsupgrade.nameMappingFile may be defined. See trakker 559871" errorCode="0002">
Configuration error. Only one of com.cognos.rspecupgrade.rsupgrade.nameMappingRules or com.cognos.rspecupgrade.rsupgrade.nameMappingFile may be defined.</string>
			<string name="FILE_NOT_READABLE" usage="The file given by the property com.cognos.rspecupgrade.rsupgrade.nameMappingFile is not valid.  Do not give the path of the file as it could be a security leak. See trakker 599871." errorCode="0003">
Configuration error. Unable to read the file defined by property com.cognos.rspecupgrade.rsupgrade.nameMappingFile.</string>
			<string name="RULE_BAD_REGEX" usage="The name mapping rule definition is not correct.  The regular expression will not compile.  See trakker 599871. The regular expression is not given to prevent security leaks." errorCode="0004">
Configuration error. The name mapping rule regular expression is incorrect.</string>
			<string name="RULE_TYPE_UNDEFINED" errorCode="0005" usage="Value of ruleType attribute in name mapping rule is incorrect">Value of ruleType attribute for name mapping rule is incorrect: <param index="1" name="value" type="string" usage="Value of the attribute that was found."/>
			</string>
			<string name="ELEMENT_MISSING" errorCode="0006" usage="A manditory element in the definition of a mapping rule is missing.">Mapping rule is missing element <param index="1" name="element" type="string" usage="Name of the element that is needed."/>
			</string>
			<string name="SRC_PART_INCORRECT" errorCode="0007" usage="The reference to a source part in a name fragment is incorrect. It refers to a part that is too small, or too large, or is not an integer.">srcPart attribute value index is invalid: <param index="1" name="scrPath" type="string" usage="The value of the srcPart attribute"/>
			</string>
		</section>
		<!--The following section contains messages that are private diagnostics that are inserted into the report specification.-->
		<section name="CHK" usage="Message used in generating and validating checksums in an upgraded report.">
		<string name="XMLDOC_IS_NULL" errorCode="0001" usage="The Xml document may not be null.">The Xml document may not be null.</string>
		<string name="CHKSUM_NOT_UNIQUE" errorCode="0002" usage="The Xml document may not have multiple checksum nodes.">The Xml document may not have multiple checksum nodes.</string>
		<string name="CHKSUM_GENERATOR_NULL" errorCode="0003" usage="The checksum generator may not be null.">The checksum generator may not be null.</string>
		<string name="CHKSUM_STRING_NULLOREMPTY" errorCode="0004" usage="The checksum string may not be null or empty.">The checksum string may not be null or empty.</string>
		<string name="CHKSUM_NOT_FOUND" errorCode="0005" usage="There is no checksum node found in the Xml document.">There is no checksum node found in the Xml document.</string>
		<string name="CHKSUM_VALIDATOR_NULL" errorCode="0006" usage="The checksum validator may not be null.">The checksum validator may not be null.</string>
		<string name="CHKSUM_VALIDATOR_HELP" errorCode="0007" usage="Help: Please provide the report specification Xml file to be validated. Do not translate [-i]">
		[-i] &lt;reportspec.xml&gt;: A report specification to validate the checksum.\n
		</string>
		<string name="CHKSUM_VALIDATION_PASSED" errorCode="0008" usage="Checksum validation passed.">Checksum validation passed.</string>
		<string name="CHKSUM_VALIDATION_FAILED" errorCode="0009" usage="Checksum validation failed.">Checksum validation failed.</string>
		<string name="CHKSUM_INVALID_FILE" errorCode="0010" usage="The input Xml file is invalid.">Invalid input Xml file "<param type="string" index="1" name="path" usage="Path of file that failed"/>" </string>
		</section>
	</component>
</stringTable>