The PM Procedure

invokes the procedure in a noninteractive mode. The schedule for the project is still computed and the requested output data sets are created and saved. However, the PM window is not displayed. This option is useful for scheduling large projects that do not need to be updated interactively. Note that invoking PROC PM with the NODISPLAY option is similar to invoking PROC CPM; however, because the format of the Schedule output data set is different for the two procedures, you might see some differences in the order and content of the observations. See Schedule Data Set for details.

identifies a SAS data set that can be used to save and restore preferences that control the project view. For example, preferences such as the font, column order, column widths, filters, and so forth, can be saved from one invocation to another. See PROJECT Data Set for more details about this data set and the preferences that can be saved in it.

specifies a descriptive string identifying the name of the project. This string is used to label the PM window.

specifies a descriptive string identifying the summary task. By default, when there is more than one root parent activity in a project, PROC PM creates a summary task named “Summary” (or “Project Summary” if the input format for the activity variable is 15 or greater). So, if there is already a child activity named “Summary” (or “Project Summary”) in the input data, the resulting schedule forms a cycle. The SUMMARYNAME= option enables you to override the default by specifying a different name for the summary task, thereby avoiding the previously described problem.

indicates that an observation is to be added to the Schedule output data set (and the Resource Schedule output data set) for each activity that appears as a value of the variables specified in the SUCCESSOR or PROJECT statements without appearing as a value of the variable specified in the ACTIVITY statement. In other words, the Schedule output data set produced by PROC PM contains one observation for every activity that appears as a value of the ACTIVITY, SUCCESSOR, or PROJECT variables (as long as it has not been deleted in the current invocation of the procedure). It also contains an observation for every activity that is added to the project using the graphical user interface.

indicates that all relevant variables are to be copied from the Activity data set to the Schedule data set. The procedure carries over to the output data set all the relevant variables from the input data set. Thus, the Schedule output data set contains all the project information that is necessary to schedule it.

requests that the procedure assume automatic completion (or start) of activities that are predecessors to activities already completed (or in progress).

indicates that a variable named PCT_COMP is to be added to the Schedule output data set (and the Resource Schedule output data set) that contains the percent completion time for each activity (for each resource used by each activity) in the project.

indicates that activities that are completed or in progress have nonzero float.

indicates that the PM procedure is to compute a WBS code for the activities in the project using the project hierarchy structure specified. This code is computed for each activity and stored in the variable WBS_CODE in the Schedule output data set.

indicates that, in addition to the ascending sort variables (ES_ASC, LS_ASC, and SS_ASC) that are requested by the ESORDER, LSORDER, and SSORDER options, the corresponding descending sort variables (ES_DESC, LS_DESC, and SS_DESC, respectively) are also to be added to the Schedule output data set.

indicates that a variable named ES_ASC is to be added to the Schedule output data set; this variable can be used to order the activities in such a way that the activities within each subproject are in increasing order of the early start time. Note that this order is not necessarily the same as the one that would be obtained by sorting all the activities in the Schedule data set by E_START.

indicates that a variable named LS_ASC is to be added to the Schedule output data set; this variable can be used to order the activities in such a way that the activities within each subproject are in increasing order of the late start time.

is equivalent to specifying the ESORDER and LSORDER options (and the SSORDER option when resource constrained scheduling is performed).

indicates that a variable named SS_ASC is to be added to the Schedule output data set; this variable can be used to order the activities in such a way that the activities within each subproject are in increasing order of the resource-constrained start time.