Last updated 18 Nov 97
GRPMOD creates a Module Title file by reading in the task membership masks for specified groups of tasks. A Module Title file can be used with MODVAR to compute the amount of time spent in each module by each incumbent. The resulting Module variables on the incumbent file can be reported with PRTVAR to greatly assist in the job typing process.
The first module contains all tasks associated with the first group, the second module contains all tasks associated with the second group, etc.. For this reason, one typically specifies non-overlapping stages from the task clustering in ascending order based upon the lowest TPATH sequence number within each stage.
Automatic Process Generation
A MODULE runstream is automatically generated by GRPMOD. If the 'P' option is used, a TASKXX will also be run.
Program Invocation
The specific syntax for program invocation varies between operating systems. This document diplays the code for the AIX version.
opt: E Expand the tasks-not-referenced into duties
P Print a TASKXX listing of the module title file
ssss: The study number
TF6: Input Task Factor file with stages from the task clustering
TT: Input Task Title file
MT: Output Module Title file
GRPMOD Control Card
GRPMOD: cc 01-06 The literal 'GRPMOD' study: cc 08-11 The study number for this run matrix: cc 13-18 The module set identifier title: cc 20-79 The title for the Module Title file
Group Specification Card(s)
Up to 3000 task groups may be specified. The group must have an 'MBR' vector on the input factor file. These cards are terminated by an '@EOF'.
group: cc 01-06 The group to be associated with this module title: cc 08-67 Optional new title for this module
Example
@codap grpmod - ssss tf600 tt001 mt000 grpmod ssss MOD001 Title for output file ST0193 Supervisor tasks ST0130 Clerical tasks ST0118 Maintenance tasks ST0214 Technical tasks @eof
This example would create a Module Title file with five modules (one for tasks-not-referenced).