The GANTT Procedure
- Overview
- Getting Started
-
Syntax
-
Details
Schedule Data Set Missing Values in Input Data Sets Specifying the PADDING= Option Page Format Multiple Calendars and Holidays Full-Screen Version Graphics Version Specifying the Logic Options Automatic Text Annotation Web-Enabled Gantt Charts Mode-Specific Differences Displayed Output Macro Variable ORGANTT Computer Resource Requirements ODS Style Definitions
-
Examples
Line-Printer Examples Printing a Gantt Chart Customizing the Gantt Chart Graphics Examples Marking Holidays Marking Milestones and Special Dates Using the COMPRESS Option Using the MININTERVAL= and SCALE= Options Using the MINDATE= and MAXDATE= Options Variable Length Holidays Multiple Calendars Plotting the Actual Schedule Comparing Progress Against a Baseline Schedule Using the COMBINE Option Plotting the Resource-Constrained Schedule Specifying the Schedule Data Directly BY Processing Gantt Charts by Persons Using the HEIGHT= and HTOFF= Options Drawing a Logic Gantt Chart Using AON Representation Specifying the Logic Control Options Nonstandard Precedence Relationships Using the SAS/GRAPH ANNOTATE= Option Using the Automatic Text Annotation Feature Multiproject Gantt Charts Multisegment Gantt Charts Zoned Gantt Charts Web-Enabled Gantt Charts Using the CHARTWIDTH= Option Using the TIMEAXISFORMAT= Option Statement and Option Cross-Reference Tables
- References
| Computer Resource Requirements |
There is no inherent limit on the size of the project that can be accommodated by the GANTT procedure. The number of activities in the Gantt chart is restricted only by the amount of memory available. Other memory-dependent factors are the type of Gantt chart required and the desired display mode.
Naturally, there needs to be a sufficient amount of core memory available in order to invoke and initialize the SAS System as well as to meet the memory requirements of the specific mode in which you invoke the procedure. For example, more memory is required when using high-resolution graphics than when using line-printer mode since the graphics sublibrary has to be loaded. As far as possible, the procedure attempts to store all the data in core memory. However, if there is insufficient core memory available for the entire project, the GANTT procedure resorts to the use of Utility data sets and swaps between core memory and Utility data sets as necessary.
The data storage requirement for the GANTT procedure is proportional to the number of activities in the project, and it depends on the number of schedule variables, the number of ID variables, and whether the Logic and Labeling options have been specified or not.