#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Support for CLOB files on ODBC lsxlc connector from Db2 on AS400 to Domino Server

This provide unique access to our data from Domino.

We have no options to retrieve data in CLOB format in DB on AS400 from Domino, as the other option is not valid (notesjsonnavigator crash the server in that specific case)

  • Guest
  • Nov 30 2021
  • Needs Clarification
  • Attach files
  • Guest commented
    13 Dec, 2021 12:11pm

    3. notesjsonnavigator should of course not crash the server => this should be investigated


    >> is under investigation, with action needed > upgrade to 11.0.1 fp4 undergoing

  • Guest commented
    9 Dec, 2021 03:03pm

    Hello Thomas,
    We openned a support ticket for this and the answer was:"Using the lsxlc connectors you can not interpret clob data, this data type is specific to as/400 platform. There are no plans to fix it."

    Also they give as this SPR matching with our issue:
    SPR # SSHE4JHKG5 - the notes connectors do not support Clob data types.


    the case we openned was: CS0276829

  • Admin
    Thomas Hampel commented
    6 Dec, 2021 01:27pm

    Can you please open a support ticket for this? It seems like you are mixing up several different problems.

    1. clob data works fine using lcstream method
    2. what odbc driver are you using? there is one specifically downloadable from the AS400 site
    3. notesjsonnavigator should of course not crash the server => this should be investigated.