this configuration setting affects code at load time. This is why the setup phase is too late.
Some (most) configuration settings can be set in setup(), but not this one (and some others
which affect loading of code). So unfortunately you will have to pass this as a command
or a pre_command to Specman before you load any code with such list constraints.
The commands you list work by themselves. I've just tried both options (set_config and config -gen)
and they seem to work:
Welcome to Specman Elite (11.10.057-s Build 444) - Linked on Sun Feb 10 16:18:19 2013
Protected by U.S. Patents 6,141,630 ;6,182,258; 6,219,809; 6,347,388;6,487,704; 6,499,132; 6,502,232; 6,519,727; 6,530,054; 6,675,138; 6,684,359; 6,687,662; 6,907,599; 6,918,076; 6,920,583; Other Patents Pending.
Checking license ... OK
Specman> show config gen
configuration options for: IntelliGen
-seed = 1
-improve_correlated_random = TRUE
-default_max_list_size = 50
-absolute_max_list_size = 524288
-default_min_list_size = 1
-default_list_size_policy = ALWAYS
-automatic_tc_util = FALSE
-tc_util_test_name = ""
-compile_gen_actions = FALSE
-check_constraints_under_point* = FALSE
-bidir_list_pseudo_methods = ALL
-solvability_mode = DEFAULT
-collect = OFF