[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xml-sax issue



One other thing to Alan, I even added a small XML doc inside the program
myself :
<MYXML><CLAIM><results><claimno>123</claimno></results></claim></myxml>

and it doesn't work with that either.

Dutch


> As a follow up, WDSL2RPG just builds the framework, there is no code
> included that handles the incoming XML that is what I was using xml-sax
> for.
>
> We have an existing process that is running today using the same mechanism
> but unfortunately that developer is no longer here.
>
> Also, WSDL2RPG just builds the service program it doesn't process the
> incoming XML.
>
> Dutch
>
>
>>    So what I hear is that this is not an XML-SAX issue at all. It is a
>>    WSDL2RPG issue and how you use that program. I had thought you were
>>    using XML-SAX directly but based on what you are saying you are using
>>    WSDL2RPG. Trying to give you instructions on how to play tennis when
>>    you are playing golf. Two different games.
>>    You need to either use XML-SAX directly or use WSDL2RPG and ask for
>>    help on that program.
>>
>>    On Tue, Sep 8, 2015 at 7:09 PM, RPG List <[1]rpglist@xxxxxxxxxxx>
>>    wrote:
>>
>>      The service program was build with WSDL2RPG and that is where the
>>      varying
>>      was set.  I just never changed it.
>>      > Stripped out the subst and it bombs.
>>      >
>>      > the XML parser detected error code 302.
>>      >
>>      >
>>      >>Â  Â  I am not clear as to why you would be using a VarChar field
>>      in any
>>      >>Â  Â  case.
>>      >>Â  Â  The data coming in is not a VarChar. It is a straight
>>      character and
>>      >> you
>>      >>Â  Â  would not be trimming it.
>>      >>Â  Â  The data length parameter says how long the data actually
>>      is. All it
>>      >> is
>>      >>Â  Â  passing is a pointer to the data so as in my example
>> program
>>      >>Â  Â  dcl-s Data Char(32765) Based(InPointerToData);
>>      >>Â  Â  So lets say it a Order number and the length says 7.
>>      >>Â  Â  OrderNumber = %Subst(Data:1:Length);
>>      >>Â  Â  This pulls that value out of the incoming field.
>>      >>Â  Â  Now if you try to reference anything past 7 in this
>> example,
>>      you are
>>      >>Â  Â  going to get garbage.
>>      >>Â  Â  On the next *XMLCHARS event it might be 50.
>>      >>Â  Â  You need to look for *XML_START_ELEMENT and see if this an
>>      element
>>      >> that
>>      >>Â  Â  you want.
>>      >>Â  Â  What I do is just build a tag.
>>      >>Â  Â  So first time in
>>      >>Â  Â  /REQUEST
>>      >>Â  Â  Then
>>      >>Â  Â  /REQUEST/ORDER
>>      >>Â  Â  then
>>      >>Â  Â  /REQUEST/ORDER/NUMBER
>>      >>Â  Â  Then in the *XML_CHARS event I just compare to see if I
>> want
>>      to
>>      >> process
>>      >>Â  Â  that event
>>      >>Â  Â  If Tag = '/REQUEST/ORDER/NUMBER';
>>      >>Â  Â  ÃÂ  // Process order number.
>>      >>Â  Â  etc.
>>      >>
>>      >>Â  Â  On Tue, Sep 8, 2015 at 12:44 PM, Elbert Cook
>>      >>Â  Â  <[1][2]elbert@xxxxxxxxxxxxxxx> wrote:
>>      >>
>>      >>Â  Â  Â  ÃÂ  Ã Could the problem be something like the following
>>      scenario. If
>>      >>Â  Â  Â  not my
>>      >>Â  Â  Â  ÃÂ  Ã apologizes for not understanding the question.
>>      >>Â  Â  Â  ÃÂ  Ã xml = %trim(%subst(GetResponse: 3: 5000));
>>      >>Â  Â  Â  ÃÂ  Ã When you have a varying field, the field contains
>> 2
>>      extra
>>      >>Â  Â  Â  invisible
>>      >>Â  Â  Â  ÃÂ  Ã positions, contain the length of the data.
>>      >>Â  Â  Â  ÃÂ  Ã D Data1 s 20a
>>      >>Â  Â  Â  ÃÂ  Ã D Data2 s 20a
>>      >>Â  Â  Â  ÃÂ  Ã D Data3 s 20a
>>      >>Â  Â  Â  ÃÂ  Ã D ds
>>      >>Â  Â  Â  ÃÂ  Ã D GetResponse 20a varying inz('<MMMProcess>')
>>      >>Â  Â  Â  ÃÂ  Ã D InvisLen 2a overlay(GetResponse: 1)
>>      >>Â  Â  Â  ÃÂ  Ã D Value 20a overlay(GetResponse: 3)
>>      >>Â  Â  Â  ÃÂ  Ã Data1 = Value;
>>      >>Â  Â  Â  ÃÂ  Ã Data2 = %subst(GetResponse: 1)
>>      >>Â  Â  Â  ÃÂ  Ã Data3 = %subst(GetResponse: 3)
>>      >>Â  Â  Â  ÃÂ  Ã Data1 contains "<MMMProcess>"
>>      >>Â  Â  Â  ÃÂ  Ã Data2 contains "<MMMProcess>"
>>      >>Â  Â  Â  ÃÂ  Ã Data3 contains "MMProcess>"
>>      >>Â  Â  Â  ÃÂ  Ã With %subst your start with position 1, if you are
>>      using a
>>      >> data
>>      >>Â  Â  Â  ÃÂ  Ã structure
>>      >>Â  Â  Â  ÃÂ  Ã you start with position 3.
>>      >>Â  Â  Â  ÃÂ  Ã ----> I'm getting a weird character Ã<MMMProcess>
>>      >>Â  Â  Â  ÃÂ  Ã Yes, GetResponse would have a weird first two
>>      position if you
>>      >>Â  Â  Â  are
>>      >>Â  Â  Â  ÃÂ  Ã retrieving
>>      >>Â  Â  Â  ÃÂ  Ã the first two invisible fields.
>>      >>Â  Â  Â  ÃÂ  Ã -----Original Message-----
>>      >>Â  Â  Â  ÃÂ  Ã From: Paul Roy [mailto:[2][3]paul.roy@xxxxxxx]
>>      >>Â  Â  Â  ÃÂ  Ã Sent: Tuesday, September 08, 2015 3:02 PM
>>      >>Â  Â  Â  ÃÂ  Ã To: HTTPAPI and FTPAPI Projects
>>      >>Â  Â  Â  ÃÂ  Ã Subject: Re: xml-sax issue
>>      >>Â  Â  Â  ÃÂ  Ã that's looks like a problem of a variable length
>>      string not
>>      >>Â  Â  Â  correctly
>>      >>Â  Â  Â  ÃÂ  Ã defined...
>>      >>Â  Â  Â  ÃÂ  Ã mismatch in a definition of a program/procedure ?
>>      >>Â  Â  Â  ÃÂ  Ã Paul
>>      >>Â  Â  Â  ÃÂ  Ã From: "RPG List" <[3][4]rpglist@xxxxxxxxxxx>
>>      >>Â  Â  Â  ÃÂ  Ã To: "HTTPAPI and FTPAPI Projects"
>>      >>Â  Â  Â  <[4][5]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
>>      >>Â  Â  Â  ÃÂ  Ã Date: 08/09/2015 19:42
>>      >>Â  Â  Â  ÃÂ  Ã Subject: Re: xml-sax issue
>>      >>Â  Â  Â  ÃÂ  Ã Sent by:
>>      [1][5][6]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>      >>Â  Â  Â  ÃÂ  Ã John,
>>      >>Â  Â  Â  ÃÂ  Ã I don't recall off the top of my head. He tried
>>      sending it as
>>      >>Â  Â  Â  UTF-16
>>      >>Â  Â  Â  ÃÂ  Ã but
>>      >>Â  Â  Â  ÃÂ  Ã its defaulting to 8 so I'm not sure if that's the
>>      problem or
>>      >>Â  Â  Â  not.
>>      >>Â  Â  Â  ÃÂ  Ã I recompiled the srvpgm and stubs and created the
>>      sample
>>      >>Â  Â  Â  program, in
>>      >>Â  Â  Â  ÃÂ  Ã debug
>>      >>Â  Â  Â  ÃÂ  Ã when I check the xml value immediately following
>>      the web
>>      >>Â  Â  Â  service call
>>      >>Â  Â  Â  ÃÂ  Ã I'm
>>      >>Â  Â  Â  ÃÂ  Ã getting a weird character Ã<MMMProcess>
>>      >>Â  Â  Â  ÃÂ  Ã and it is starting in position 2. I don't recall
>>      seeing this
>>      >>Â  Â  Â  before.
>>      >>Â  Â  Â  ÃÂ  Ã Ideas?
>>      >>Â  Â  Â  ÃÂ  Ã > XML-INTO is usually a lot less work than XML-SAX
>>      unless you
>>      >>Â  Â  Â  only want
>>      >>Â  Â  Â  ÃÂ  Ã > a small portion of the data. From what you
>> posted
>>      earlier it
>>      >>Â  Â  Â  didn?t
>>      >>Â  Â  Â  ÃÂ  Ã > look that complex - what problems did you
>>      encounter with
>>      >>Â  Â  Â  XML-INTO?
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã > On Sep 8, 2015, at 2:21 PM, RPG List
>>      >> <[6][7]rpglist@xxxxxxxxxxx>
>>      >>Â  Â  Â  wrote:
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã >> Scott the 3:5000 is a typo, that should be a 1.
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  ÃÂ  Ã >> I am using XML-SAX because I wasn't able to get
>>      XML-INTO to
>>      >>Â  Â  Â  work.
>>      >>Â  Â  Â  ÃÂ  Ã >> However, I found out this morning that the XML
>>      is coming in
>>      >>Â  Â  Â  as
>>      >>Â  Â  Â  ÃÂ  Ã UTF-8.
>>      >>Â  Â  Â  ÃÂ  Ã >> I asked him to change that to 16 for a test,
>>      since I recall
>>      >>Â  Â  Â  reading
>>      >>Â  Â  Â  ÃÂ  Ã >> that RPG does not like 8.
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  ÃÂ  Ã >> I'm open to suggestions to make this learning
>>      curve easier
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  ÃÂ  Ã >>> Dutch,
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>> You are doing this:
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>> xml = %trim(%subSt(GetResponse:3:5000));
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>> Can you explain why you are doing that %subst?
>>      Wouldn't
>>      >>Â  Â  Â  that cause
>>      >>Â  Â  Â  ÃÂ  Ã the
>>      >>Â  Â  Â  ÃÂ  Ã >>> '<M' at the start of the XML document to be
>>      chopped off,
>>      >>Â  Â  Â  making
>>      >>Â  Â  Â  ÃÂ  Ã this
>>      >>Â  Â  Â  ÃÂ  Ã an
>>      >>Â  Â  Â  ÃÂ  Ã >>> invalid document?
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>> The %trim() is not necessary, but shouldn't
>>      hurt anything.
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>> Can you explain why you want to use XML-SAX
>>      here instead
>>      >> of
>>      >>Â  Â  Â  ÃÂ  Ã XML-INTO
>>      >>Â  Â  Â  ÃÂ  Ã or
>>      >>Â  Â  Â  ÃÂ  Ã >>> the XML parser included with HTTPAPI? (Which
>> is
>>      a wrapper
>>      >>Â  Â  Â  around
>>      >>Â  Â  Â  ÃÂ  Ã >>> Expat)
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>> On 9/4/2015 4:34 PM, RPG List wrote:
>>      >>Â  Â  Â  ÃÂ  Ã >>>> Scott,
>>      >>Â  Â  Â  ÃÂ  Ã >>>> I'm not sure we don't have another problem.
>>      Here's why
>>      >>Â  Â  Â  when I step
>>      >>Â  Â  Â  ÃÂ  Ã >>>> through the xmlhandler, I get the
>>      start_document on the
>>      >>Â  Â  Â  first
>>      >>Â  Â  Â  ÃÂ  Ã read,
>>      >>Â  Â  Â  ÃÂ  Ã >>>> and then I get end_document on the second
>>      read. That's
>>      >> it.
>>      >>Â  Â  Â  Its
>>      >>Â  Â  Â  ÃÂ  Ã >>>> almost
>>      >>Â  Â  Â  ÃÂ  Ã as
>>      >>Â  Â  Â  ÃÂ  Ã >>>> though its never seeing the data further. I
>>      ran a test
>>      >>Â  Â  Â  using the
>>      >>Â  Â  Â  ÃÂ  Ã >>>> following:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>> XML = '<xmlTest>+
>>      >>Â  Â  Â  ÃÂ  Ã >>>> <name type="author">AS400 Sample Code/name>+
>>      >>Â  Â  Â  ÃÂ  Ã >>>> </xmlTest>';
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>> that worked.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>> Here is what the xml document looks like
>>      coming in:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â
>>      '<MMMProcess><Results><Claim>8104550</Claim><Amount>1995.83</'
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      'Amount><Code>7320</Code><Xrg>53</Xrg><MEANLOS2>2</MEAN'
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      'LOS2><Error_Code>0</Error_Code></Results></MMMProcess>'
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>> I just can't find what's wrong with the xml..
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> Dutch,
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> The XML processing instructions ("header" as
>>      you call
>>      >> it)
>>      >>Â  Â  Â  are
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> optional.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> They are not required.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> The problem is what I said in my first reply
>>      to you.
>>      >>Â  Â  Â  Please read
>>      >>Â  Â  Â  ÃÂ  Ã the
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> article I linked to so you can learn how
>>      XML-SAX works.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> -SK
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>> On 9/4/2015 3:18 PM, RPG List wrote:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>> one additional issue I saw this morning
>>      Scott and maybe
>>      >>Â  Â  Â  this is
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>> the problem, the incoming XML does not have
>>      what I
>>      >> would
>>      >>Â  Â  Â  call a
>>      >>Â  Â  Â  ÃÂ  Ã standard
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>> header:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>> IE: it does not have a version or
>>      description that I
>>      >> see
>>      >>Â  Â  Â  in most
>>      >>Â  Â  Â  ÃÂ  Ã xml
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>> documents, maybe that's needed or maybe
>> not?
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> Dutch,
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> This looks an awful lot like a program
>> that
>>      I wrote a
>>      >>Â  Â  Â  long time
>>      >>Â  Â  Â  ÃÂ  Ã ago
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> to
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> print the XML events. I would not
>> recommend
>>      using this
>>      >>Â  Â  Â  to
>>      >>Â  Â  Â  ÃÂ  Ã actually
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> parse a document -- to parse with XML-SAX
>>      you're going
>>      >>Â  Â  Â  to need
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> to create a stack of XML elements
>>      (implemented in RPG
>>      >>Â  Â  Â  as an
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> array, most
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> likely)
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> and keep track of the current XML element
>>      you're
>>      >>Â  Â  Â  working on,
>>      >>Â  Â  Â  ÃÂ  Ã etc.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> There
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> was another program included in that same
>>      article
>>      >>Â  Â  Â  called
>>      >>Â  Â  Â  ÃÂ  Ã "CustXml"
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> that
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> demonstrates this -- that program would be
>>      a better
>>      >>Â  Â  Â  starting
>>      >>Â  Â  Â  ÃÂ  Ã point.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      [2][7][8]http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax
>>      -
>>      >>Â  Â  Â  opco
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> de
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> (use the "print" option to format the code
>>      better,
>>      >>Â  Â  Â  Penton media
>>      >>Â  Â  Â  ÃÂ  Ã has
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> screwed up the code figures in their
>>      article archive)
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> Based on what you've shown us, the only
>>      thing you'd
>>      >> get
>>      >>Â  Â  Â  in your
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> string is the name of the XML tag you're
>>      parsing.
>>      >>Â  Â  Â  (Since that's
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> what's pointed to by "string" during the
>>      >>Â  Â  Â  XML_START_ELEMENT
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> event.)
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> You say you're getting nothing at all...?
>>      Since you're
>>      >>Â  Â  Â  getting
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> it from the 'value' field, you'd need to
>>      show us the
>>      >>Â  Â  Â  definition
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> and/or
>>      >>Â  Â  Â  ÃÂ  Ã code
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> that
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> populates 'value' for us to see how that
>>      works. Funny
>>      >>Â  Â  Â  that you
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> omitted that part of the code considering
>>      that your
>>      >>Â  Â  Â  question is
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> about it?
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> Also, is this part of a program that uses
>>      HTTPAPI or
>>      >>Â  Â  Â  FTPAPI? If
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> so, I
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> guess we can discuss it here... if not,
>>      however, this
>>      >>Â  Â  Â  really
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> doesn't
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> belong on this mailing list.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> -SK
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>> On 9/3/2015 9:17 PM, RPG List wrote:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> I am attempting to parse out the data I'm
>>      getting
>>      >> from
>>      >>Â  Â  Â  a web
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> service and I'm having a little trouble.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> I'm using the following as my to the
>>      handler:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> xml = %trim(%subSt(GetResponse:3:5000));
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> xml-sax %handler(xmlHandler: ignoreMe)
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> %XML(xml: 'doc=string');
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> GetResponse has the full xml string I'm
>>      expecting.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> my xmlhandler is defined as follows:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> P xmlHandler b
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> D pi 10i 0
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> D ignore 1a
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> D event 10i 0 value
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> D string * value
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> D stringLen 20i 0 value
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> D exceptionId 10i 0 value
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> I then have the following code in the
>>      procedure:
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> OutputXML.name = XML_Event_Name(event);
>>      >> OutputXML.data
>>      >>Â  Â  Â  =
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> *blanks;
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> select;
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> when string=*null or stringlen<1;
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> // no string given...
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> when stringlen>%size(value);
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> OutputXML.data = '** string length
>>      invalid'; other;
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> OutputXML.data =
>>      %subst(value:1:stringlen); endsl;
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> // Change Current XML group if applicable
>>      Select;
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> When OutputXML.name =
>> 'XML_START_ELEMENT';
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> The problem is outputXML.data never has a
>>      value that
>>      >> I
>>      >>Â  Â  Â  can
>>      >>Â  Â  Â  ÃÂ  Ã see.
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> Am
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> I
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>> doing something wrong or am I missing a
>>      step?
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã >>> This is the FTPAPI mailing list. To
>>      unsubscribe, please go
>>      >>Â  Â  Â  to:
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      [3][8][9]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã >>>
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã >> This is the FTPAPI mailing list. To
>> unsubscribe,
>>      please go
>>      >>Â  Â  Â  to:
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      [4][9][10]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã >>
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã > Jon Paris
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã > [5][10][11]www.partner400.com
>>      >>Â  Â  Â  ÃÂ  Ã > [6][11][12]www.SystemiDeveloper.com
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã > This is the FTPAPI mailing list. To unsubscribe,
>>      please go
>>      >>Â  Â  Â  to:
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      [7][12][13]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  ÃÂ  Ã >
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã This is the FTPAPI mailing list. To unsubscribe,
>>      please go to:
>>      >>Â  Â  Â  ÃÂ  Ã
>>      [8][13][14]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  Ã
>>      >>Â  Â  Â  Ã
>>      >>
>>      ------------------------------------------------------------------
>>      >>Â  Â  Â  -----
>>      >>Â  Â  Â  ÃÂ  Ã Disclaimer
>>      >>Â  Â  Â  ÃÂ  Ã The information contained in this communication
>>      from the
>>      >> sender
>>      >>Â  Â  Â  is
>>      >>Â  Â  Â  ÃÂ  Ã confidential. It is intended solely for use by the
>>      recipient
>>      >>Â  Â  Â  and others
>>      >>Â  Â  Â  ÃÂ  Ã authorized to receive it. If you are not the
>>      recipient, you
>>      >> are
>>      >>Â  Â  Â  hereby
>>      >>Â  Â  Â  ÃÂ  Ã notified that any disclosure, copying,
>> distribution
>>      or taking
>>      >>Â  Â  Â  action in
>>      >>Â  Â  Â  ÃÂ  Ã relation of the contents of this information is
>>      strictly
>>      >>Â  Â  Â  prohibited and
>>      >>Â  Â  Â  ÃÂ  Ã may be unlawful.
>>      >>Â  Â  Â  ÃÂ  Ã This email has been scanned for viruses and
>>      malware, and may
>>      >>Â  Â  Â  have been
>>      >>Â  Â  Â  ÃÂ  Ã automatically archived by Mimecast Ltd, an
>>      innovator in
>>      >>Â  Â  Â  Software as a
>>      >>Â  Â  Â  ÃÂ  Ã Service (SaaS) for business. Providing a safer and
>>      more useful
>>      >>Â  Â  Â  place
>>      >>Â  Â  Â  ÃÂ  Ã for your human generated data. Specializing in;
>>      Security,
>>      >>Â  Â  Â  archiving and
>>      >>Â  Â  Â  ÃÂ  Ã compliance. To find out more [9]Click Here.
>>      >>Â  Â  Â  References
>>      >>Â  Â  Â  ÃÂ  Ã 1.
>>      mailto:[14][15]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>      >>Â  Â  Â  ÃÂ  Ã 2.
>>      >>Â  Â  Â
>>      [15][16]http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-
>>      opco
>>      >>Â  Â  Â  ÃÂ  Ã 3.
>>      [16][17]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã 4.
>>      [17][18]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã 5. [18][19]http://www.partner400.com/
>>      >>Â  Â  Â  ÃÂ  Ã 6. [19][20]http://www.SystemiDeveloper.com/
>>      >>Â  Â  Â  ÃÂ  Ã 7.
>>      [20][21]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã 8.
>>      [21][22]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â  ÃÂ  Ã 9. [22][23]http://www.mimecast.com/products/
>>      >>Â  Â  Â
>>      --------------------------------------------------------------------
>>      >>Â  Â  Â  ---
>>      >>Â  Â  Â  This is the FTPAPI mailing list.ÃÂ  To unsubscribe,
>>      please go to:
>>      >>Â  Â  Â
>>      [23][24]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  Â
>>      --------------------------------------------------------------------
>>      >>Â  Â  Â  ---
>>      >>
>>      >> References
>>      >>
>>      >>Â  Â  1. mailto:[25]elbert@xxxxxxxxxxxxxxx
>>      >>Â  Â  2. mailto:[26]paul.roy@xxxxxxx
>>      >>Â  Â  3. mailto:[27]rpglist@xxxxxxxxxxx
>>      >>Â  Â  4. mailto:[28]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>>      >>Â  Â  5. mailto:[29]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>      >>Â  Â  6. mailto:[30]rpglist@xxxxxxxxxxx
>>      >>Â  Â  7.
>>      [31]http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-opco
>>      >>Â  Â  8. [32]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â  9. [33]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 10. [34]http://www.partner400.com/
>>      >>Â  Â 11. [35]http://www.SystemiDeveloper.com/
>>      >>Â  Â 12. [36]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 13. [37]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 14. mailto:[38]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>      >>Â  Â 15.
>>      [39]http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-opco
>>      >>Â  Â 16. [40]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 17. [41]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 18. [42]http://www.partner400.com/
>>      >>Â  Â 19. [43]http://www.SystemiDeveloper.com/
>>      >>Â  Â 20. [44]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 21. [45]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>Â  Â 22. [46]http://www.mimecast.com/products/
>>      >>Â  Â 23. [47]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>
>>      --------------------------------------------------------------------
>>      ---
>>      >> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>>      >> [48]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >>
>>      --------------------------------------------------------------------
>>      ---
>>      >>
>>      >
>>      >
>>      >
>>      --------------------------------------------------------------------
>>      ---
>>      > This is the FTPAPI mailing list.  To unsubscribe, please go to:
>>      > [49]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      >
>>      --------------------------------------------------------------------
>>      ---
>>      >
>>      >
>>      --------------------------------------------------------------------
>>      ---
>>      This is the FTPAPI mailing list.  To unsubscribe, please go to:
>>      [50]http://www.scottklement.com/mailman/listinfo/ftpapi
>>      --------------------------------------------------------------------
>>      ---
>>
>> References
>>
>>    1. mailto:rpglist@xxxxxxxxxxx
>>    2. mailto:elbert@xxxxxxxxxxxxxxx
>>    3. mailto:paul.roy@xxxxxxx
>>    4. mailto:rpglist@xxxxxxxxxxx
>>    5. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>>    6. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>    7. mailto:rpglist@xxxxxxxxxxx
>>    8. http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-
>>    9. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   10. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   11. http://www.partner400.com/
>>   12. http://www.SystemiDeveloper.com/
>>   13. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   14. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   15. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>   16. http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-opco
>>   17. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   18. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   19. http://www.partner400.com/
>>   20. http://www.SystemiDeveloper.com/
>>   21. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   22. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   23. http://www.mimecast.com/products/
>>   24. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   25. mailto:elbert@xxxxxxxxxxxxxxx
>>   26. mailto:paul.roy@xxxxxxx
>>   27. mailto:rpglist@xxxxxxxxxxx
>>   28. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>>   29. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>   30. mailto:rpglist@xxxxxxxxxxx
>>   31. http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-opco
>>   32. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   33. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   34. http://www.partner400.com/
>>   35. http://www.SystemiDeveloper.com/
>>   36. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   37. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   38. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>   39. http://iprodeveloper.com/print/rpg-programming/rpgs-xml-sax-opco
>>   40. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   41. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   42. http://www.partner400.com/
>>   43. http://www.SystemiDeveloper.com/
>>   44. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   45. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   46. http://www.mimecast.com/products/
>>   47. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   48. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   49. http://www.scottklement.com/mailman/listinfo/ftpapi
>>   50. http://www.scottklement.com/mailman/listinfo/ftpapi
>> -----------------------------------------------------------------------
>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>> http://www.scottklement.com/mailman/listinfo/ftpapi
>> -----------------------------------------------------------------------
>>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>
>


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------