One method to use is the inline composite argument list provided on the calculation operation line. This method is very similar in theory to the KLIST scheme. Fields are specified in a parameter-style list, and together, these fields comprise the look-up key argument. No KLIST or KFLD operations are needed. An example would be as follows:
D Fld2 s 5 0
/free
. . .
Chain (Fld1:Fld2) Filex;
If not %found(Filex);
. . .
In this example, the two fields named Fld1 and Fld2 are the key fields used to find a record in the file Filex. The data type and length of the fields specified must match the file key(s). This scheme is easy to implement, and it follows all the same rules as key fields that are coded in fixed-format KFLD operations. The only difference is that, in free-format, these fields must be predefined, and no temporary values can be specified, as Factor 2 provides on KFLD statements. Literals can be specified instead of variables in the composite key list. (Note: CHAIN offers many other options that I will not explore here.)
The other method to use, instead of KLIST and KFLD, uses the following elements:
First, define a named data structure in the D-specs that uses keyword LIKEREC with a value of the data file record name and *KEY as the second parameter. Another alternative is the same data structure with keyword EXTNAME with the data file record name and *KEY as the second parameter. The record name specified should match the record name of the file that will be used in CHAIN (and other) operations later in calculations. This data structure then becomes a qualified data structure, with subfields referenced using a recordname.fieldname format. The subfields of this data structure that are related to the keys of the file will be used as the argument key fields in the CHAIN, READE, or SETxx operations that come later in calculations.
Second, use the %kds built-in function (Search Arguments in a Data Structure) with parameters as the argument on the CHAIN (etc.) operations. The %kds built-in function has two parameters. The first parameter is the named data structure explained above, and the optional second parameter is a constant representing the number of key fields to use on the operation. Any number from 1 to n can be specified, where n is the number of key fields specified in the data file. Any number less than n would be considered a partial key list. A "highest order to lowest order" key scheme is used when this parameter is specified. If no second parameter is specified, then all key field values are used.
An example of this method follows:
Assume a keyed data file ARTRANSACT, record name ARRECORD, has key fields ARcompany, ARcustomer, and ARinvoice, and many other non-key fields.
*
D KeyStruct DS LikeRec(ARRECORD:*KEY)
*
/free
. . .
KeyStruct.ARcompany = ScreenComp;
KeyStruct.ARcustomer = ScreenCust;
Setll %kds(KeyStruct:2) ARTRANSACT; // Set file-ptr
Dou %eof(ARTRANSACT); // Loop through invoices
ReadE %kds(KeyStruct:2) ARTRANSACT;
If not %eof(ARTRANSACT);
// Process an invoice for this Company/Cust group
Endif;
Enddo;
. . .
The above example picks up company and customer number values from another file, possibly a display device file, and puts them in the appropriate qualified data structure subfields. Now, the key data structure can be used on the SETLL, READE, or other operations. A partial key is used in this example to access all invoices for a specified company and customer.
Try one of these two alternatives when coding free-format RPG IV!
Jim Martin is corporate technical instructor at Jack Henry & Associates in Monett, Missouri. He is a veteran of RPG programming, beginning in 1967 with a position at IBM as a Systems Engineer and later becoming a staff programmer at the Rochester systems programming lab. For eight years, he was at Lakeview Technology as an AS/400 and RPG instructor and was a speaker at various local midrange user group meetings and conferences. He can be reached by email at
Jim Martin holds a BS degree in mathematics and an MS in computer science. For 26 years, he was employed by IBM, where he wrote RPG applications for customers and worked in the programming laboratory as a programmer on portions of CPF and the OS/400 operating system. After leaving IBM, Jim took post-graduate work in computer science and performed RPG training. He is an IBM-certified RPG IV developer and author of multiple bestselling editions of Free-Format RPG IV, which, since the book's initial publication in 2005, have taught thousands of RPG IV programmers how to be successful with the free-format coding style.
MC Press books written by Jim Martin available now on the MC Press Bookstore.
 |
||
 |
|
Free-Format RPG IV: Third Edition Improve productivity, readability, and program maintenance with the free-format style of programming in RPG IV. List Price $59.95 Now On Sale
|
|
||
 |
|
Free-Format RPG IV: Second Edition >Make the transition from coding in fixed-format RPG to free format. List Price $59.95
Now On Sale
|
|
||
 |
|
Functions in Free-Format RPG IV Here’s the ultimate guide to writing RPG IV programs with functions in the free-format style. List Price $59.95
Now On Sale
|
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.
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:
LATEST COMMENTS
MC Press Online