Exploring V5R2's Data Structure Arrays

RPG
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

For decades, RPG has included the ability to have multiple occurrences of a data structure in a program. Multiple occurrence data structures are defined in RPG IV through the use of the OCCURS keyword on the data structure declaration specification. In RPG III, multiple occurrence data structures are specified by placing the number of occurrences in the "From" columns of the Input specification for the data structure.

In RPG IV, the OCCURS keyword is used to set the number of occurrences, while the OCCUR opcode is used to set or extract the current occurrence. The use of the OCCUR opcode is somewhat clumsy in that you can never address the nth occurrence of a data structure without moving the occurrence index to the desired occurrence and then addressing the data structure subfields.

With OS/400 V5R2, multiple occurrence data structures have been deprecated. The new "Data Structures as Arrays" feature allows you to use the DIM keyword to declare a data structure as an array, effectively giving it multiple occurrences. Figure 1 illustrates the use of the DIM keyword being used to declare a data structure as an array.

     D  Contact        DS                  Dim(20) 
     D                                     QUALIFIED
     D  CustNo                        7P 0
     D  Name                         30A
     D  Addr1                        20A
     D  City                         20A
     D  State                         2A
     D  ZipCode                      10A
     D  BalDue                        72

Figure 1: A data structure being declared as an array

Subscripting a data structure array is similar to subscripting a regular array index; simply enclose the index in parentheses following the data structure name. The array index is followed by a qualified subfield name. This is the subfield being modified or retrieved. In the example that follows, the subfield CUSTNO of the fifth element (occurrence) of the CONTACT data structure is set to 12345.

     C                   eval      Contact(5).CustNo = 12345

Only qualified data structures may be declared as an array. Therefore, the data structure must be declared with one of the QUALFIED, LIKEDS, or LIKEREC keywords. Qualification allows the subfields to be manipulated in do loops or the contemporary for loops. In Figure 2, the for loop iterates through each element of the CONTACT data structure array and sets the value of the BALDUE subfield to zero.

     C                   for       i = 1 to i = %elem(Contact)
     C                   eval      Contact(i).BalDue = 0
     C                   endif

Figure 2: Accessing an array data structure's subfields

The V5R2 Data Structure as Arrays feature makes multiple occurrence data structures much more usable. We no longer need to set the occurrence before accessing the subfields of the occurrence we want. We simply use array subscripting, and we are there.

In Figure 3, I illustrate how multiple occurrence data structures are handled in V5R1 and earlier.

0001 D Contact         DS                  Occurs(20)
0002 D  CustNo                        7P 0
0003 D  Name                         30A
0004 D  Addr1                        20A
0005 D  City                         20A
0006 D  State                         2A
0007 D  ZipCode                      10A
0008 D  BalDue                        7P 2

0009                   for       i = 1 to i = %elem(Contact)
0010     I             OCCUR     Contact
0011                   eval      BalDue = 0
0012                   endif

Figure 3: Traditional multiple occurrence data structure

In this example, line 1 declares the CONTACT data structure as a multiple occurrence data structure; the OCCURS(20) keyword is used to declare 20 occurrences. Line 9 in this example is identical to that used in the example in Figure 2. Line 10, however, is where the difference is; it uses the OCCUR operation code to set the current occurrence of the data structure. Finally, on line 11, the BALDUE field is set to zero.

Note that since this is not a qualified data structure, the BALDUE field is not qualified to the parent data structure. If the CONTACT data structure listed in Figure 3 had also included the QUALIFIED keyword, then line 11 would have been specified as follows:

0011 C                   eval      Contact.BalDue = 0

The difference in syntax between this example and what is used in Figure 2 is that the data structure is not an array here but is an array in the example in Figure 2. Therefore, the array scripting parentheses are not specified.

A few things to remember:

  • Qualified data structures were introduced in OS/400 V5R1.
  • Data structures as arrays were introduced in OS/400 V5R2.
  • The LIKEREC keyword (an enhancement to qualified data structures) was introduced in OS/400 V5R2.
  • The QUALIFIED, LIKEDS, and LIKEREC keywords cause the data structure to be qualified.
  • Only Qualified Data Structures may be declared as arrays.

BOB COZZI

Bob Cozzi is a programmer/consultant, writer/author, and software developer. His popular RPG xTools add-on subprocedure library for RPG IV is fast becoming a standard with RPG developers. His book The Modern RPG Language has been the most widely used RPG programming book for more than a decade. He, along with others, speaks at and produces the highly popular RPG World conference for RPG programmers.


MC Press books written by Robert Cozzi available now on the MC Press Bookstore.

RPG TnT RPG TnT
Get this jam-packed resource of quick, easy-to-implement RPG tips!
List Price $65.00

Now On Sale

The Modern RPG IV Language The Modern RPG IV Language
Cozzi on everything RPG! What more could you want?
List Price $99.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  •  

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: