Skip to main content

RPG's new Built-In Function %RANGE and new Operator IN - IBM i

RPGLE

Keeping the debate aside on whether the RPG is a dead programming language, Most of the recent surveys showed RPG is the primary program language for development on IBM i.

And, IBM continues to provide enhancements to RPG. In this post, we will see couple of recent additions to RPG. 
  • Built-in Function %RANGE
  • Operator IN

%RANGE

In SQL, we often use BETWEEN - AND in WHERE condition to check if a value is present in a particular range (specified using BETWEEN - AND). 

%RANGE BIF (Built-In Function) works in a similar way and used to check if a value is present in a particular range. This can be used to compare the data of any data type (and data we are comparing should be of same data type as the data mentioned in the RANGE)

Syntax:

%RANGE(lower-limit : upper-limit) ;

%RANGE accepts two arguments - Lower limit and Upper limit. Both Lower limit and Upper limit would be considered. 

%RANGE doesn't return any value and should always be used with operator 'IN'.

IN

IN operator is used to check if a value is present in the list of values provided. The list here can be, 
  • An array.
  • Range of values specified in %RANGE.
  • List of values specified using % LIST.
IN operator returns '1' if the value provided is present in the list and '0' if the value isn't present. 

Syntax:

x IN y

This can be used with in IF condition or DOW loop.

We will see an example using both %RANGE and IN to understand better. 

RPG's new BIF %RANGE and new Operator IN

In the above example, 
  • Line - 6: 'IN' operator is used to verify if Packed decimal value 'wNumber' is present in the range between 1 and 15. 
  • Line - 10: 'IN' operator is used to verify if Character value 'wString' is present in the range between 'AA' and 'AB'. 
    • Character value cannot be compared by specifying decimal values in %RANGE and vice-versa.
  • Line - 14: 'IN' operator is used to check the condition on DOW loop. 

Hope the above info was a bit of help to understand %RANGE and IN better. 


If you have any Suggestions or Feedback, Please leave a comment below or use Contact Form. 

Comments

Post a Comment

Popular posts from this blog

All about READ in RPGLE & Why we use it with SETLL/SETGT?

READ READ is one of the most used Opcodes in RPGLE. As the name suggests main purpose of this Opcode is to read a record from Database file. What are the different READ Opcodes? To list, Below are the five Opcodes.  READ - Read a Record READC - Read Next Changed Record READE - Read Equal Key Record READP - Read Prior Record READPE - Read Prior Equal Record We will see more about each of these later in this article. Before that, We will see a bit about SETLL/SETGT .  SETLL (Set Lower Limit) SETLL accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Corresponding Record (or Next Record if exact match isn't found).  SETGT (Set Greater Than) SETGT accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Next Record (Greater Than the Key value). Syntax: SETLL SEARCH-ARGUMENTS/KEYFIELDS FILENAME SETGT  SEARCH-ARGUMENTS/KEYFIELDS FILENAME One of the below can be passed as Search Arguments. Key Fiel

What we need to know about CHAIN (RPGLE) & How is it different from READ?

CHAIN READ & CHAIN, These are one of the most used (& useful) Opcodes by any RPG developer. These Opcodes are used to read a record from file. So, What's the difference between CHAIN & READ?   CHAIN operation retrieves a record based on the Key specified. It's more like Retrieving Random record from a Database file based on the Key fields.  READ operation reads the record currently pointed to from a Database file. There are multiple Opcodes that start with READ and all are used to read a record but with slight difference. We will see more about different Opcodes and How they are different from each other (and CHAIN) in another article. Few differences to note.  CHAIN requires Key fields to read a record where as READ would read the record currently pointed to (SETLL or SETGT are used to point a Record).  If there are multiple records with the same Key data, CHAIN would return the same record every time. READE can be used to read all the records with the specified Ke

Extract a portion of a Date/Time/Timestamp in RPGLE - IBM i

%SUBDT Extracting Year, Month, Day, Hour, Minutes, Seconds or Milli seconds of a given Date/Time/Timestamp is required most of the times.  This can be extracted easily by using %SUBDT. BIF name looks more similar to %SUBST which is used to extract a portion of string by passing from and two positions of the original string. Instead, We would need to pass a value (i.e., Date, Time or Timestamp ) and Unit (i.e., *YEARS, *MONTHS, *DAYS, *HOURS, *MINUTES, *SECONDS or *MSECONDS) to %SUBDT.  Valid unit should be passed for the type of the value passed. Below are the valid values for each type. Date - *DAYS, *MONTHS, *YEARS Time - *HOURS, *MINUTES, *SECONDS Timestamp - *DAYS, *MONTHS, *YEARS, *HOURS, *MINUTES, *SECONDS, *MSECONDS Syntax: %SUBDT(value : unit { : digits { : decpos} }) Value and Unit are the mandatory arguments.  Digits and Decimal positions are optional and can only be used with *SECONDS for Timestamp. We can either pass the full form for the unit or use the short form. Below i