Sorry for the late reply.
I just checked.

*** This is only a subset of the PTFs which I think is relevant to my DB2
query ***

*On the machine that my SQL works with HTTPS*
Level PTF Group Text
3 SF99711 ALL PTF GROUPS EXCEPT CUMULATIVE PTF
PACKAGE
14283 SF99710 CUMULATIVE PTF PACKAGE C4283710

15317 SF99710 CUMULATIVE PTF PACKAGE C5317710

33 SF99701 DB2 FOR IBM I
39 SF99701 DB2 FOR IBM I
2 SF99657 DB2 WEB QUERY FOR I V2.1.1
11 SF99647 DB2 WEB QUERY FOR I V2.1.0
13 SF99647 DB2 WEB QUERY FOR I V2.1.0
9 SF99637 DB2 WEB QUERY FOR IBM I V1.1.2
11 SF99627 7.1 ELECTRONIC SERVICES GROUP PTF
6 SF99617 DB2 WEB QUERY FOR IBM I V1.1.1
21 SF99572 JAVA
23 SF99572 JAVA

*On the machine that my SQL does not work with HTTPS*
Level PTF Group Text
14283 SF99710 CUMULATIVE PTF PACKAGE C4283710
137 SF99709 GROUP HIPER
39 SF99708 GROUP SECURITY
17 SF99705 HARDWARE AND RELATED PTFS
33 SF99701 DB2 FOR IBM I
11 SF99627 7.1 ELECTRONIC SERVICES GROUP PTF
20 SF99572 JAVA
24 SF99368 IBM HTTP SERVER FOR I


I'm not familiar with PTFs and hardware but judging from the list.
There are a lot of missing DB2 Web Query which I assume is needed to run
the DB2 service sql?

Eric

On 25 July 2016 at 14:42, Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

It works on V7.1 and V7.3.

Check your PTF levels

<httpHeader responseCode="200">
<responseMessage>OK</responseMessage>
<header name="HTTP_RESPONSE_CODE" value="HTTP/1.1 200 OK"/>
<header name="Server" value="nginx"/>
<header name="Access-Control-Allow-Origin" value="*"/>
<header name="Content-Length" value="434"/>
<header name="Date" value="Mon, 25 Jul 2016 13:34:12 GMT"/>
<header name="Content-Type" value="application/json"/>
<header name="Connection" value="keep-alive"/>
<header name="Access-Control-Allow-Credentials" value="true"/>
</httpHeader>

{
"args": {},
"data": "testing",
"files": {},
"form": {},
"headers": {
"Accept": "text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2",
"Accept-Encoding": "gzip,deflate",
"Content-Length": "7",
"Content-Type": "text/plain;charset=utf-8",
"Host": "httpbin.org",
"User-Agent": "DB2 HTTP Consumer 1.0"
},
"json": null,
"origin": "198.89.160.22",
"url": "https://httpbin.org/post";

}


Eric wrote on 7/25/2016 9:10 AM:

Hi,

I tried running this SQL

SELECT * FROM
TABLE(SYSTOOLS.HTTPPOSTCLOBVERBOSE('https://httpbin.org/post', '',
'testing')) AS X


... which sends a web service to https but there is an issue.

This is from the job log.

Message ID . . . . . . : CPF503E

Date sent . . . . . . : 16/07/25 Time sent . . . . . . :
14:06:59


Message . . . . : User-defined function error on member QSQPTABL.



Cause . . . . . : An error occurred while invoking user-defined function

HTTPPOSTCLOBVERBOSE in library SYSTOOLS. The error occurred while
invoking
the associated external program or service program B2RESTUDF: in library

SYSTOOLS.D, program entry point or external name

com.ibm.db2.rest.DB2UDFWrapper.httpPostClobVerbose, specific name

HTTPPOSTCLOBVERBOSENONXML. The error occurred on member QSQPTABL file

QSQPTABL in library QSYS2. The error code is 1. The error codes and
their

meanings follow:

1 -- The external program or service program returned SQLSTATE 38000.
The
text message returned from the program is:

SYSTOOLS.HTTPPOSTCLOBVERBOSE HTTPPOSTCLOBVERBOSENONXML
ãjava.lang.ArrayIn

If I change it to use http, it is fine.

Any ideas?

Thanks,
Eric

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.