Troubleshooting
Problem
Not all XML produced by DLA applications are compatible with the "loadidml" -g switch.
Symptom
DLA XML output loads error-free without the -g switch.
Errors appear in the bulkload.log in TADDM when loading with the -g switch.
Cause
There are stringent requirements for XML load with the -g switch. Because of this, not every
Loading the data with the -g switch requires that XML follows a much more stringent set of requirements than loading data without the -g switch. The z/OS DLA is the only known DLA that is configured to load with the -g switch.
From the TADDM User's Guide:
Restriction: Because of current API limitations, the IDML file must have source tokens present for each object in order to perform graph writing. Source tokens, however, are an optional value in an IDML XML file. Therefore, if the -g option is provided and no source token is available for an object, a dummy source token is automatically generated for that object using the required object ID from the XML file. The use of dummy source tokens is harmless, and these source tokens do not display as launch in context tokens. However, the dummy source tokens display on individual object attributes as well as the bulk load log file. This behavior is a normal part of the algorithm.
If any single element does not satisfy naming rules, or it fails to be written to the database for any reason, the entire graph, or a subset of elements might fail to be persisted. Error messages indicating the specific object that caused the failure are not available due to current limitations. Run the file without the -g option to pinpoint a problem.
Certain IDML files reuse source token values for more than one object. While permissible in IDML, these files cannot be processed with the -g option due to current limitations. Files that reuse source tokens between objects must be loaded without the -g option.
Extended attributes and abstract resources are not supported during graph writing. Process files that contain these characteristics without the -g option.
Environment
Loading data into a TADDM server.
Diagnosing The Problem
When XML is loaded into TADDM without the -g switch, data loads and is visible on the console. When data is loaded with the -g switch, the bulkload.log shows errors and the new data is not visible on the console.
Resolving The Problem
The ITM, ITNM and z/OS VM DLAs are not built to be loaded with the -g switch. The documentation for these products does not show the use of the -g switch.
Only the z/OS DLA XML should be loaded into TADDM using the -g switch, unless you are using self-written XML that you have tested with the -g switch.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21670332