Modernizing RPG’s indicator with INDARA (Indicator Area) keyword


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;

That’s it!

 

IBM i Data Validation – find out what is really going on under the covers

IBM i Data Validation – find out what is really going on under the covers

IBM i applications are rich in database activity and much of that processing is performed by APIs or batch processes that do not have any form of user interface. Given the damage that a poorly written program can inflict on this key corporate asset, validating that every database activity is correct is difficult and IBM provide few tools to help.

By using TestBench’s Data Validation module, you can track every insert, update and delete operation. You will understand what errors have been introduced and by what process. There are even rules so data changes get flagged automatically.

Find out more in our best practice guide.

This guide explores the key principles and techniques as they relate to the creation, maintenance, validation, use, and re-use of test data environments on the IBM i, IBM iSeries & IBM AS/400 and offers practical solutions for success.

Share Online:


Share on facebook

Share on twitter

Share on linkedin

Share on email

Share on whatsapp

The post IBM i Data Validation – find out what is really going on under the covers appeared first on i400Quality.

IBM i test data management challenges and how to solve them. No. 2 Data Confidentiality

IBM i test data management challenges and how to solve them. No. 2 Data Confidentiality

The key challenges comprise four elements:

Test DataData ConfidentialityData ReuseValidation

You may now have an extract of live data, however, if you use it you run a great risk of a data breach and severe penalties.  It can also be difficult to mask test data without destroying its usefulness.

Thankfully we have a solution simple, but effective, data masking or obfuscation can be employed to remove the ability to identify an individual from the data held in your Test Data Environments, from Name and Address, to SSNs and credit card numbers.

. Find out how in our best practice guide.

This guide explores the key principals and techniques as they relate to the creation, maintenance, validation, use, and re-use of test data environments on the IBM i, IBM iSeries & IBM AS/400 and offers practical solutions for success.also

Share Online:


Share on facebook

Share on twitter

Share on linkedin

Share on email

Share on whatsapp

The post IBM i test data management challenges and how to solve them. No. 2 Data Confidentiality appeared first on i400Quality.

Verified by MonsterInsights