PM89356: FM/DB2 ROW SELECTION CRITERIA NOT SAVED WHEN USING '1' ON COLUMNSELECTION/EDIT PANEL, THEN ON 2ND ITERATION USING 'SQL' COMMAND.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When using '1' on the Column Selection/Edit panel to enter row
  selection criteria, then on next iteration with the same
  template, new row selection criteria is entered using the
  'SQL' command, the row selection criteria of the latter is not
  saved.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of File Manager DB2 component.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. In the File Manager DB2 component    *
  *                      template editor, the values shown on    *
  *                      the "Row Selection Criteria" panel do   *
  *                      not reflect previous changes made by    *
  *                      direct entry of an SQL WHERE clause.    *
  *                      2. In the File Manager DB2 component    *
  *                      template editor, message 'WHERE clause  *
  *                      too long' and garbage in the "Sel"      *
  *                      field after the user enters an invalid  *
  *                      WHERE clause using the SQL command, or  *
  *                      enters an SQL statement > 32K in        *
  *                      length.                                 *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  1. In the File Manager DB2 component template editor (Column
  Selection/Edit panel), there are two methods for entering an
  expression:
  a.  By field specification, using the Row Selection Criteria
      panel.
  b.  By entering an SQL WHERE clause (SQL command).
  An expression entered using method a. is always convertible to
  an SQL WHERE clause, however not every WHERE clause entered
  is convertible to an expression that can be displayed/entered
  using method a.  Once the user has modified the WHERE clause
  using method b, any expression entered using method a. should
  be discarded.
  2. The ISPF editor session of the SQL statement should not
  allow the user to save an invalid WHERE clause, or an SQL
  statement that is > 32K in length.
  

Problem conclusion

• File Manager DB2 component has been changed to correct the
  problems.
  

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:

Modules/Macros

• FMN2LVL  FMN2LVLJ FMN2LVLK
  

Fix information

• Fixed component name

  FILE MANAGER Z/

• Fixed component ID

  5655W6800

Applicable component levels

• RC1B PSY UK96967

     UP13/08/28 P F308

• RC12 PSY UK96969

     UP13/08/28 P F308

• RC13 PSY UK96970

     UP13/08/28 P F308

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.