Re: Setting up a SQL webservice.

[a4g atl <a4ginatl2@xxxxxxxxx>]

All the set up stuff for the web service is included in my first email.
Changing the user-defined message was not much of a change. I used the
message provided by the system, that is, "Invalid request". I added for
isGateOpen to it to distinguish between messages return by this service and
other system messages.
Thank you, Darryl.

On Thu, May 25, 2023 at 11:53 AM Nadir Amra <amra@xxxxxxxxxx> wrote:

> You may also want to clear out user-defined message so we can see the
> actual error message returned by SQL instead of “Invalid request for
> iSGateOpen.”
>
> -----------------------------------------------
> Nadir Amra
> e-mail: amra@xxxxxxxxxx
>
>
> From: Nadir Amra <amra@xxxxxxxxxx>
> Date: Thursday, May 25, 2023 at 10:52 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: [EXTERNAL] Setting up a SQL webservice.
> Are you on latest IWS Server PTF[1]? If not, load and apply, and redeploy.
>
> What are the SQL types of the data being returned?
>
> Can you specify simple instructions on how one could recreate (I suppose
> what would I need to do for data area?)
>
>
> [1] https://www.ibm.com/support/pages/node/1138612
>
> -----------------------------------------------
> Nadir Amra
> e-mail: amra@xxxxxxxxxx
>
>
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of a4g
> atl <a4ginatl2@xxxxxxxxx>
> Date: Thursday, May 25, 2023 at 7:29 AM
> To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: [EXTERNAL] Setting up a SQL webservice.
> I cannot get this simple webservice to work. I need the help of the guru's
> on this one puh leez.
>
> The details are below.
>
> There are no input parameters but there is one output parameter.
>
> When I call the service, it does not appear to be calling the service
> correctly. I do get the JSON message below.
>
> The service is call as follows:
>
> *http://my_system:10010/web/service/isGateOpen
> <http://my_system:10010/web/service/isGateOpen >*
>
>
> Can someone help with what's not right?
>
> TIA, Darryl Freinkel.
>
> URI path template: = /
>
> Secure transport required: = No
>
> Protect using authentication method: = *NONE
>
> Database system: = localhost
>
> Default schema: = qsys2
>
> Naming convention: = *SQL
>
> Library list: = *LIBL
>
> Procedure name = isGateOpen
>
> SQL statement/Parameter name = select data_area_value from
>   table(qsys2.data_area_info(DATA_AREA_LIBRARY => 'THE_LIBRARY',
>                              DATA_AREA_NAME    => 'THE_DATA_AREA'))
>
> Usage = No options to enter any values.
>
> Data Type = No options to enter any values.
>
> SQL result type: = Single-row result set
>
> Trim mode for output fields = None
>
> SQL state information in response: = On errors
>
> User-defined error message: = Invalid request for iSGateOpen.
>
> HTTP status code on SQL success: = 200
>
> HTTP status code on SQL failure: = 500
>
> Procedure name: = isGateOpen
>
> URI path template for resource: = /
>
> HTTP request method: GET
>
> URI path template for method: *NONE
>
> HTTP header information: = *NONE
>
> Allowed input media types: = *ALL
>
> Returned output media types: = JSON
>
> Identifier for input wrapper element: = isGateOpenInput
>
> Identifier for output wrapper element: = isGateOpenResult
>
> Use existing ID = entered the user ID
>
>
>
>
> This is what was returned in the JSON:
>
>
> {
>
>   "SQLStateInfo": {
>
>     "rowsAffectedCounts": null,
>
>     "SQLError": null,
>
>     "SQLWarnings": [
>
>       {
>
>         "SQLState": "HY001",
>
>         "SQLCode": 1301,
>
>         "message": "Invalid request for iSGateOpen."
>
>       }
>
>     ]
>
>   }
>
> }
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l .
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.