Previous Topic: Copying Internally-Referenced Template Functions

Next Topic: Assigning Access Paths for Referenced Functions

Creating and Naming Referenced Functions

The copy process first searches the target file for a function with a name matching that of the template function. Note that if the source function name contains *Template, it is replaced with the name of the target file before the search for matching names; for example, ‘Change *Template’ translates to ‘Change Customer’ for the Customer file.

Note: If the DBF functions (CHGOBJ, CRTOBJ and DLTOBJ) attached to the *Template file contain user-defined processing, you need to change their default names; otherwise, the default functions on the target file are used. This is true even if the default DBF functions are not yet been created for the target file.

Template Function Type

Compatible with These Target Function Types

EXCINTFUN

EXCEXTFUN

EXCUSRPGM

All except PRTOBJ

 

 

CHGOBJ

CRTOBJ

DLTOBJ

EXCINTFUN / EXCEXTFUN / EXCUSRPGM DSPRCDn / EDTRCDn / PMTRCD

 

 

RTVOBJ

EXCINTFUN / EXCEXTFUN / EXCUSRPGM

 

 

DSPRCDn

EDTRCDn

PMTRCD

EXCINTFUN / EXCEXTFUN / EXCUSRPGM

DSPRCDn / EDTRCDn / PMTRCD

CHGOBJ / CRTOBJ / DLTOBJ

 

 

PRTFIL

EXCINTFUN / EXCEXTFUN / EXCUSRPGM

PRTOBJ

Not compatible with any other type

Notes:

1. EXCINTFUN, EXCEXTFUN, and EXCUSRPGM are compatible with all other types (except PRTOBJ, which is incompatible with all other types.

2. The internal functions (except RTVOBJ and PRTOBJ) are compatible with the single record display functions.

3. The subfile function types are fully compatible with each other.

If the type is not compatible, a new function of the same type as the template function is created over the target file.