Creating multiple subflows from within the same Data Analysis
project causes conflicts
Scenario: You cannot implement multiple subflows,
created from different Data Analysis projects, and based upon the
same schema and sample documents.
Explanation: Conflicts arise if you accept the default
value for Target XML Namespace when you create
your target models.
Solution: Ensure that the Target XML
Namespace value is unique among all target models that
are based upon the same schema.
Error running subflow using non UTF-8 encoded xml files
Scenario: You import an xml file
with non UTF-8 encoding into your subflow. When you send a message
through the subflow, an error is displayed.
Explanation: Only documents with UTF-8 encoding
of xml are supported.
Solution: In the flow that references your subflow,
select your File Input node. In the Properties view,
click Input Message Parsing and set Message
coded character set ID to the Coded Character Set Identifier
(CCSID) that corresponds to the character encoding that you use. To
set the output to non UTF-8, select the XSL Transform node.
In the Properties view, click Output
Message Parsing and set Character set to
the CCSID that corresponds to the character encoding that you use.
'DOCID' column appears in my database
Scenario: You map your database to the Data Analysis
perspective and a column 'DOCID' is inserted into your database.
Explanation: The 'DOCID' column is added into the
Local Environment schema to provide a map with a unique key string
for database operations. This is set to a random number that you can
use to identify the insertion of each entry into the database and
remove if necessary.
Solution: Works as designed.
No DDL script when using a z/OS DB2 database
Scenario: You complete the steps in the Generate
DDL wizard, but the DDL script is empty.
Explanation: When the Check model option
in the Generate DDL wizard is selected, the DDL
script is not generated.
Solution: When you configure the DDL script in the Generate
DDL wizard, do not select Check model .