Hello

  I meet a problem when translating the old configuration files to the python format. The case is simplified as follows:

  In the old configuration files:

<subsystem_a>/<package_a>/data/A.cfi
====================================
...
# we declare a block of parameters
block somename = 
{
  ...# parameter declarations here  
}
...


<subsystem_b>/<package_b>/data/B.cfi
====================================
...
# we are going to use these parameters
using somename
...


<subsystem_c>/<package_c>/test/C.cfg
====================================
...
# we include A.cfi so that "somename" is available in the scope
include "<subsystem_a>/<package_a>/data/A.cfi"
...
# we include B.cfi. "somename" is now accessible
include "<subsystem_b>/<package_b>/data/B.cfi"
...


  After translating the old configuration files one by one using translate.py, the result is like the following:

<subsystem_a>/<package_a>/python/A_cfi.py
=========================================
...
# we declare a block of parameters
somename = cms.PSet (
  ... # parameter declarations here  
)
...


<subsystem_b>/<package_b>/python/B_cfi.py
=========================================
...
# we are going to use these parameters
somename,
...


<subsystem_c>/<package_c>/test/C_cfg.py
=======================================
...
# we include A.cfi so that "somename" is available in the scope
process.load("<subsystem_a>.<package_a>.A_cfi")
...
# we include B.cfi and "somename" is now accessible
process.load("<subsystem_b>.<package_b>.B_cfi")
...


  However, when I use "python C_cfg.py" to compile, the compiler complains that "somename" is no defined. I wonder if there is an equivalent mechanism of the "using" in the cfg format as in the python format.

  Did anyone meet the same problem? How did you solve it? I am looking forward to your reply!!! Thank you for your time!!!