PROC OPTMODEL comes with SAS-OR License. Which is bit costly and sometimes is not available. Whereas Proc PLAN comes with the BASE SAS only.     ... View more

Answered in this thread. ... View more

What version of SAS are you using? Do you know who made the data set and which version of SAS was used? SAS 9.4 datasets are not readable by version 9.2 32 bit at least. So if you have an older version of SAS that may be the cause.     ... View more

So this is basically aneed Oracle question and best asked at an Oracle forum, perhaps with little chance for success. But in well organised ships the DBA keeps all create table SQL in a version control system or similar, so talk to the DBA. Just out of curiosity - why do you want to see the SQL that created the table? Usually this says very little about subsequent updates, inserts etc. ... View more

In SAS/OR 14.1 (just released in July), PROC OPTMODEL has a new PROFILE statement that shows execution time for each statement: http://support.sas.com/documentation/cdl/en/ormpug/68156/HTML/default/viewer.htm#ormpug_optmodel_syntax11.htm   But it sounds like you are looking for detailed information about the solver execution invoked by the SOLVE statement, and the best source for that is the node log: http://support.sas.com/documentation/cdl/en/ormpug/68156/HTML/default/viewer.htm#ormpug_milpsolver_details10.htm   Can you share that?  And can you share the MILP formulation? ... View more

Yes, they are equivalent, and neither one is more efficient than the other.  In both cases, the LP solver sees a single vector of objective coefficients and optimizes the x and y parts simultaneously.  The variable names do not influence the solver, which internally considers all problems as having one set of variables indexed from 0 to n - 1. ... View more

Your latest version is not equivalent to the other two.  Instead, it should be:      con test{t in ASC}:sum{u in UIN:<t,u> in Map}y>=0; Also, the "Constraint is empty" message is only a NOTE and not an ERROR.  If you use the EXPAND statement, you will see that the constraint is 0 >= 0 because the sum is empty.  If you really want to avoid generating these constraints, you can use a logical condition:      con test{t in ASC: card(slice(<t,*>,Map)) > 0}:sum{u in slice(<t,*>,Map)}y>=0; ... View more

That note is probably because you did not populate the index set for Slope.  Compare to the READ DATA in my first reply. It is hard to tell what's going on without seeing the rest of your code.  Please show at least the declarations and READ DATA statements related to likelihood_to_apply and expected_profit. ... View more