PH55684: DB2 SELECT INTO WITH NULL INDICATOR ON 2 LINES NOT BEING HANDLEDCORRECTLY

APAR status

• Closed as program error.

Error description

• PLI program produces the incorrect output in the Impact Analysis
  Report;
  The issue occurs by when the VALUES line is broken:
  EXEC SQL
          INSERT INTO NO@NOMO
             (INSTANCE_ID
             ,NONOMONO
             ,NON_OMON_ONOM_ON)
          VALUES
             (:CNONOMO.INSTANCE_ID
             ,:CNONOMO.NONOMONO
             ,:CNONOMO.NON_OMON_ONOM_ON
                  :NON_OMON_ONOM_ON_NULL_IND);
  
  Each variable in the INSERT needs to match the each VALUE;
  However, AD does not take in consideration as a single value the
  statments broken into two lines as below:
  ,:CNONOMO.NON_OMON_ONOM_ON
      :NON_OMON_ONOM_ON_NULL_IND);
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * AD Build Client on Windows Server                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When mapping fields with variables, we took everything found *
  * after ':' as a candidate to be mapped to a field.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix consists in taking as a candidate for mapping only if
  it's the first variable in a separated group delimitated by
  comma (,) or by a key-word and it is not part of an arithmetic
  expression or function call.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  APPL DISCOVERY

• Fixed component ID

  5737B1600

Applicable component levels