There is a central module 'database' that has information about all modules.
It is accessed by BLDRUN.COM which has replaced several
procedures.
(They have never been really documented, so they are not listed here either).
BLDRUN.COM
@@ explain passing of information between BLDRUN.COM and CC_PYTHON.COM
usage
Parameters:
@@ to be enhanced
examples:
$ @ PYTHON_VMS:BLDRUN "$ALL"
$ @ PYTHON_VMS:BLDRUN "C:name"
%BLDRUN-W-NOMODULE, no modules in component: name
$
$ @ PYTHON_VMS:BLDRUN c:PYTHON.VMS_LBR
%BLDRUN-I-MODCNT, found 16 modules in component: PYTHON.VMS_LBR
%CC_PYTHON-I-COMPILE, module ( 1/ 16): VMS_LBR
%CC_PYTHON-I-COMPILE, module ( 2/ 16): VMS_LBR_CLOSE
[...]
%CC_PYTHON-I-COMPILE, module ( 16/ 16): VMS_LBR_SET_MOVE
%BLDRUN-I-DONE, completed: C:PYTHON.VMS_LBR
$
In the example above no new object library has been created.
$ @ PYTHON_VMS:BLDRUN "C:*"
%BLDRUN-I-CMPLIS, listing component names...
PYTHON.BASE
PYTHON.VMS_LBR
PYTHON.VMS_SMG
$ @ PYTHON_VMS:BLDRUN "PYTHON" "*"
%BLDRUN-I-MODCNT, found 23 modules in OLB: PYTHON
%BLDRUN-I-OLBCRE, creating PYTHON_DDT.OLB
%CC_PYTHON-I-COMPILE, module ( 1/ 23): BLTINMODULE
%CC_PYTHON-I-COMPILE, module ( 2/ 23): CEVAL
[...]
%CC_PYTHON-I-COMPILE, module ( 23/ 23): TRACEBACK
%BLDRUN-I-DONE, completed: PYTHON
internals