Skip to main content
ng-21-Visitor
1-Visitor
February 5, 2016
Solved

setconfig.mcc files

  • February 5, 2016
  • 4 replies
  • 1881 views

Hello every one please can anyone tell me that how the creo knows to pick a proper file during model check execution, means there are 3 files in setconfig.mcc

1.heavy

2.medium

3.light

 

how it knows to set any one of above file when modelcheck is run. what is the procedure or mechanism to know which file to be set..


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by James62

It depends on CNFG_SELECT_AUTO option in config_init.mc file.

4 replies

James621-VisitorAnswer
1-Visitor
February 5, 2016

It depends on CNFG_SELECT_AUTO option in config_init.mc file.

ng-21-VisitorAuthor
1-Visitor
February 5, 2016

Hi james

       I agree that it depends on config_select_auto option , if its value is set to "Y" then system will go through condition.mcc file and if its value is set to "N" or "A" then system will go through setconfig.mcc file. but inside setconfig.mcc file there are three options- 1. heavy 2. medium 3. light. Each of these options have different combination of config files.

My question is - when i go through setconfig.mcc file then how modelcheck will understand to pic which option among 1. heavy 2. medium 3. light.

James621-Visitor
1-Visitor
February 5, 2016

Setconfig.mcc makes a list of those three options available to the user in File -> Options -> Environment menu. The user selects the option then the specified configs in setconfig.mcc file get loaded to modelcheck.

http://help.ptc.com/creo_hc/creo30_pma_hc/usascii/index.html#page/pma/model_analysis/To_Set_Up_the_setconf_mcc_File_Usin…

Terms & ConditionsAccessibility statement