Administrative and Operational Enhancements › CA ADS Enhancements › Improved BIF Management

Improved BIF Management

CA ADS built-in functions are now managed in a way that provides better run time performance while simplifying product installation and maintenance.

In previous releases, you could improve run time performance by linking selected BIF modules with ADSOMAIN, which avoided the overhead of loading a module on each function invocation. The benefit was limited, however, because not all BIF modules could be linked with ADSOMAIN. Furthermore, you had to take extra steps each time the product was upgraded or maintenance was applied to ADSOMAIN or any of the BIF modules linked with it.

In Version 18.0, CA ADS manages BIFs to overcome these shortcomings. All CA-supplied BIF modules are linked with ADSOMAIN and all user-written BIF modules can optionally be linked together as a new ADSOVCON module. These changes have the following benefits:

• Reduced overhead for invoking CA-supplied BIFs because no additional modules are loaded at runtime.
• Reduced overhead for invoking user-written BIFs by creating an ADSOVCON module.
• Simplified product installation and maintenance because there is no need to relink a tailored ADSOMAIN when performing these activities.

Note: Creating an ADSOVCON module is not required. CA ADS dynamically loads user-written BIFs if they are not linked with ADSOVCON.

ADSOVCON Module Creation

Optionally create an ADSOVCON module using the #BIFVCON macro to identify your user-written BIF modules to be linked together. The following sample ADSOVCON module indicates that the UDATE and UCHECK BIF modules are to be linked with ADSOVCON.

#BIFVCON TYPE=INITIAL                             
#BIFVCON TYPE=ENTRY,PROGRAM=UDATE,EPNAME=UDATE 
#BIFVCON TYPE=ENTRY,PROGRAM=UCHECK,EPNAME=UCHKEP1
#BIFVCON TYPE=FINAL

To create an ADSOVCON module, create a source member as described in the following section and save it in your custom source library. Then assemble and link it into your custom load library.

The following diagram shows the syntax for the #BIFVCON macro:

►►──────── #BIFVCON TYPE= ─┬─ INITIAL ─┬──────────────────────────────────►
                           ├─ ENTRY ───┤  
                           └─ FINAL ───┘  

 ►──────────────── ,PROGRAM=program-name ─────────────────────────────────►

 ►───────────────── ,EPNAME=entry-point-name ─────────────────────────────►◄

#BIFVCON Macro Parameters

This section describes the parameters for for the #BIFVCON macro.

TYPE

Indicates the type of BIFVCON statement being generated.

INITIAL

Identifies the first BIFVCON statement in the program.

ENTRY

Identifies a BIFVCON statement defining a user-written BIF module.

FINAL

Identifies the last BIFVCON statement in the program.

PROGAM=program-name

Identifies the name of a user-written BIF module to be linked with ADSOVCON. program-name must be the same as the program name associated with a built-in function declared in your RHDCEVBF module.

This parameter is valid only if TYPE=ENTRY is coded.

EPNAME=entry-point-name

Identifies the name of the entry point of the user-written BIF module. entry-point-name must be the name of the entry point in the program identified by program-name.

This parameter is valid only if TYPE=ENTRY is coded.