CALL: Automatic library call option

During input processing AUTOCALL control statements instruct the binder to resolve external references against a specified library.

At the end of input processing the binder performs final autocall, where libraries specified on LIBRARY control statements and the SYSLIB DD are used to resolve any remaining external references (while AUTOCALL and LIBRARY control statements are optional, automatic library call requires that there is a SYSLIB DD, otherwise a severity 8 error is issued). External references that are unresolved at the end of final autocall are treated as severity 8 errors.

You can turn this processing off by coding the option NOCALL or NCAL in the PARM field as follows:

{NCAL | NOCALL}

When the no automatic library include option is specified, the binder does not search any library members to resolve external references. Unresolved external references will be treated as severity 4 errors. If this option is specified, you do not need to use the LIBRARY statement to negate the automatic library call for selected external references, and you do not need to supply a SYSLIB DD statement.

Unless the LET option is also specified, other errors might still cause the module to be marked not executable.

Note: If autocall processing is disabled, references to modules in the C run-time library will not be resolved. For example, if the SMP/E link-edit utility entry PARM subentry is not left to use the default value and NCAL is not explicitly listed in the specified value, the binder default of CALL=YES (or the binder installation default) is used. This can cause frequent errors when using SMP/E to install products that use the binder. See SMP/E for z/OS Reference for more information about SMP/E utility entries and CALLLIBS.