IBM Content Manager, Version 8.5

Receiving a content not allowed in prolog error during XML import or export

If you run XML import or export on IBM® z/OS® UNIX System Services and observes the error "DGL0627A, Content is not allowed in prolog," it might suggest a file encoding issue.

Symptoms

Besides the "DGL0627A, Content is not allowed in prolog" error, you might also see the following errors in dklog:

[EXC]: com.ibm.mm.sdk.common.DKXMLException # com.ibm.mm.sdk.logtool.DKLogManager_
Log4J 
[THD]: main ( 307e64a )
[THG]: main = { FileWatchdog, Attach API wait loop, Signal Dispatcher, main }
[LOC]: com.ibm.mm.sdk.xml.PXMLDataInstanceServiceICM:ingest
[MSG]: DGL0627A: The following error was reported during the parsing at line '1' 
and column '1': Content is not allowed in prolog:
at com.ibm.mm.sdk.xml.PXMLDataInstanceServiceICM.ingest(PXMLDataInstanceServiceICM.
java:251)
at com.ibm.mm.sdk.xml.PXMLDataInstanceServiceICM.ingest(PXMLDataInstanceServiceICM.
java:105)
at com.ibm.mm.sdk.xml.DKXMLDataInstanceService.ingest(DKXMLDataInstanceService.
java:174)

Causes

This error occurs because the file encoding format is not correct. XML documents must be encoded in UTF-8 format on z/OS UNIX System Services.

Resolving the problem

You might add a JVM system property file.encoding=UTF-8 to ensure that UTF-8 is the encoding format. You can specify -Dfile.encoding=UTF-8 when invoking the Java™ program.

Feedback