The AUPDFLDDBR command

The AUPDFLDDBR command allows you to generate database links at the field level. Once generated, the links can be displayed and used via the ARCAD Observer perspective in the ARCAD Client RCP or the plug-in in RDi.

The generation of the database links using the AUPDFLDDBR command proceeds as follows:

  1. The command links the fields of the different physical files using:
    • the references to the fields of the common reference file, or
    • the codification of the field name.
  2. The command searches for and memorizes the primary keys (or principal identifiers) in each file. These primary keys are taken from the first file that meets the following conditions:
    1. The physical file has a unique key.
    2. One of the non-joined logical files that depends on the physical file has a unique key.
    3. The physical file has a specified key.
    4. One of the non-joined logical files that depends on the physical file has a specified key.
  3. The command creates links between the fields of the two physical files if all the primary keys of one of the files are found in the other file.

The logical files are processed in alphabetical order. However, the numbers are processed before the letters.

Example

The XXXXL1 and XXXXL2 files are processed before the XXXXLA and XXXXLB files.

Note

The first time you run this command, the primary keys are memorized (accessible from the field repository) and you can modify them. Then, when you re-run the AUPDFLDDBR command, it will take into account the primary keys that you have modified.

The parameters available in the AUPDFLDDBR command are described below.

If a parameter has a default value, it is indicated in bold.

Summary of the AUPDFLDDBR options
Options Values
Application ID (APPID) *CURENV
Component display level (VERSLVL) *LASTPRD, *LAST, *CURENV
Replace or add record (OPTION) *ADD, *REPLACE
With the reference files (USEFLDREF) *YES, *NO
Use field naming (USEFLDNAME) *NO, *YES
Use repository constraints (USEREFCST) *YES, *NO
Use program analysis (USEPGMPRP) *NO, *YES
List of reference files (REFFILLIST) *APP, list-name = *LIBL, *CURLIB, library-name
List of physical files (PFFILLIST) *FLDDCT, list-name = *LIBL, *CURLIB, library-name
List of propagation monitoring (DRVFLDLIST) *CURENV, *LIBL, *CURLIB, library-name
Substitute the field names (FLDNAMRPL) up to 50 substitutes
Search words to be known (FLDNAMCOD) up to 20 words
Fields or codes to omit (FLDOMT) *NONE, field/code-name
% Fields without prefix/suffix (PRXSFX) percentage
With inter application links (USEAPPLNK) *USE, *ALL, *NONE

This parameter allows you to identify the application to process.

*CURENV The current environment's application.
Alpha-Value Enter the ID code of the application.

This parameter allows you to display the repository at a different level than the current level.

The possible values are as follows:

*LASTPRD Enter this value to display the repository at the last transfer to production level.
*LAST Enter this value to display the repository at the last version that includes the literal.
*CURENV Enter this value to display the repository at the current version level.
Alpha-Value Enter the version number level for which you want to have the repository display.

Specifies if this process should add the new links or totally regenerate them.

*ADD Only the new links are added. The old links, which have already been defined, are neither changed nor deleted.
*REPLACE All the defined database links of this application are deleted; they are then regenerated.

This parameter allows you to indicate if the method usedto use to generate the database links is based on the references to the common reference file fields.

*YES All fields defined by external references relating to the same reference file field will be matched for the establishment of database links.
Fields that do not have a reference for a reference file field will be linked in relation to their complete name.
*NO In relation to a reference file, external field references are not taken into account.
Note

If the 2 methods (USEFLDREF and USEFLDNAME) for linking fields are chosen, it is the one based on the external references to the common reference file fields which takes precedence over the method based on the codification of field names.

Specify if the method used to generate the database links is based on the codification of field names.

*YES

The physical file field names are assumed to adhere to the following codification:

  • a prefix (or suffix) of one or more characters, identical for all fields in the physical file.
  • the remainder of the field name corresponds to an identifier: all fields with the same type, length, number of decimals, and identifier are matched to define the database links.
*NO The codification of the field names is ignored.

Specify if the method used to generate the database links takes Referential Constraints into consideration.

*YES Referential Constraints are used to determine database links.
*NO Referential Constraints are ignored.

Specify if the method used to generate database links is based on the derived field list created by an ARCAD-Transformer propagation process. See the ACVTPGMFLD command which creates a list of derived fields (specified in the DRVFLDLIST parameter) that can be used by this command.

Reference

See the OBSDBRXRF macro command, for an example of the use of this parameter (after the ACVTPGMFLD command).

Refer to the OBSDBRXRF macro-command documentation.

*YES There are derived fields, processed by the ARCAD-Transformer command ACVTPGMFLD, to take into account. The field list is specified in the DRVFLDLIST parameter.
*NO ARCAD-Transformer is not used.

Indicate here, the (source or object) list name that corresponds to the application's reference files.

No database link will be established on these reference files, they will be ignored.

*APP The reference files are those defined on the operational attributes level of the application.
list-name Enter the name of a list containing the reference files to be omitted.

The possible values for the name of the library are as follows:

*LIBL The object is searched for in the list of libraries.
*CURLIB The specified object is searched for in the current library for the job.
If no *CURLIB was specified, QGPL is used by default.
Library name Enter the name of the library containing the object.

Indicate here the (source or object) list that corresponds to all the physical files for which you must analyze the database links at the field level.

These fields must belong to the application to be processed and their cross-references must be updated.

*FLDDCT All the physical files defined in the application and present in the field repository are processed (except for the reference files).
list-name Enter the name of a list containing the physical files to be processed.

The possible values for the name of the library are as follows:

*LIBL The object is searched for in the list of libraries.
*CURLIB The specified object is searched for in the current library for the job.
If no *CURLIB was specified, QGPL is used by default.
Library name Enter the name of the library containing the object.

Indicate the name and library of the list file where the propagation process will list the derived fields. This file will contain one record per field/program combination.

*CURENV The object is searched for in the current environment. (Run the ADSPCURENV command to identify this environment).
*LIBL The object is searched for in the list of libraries.
*CURLIB The object is searched for in the current library for the job.
If no *CURLIB was specified, QGPL is used by default.
Library name Enter the name of the library containing the object.

The *OBJ special value is reserved for the propagation in mode *ALLFLD, or *RNMOBJ in order to give this list the same name as the referenced object.

Note

The name of this file (with its library) identifies the propagation. This is the file name that you will specify in the ACLRDRVFLD command to clear the data that a propagation generates in ARCAD files.

This parameter is only operational if you use the matching method according to the codification of field names (Use field naming (USEFLDNAME) is set to *YES).

It allows you to indicate from 0 to 50 substitutions on the complete or partial ("identifiers") field names to compensate a codification of field names that is not always normalized.

This parameter is only operational if you use the matching method according to the codification of field names (Use field naming (USEFLDNAME) is set to*YES).

It allows you to indicate from 0 to 20 "words" that would have been used as identifiers for the main key field of the file.

Example

For the Customer (prefix CU) and Supplier (SU) files, the customer code field name is CUCODE and the supplier code is SUCODE, while they should have been CUCUS and SUSUP (CUS and SUP being the Customer and Supplier identifiers).

In this case, specify that CODE is a word to be recognized.

Note

This substitution method only works if there are other files where the field names begin with the prefix (or suffix) of the file and have similar text (although not necessarily identical).

This parameter is operational whatever the field matching method you are using.

It allows you to indicate from 0 to 50 fields, with or without prefixes (or suffixes), that should not be taken into account during the matching process.

*NONE None of the fields or codes are omited.
Alpha-Value Enter the text to omit.

This parameter defines the percentage of fields without prefixes (or without suffixes) accepted by the process.

Example

0% means that all fields should have the same prefix (or suffix), in order for it to be taken into account.

20% means that one field out of five can have a different prefix (or suffix) than the other fields. This tolerance allows you to keep the prefix (or suffix) previously detected.

Specify whether or not to use inter-application links for cross-references. The list of applications linked to the current application is obtained by examining the links defined in the application's descriptive parameters (found using the ADSPAPPINT command).

*USE The inter-application links are used to simulate the real use context for components. The link is made towards the applications used or with a reciprocal link.
In the case of a component homonym, only the first one found is taken.
*ALL The inter-application links are used to determine all the applications concerned for a component. The link is made in all directions (applications used by or using the current application or reciprocal link).
In the case of a component homonym, all the applications of this component are displayed, in the order defined in the inter-application links.
*NONE The inter-application links are not used. Only the components present in the interrogating application are known.