The INTPOINT Procedure
-
Overview
-
Getting Started
-
SyntaxFunctional SummaryDictionary of OptionsPROC INTPOINT StatementCAPACITY StatementCOEF StatementCOLUMN StatementCOST StatementDEMAND StatementHEADNODE StatementID StatementLO StatementNAME StatementNODE StatementQUIT StatementRHS StatementROW StatementRUN StatementSUPDEM StatementSUPPLY StatementTAILNODE StatementTYPE StatementVAR Statement
-
DetailsInput Data SetsOutput Data SetsConverting Any PROC INTPOINT Format to an MPS-Format SAS Data SetCase SensitivityLoop ArcsMultiple ArcsFlow and Value BoundsTightening Bounds and Side ConstraintsReasons for InfeasibilityMissing S Supply and Missing D Demand ValuesBalancing Total Supply and Total DemandHow to Make the Data Read of PROC INTPOINT More EfficientStopping Criteria
-
ExamplesProduction, Inventory, Distribution ProblemAltering Arc DataAdding Side ConstraintsUsing Constraints and More Alteration to Arc DataNonarc Variables in the Side ConstraintsSolving an LP Problem with Data in MPS FormatConverting to an MPS-Format SAS Data SetMigration to OPTMODEL: Production, Inventory, Distribution
- References
SUPPLY variable ;
The SUPPLY statement identifies the SAS variable in the ARCDATA= data set that contains the supply at the node named in that observation’s TAILNODE list variable. If a tail node does not supply flow, use zero or a missing value for the observation’s SUPPLY list variable
value. If a tail node has supply capability, a missing value indicates that the supply quantity is given in another observation.
It is not necessary to have a SUPPLY statement if the name of this SAS variable is _SUPPLY_. See the section Missing S Supply and Missing D Demand Values for cases when the SUPDEM list variable values can have other values. There should be no SUPPLY statement if you are solving
an LP.