Distributed Relational Database Architecture › Commands for DRDA › YWRKDSTFIL: Work with Distributed Files

YWRKDSTFIL: Work with Distributed Files

Two CA 2E files, *Configuration Table and *Distributed File, are present in every model. These files contain functions and access paths shipped for DRDA. When generated, they form the set of objects that make up the configuration table editor environment.

Note: The YWRKDSTFIL command operates outside the model environment. Security for this command, and associated functions and objects, are your responsibility.

You can copy the functions shipped with *Distributed File and *Configuration Table files and make modifications to the copied versions as required. You can also create functions and customize them to your own standards and requirements. You may even want to create an NLS version of the editors by generating NLS applications in CA 2E.

The YCVTDSTFIL and YWRKDSTFIL commands and the shipped RDB loader (Y2LRDBR, Load RDBs for View) use the access paths described in the model built over the *Distributed File and *Configuration Table files. Any changes that impact these access paths may cause these functions to behave incorrectly. The source for Y2LRDBR and the associated display file is shipped in Y2SYSRC.

Note: CA does not recommend adding any fields to either the shipped *Distributed File or *Configuration Table files, nor directly modifying the system functions and access paths.

To begin to use the shipped configuration table editor, generate and compile the following:

• *Distributed File Access Paths:
  • Physical file—Y2DSTFP
  • Update index—Y2DSTFL0
  • Retrieval index—Y2DSTFL1
  • *DSTFNM/*TYPE/*TABVIEWNM—Y2DSTFL2
  • Dist. File - Config Tbl—Y2DSTFL3255
• Functions:
  • Work With Config Table—Y2CFGTR
  • Work With Dist. File—Y2DSTFR
• *Configuration Table Access Paths:
  • Physical file—Y2CFGTP
  • Update index—Y2CFGTL0
  • Retrieval index—Y2CFGTL1
  • *TABVIEWNM/*SEQ/*RDBNM—Y2CFGTL2

Once you generate and compile these objects, run the YCVTCNDVAL (Convert Condition Values) command, then the YCVTMDLMSG (Convert Model Messages) command for your model.

You can then use the YWRKDSTFIL command to invoke the configuration table editor. This command displays a list of the access paths enabled for distribution. These entries are created with the YCVTDSTFIL command and displayed on the Work With Distributed Files panel. On this panel, files are identified as tables or views. A table in SQL is equivalent to a physical file, and a view is similar to a logical file.

You can work with the tables and/or views from this panel. You may wish to define the distributed nature of data at the table level (physical file) or to differentiate the distribution of that at the view (logical file) level.

While you are not required to do so for DRDA support, you can reference the access paths by any valid CA 2E functions.

Note: You cannot remove any of the distributed file table entries, except by running the YCVTDSTFIL command.