Difference: 0LASubrDataBadRequest (1 vs. 2)

Revision 22020-03-04 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="FullAPIList"

.DATA BAD REQUEST

Line: 6 to 6

.DATA BAD REQUEST

Usage:

Changed:

<
<

      PASS         <stream_name>              FIELD            SHARE? N
      PASS         <pathname>                 FIELD            SHARE? N
      PASS         <open_mode>                FIELD            SHARE? N
      PASS         <line_termination>         FIELD            SHARE? N
      GOSUB    --- .STREAM OPEN
      *        check for errors
      IF       --- .STREAM OPEN               NE

>
>

      PASS         <error_message>            FIELD            SHARE? N
      GOSUB    --- .DATA BAD REQUEST

Description:

Added:

>
>

This subroutine will return a JSON formatted message to the caller in the form { "Error":"<error_message"}

<error_message> is the text you want to return to the caller (Optional). If nothing is received, then it will default to 'Invalid Request'.

Comments

<--/commentPlugin-->

Revision 12020-03-04 - JeanNeron

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="FullAPIList"

.DATA BAD REQUEST

This subroutine allows you return an error message to the caller. This is only useful when working with the Data API (Release 5.5.0 & higher)

.DATA BAD REQUEST

Usage:

      PASS         <stream_name>              FIELD            SHARE? N
      PASS         <pathname>                 FIELD            SHARE? N
      PASS         <open_mode>                FIELD            SHARE? N
      PASS         <line_termination>         FIELD            SHARE? N
      GOSUB    --- .STREAM OPEN
      *        check for errors
      IF       --- .STREAM OPEN               NE

Description:

Comments

<--/commentPlugin-->

-- Jean Neron - 2020-03-03

View topic | History: r2 < r1 | More topic actions...