== Why is this an issue?

This rule applies whenever an ``++IF++`` statement is followed by one or more ``++ELSEIF++`` statements; the final ``++ELSEIF++`` should be followed by an ``++ELSE++`` statement.

The requirement for a final ``++ELSE++`` statement is defensive programming. 

The ``++ELSE++`` statement should either take appropriate action or contain a suitable comment as to why no action is taken. This is consistent with the requirement to have a final ``++OTHER++`` clause in a ``++SELECT++`` statement. 

=== Noncompliant code example

[source,rpg]
----
C                   IF         RESULT = 0
C                   ...
C                   ELSEIF     RESULT > 0
C                   ...
C                   ENDIF
----

[source,rpg]
----
 /free
   if result = 0;
     ...
   elseif result > 0;
     ...
   endif;
 /end-free
----

=== Compliant solution

[source,rpg]
----
C                   IF         RESULT = 0
C                   ...
C                   ELSEIF     RESULT > 0
C                   ...
C                   ELSE
C                   EXSR       ERRO
C                   ENDIF
----

[source,rpg]
----
 /free
   if result = 0;
     ...
   elseif result > 0;
     ...
   else;
     exsr ERR0;
   endif;
 /end-free
----


ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

include::../message.adoc[]

'''
== Comments And Links
(visible only on this page)

include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]