IBM Support

II14827: DB2 FOR Z/OS NATIVE RESTFUL SERVICES - ADDITIONAL DOCUMENTATION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • INTRAN

Error description

  • 5740XYR00 Information APAR for DB2 for z/OS native RESTful
    services support
    
    APARs related to DB2 native REST services support can be
    located by searching retain using the keyword "DB2REST".
    
    Additional Documentation Items:
    
    - There are no additional documentation items at this time.
    
    DB2 V11 APAR Information
    ========================
    
    -------------------------------------------------------------
    Known Restrictions/Limitations for DB2 V11:
    -------------------------------------------------------------
    
    - A Db2 RESTful service created with an SQL statement which
      refers to data at a remote DRDA location is not supported.
      There are no future plans to remove this restriction.
    
    - Using a Db2 RESTful service to call a Db2 stored procedure
      which returns an output parameter or returned result set
      which refers to data at a remote DRDA location is not
      supported.
      There are no future plans to remove this restriction.
    
    -------------------------------------------------------------
    Known DSN BIND SERVICE Restriction/Limitation at DB2 V11
    APAR PI86867, fixed with PI90243.
    -------------------------------------------------------------
    - After delivery of PI86867, it was discovered that the DSN
      BIND SERVICE support delivered in Db2 V11 APAR PI86867 was
      incomplete, and will not work correctly in a Db2 Data
      Sharing mixed release environment with both Db2 V11 and
      Db2 V12.  The issue described is specific to the DSN BIND
      SERVICE command usage, and does not affect any other Db2
      functionality.
      Using Db2 V11 APAR PI86867 level DSN BIND SERVICE in a mixed
      release environment could result in various unexpected BIND
      SERVICE errors, including possible ABEND S0C4 in BIND related
      modules such as DSNTBAP2.  Although a defect exists in the
      DSN BIND SERVICE support that was initially delivered with
      Db2 V11 APAR PI86867, the corresponding PTF UI51795 will NOT
      be marked as "PE" because the error is isolated to the new
      BIND SERVICE functionality that was delivered in new
      function APAR PI86867.
      This Db2 V11 BIND SERVICE release incompatibility issue is
      corrected by Db2 V11 PI90243.  However, please note that in
      order to correct the BIND SERVICE command support to work
      correctly in a Db2 Data Sharing mixed maintenance and
      release environment going forward, it was REQUIRED that the
      BIND SERVICE fix shipped in Db2 V11 PI90243 be INCOMPATIBLE
      with  Db2 V11 APAR PI86867 level of BIND SERVICE.
    
      THIS MEANS THAT Db2 V11 APAR PI90243 MUST BE APPLIED TO ALL
      Db2 V11 SUBSYSTEM ENVIRONMENTS, INCLUDING ALL TSO/BATCH
      ENVIRONMENTS WHERE THE DSN BIND SERVICE COMMAND WILL BE
      ISSUED FROM AND THE Db2 SUBSYSTEM(S) PROCESSING THE BIND
      SERVICE COMMAND, IN ORDER FOR THE BIND SERVICE COMMAND TO
      WORK CORRECTLY.
    
      Using the DSN BIND SERVICE command in a Db2 V11 environment
      where PI90243 is not fully applied and active in all
      environments will likely result in failures similar to the
      BIND SERVICE failures described above that could occur in a
      Db2 V11 APAR PI86867 level Db2 Data Sharing mixed release
      environment with both Db2 V11 and Db2 V12.
    
    -------------------------------------------------------------
    Known Restrictions/Limitations at DB2 V11 APAR PI86867 or
    earlier level:
    -------------------------------------------------------------
    
    - A DB2 RESTful service created with an SQL statement which
      refers to data which has been offloaded to an IBM
      DB2 Analytics Accelerator for z/OS (IDAA) is not supported.
      This restriction is addressed by APAR PI90243.
    
    - DB2 system profile monitoring is not supported for a
      DB2 RESTful service invocation.
      This restriction is addressed by APAR PI90243.
    
    -------------------------------------------------------------
    Known Restrictions/Limitations at DB2 V11 APAR PI66828 level:
    -------------------------------------------------------------
    
    - Due to potential scalability issues, it is strongly
      recommended that the overall size of the request and
      reply messages of a DB2 native RESTful service be
      limited to a maximum of one (1) Megabyte.
      This restriction will be addressed by APAR PI70477.
    
    - A DB2 RESTful service created with an SQL statement which
      refers to LOB or XML data is not supported at this level.
      Although a service that refers to LOB/XML data can be
      successfully created, any attempt to invoke the service
      will result in a REST error being returned to the invoker.
      This restriction will be addressed by APAR PI70477.
    
    - While the SQL CALL statement is supported for a RESTful
      service, there is currently no support for handling of
      stored procedure returned resultsets.  Stored procedure
      parameters, including IN, OUT, and INOUT usage modes,
      are supported.
      This restriction will be addressed by APAR PI70477.
    
    DB2 V12 APAR Information
    ========================
    
    -------------------------------------------------------------
    Known Restrictions/Limitations for DB2 V12:
    -------------------------------------------------------------
    
    - A Db2 RESTful service created with an SQL statement which
      refers to data at a remote DRDA location is not supported.
      There are no future plans to remove this restriction.
    
    - Using a Db2 RESTful service to call a Db2 stored procedure
      which returns an output parameter or returned result set
      which refers to data at a remote DRDA location is not
      supported.
      There are no future plans to remove this restriction.
    
    -------------------------------------------------------------
    Known Restrictions/Limitations at DB2 V12 APAR PI86868 or
    earlier level:
    -------------------------------------------------------------
    
    - A DB2 RESTful service created with an SQL statement which
      refers to data which has been offloaded to an IBM
      DB2 Analytics Accelerator for z/OS (IDAA) is not supported.
      This restriction is addressed by APAR PI90244.
    
    - DB2 system profile monitoring is not supported for a
      DB2 RESTful service invocation.
      This restriction is addressed by APAR PI90244.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II14827

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-10

  • Closed date

  • Last modified date

    2019-02-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Document information

More support for: z/OS family

Software version: 001

Operating system(s): MVS

Reference #: II14827

Modified date: 13 February 2019