Arg. I spoke too soon. Though it now properly lists the parameters, it still also includes a terminated OpGetList. I do not get the appeal of SOAP. It is way too complicated and verbose for what it is trying to do. It's like doing math in Roman Numerals. That stalled math from about 0 until 1400. 8-P

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:s0="urn:HD_Netcool_v1">
  <soap:Header>
    <AuthenticationInfo>
      <userName xsi:type="xsd:string">xx</userName>

      <password xsi:type="xsd:string">xx</password>
    </AuthenticationInfo>
  </soap:Header>

  <soap:Body>
    <s0:OpGetList>
      <OpGetList xsi:nil="true" xsi:type="s0:GetListInputMap" />

      <c-gensym8 xsi:type="xsd:string">OpGetList</c-gensym8>

      <OpGetList xsi:type="s0:GetListInputMap">
        <Qualification xsi:type="xsd:string">'Submitter'="RemedyTicket
+"</Qual           ification>

        <startRecord xsi:type="xsd:string">0</startRecord>

        <maxLimit xsi:type="xsd:string">10</maxLimit>
      </OpGetList>
    </s0:OpGetList>
  </soap:Body>
</soap:Envelope>
[download]