Q: I have a display screen which consists of input/output fields for 18 part numbers and quantities, a single field for a warehouse number, and a function key. I defined a portion of the screen input/output buffer as an array of quantities in the RPG program that controls the display file. The code I'm using looks similar to the code in 1.
Q: I have a display screen which consists of input/output fields for 18 part numbers and quantities, a single field for a warehouse number, and a function key. I defined a portion of the screen input/output buffer as an array of quantities in the RPG program that controls the display file. The code I'm using looks similar to the code in Figure 1.
When I compile the RPG program, I get a compile-time error that says the field *IN03 is not valid for a data structure because the compiler repeats the "fields" from the file the data structure is referring to. For screens, the indicators are part of the I/O buffer and are therefore being included. I'd like to be able to manipulate my screen input to the program using array logic, if there is a means of doing so. Is there a way I can accomplish this?
A: There is a way to do what you want, but you can't use an external data structure. You have to rename the fields from the display file to array elements. For example, look at the RPG code in 2. In this example the quantity fields in the display file are named QTY01, QTY02, QTY03, and so on. The RPG program first defines an array called QTY. It then renames each of the quantity fields in the display file to a corresponding element of the QTY array. From that point on, the program can perform calculations or output by specifying the QTY array instead of the individual screen field names.
A: There is a way to do what you want, but you can't use an external data structure. You have to rename the fields from the display file to array elements. For example, look at the RPG code in Figure 2. In this example the quantity fields in the display file are named QTY01, QTY02, QTY03, and so on. The RPG program first defines an array called QTY. It then renames each of the quantity fields in the display file to a corresponding element of the QTY array. From that point on, the program can perform calculations or output by specifying the QTY array instead of the individual screen field names.
Array Screen Fields
Figure 1 Defining the I/O Buffer as an Array
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 FSFC351DFCF E WORKSTN E QTY 18 3 0 IEXTDS1 E DSSFC351DF I 2 55 QTY
Array Screen Fields
Figure 2 Renaming Screen Fields to Array Elements
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 FSFC351DFCF E WORKSTN E QTY 18 3 0 ISFC351FM I QTY01 QTY,01 I QTY02 QTY,02 I QTY03 QTY,03 . . . I QTY16 QTY,16 I QTY17 QTY,17 I QTY18 QTY,18
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