| Author |
Message
|
| Glass |
 Posted: Thu Jul 12, 2007 11:47 am Post subject: mqsiimpxmlschema log |
 |
|
Acolyte
Joined: 02 Mar 2006
Posts: 56
|
Hi,
I am using WMB v2.1 and am having trouble running mqsiimpxmlschema to import the XSD files. I am trying to import a few large XSDs and I do not get any error while runniing it. The following is the command I am using:
mqsiimpxmlschema -f test.txt -v -t > logs.txt
After it runs, I do not see the message set created and the log file (logs.txt) stops abruptly. I tried to import a smaller XSD and it works fine.
Is there some file/heap size I need to increase or look at certain log file? db2diag.log did not show anything.
Here is the top and bottom end of the logs.txt file:
| Code: |
XML schema Import Utility V1.10 for WMQI V2.1 - Copyright (C) IBM Corp. 2002 (Aug 23 2002)
Execution date and time 2007-07-12-14.07.30
Processing parameters file parameters.txt
==> checkMRMRelease
<== checkMRMRelease
==> connectToMRM, Database = MRDEV1, User = MQSI
Connection successful MRDEV1
<== connectToMRM
Accessing MRM database: MRDEV1 using: MQSI schema:
==> getMRMInfo. Message Set Name XMLCAN1
==> getPluginHandles
==> insertName WebDav Plug-in Extension
<== insertName returned 1
<== getPluginHandles
==> createAttribute compHandle 00ca9360 pluginHandle 0225e6c0 attrKey 1
<== createAttribute
BIP9404I: The Identifier for Message Set XMLCAN1 is E3211IC096001.
<== getMRMInfo returned 0 errSw 0
==> checkDupMessageName, name CANCELREQUEST
Checking for duplicate message CANCELREQUEST in MessageSet XMLCAN1
<== checkDupMessageName
reading in the schema files
==> readFileData name=cancel.xsd
...
...
...
==> Found an element node - parent=268 elemName=xs:annotation
==> recurseLevel: topLevel=0 parent=268 schemaId=16
==> recurseLevel: topLevel=0 parent=16 schemaId=16
==> recurseLevel: topLevel=0 parent=16 schemaId=16
==> Found an element node - parent=16 elemName=xs:element
==> insertName element
<== insertName returned 266
==> insertName xs
<== insertName returned 66
==> getAttrValue attrName name value contentTypeCode
==> insertName contentTypeCode
<== insertName returned 12029
<== getAttrValue attrFound 1
==> createXMLname xmlId=269
==> createQualName xmlId=269 schemaId=16
==> findPrefixBlock nameSpace=http://integration.sprint.com/v2/common/CanonicalDataModel.xsd
<== findPrefixBlock returned prefixPtr=00000084
==> insertName cdm:contentTypeCode
<== insertName returned 12045
<== createQualName xmlId=269 qName=cdm:contentTypeCode
==> createXMLname xmlId=269 qualName=16
==> recurseLevel: topLevel=0 parent=269 schemaId=16
==> recurseLevel: topLevel=0 parent=269 schemaId=16
==> Found an element node - parent=269 elemName=xs:annotation
==> recurseLevel: topLevel=0 parent=269 schemaId=16
|
The end of the log froma smaller XSD is as follows:
| Code: |
...
Created m_attribute entry for XML Name - id 36134624 attrId 0 name cust:customerDetails
<== insertXMLName AttrId -1
<== CreateMessage
<== buildMRMdata: msgId=36134624
==> endTransaction
<== endTransaction
items added to tables in repository database MRDEV1
M_MESSAGE - 1
M_ELEMENT - 13
M_VALUE - 10
VALUE_MEMBER - 13
M_TYPE - 5
TYPE_MEMBER - 14
M_ATTRIBUTE - 25
MEMBER_ATTRIBUTE - 17
elements reused from existing entries in MessageSet - 0
types reused from existing entries in MessageSet - 0
values reused from existing entries in MessageSet - 1
duplicate elements reused in MessageSet - 0
duplicate values reused in MessageSet - 0
releasing storage areas
releasing file storage areas
Total elapsed time = 0.86
BIP9350I: The message 'customerDetails' has been successfully imported into Message Set 'CUSTOMER3', Identifier E3211IC08Q001.
Informational message - no user action required.
|
Thanks! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Thu Jul 12, 2007 11:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Before Jeff says it...you need to uninstall v2.1 and install v6 as soon as possible. 
Good reasons include:
- v2.1 is out of service
- v6 uses XML Schema as the basis for its message model, so importing and using an XML schema is much more likely to work the way you want it to. |
|
| Back to top |
|
|
| Glass |
| Posted: Thu Jul 12, 2007 12:01 pm Post subject: |
|
|
Acolyte
Joined: 02 Mar 2006
Posts: 56
|
I agree. We will be upgrading to v6 in a few months. but I need to get over this before that. 
Any help for v21 will be great!
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jul 12, 2007 7:14 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess odds were good I would say that...
I do vaguely remember something about adjusting broker memory usages in v2.1... at least it's the kind of thing I remember being at least hinted at in the 2.1 administration guide.
But that's as far as my memory goes.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 12, 2007 10:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I've worked with moderatly sized xsd files on the default settings.
But those days are now behind me! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 12, 2007 10:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Glass wrote: |
| I agree. We will be upgrading to v6 in a few months. but I need to get over this before that. |
Or maybe now? Would get you past this problem..... 
| Glass wrote: |
| Any help for v21 will be great! |
IMHO MQSI 2.1 is beyond help, and has been for some time. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Glass |
| Posted: Fri Jul 13, 2007 3:13 pm Post subject: |
|
|
Acolyte
Joined: 02 Mar 2006
Posts: 56
|
| Thanks guys! I will try to split the XSD and use it. Hopefully it will accept it. |
|
| Back to top |
|
|
|
|
