Minimizing Problems for Future Upgrades

When future versions are released, the product documentation will identify which macro files (Form, Object, Function, Command macro) and which parts of the directory hierarchy have been modified. You must then decide on one of three courses of action for dealing with any customized Appware which you may have been using:

• Run your existing Appware, thereby ignoring any enhanced features which may have been incorporated into the standard versions.

• Revert to using standard Appware instead of your customized versions.

• Update your customized Appware to take advantage of any enhanced features now available.

In order to minimize any problems resulting from updating your customized Appware, you should adopt the following key principles as part of your customization policy:

• The directory which holds the Appware files associated with your Applications is divided into two main areas: a standard product area and a user area. You should make changes only in the User area using only copies of the standard Application macros.

  Warning:
  You should never modify the original files, so that you can always revert to using these if things go wrong.

• The environment variable PMLLIB is a search path which must be set to the directory or list of directories under which User-defined PML functions, objects and forms are stored. The directory specified can contain sub-directories which will automatically be scanned by PML.

• When writing your own PML Appware, follow the styles and conventions used in the AVEVA standard AppWare.

• Make sure that the names of any new objects, forms and functions which you create cannot conflict with the names of any standard AVEVA Appware which may be used in the AVEVA Applications. You should prefix the names of your objects, forms and Global variables with a suitable code to distinguish them from AVEVA names. For example, a company XYZ could choose to start all form and Global variables names with the characters XYZ.