SE55338: RDP 8.5.1 LPEX FINDMATCH ACTION FAILS DUE TO CONTINUED LITERAL THAT STARTS WITH SELECT

Rational Developer for i Fix Pack 9.0.1 for 9.0

APAR status

• Closed as fixed if next.

Error description

• The findMatch action in LPEX  (Ctrl-M) fails saying that there
  is no match when there is or goes to the wrong match.  This can
  happen due to a continued literal that begins with a keyword
  such as 'SELECT'.  For example:
  
  
  mySql = 'insert into .... as ( +
          select * from .... ;
  

Local fix

• To work around this problem adjust the source so that
  continued literal lines do not start with the word 'SELECT'.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Those who edit RPGLE or SQLRPGLE source.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Find matching end action does not       *
  *                      work correctly.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is fixed in the RDi 9.0.1 update.
  
  The find matching end action (Ctrl+M) does not work correctly
  when a continued line of a statement starts with a word which
  matches an RPG opcode name.
  

Problem conclusion

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

Applicable component levels

• R850 PSY

     UP