Q: How can I allow field duplication for input-capable fields? I want a data entry operator to have the option of duplicating information keyed from the previous input operation.
A: Use the duplication (DUP) field-level keyword in your display file DDS for any field you want duplication-enabled. Pressing the DUP key initiates the duplication process by allowing your application program to become aware that the DUP key was pressed. Your application program must perform the actual duplication. There are two ways you can duplicate fields: duplicate the entire field or duplicate the field one character at a time. The easiest method is to duplicate the entire field, which can be done with the following procedure.
Specify two fields in your DDS for each input-capable field you want to allow duplication for. Create one field as input-capable and specify the DUP keyword with a response indicator. Condition the DUP keyword with an indicator. Create another field as a hidden field. 10 illustrates the DDS.
Specify two fields in your DDS for each input-capable field you want to allow duplication for. Create one field as input-capable and specify the DUP keyword with a response indicator. Condition the DUP keyword with an indicator. Create another field as a hidden field. Figure 10 illustrates the DDS.
On the first output operation, make sure the conditioning indicator for the DUP keyword is off.
After the first input operation, move the input-capable field to the hidden field.
Set the conditioning indicator for the DUP keyword on for the remaining output operations.
For the remaining input operations, test the DUP keyword response indicator. If it's on, the value of the hidden field should be moved to the input-capable field. If the response indicator is off, just move the input-capable field to the hidden field.
The procedure for duplicating a field one character at a time is a little more complicated. You can find out how to perform this procedure in the DDS Reference manual.
-Matt Kofsky
DUP Key Processing
Figure 10 DDS Required for DUP Key Activation
*.. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 A R INFMT A INDTE 5 I 3 2 A 20 DUP(30) A INDTEH 5 2H
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