Topic
  • 4 replies
  • Latest Post - ‏2011-06-15T15:04:52Z by SystemAdmin
SystemAdmin
SystemAdmin
230 Posts

Pinned topic SQLCODE=-20340

‏2011-06-08T13:35:56Z |
We were sent xmlschema documents by a business partner and we registered this XMLSCHEMA that contained 41 documents in a db2/luw V9.5 fp5 database. The xmlvalidate has been working well against this XMLSCHEMA. We recently upgraded our DB2/ZOS to V9 NFM and are trying to move this functionality to the ZOS platform. After making the necessary changes to the REGISTER XMLSCHEMA (must use SYSXSR schema and changes in the commands), I attempted to register the same documents from USS. However, I receive the following message from the complete xmlschema SYSXSR.swml_4_7
SQLCA Information

sqlcode : -20340 sqlerrmc: SWML_4_7;1063 sqlerrp : DSNX9CAC
sqlerrd : (1) 0 (2) 0 (3) 0
(4) -1 (5) 0 (6) 0
sqlwarn : (1) (2) (3) (4) (5)
(6) (7) (8) (9) (10)
sqlstate: 22534

sqlerr Message: XML SCHEMA SWML_4_7 INCLUDES AT LEAST ONE XML SCHEMA DOCUMENT IN NAMESPACE 1063 THAT IS NOT CONNECTED TO THE OTHER XML SCHEMA DOCUMENTS. SQLCODE=-20340, SQLSTATE=22534, DRIVER=3.61.84

The same order of documents works in LUW but does not work in ZOS. Does anyone know what should be done? There are 3 documents with no include, but which are referenced by other documents.

Thanks!
Updated on 2011-06-15T15:04:52Z at 2011-06-15T15:04:52Z by SystemAdmin
  • Jane Man
    Jane Man
    10 Posts

    Re: SQLCODE=-20340

    ‏2011-06-08T18:01:07Z  
    Hi TJHOCC,

    As the first step, please find out the namespace name using the following SQL:

    SELECT * FROM SYSIBM.SYSXMLSTRINGS WHERE STRINGID=1063

    After that, you may need to collect the XML documents with such namespace and find out why they are not connected.

    Hope this help.
  • SystemAdmin
    SystemAdmin
    230 Posts

    Re: SQLCODE=-20340

    ‏2011-06-10T21:43:43Z  
    • Jane Man
    • ‏2011-06-08T18:01:07Z
    Hi TJHOCC,

    As the first step, please find out the namespace name using the following SQL:

    SELECT * FROM SYSIBM.SYSXMLSTRINGS WHERE STRINGID=1063

    After that, you may need to collect the XML documents with such namespace and find out why they are not connected.

    Hope this help.
    Thank you! The namespace is http://www.fpml.org/2009/FpML-4-7
    The documents in that namespace are connected.
    The digital Signature document xmldsig-core-schema.xsd is in a different namespace (http://www.w3.org/2000/09/xmldsig#) and is the only one in this XMLSCHEMA that is not connected.
    I don't know what else to do, except open a PMR with IBM.
  • Jane Man
    Jane Man
    10 Posts

    Re: SQLCODE=-20340

    ‏2011-06-10T22:18:04Z  
    Thank you! The namespace is http://www.fpml.org/2009/FpML-4-7
    The documents in that namespace are connected.
    The digital Signature document xmldsig-core-schema.xsd is in a different namespace (http://www.w3.org/2000/09/xmldsig#) and is the only one in this XMLSCHEMA that is not connected.
    I don't know what else to do, except open a PMR with IBM.
    That is interesting. If http://www.fpml.org/2009/FpML-4-7 is referenced(include/import) by other schema documents, there should not be any error during xsr_complete.

    Openning a PMR may not be a bad idea. Be prepared to submit all the schema files(maybe, the USS commands you used to register this schema as well).
  • SystemAdmin
    SystemAdmin
    230 Posts

    Re: SQLCODE=-20340

    ‏2011-06-15T15:04:52Z  
    • Jane Man
    • ‏2011-06-10T22:18:04Z
    That is interesting. If http://www.fpml.org/2009/FpML-4-7 is referenced(include/import) by other schema documents, there should not be any error during xsr_complete.

    Openning a PMR may not be a bad idea. Be prepared to submit all the schema files(maybe, the USS commands you used to register this schema as well).
    I finally found the answer.
    In LUW, we began in the REGISTER XMLSCHEMA with the signature xmldsig-core-schema.xsd and ended the series of add xmlschema document commands with the main document.
    In ZOS, I began in the REGISTER XMLSCHEMA with the main document and ended the series of add xmlschema document commands with the signature xmldsig-core-schema.xsd.
    This worked.