You can impose an explicit "objective cut" constraint:
con NonnegativeCost:
cost >= 0;
But that will probably actually increase the solve time.
A more promising approach is to try different choices for the ALGORITHM= option. If you can share the SOLVE statement you are currently using, as well as the LP solver's iteration log, I might be able to give a more specific recommendation.
... View more
![SASGF 2020 [Virtual] Attendee](/html/@A53A708409112314CE528E074D4C8C1F/badge_icons/badge_sasgf20_attendee.png "SASGF 2020 [Virtual] Attendee"){kind=icon}
