The build process calls a predefined entry point in your library codefile that you might set up, and passes your Autoload file name (your COMS configuration file name to be loaded automatically) as a parameter. Your usercoded procedure might check and modify the COMS CONFIG file programmatically, and return a value to allow or disallow the automatic load.

If your library file is not found, or if library linkage fails, automatic loading proceeds.

Your library codefile must be accessible under the file search path for the usercode under which your application is configured. This file is named as follows:

*NGEN28/USERLIB

The entry-point is COMSVERIFY, defined as follows.

INTEGER PROCEDURE COMSVERIFY (COMS_LOAD_FILE_TITLE);
EBCDIC ARRAY COMS_LOAD_FILE_TITLE [0];

The COMS_Load_FILE_TITLE parameter contains the title of the Autoload file you want to load. You can change or replace this file by a privileged process.

Your COMSVERIFY procedure should return one of the values shown in the following table:

Example

In this example, system parameter values are shown in the following table:

The following table shows COMS filenames based on these system parameter values: