• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • Another Reason to Use P-Fields

    January 26, 2005 Hey, Ted

    Within a subfile, I am using an indicator to highlight a field if the value of that field is invalid. Is there a way, when I read a subfile record, to analyze the attributes of the field to see if the indicator was switched on or off when the subfile record was written? My problem is that the display attribute is losing its original setting.

    –Alan

    I don’t know of a way to determine the original setting. I have included hidden one-byte fields in a subfile to store the settings of indicators so I could reset the indicators before updating the subfile record. You have put your finger on a good reason to use p-fields instead of indicators to control display file attributes.

    Here’s a display file, SFL223D, which uses indicator 71 to display a negative balance amount in reverse image.

     A                                      DSPSIZ(24 80 *DS3)
     A          R SFL01                     SFL
     A            LINENBR01      3  0O  9  2EDTCDE(4)
     A            NAME01        20   O    +2
     A            BALANCE01      9  2O    +2EDTCDE(J)
     A  71                                  DSPATR(RI)
     A          R CTL01                     SFLCTL(SFL01)
     A                                      CA03(03)
     A                                      SFLDSP
     A                                      SFLDSPCTL
     A                                      SFLSIZ(11)
     A                                      SFLPAG(10)
    

    Here’s a short program, SFL223R, which loads some records into the subfile and updates one of them. The first time the subfile is displayed, Don’s and Lou’s records show a balance in reverse image. When Don’s name is changed to Bubba, the reverse image attribute disappears.

     H dftactgrp(*no) actgrp(*caller)
     H option(*srcstmt: *nodebugio)
    
     Fsfl223d   cf   e             workstn
     F                                     sfile(sfl01:rrn)
    
     D rrn             s              3  0
    
     D Load            pr
     D  Name                         20    value
     D  Balance                       9p 2 value
     D  RecNbr                        3p 0
    
     D ChangeName      pr
     D  RecNbr                        3p 0 value
     D  NewName                      20    value
    
      /free
          Load('Bob': 200: RRN);
          Load('Don': -35: RRN);
          Load('Jim': 25.95: RRN);
          Load('Lew': 180: RRN);
          Load('Lou': -99999: RRN);
          Load('Sue': 500: RRN);
          Load('Tom': 1750: RRN);
          exfmt ctl01;
          ChangeName(2: 'Bubba');
          exfmt ctl01;
          *inlr = *on;
      /end-free
    
     P Load            b
     D                 pi
     D  Name                         20    value
     D  Balance                       9p 2 value
     D  RecNbr                        3p 0
      /free
        RecNbr += 1;
        LineNbr01 = RecNbr;
        Name01 = Name;
        Balance01 = Balance;
        *in71 = (Balance01 < *zero);
        write sfl01;
      /end-free
     P                 e
    
     P ChangeName      b
     D                 pi
     D  RecNbr                        3p 0 value
     D  NewName                      20    value
      /free
        chain RecNbr sfl01;
        if %found();
           Name01 = NewName;
           update sfl01;
        endif;
      /end-free
     P                 e
    

    Here’s the same display file, but the setting of the balance field is now controlled by p-field BALATTR01, which is written to the subfile record. The display attributes of the balance field are no longer dependent on the setting of an indicator.

     A                                      DSPSIZ(24 80 *DS3)
     A          R SFL01                     SFL
     A            LINENBR01      3  0O  9  2EDTCDE(4)
     A            NAME01        20   O    +2
     A            BALANCE01      9  2O    +2EDTCDE(J)
     A                                      DSPATR(&BALATTR01)
     A            BALATTR01      1A  P
     A          R CTL01                     SFLCTL(SFL01)
     A                                      CA03(03)
     A                                      SFLDSP
     A                                      SFLDSPCTL
     A                                      SFLSIZ(11)
     A                                      SFLPAG(10)
    

    Here’s the revised RPG code. When Don’s name is changed to Bubba, the balance of -35 continues to be displayed in reverse image.

     H dftactgrp(*no) actgrp(*caller)
     H option(*srcstmt: *nodebugio)
    
     Fsfl224d   cf   e             workstn
     F                                     sfile(sfl01:rrn)
    
     D rrn             s              3  0
     D Normal          c                   x'20'
     D Reverse         c                   x'21'
    
     D Load            pr
     D  Name                         20    value
     D  Balance                       9p 2 value
     D  RecNbr                        3p 0
     D ChangeName      pr
     D  RecNbr                        3p 0 value
     D  NewName                      20    value
    
      /free
          Load('Bob': 200: RRN);
          Load('Don': -35: RRN);
          Load('Jim': 25.95: RRN);
          Load('Lew': 180: RRN);
          Load('Lou': -99999: RRN);
          Load('Sue': 500: RRN);
          Load('Tom': 1750: RRN);
          exfmt ctl01;
          ChangeName(2: 'Bubba');
          exfmt ctl01;
          *inlr = *on;
      /end-free
    
     P Load            b
     D                 pi
     D  Name                         20    value
     D  Balance                       9p 2 value
     D  RecNbr                        3p 0
      /free
        RecNbr += 1;
        LineNbr01 = RecNbr;
        Name01 = Name;
        Balance01 = Balance;
        if (Balance01 >= *zero);
           BalAttr01 = Normal;
        else;
           BalAttr01 = Reverse;
        endif;
        write sfl01;
      /end-free
     P                 e
    
     P ChangeName      b
     D                 pi
     D  RecNbr                        3p 0 value
     D  NewName                      20    value
      /free
        chain RecNbr sfl01;
        if %found();
           Name01 = NewName;
           update sfl01;
        endif;
      /end-free
     P                 e
    


    To learn more about p-fields, see the article “Anatomy of a P-Field.”

    –Ted

    Click here to contact Ted Holt by e-mail.

    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    Tags:

    Sponsored by
    Lightedge

    Your IBM Power Cloud Strategy Should Start With “Why?”

    Moving IBM i to the cloud isn’t just an infrastructure decision.

    A hardware refresh, data center exit, IBM i skills gap, disaster recovery requirement, or broader cloud initiative can each lead to a very different architecture.

    At Lightedge, we start by understanding what you’re trying to accomplish. Then we look at the workload, application dependencies, resiliency requirements, operating model, and long-term strategy to determine where that workload belongs.

    Managed IBM Power cloud? IBM Power Virtual Server? DR in the cloud? A hybrid architecture connecting IBM Power with AWS or Azure?

    There isn’t one right answer for every IBM i environment.

    Start with the business requirement. Understand the workload. Then decide where it belongs.

    Explore IBM Power cloud, managed services, and hybrid solutions from Lightedge.

    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    An Introduction to WDSc Table Views The Save-Restore Commands

    Leave a ReplyCancel reply

Volume 5, Number 4 -- January 26, 2005
THIS ISSUE
SPONSORED BY:

Advanced Systems Concepts
Patrick Townsend & Associates
Guild Companies

Table of Contents

  • An Introduction to WDSc Table Views
  • Another Reason to Use P-Fields
  • The Save-Restore Commands

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • IBM i Delivers New Development Tooling With 2026 Fall Tech Refreshes
  • Big Blue Says AI Is Not Behind The Big Uptick In IBM i Security Alerts
  • Guru: Web Service With Pagination
  • The GenAI Revolution And Product Shortages Send IT Budgets Skyward
  • IBM i PTF Guide, Volume 28, Number 40
  • IBM i PTF Guide, Volume 28, Number 41
  • Bob Code Assistant Gets Better Understanding Of IBM i Applications
  • IBM i In The Cloud And The Case For Reversing Replication
  • Guru: From Hiking Boots To Long-Term Memory
  • Inside IBM’s New PowerHA Cloud Offering, Full System Manager

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle