You can scan the main headers of the message for a content-type header with a boundary=string value.  That string, with a "--" prefix, delimits the parts of the message.  And the very end of the message both a prefix and suffix value (--string--).  If you just want the first part, typically the text message, you can just watch for the second part and exit.  I would write some whole messages out to files to see how they are structured.

Here is a sample of what it might look like:

Content-Type: multipart/alternative; boundary=f64af71f2a384073bb33579fd1ecabfd

The various parts of this message have a line "--f64af71f2a384073bb33579fd1ecabfd" at the start.

Note you can also speed up string appends with the += operator.  Line 3130 could be: message$+=x$.

When we install UnForm, we generally have to create the generic libssl.so and libcrypto.so symlinks pointing to whatever the installed version is, if they aren't already there.

My guess would be there is a bug in the older 1.0.1e builds on S1/S2.  You could try 'yum update libssl' and see if that helps.  If they are the same levels of redhat as S3, you might be able to just copy the 1.0.1e files, though I'd sure back up the current ones first.

Are there symlinks pointing to older libssl/libcrypto .so files?

Quotes in csv columns should be ignored by reading applications.  Their purpose is just to hide commas in strings.  So does it matter?

I am trying to parse a fairly large json response from a web service, and just installed the very latest pxplus 2019 to test with. 

Scanning the json string as best I can visually (it's about 2.5mb), I don't see anything but simple json objects, arrays, strings, and numbers (no nested arrays, for example, which have caused errors for me before).  The json does pass validation at jsonlint.com.  But I get an error 17 when trying to use 'dim load' on it.

Is anyone aware of a system variable or tcb() function or whatever that would provide any hint about where in the string the error occurs?

If anyone wants to look at the json, it is here:

https://unform.com/download/test.05292019.json

You can use the xml() function to loop through the xml nodes, and the attribute nodes as well.

 open (unt,isz=1)"test.xml"
 read record (lfo,siz=9999999)xml$
 close (lfo)
 let ofs=0
 let xml1$=xml(next from xml$,ind=ofs,key=tag$) ! get first level xml
 let ofs1=0
 while 1
 let xml2$=xml(next from xml1$,ind=ofs1,key=tag$,opt=prop$,err=*break) ! loop through tags 
 let propofs=0
 while 1
 let propval$=xml(property next from prop$,ind=propofs,key=propname$,err=*break) ! loop through attributes until Name="Shape"
 if propname$="Name" and propval$="Shape" then let found=1; break
 wend
 if found then break
 wend
 print xml2$

I must be blind, but I'm not seeing the download for pxserver anywhere on the pvxplus.com download pages.  Can anyone point me the way?

Devon, is that utility documented?  I don't see it in the pxplus manual.