Evaluating lists of impacted fields
This list you created contains the list of fields for which you want to analyze the links.
Evaluating lists of physical file fields
This is the most common case when using ARCAD Transformer Field.
For more information about the creation of this list, refer to Field lists.
This list only takes the physical file fields into account (PF, PF38). There is no need to include any logical file fields (they will be deducted by the propagation).
It can sometimes be useful to include (or exclude) the reference file fields or physical file fields. This only has an impact in the case of propagation with automatic modification of the file sources.
Evaluating lists of program fields
[Optional] It may be necessary to analyze the impact on one or more program fields that we know of, in order to establish the list of the other related program fields, as well as those of the file fields.
Follow the subsequent steps to establish the list of related program fields.
Step 1 Use the ACRTFLRLST command to create a list of all the fields of one or more programs.
Field cross-references (ACRTFLRLST)
Type choices, press Enter.
By field, literal or component *FLD *FLD, *OBJ, *IFS, *LIT
Field name . . . . . . . . . . .
+ for more values
Application ID . . . . . . . . . *CURENV Character value, *CURENV
Component display level . . . . *CURENV Character value, *CURENV
Only if the field is used . . . *USED *USED, *IMPL, *UPD...
TO list . . . . . . . . . . . . LSTTMP Name
Library . . . . . . . . . . . QTEMP Name, *LIBL, *CURLIB, *CURENV
Replace or add record . . . . . *REPLACE *REPLACE, *ADD
Retrieve system function tree . *NO *YES, *NO
1st selection field . . . . . . *FLDUSE Character value, *BLANK
2nd selection field . . . . . . *FLDNAME
Type of list to generate . . . . *LST *LST, M, O, F
Step 2 Use the AEDTLST command on the created list (with Option 3=Copy) or AEXTLST (extract the items from a list) for moving the field or fields into the list of fields to process.
You could have also created an item in the list with AADDLSTE, but in this case you would have to correctly specify each required argument.
In COBOL, several fields can be homonyms when they are described in groups of different fields. In ARCAD, the name of these fields is followed by ‘DUPxx’ in order to get the names of the unique fields. You must verify using the repository which field you want to choose.
Evaluating lists of display or printer fields (DSPF/PRTF)
You may also want to begin an impact analysis on one or more display or printer fields to determine with which program or file fields they are linked to.
In this case, use the ACRTFLRLST command to create the list of display (or printer) fields.
Evaluating lists of fields in the L.D.A. to propagate
If the fields to be propagated are systematically present in most of the L.D.A. part (common to the entire application), you can add them to the list of fields to propagate (using F6) as follows:
Add an entry to the list (AADDLSTE)
Type choices, press Enter.
Object/member/field . . . . . . Name, *IFS
Library (object or source) . . *LIBL Name, *CURLIB, *LIBL, *IFS
Type (object/source/field) . . . Character value, *ONLY
List . . . . . . . . . . . . . . *CURRENT Name, *CURRENT
Library . . . . . . . . . . . Name, *LIBL, *CURLIB
Check existence of element . . . *YES *YES, *NO
IFS object . . . . . . . . . . .
Destination directory . . . . . *DFT
Additional Parameters
Type of list . . . . . . . . . . *LST *LST M O F I
Object attribute/component typ *OBJMBR Character value, *OBJMBR
Compil type/Field format . . . . *OBJMBR *OBJMBR, *BLANK, Type (F4=List
Source file/field file . . . . . *OBJMBR Name, *OBJMBR, *BLANK
Creation library . . . . . . . . *OBJMBR Name, *OBJMBR, *BLANK
Object/member modif date . . . . *OBJMBR Date, *OBJMBR, *BLANK
Object/member change time . . . *OBJMBR Time, *OBJMBR, *BLANK
# for compilation sequence . . . *OBJMBR Number, *OBJMBR
Flag . . . . . . . . . . . . . . ' ' X, ' ', A, H, L
1st selection field . . . . . . *BLANK Character value, *BLANK...
System function tree info:
Sub-system . . . . . . . . . . *OBJMBR Character value, *OBJMBR
Function . . . . . . . . . . . Character value
Sub-function . . . . . . . . . Character value
Text . . . . . . . . . . . . . *OBJMBR
The name of the P0017L0009 field indicates the position and length concerned.
The Type A(9) shows the type and length and the format Z specifies the field format.
The attribute must be *LDA.
The format and file field are at X because a valid character must be entered.
Therefore, each time the LDA is used in RPG(LE), CLP, or OCL36, any eventual variables loaded from this LDA position will be propagated. When extending fields, the length and position will be extended to take into account the size increase of this field (even if the position in question wasn’t defined in the program).
