22
Sun, Dec
3 New Articles

Reusing a Single File Description on Multiple Files

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

 

Dynamically specify files in RPG without the use of embedded SQL.

 

Do you have physical files with the same file format that are separated into multiple physical files--whether it be for legal reasons, query speed, or storage archiving--which requires you to keep modifying your programs when the new files are created? This article will show you how to continue creating new physical files, without the need for additional program compiling and maintenance.

 

In my shop, we had a physical file that needed to be physically separated into different files for legal reasons. These files reused the same physical file layout for each version, and at the end of each year a new file would be created to isolate the data. There was at least one program that would perform historical reporting by accessing several of the files, and this program would need to be maintained each year to include the additional physical file that was created.

 

This type of programming maintenance is highly undesirable, especially at year-end, when you're at your busiest! My initial solution to this problem was to write dynamic embedded SQL in the RPG program. This would have allowed me to specify the file name within the SQL statement to retrieve the data from the file. But this solution would have required a notable amount of program logic to be rewritten. Instead, I chose to use the EXTFILE and EXTMBR keywords on my file specifications to accommodate this capability.

 

Using EXTFILE instead of embedded SQL allowed me to make minimal programming changes to the existing program. All I needed to do was change the file specifications and the existing logic that opened the files.

The File Specification Keywords: EXTFILE and EXTMBR

The file referred to in the file specification must exist in order for your program to compile. You could create an empty generic dummy file to represent the file you will be using throughout the years, or you may chose to use an arbitrary file from a specific year. The only problem with this would come into play when you decide sometime down the line that you want to start archiving older files off of the system. Then the file that your program is referring to would no longer exist, and your program would not be able to compile.

 

     FEMPLOYEE  IF   E           K DISK    USROPN

     F                                     EXTFILE(fileName)

     F                                     EXTMBR(fileMember)

 

 

In the file specification above, you can see the EXTFILE and EXTMBR keywords being specified for the file. Each of these keywords will accept a parameter to specify the external file and member, respectively, to use within the program. The fileName and fileMember parameters are variables that will be defined in your program to determine the file and member to use.

 

The EXTFILE keyword allows you to specify the file to use during run time, instead of at compile time. The compiler will still validate the file existence and its use during the compile, but the actual file that will be used will be determined during run time. When you are using the EXTFILE keyword, you must also specify the USROPN keyword. This is required to specify the file that will be used prior to opening it.

 

You can specify the name of the file with or without the library, and you can also use *LIBL as the library reference. The library is separated from the file using the forward slash. For our example, we will be using the EMPLOYEE file in the MYLIB library, so the fileName will be set to MYLIB/EMPLOYEE. The file name parameter of the EXTFILE keyword is case-sensitive.

 

The EXTMBR keyword can be used to specify the member of the file to open. The EXTMBR keyword is independent of the EXTFILE keyword, so you can use EXTFILE and EXTMBR together or separately. You may decide to use the EXTMBR keyword as a replacement to the OVRDBF command to override your physical file members even if you aren't using EXTFILE. The member parameter of the EXTMBR keyword is case-sensitive.

The DDS

For our programming example, we will be working with a common file layout that will be named EMPLOYEE. The EMPLOYEE DDS will be reused for each new file that is created with the naming convention of "EMP" + YYYY, where YYYY indicates a four-digit year.

 

 

     A          R MCFMT

     A            MCACCT         6S 0       COLHDG('ACCOUNT NUMBER')

     A            MCFNAME       32A         COLHDG('FIRST NAME')

     A            MCLNAME       32A         COLHDG('LAST NAME')

     A          K MCACCT

 

The Example

Suppose we have an employee named Eibeamma that seems to remarry every year and keeps changing her name. The data in our EMPLOYEE file will have a record of this, and we will be able to see any name changes when we read through the EMP2007, EMP2008, and EMP2009 files with our program using EXTFILE and EXTMBR keywords on our F specification.

 

Eibeamma's name may change every year, but her account number of 400 remains the same. So, we will open and close the EMPLOYEE files for the past three years and use her account number to see the changes.

The RPG Code (Free-Format)

     FEMPLOYEE  IF   E           K DISK    USROPN

     F                                     EXTFILE(fileName)

     F                                     EXTMBR(fileMember)

     D*

     D currentKey      S              6S 0

     D currentDate     S               D

     D currentYear     S              4S 0

     D displayBytes    S             52A

     D fileName        S             21A

     D fileMember      S             10A

     C*

      /free

       currentKey = 400;

       // Current Year

       currentDate = %date();

       exsr getAcctName;

       // Last Year

       currentDate = currentDate - %years(1);

       exsr getAcctName;

       // Two Years Ago

       currentDate = currentDate - %years(1);

       exsr getAcctName;

       *inlr = *ON;

       //------------------------------------------------------

       //--- Subroutine: getAcctName                        ---

       //------------------------------------------------------

       begsr getAcctName;

       currentYear = %subDt(currentDate: *YEARS);

       fileName = 'MYLIB/EMP' + %editc(currentYear: '3');

       fileMember = 'MCPRESS';

       displayBytes = 'fileName: ' + %trim(fileName)

                    + ' MBR: ' + %trim(fileMember);

       DSPLY displayBytes;

       open EMPLOYEE;

       chain currentKey EMPLOYEE;

       displayBytes = 'Account '

                    + %trim(%editc(currentKey: '3'));

       if %found();

         displayBytes = %trim(displayBytes) + ': '

                      + %trim(MCLNAME) + ', '

                      + %trim(MCFNAME);

       else;

         displayBytes = %trim(displayBytes) + ': '

                      + ' NOT FOUNDÜ';

       endif;

       DSPLY displayBytes;

       close EMPLOYEE;

       endsr;

      /end-free

The RPG Code (Fixed-Format)

     FEMPLOYEE  IF   E           K DISK    USROPN

     F                                     EXTFILE(fileName)

     F                                     EXTMBR(fileMember)

     D*

     D currentKey      S              6S 0

     D currentDate     S               D

     D currentYear     S              4S 0

     D displayBytes    S             52A

     D fileName        S             21A

     D fileMember      S             10A

     C*

     C                   EVAL      currentKey = 400

     C* Current Year

     C                   EVAL      currentDate = %date()

     C                   EXSR      getAcctName

     C* Last Year

     C                   EVAL      currentDate = currentDate - %years(1)

     C                   EXSR      getAcctName

     C* Two Years Ago

     C                   EVAL      currentDate = currentDate - %years(1)

     C                   EXSR      getAcctName

     C                   EVAL      *inlr = *ON

     C***********************************************************************

     C*  --- Subroutine: getAcctName                        ---

     C***********************************************************************

     C     getAcctName   BEGSR

     C                   EVAL      currentYear = %subDt(currentDate: *YEARS)

     C                   EVAL      fileName = 'MYLIB/EMP'

     C                                      + %editc(currentYear: '3')

     C                   EVAL      fileMember = 'MCPRESS'

     C                   EVAL      displayBytes = 'fileName: '

     C                                          + %trim(fileName)

     C                                          + ' MBR: '

     C                                          + %trim(fileMember)

     C     displayBytes  DSPLY

     C                   OPEN      EMPLOYEE

     C     currentKey    CHAIN     EMPLOYEE                           68

     C                   EVAL      displayBytes = 'Account '

     C                                          + %trim(%editc(currentKey: '3'));

     C                   IF        *IN68 = *OFF

     C                   EVAL      displayBytes = %trim(displayBytes) + ': '

     C                                          + %trim(MCLNAME) + ', '

     C                                          + %trim(MCFNAME)

     C                   ELSE

     C                   EVAL      displayBytes = %trim(displayBytes) + ': '

     C                                          + ' NOT FOUNDÜ'

     C                   ENDIF

     C     displayBytes  DSPLY

     C                   CLOSE     EMPLOYEE

     C                   ENDSR

The Output

There are DSPLY statements throughout the program, so running the program will generate the following results:

 

DSPLY  fileName: MYLIB/EMP2009 MBR: MCPRESS

DSPLY  Account 400: Systumeye, Eibeamma

DSPLY  fileName: MYLIB/EMP2008 MBR: MCPRESS

DSPLY  Account 400: Isereez, Eibeamma

DSPLY  fileName: MYLIB/EMP2007 MBR: MCPRESS

DSPLY  Account 400: Ausfurhundrid, Eibeamma 

 

As you can see, Eibeamma has been busy. But she'll always be known as Ausfurhundrid to me.

Download the Code

You can download this article's code (in both free-format and fixed-format) as well as the DDS for the EMPLOYEE file by clicking here.

 

 

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • 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.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • 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

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • 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: