[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Question on using the HTTPAPI to receive a GUID
GUID's are 128bit (16 byte) integer values...
However, 8 byte integers are the largest most systems support.� So
GUIDs are normally treated as a 16 byte binary string.
When passing between systems, they are usually passed as a human
readable hexadecimal string of either 32 bytes (no dashes) or 36 bytes
(with dashes)
x'c67c7891-267b-42fc-a5da-2ebd30b566fc'
You'll have to see what the web server is returning and simply pass it
back in your next request.
If the web service is using a 16 byte binary string, be careful that
you don't try to translate it into EBCDIC.� Charles
On Mon, Mar 21, 2016 at 10:29 PM, Baeten, John
<[1]John.Baeten@xxxxxxxxxx> wrote:
� �I have a question that I am hoping someone out there has done
before or
� �can point me in the correct direction. At our company we need
to send
� �data to a new SQL server database that will take the formatted
data as
� �XML by doing a POST to a web service URL address.� Our iSeries
is at
� �V7R1M0.
� �To create the XML we are using the CGIDEV2 to create our XML by
using
� �templates.� And this part is working great to create the XML
with no
� �issues.� Then to perform the POST to the URS we are using the
HTTPAPI
� �from Scott Klement.� This part is also working great.
� �We now need to get data back from the SQL server.� The issues
is we
� �need to POST to a URL which will give us back a GUID.� This
GUID will
� �be used to do another POST to retrieve the XML from the SQL
server
� �database that will be processed in our back end programs on the
� �iSeries.
� �I am not sure if the HTTPAPI allows retrieving a GUID.� I have
done
� �numerous searches online and I have not found anything relating
to how
� �to make this work.� So I am asking if anyone knows how to do
this, or
� �could point me in the right direction of some other API or
process to
� �make this work for us.
� �Thank you for your help,
� �John
� �CONFIDENTIALITY NOTICE: This e-mail communication and any
attachments
� �may contain proprietary and privileged information for the use
of the
� �designated recipients named above. Any unauthorized review,
use,
� �disclosure or distribution is prohibited. If you are not the
intended
� �recipient, please contact the sender by reply e-mail and
destroy all
� �copies of the original message.
--------------------------------------------------------------------
---
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[2]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
References
1. mailto:John.Baeten@xxxxxxxxxx
2. 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
-----------------------------------------------------------------------