Skip to main content



I have always ignored the Keyword RPGPPOPT until I have faced the strange issue with Compiling my SQLRPGLE code which hasn't really modified for last couple of years.

After a little investigation I have found that the recent upgrade has changed the default value for keyword 'RPGPPOPT' to '*NONE'.

RPG preprocessor options . . . .   *NONE 
  *NONE - The compiler is not called for preprocessing
  *LVL1 - The compiler is called for preprocessing to expand /COPY and handle the conditional compilation directives except the /INCLUDE directive
  *LVL2 - The compiler will be called for preprocessing to expand /COPY and /INCLUDE and handle the conditional compilation directives

When we use CRTSQLRPGI, SQL precompiler would first validate SQL statements. However, some times the variables which are needed by the SQL statements would reside in the source code mentioned under compiler directives such as /COPY, /INCLUDE, /DEFINE, and /IF. This would cause the compilation failures.

It is always important to check for RPG Pre-processor Options (RPGPPOPT) while compiling the SQLRPGLE (specially if we use compiler directives).

Or, It would be easier, if we could default the Preprocessor Option to '*LVL2' (or '*LVL1' as required, Please see the description above against each of this value). instead of '*NONE' (default supplied by IBM).

Below is the command we could use to change the default.


Last thing, This default would be reset to '*NONE' if there is an upgrade performed and the default value needs to be changed again.


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