| Author |
Message
|
| Dirk |
 Posted: Fri Apr 04, 2003 5:47 am Post subject: Integrator V2.1. SupportPacs ID04 for DTD and W3C Schema |
 |
|
Newbie
Joined: 04 Apr 2003
Posts: 1
Location: Germany
|
Dear all,
I use Integrator V2.1. Tried to use SupportPacs ID04 for DTD and W3C Schema import.
After inserting a new Message Set Name in ControlCenter and Check in (no deploy) and stopping the ConfigManager I used mqsiimpschema.exe to import schema but got mistake:
***** Unable to retrieve SQLSTATE diagrc 100 for SQLFetch in routine getMRMInfo
*****Database error 100 during SQLFetch in routine getMRMInfo SQLSTATE
No data available for fetch - rc=100
MRM info gathered for MessageSet DirksTest id 0 NextElementID 0 nextAttrId 0 nextMbrAttr -1
<== getMRMInfo returned 0 errSw 1
Errors accessing MRM database - RC = 0.
What is wrong ?
What should I do for inserting the MessageSet Name in ControlCenter before using the support program ? |
|
| Back to top |
|
 |
| MVO |
| Posted: Tue Jul 27, 2004 11:43 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
It looks like id04 does NOT work with WMQI 2.1
I successfully used it with MQSI 2.0.2 to import an XML schema into MRM but cannot use it any more with WMQI 2.1. Got the same error rc100.
I know that this supportpacs has been withdrawn. Is there any equivalent utility provided by IBM ? I really need to run another import because my XML schema is changing again.
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 27, 2004 11:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
2.1 allows you to import XML schemas natively, no support pack needed.
There's an mqsiimpxmlschema (or some such) command installed in the bin folder of your configmgr machinee.
If you're at a recent FP/CSD level.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Jul 27, 2004 3:31 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I believe mqsiimpxmlschema command was added in WMQI 2.1 CSD3.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 27, 2004 4:53 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kirani wrote: |
| I believe mqsiimpxmlschema command was added in WMQI 2.1 CSD3. |
I believe that too!
I just don't remember it... 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MVO |
| Posted: Wed Jul 28, 2004 7:09 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
Hi,
I'm running mqsiimpXMLschema but getting this error:
BIP9406I: The Xerces parser has been successfully initialized.
Informational message - no action required.
BIP9422S: The DOMParser reported an error during parsing.
The DOMParser produced the following error message: Line Number '119', Column Nu
mber '1', Error Text: 'An exception occured! Type:UnexpectedEOFException, Messag
e:The end of input was not expected'
Examine your schema for errors, with the aid of the error message supplied by th
e DOMParser error handler.
BIP9351S: Errors were detected - import of message set 'MOM14' was unsuccessful
- please make corrections and rerun the import
Examine the preceding error messages, correct the problem(s) and rerun the impor
t.
BIP9358W: No changes were made to the repository
Examine the preceding messages, correct the problem(s) and rerun the import.
Line#119 is the last line of the schema, it reads:
</xsd:schema>
This is my schema:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Envelope” type=“EnvelopeType”/>
<xsd:complexType name=“EnvelopeType”>
<xsd:sequence>
<xsd:element name=“Header” type=“HeaderType”/>
<xsd:element name=“Body” type=“BodyType”/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name=“HeaderType”>
<xsd:sequence>
<xsd:element name=“CPICVer” type=“Str256”/>
<xsd:element name=“AgencyId” type=“Str256” minOccurs=“0”/>
<xsd:element name=“UserId” type=“Str256” minOccurs=“0”/>
<xsd:element name=“Role” type=“Str256” minOccurs=“0”/>
<xsd:element name=“Origin” type=“QueueType” minOccurs=“0”/>
<xsd:element name=“Routing” type=“QueueType” minOccurs=“0”/>
<xsd:element name=“UDF” type=“Str256” minOccurs=“0”/>
<xsd:element name=“Priority” type=“Str256” minOccurs=“0”/>
<xsd:choice>
<xsd:element name=“TxcnSrvc”>
<xsd:complexType>
<xsd:attribute name=“txcnActn” use=“required”>
<xsd:simpleType>
<xsd:restriction base=“xsd:string”>
<xsd:enumeration value=“Ping”/>
<xsd:enumeration value=“Pong”/>
<xsd:enumeration value=“Request”/>
<xsd:enumeration value=“Reply”/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name=“MsgSrvc”>
<xsd:complexType>
<xsd:attribute name=“msgActn” use=“required”>
<xsd:simpleType>
<xsd:restriction base=“xsd:string”>
<xsd:enumeration value=“Ping”/>
<xsd:enumeration value=“Pong”/>
<xsd:enumeration value=“Send”/>
<xsd:enumeration value=“Receive”/>
<xsd:enumeration value=”OffLine”/>
<xsd:enumeration value=”OnLine”/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name=“BodyType”>
<xsd:choice>
<xsd:element name=“TxcnFmt” type=“IllegalXMLCharacterTagsType”/>
<xsd:element name=“MsgFFmt” type=“IllegalXMLCharacterTagsType”/>
<xsd:element name=“MsgData”>
<xsd:complexType>
<xsd:sequence>
<xsd:element name=“GMTTime” type=“Str256”/>
<xsd:element name=“QMgrName" type="Str256”/>
<xsd:element name=“ORI" type="Str256”/>
<xsd:element name=“AgencyDecsription" type="Str256”/>
<xsd:element name=“AgencyNotes" type="Str256”/>
<xsd:element name=“OffLineTime" type="Str256”/>
<xsd:element name=“OnLineTime" type="Str256”/>
<xsd:element name=“PlannedOffLineGMTTime" type="Str256”/>
<xsd:element name=“PlannedOnLineGMTTime" type="Str256”/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name=“QueueType”>
<xsd:sequence>
<xsd:element name=“QMgrName” type=“Str256”/>
<xsd:element name=“QName” type=“Str256”/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name=“Str256”>
<xsd:restriction base=“xsd:string”>
<xsd:maxLength value=“256”/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name=“IllegalXMLCharacterTagsType” mixed=“true”>
<xsd:element name=“NUL” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“SOH” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“STX” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“ETX” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“EOT” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“ENQ” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“ACK” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“BEL” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“BS” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“VT” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“FF” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“SO” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“SI” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“DLE” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“DC1” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“DC2” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“DC3” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“DC4” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“NAK” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“SYN” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“ETB” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“CAN” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“EM” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“SUB” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“ESC” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“FS” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“GS” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“RS” type=“EmptyType” minOccurs=“0”/>
<xsd:element name=“US” type=“EmptyType” minOccurs=“0”/>
</xsd:complexType>
<xsd:complexType name=“EmptyType”>
</xsd:complexType>
</xsd:schema>
What's wrong ? |
|
| Back to top |
|
|
| MVO |
| Posted: Wed Jul 28, 2004 7:19 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
Forget about my previous post. I realize that I have invalid characters in my schema file....
 |
|
| Back to top |
|
|
| MVO |
| Posted: Wed Jul 28, 2004 7:44 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
Now I'm getting this error:
BIP9398S: An error occurred whilst accessing the MRM database.
The error occurred in Function getSimpleTypeHandle calling MRMFindDefinition. The return code = -4.
The meaning of the error code is : Requested Component does not exist
Check that the XML Schema being imported is valid. The meaning of the error
code displayed will help determine the cause of the error. More diagnostic
information can be obtained from the XML schema importer by using the verbose
and trace options. If the cause of the error cannot be determined please contact
your IBM support center. |
|
| Back to top |
|
|
| Empeterson |
| Posted: Wed Jul 28, 2004 11:32 am Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
2.1 does not support namespaces, so that COULD be your problem.
_________________
IBM Certified Specialist: MQSeries
IBM Certified Specalist: Websphere MQ Integrator |
|
| Back to top |
|
|
|
|
