entries in triggers force: warning: 1000 - Procs statements seen after 'end' instruction

Author: ulrichmerkel@web.de (ulrich-merkel)

when entries are defined let's say in the EXEC trigger and closed with an end statement (as good coders do), the migration will force a situation where we will get warning:   1000 - Procs statements seen after 'end' instruction Trigger <CSCR> from Form: JAVATEST_UME [         1]              ;- [Start 'Execute'] [         2]              #startdefine [         3]              #define $triggerAbbr=EXEC snip [        51]******        entry load_test [        52]              variables [        53]                 string v_occlist snip [        67]    13        end ; load_test [        68]     1        end  warning:   1000 - Procs statements seen after 'end' instruction [        69]              #enddefine [        70]              ;- [End 'Execute']

2 Comments

  1. True. While migrating code from V9 to v10, all V9 containers are concatenated into one container, the SCRIPT container. To avoid dead code, which might occur in the next container, in your case that would be the container after the Execute Trigger container, to suddenly come alive, all containers explicitly ended with an 'end' statement. Unfortunately, this might lead to unwanted duplicate 'ends'. Currently, the Migration Utility does not inspect (parse) the code so it could look for conditions not to include the additional 'end'. More custoemrs have this problem, so we might need to reconsider this. Thanks for the input Ulrich.


    Author: Gerton Leijdekker (gerton.leijdekker@uniface.com)
  2. Hi Gerton, to avoid that all "good men" following the "you should always END your code" guideline suffer from the warning, but on the other hand save you from parsing the code: what about appending instead of the "end" some do-nothing entry (based on a counter held in registy): entry end_1234567890 ;   if it is required, add some code end


    Author: ulrich-merkel (ulrichmerkel@web.de)