Wouldn't life be easier if the field names on the display file matched the field names in the physical file? To display the values in the database using RPG, the program would simply CHAIN to the file before the EXFMT.
The problem is, when the program is updating the file, the record is locked. It would be advantageous if the record could be shared by multiple users. You can accomplish this by specifying an N in column 53 on the CHAIN op code so the record isn't locked.
When the display fields are modified and the user wants to update the record, the program must CHAIN to the record again and lock the record. Since the field names are the same, the second CHAIN would destroy the displayed values. This explains why many programs have hundreds of lines of code that do nothing more than move data fields.
There is an easier way; use a multiple occurrence data structure. Simply name a data structure, specify E in position 17 to indicate that the subfields are externally described, use the same file name as in the F-specs, and insert a 2 for the number of occurrences. Prior to the update, use the OCUR op code as shown in 8.
There is an easier way; use a multiple occurrence data structure. Simply name a data structure, specify E in position 17 to indicate that the subfields are externally described, use the same file name as in the F-specs, and insert a 2 for the number of occurrences. Prior to the update, use the OCUR op code as shown in Figure 8.
The first OCUR op code points to the second occurrence of the data structure to preserve the field values on the screen. This technique simplifies coding; the field names on the screen are consistent with the field names in the file, and you can use another feature of the AS/400; referencing the field definitions in the display file.
Another approach to this problem is to use the RTNDTA display file keyword. See the DDS Reference manual (SC41-9620) for additional information.
Matching Field Names
Figure 8 Using Display File Field Names with OCUR
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+.. C 2 OCUR DSNAME C KEY CHAINFNAME 88 C 1 OCUR DSNAME C *IN88 IFEQ *OFF C UPDATRECNAM C ENDIF
More 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.
TRY 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.
Forms 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.
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:
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