IBMi (AS400) fans only * Modernizing RPG's indicator with INDARA (Indicator Area) keyword

By -


#IBMiSample

INDARA (Indicator Area) keyword for ICF files

workstn indds
indicator data structure
INDARA is used to put the field option indicators and function(response) key indicators in a separate area of memory called indicator area.

By using this keyword, we can make indicator data structure in our program to give the customized name to indicators defined in the display file. Hence, it makes the program more readable and easy to understand.

Step 1. indicate INDARA keyword in your Display File



Step 2. indicate INDDS in your RPG workstation file declaration
dcl-f PKLTSFV workstn indds(Dspf) sfile(SFL1 : SF1NUM);


Step 3. declare the indicator area

       dcl-ds Dspf qualified ;

         Exit            ind pos(03) inz(*off);

         SflClr          ind pos(50) inz(*off);

         DspAtrRI        ind pos(61) inz(*off);

         DspClrRed       ind pos(62) inz(*off);

         SflEnd          ind pos(91) inz(*off);

       end-ds ;


   

Step 4. In the RPG source program replace all the indicator in the form *inNN or *inKK with the name defined in the indicator area,
for instance:
replace *in50 = *on with Dspf.SflClr = *on;
replace *in61 = *on with Dspf.DspAtrRI = *on;
replace *in03 = *on with Dspf.Exit = *on;
replace *inKC = *on with Dspf.Exit = *on;



Here's how to test and set indicators:

dcl-ds Dspf qualified ;                    
  Exit            ind pos(03) inz(*off)   ;
  SflClr          ind pos(50) inz(*off)   ;
  SflEnd          ind pos(91) inz(*off)   ;
end-ds ;                                   

dow Dspf.Exit = *off;
...
enddo;


Dspf.SflClr = *on;



That's it!





I appreciate all the comments made on this blog.













 

Comments

  1. AnonymousMay 2, 2022 at 3:36 PM

    As an aside - I RARELY code things as xxx = *on - I prefer the logical expression forms of xxx and NOT xxx. To me that is easier to read, and especially for developers that come from languages other than RPG it's easier to understand because it reads as a boolean. Indicators are unknown to developers of other programming languages, booleans are well known. I go so far as to define contants of "on", "off", "true" and "false" in a copybook in case I decide to use the explicit expression form. Cheers :)

    ReplyDelete
  2. santhoshNovember 25, 2022 at 1:00 PM

    how to use INDDS along with INFDS?

    ReplyDelete
    Replies
    1. Aldo SUCCIJanuary 18, 2023 at 5:34 PM

      Here's how to test and set indicators:

      dcl-ds Dspf qualified ;
      Exit ind pos(03) inz(*off) ;
      SflClr ind pos(50) inz(*off) ;
      SflEnd ind pos(91) inz(*off) ;
      end-ds ;

      dow Dspf.Exit = *off;
      ...
      enddo;


      Dspf.SflClr = *on;

      Delete

Post a Comment

Popular posts from this blog

(IBM i fans only) Efficient WRKSPLF with WSF - How to Search string into spooled files, Sort, and Generate PDFs on IBMi

By -
Image
Searching Spooled Files Made Easy: A Unique Solution Managing spooled files efficiently is crucial for users dealing with numerous rows of print data. IBM's WRKSPLF command provides a standard way to interact with spooled files, but it lacks certain features that can significantly enhance user experience. In this article, we'll delve into a powerful functionality that IBM doesn't offer — the ability to search among spooled file lists. Our goal is to highlight the advantages of this capability and introduce a practical solution. The Limitations of Standard WRKSPLF While the WRKSPLF command is a handy tool for working with spooled files, it falls short in certain aspects. One prominent limitation is the inability to search efficiently through the list of spooled file rows. Users often find it challenging to quickly locate specific files based on criteria like creation date, status, or content. Introducing a Unique Solution: WSF (WorkSpooledFiles) To address the limitations of...
Read more

(IBM i fans only) Detecting and Handling Non-Printable Characters in DB2 SQL Using LOCATE() and REPLACE() Functions

By -
Image
When working with DB2 SQL on the IBMi platform, one of the challenges we might encounter is dealing with non-printable characters in our data. These are characters that don't have a direct representation on a standard keyboard and can cause display programs to crash if not handled properly. For this example, we'll be working with the CLANA00F file, which contains customer data. You can find details on how to create this file on my blog post here . Non-printable characters can sneak into our records for various reasons, and to prevent issues, we can run an SQL query that uses the LOCATE() function. This function returns the position of the first occurrence of a substring within a string, allowing us to detect these problematic characters. Suppose we have a customer name with a non-printable character, specifically the EBCDIC '0D' character, which corresponds to the "Carriage Return" (CR) control character in ASCII. To find this character in our records, we can ...
Read more

(IBM i fans only) How to Sniff User Access

By -
Image
If you need to monitor user access on your IBM i system, you can use SQL to query the history log. Note: At the end of this post, you'll find a request directly addressed to you, the readers. Here’s a simple example of how you can do this: SELECT MESSAGE_ID,        MESSAGE_TIMESTAMP,        FROM_USER,        MESSAGE_TEXT     FROM TABLE (             QSYS2.HISTORY_LOG_INFO()         )     WHERE message_id IN ('CPF1164', 'CPF1124')           AND FROM_USER IN ('QSECOFR', 'QSYS', 'QSYSOPR')     ORDER BY MESSAGE_TIMESTAMP In this query: - QSYS2.HISTORY_LOG_INFO(): This function retrieves information from the history log. -  message_id IN ('CPF1164', 'CPF1124') : Filters the results to include only specific message IDs, which indicate sign-on and sign-off events. - FROM_USER in ('QSECOFR', 'QSYS', 'QSYSOPR'): Filters the resu...
Read more