The Ref level value refers to the level of reference by a given object to the original object that is displayed on the subfile control. This value may be changed by the user and will control the data shown in the subfile. By manipulating the range of levels available, all possible reference levels can be viewed individually or in combination.
The Ref type column in the subfile refers to the reason for the reference. The following table shows the possible reasons for references between model objects. Actual references to a given model object will depend upon the model object type.
|
Obj Type |
To Type |
Ref Code |
Reason |
Note |
|
All |
|
*ENTRY |
Displayed only on the first panel when you access the YDSPMDLREF panel for a model object list rather than for a single list entry; for example, by using the YDSPMDLREF command or F22 from the YEDTMDLLST panel. It indicates that each list entry displayed has simply been updated to reflect its current state in the model; no references have been expanded. Your original list is not changed. You can now perform impact analysis on single list entries using the selection options. See also the online Help for the panel and the Impact Analysis topic in chapter 1 of Generating and Implementing Applications. |
|
|
ACP |
ACP |
*ASSACP |
For associated access path, such as the UPD access path for a given RTV. |
|
|
|
ACP |
*REFACP |
For referenced access path, such as the RTV access path on a file-to-file relation of a referring access path. |
|
|
|
AUX |
*ACPAUX |
For access path auxiliaries. |
1 |
|
|
CND |
*ACPCND |
For access path condition. |
|
|
|
FIL |
*REFFIL |
For owning FIL. |
|
|
|
FLD |
*PHYENT |
For access path physical entries. |
2 |
|
|
FUN |
*SELRCD |
For select record override function. No references. |
|
|
CND |
CND |
*LSTCND |
For list condition. |
|
|
|
FLD |
*REFFLD |
For owning field. |
|
|
APP |
- |
|
No references. |
|
|
ARR |
ACP |
*ARRDTL |
For array entry details. |
|
|
|
FIL |
*REFFIL |
For associated FIL. |
|
|
|
FLD |
*ARRENT |
For array entries. |
|
|
FIL |
FIL |
*REFFIL |
For referenced FIL. |
|
|
|
FIL |
*SHRFIL |
For file defining a sharing level. |
|
|
|
FLD |
*FILENT |
For field appearing as an entry. |
|
|
|
FLD |
*MAPFLD |
For field mapping (user-defined field types). |
|
|
|
FLD |
*PARFLD |
For field mapping (user-defined field types). |
|
|
|
FLD |
*SRCFLD |
For field mapping (user-defined field types). |
|
|
|
FLD |
*RNMFLD |
For renamed entry. |
|
|
|
FLD |
*VRTENT |
For field as virtual entry. |
|
|
|
MSG |
*RCDEXS |
For record exists message. |
|
|
|
MSG |
*RCDNFD |
For record not found message. |
|
|
FLD |
CND |
*FLDCND |
For condition. |
|
|
|
FLD |
*REFFLD |
For domain definition. |
|
|
|
FUN |
*EXTINT |
For external/internal conversion function (user-defined field type). |
|
|
|
FUN |
*FLDUSR |
Field-attached user source function (enabled) |
|
|
|
FUN |
*INTEXT |
For internal/external conversion function (user-defined field type). |
|
|
FUN |
ACP |
*BASED |
For based-on access path. |
|
|
|
ACP |
*FUNPAR |
For function/message parameter definition. |
|
|
|
ARR |
*BASED |
For based-on array. |
|
|
|
ARR |
*FUNPAR |
For function/message parameter definition. |
|
|
|
CND |
*ABOCND |
For action bar condition. |
|
|
|
CND |
*ACTCND |
For action diagram condition. |
|
|
|
CND |
*DEVCND |
For screen entry condition. |
|
|
|
CND |
*VLDCND |
For field validation condition. |
|
|
|
DSP |
*DSPDTA |
For display file details. |
1 |
|
|
FIL |
*REFFIL |
For owning FIL. |
3 |
|
|
FLD |
*ACTION |
For action diagram compares. |
|
|
|
FLD |
*DEVENT |
For device fields. |
|
|
|
FLD |
*FUNPDT |
For function/message parameter details. |
|
|
|
FLD |
*PARAM |
For action diagram parameter fields. |
|
|
|
FLD |
*REFFLD |
For derived field. |
4 |
|
|
FLD |
*SCRMAP |
For screen field mapping (user-defined field types). |
|
|
|
FLD |
*SCRPAR |
For screen field mapping (user-defined field types). |
|
|
|
FLD |
*SCRSRC |
For screen field mapping (user-defined field types). |
|
|
|
FLD |
*SCRTXT |
For screen text field. |
5 |
|
|
FUN |
*ACTION |
For action diagram functions. |
|
|
|
FUN |
*DFTDBF |
Default database function. |
|
|
|
FUN |
*DSLDBF |
Deselected database function. |
|
|
|
FUN |
*DEVSTR |
For device structure reference. |
|
|
|
FUN |
*DEVUSR |
Device-attached user source function |
|
|
|
FUN |
*ENTUSR |
Entry-attached user source function |
|
|
|
FUN |
*FLDUSR |
Field-attached user source function (disabled) |
|
|
|
FUN |
*FMTUSR |
Format-attached user source function |
|
|
|
FUN |
*RPTUSR |
Report-attached user source function |
|
|
|
FUN |
*SCRUSR |
Screen-attached user source function |
|
|
|
FUN |
*SELRCD |
For select record override function. |
|
|
|
HLP |
*HLPDTA |
For help file details. |
1 |
|
|
MSG |
*ACTION |
For action diagram message. |
|
|
|
SRV |
*FUNAUX |
For function auxiliary. |
|
The Note column indicates whether or not there is a reciprocal entry in the usage table by the referenced object. The numbers in the column refer to the following explanations as to why there will not be a corresponding usage entry:
The referenced object is not a primary object.
Reference is for object redefinition only, the relationship is already noted using *FILENT.
The usage of FIL to FUN is not a useful piece of information. The usage might, however, be discernible via ACP. In other words, usage on a FIL will display any ACP objects attached to the FIL. These in turn will display any using FUN objects.
The relationship between FLD and FUN represents the interdependency of these two objects on each other. The FLD object actually uses the FUN. However, the FUN is not a primary object. It is not treated as a function in its own right and is not accessible except through the FLD object.
The reference of FUN to FLD for screen text is not treated as a bona fide usage since the fields involved are internal product objects only.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |