There is no standard masking of symbols (CSECTs, ENTRYs) when linking with BINDER; the symbols remain visible for subsequent linkage runs with BINDER or DBL.
When linking with DBL, this has the following effects: If a library contains individual modules created by the compiler and also LLMs with a linked runtime system, external references to the runtime system may, in certain circumstances, be resolved from any prelinked module and not from the runtime library when dynamically linking individual modules. In this event, a number of “DUPLICATES” warnings are received from the DBL. This is due to the Autolink mechanism first searching the library containing the individual module and then the runtime libraries assigned with the link names BLSLIBnn.
In order to ensure that, when performing dynamic linkage, the external references are always resolved from the current runtime library and not from any arbitrary module, it is advisable
either to keep individual modules and prelinked modules in different libraries or
to mask the symbols, for example with the statement MODIFY-SYMBOL-VISIBILITY VISIBLE=NO when linking with BINDER.