MODULE: Create Module Title File

MODULE will collect the module statements, task-module pointers, and the task statements on the specified Task Title file to produce a Module Title file. The difference between these two files is that one contains duty title statements, and the other contains the module title statements. Both files contain mapping tables that identify which tasks are assigned to each duty or module. MODULE performs limited error checking on the data collected, but the input module titles should be processed by AUDITM for a more thorough check.

Automatic Process Generation

MODULE will generate and add a TASKXX runstream if the P option is specified.

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 module
	P   Print listing of task and module titles
ssss:       The study number
TT:         Input Task Title file
MT:         Output Module Title file

MODULE Control Card

MODULE:  cc 01-06   The literal 'MODULE'
study:   cc 08-11   The study number for this run
setid:   cc 13-18   The identifier of this module set.
title:   cc 20-79   The title for this module set

Module Title Cards

This set of cards must include all the desired module titles for this module set. These control cards must be in sequence and 1 set must exist for each module. To check these cards for any errors, missing lines, or out of sequence statements the AUDITM program should be run. The format for this set of control cards is described below.

num:     cc 04-05   The line number within this title.  Each title may
		    consist of 1-15 lines.
seq:     cc 08-11   The the sequence number for this title.
title:   cc 15-74   This area must contain the module title statement. It
		     is recommended that second and subsequent lines of a
		     statement be started in column 16 instead of column
		     15 to help differentiate them from the first line of
		     a task or module title.

These cards are terminated by an '@eof' image.

Module Pointer Cards

The cards contained in this section identify which tasks are to be assigned to which modules. The cards may be in any sequence. Duplicate cards will be ignored.

module:  cc 01-04   The sequence number of the module being assigned
		    the specified task (right justified).
task:    cc 06-09   The number of the task to assign to this module
		    (right justified)

These cards are terminated by an end-of-file or an '@eof' image.

Examples

@codap module p ssss tt000 mt000
MODULE ssss STS001 This is the title for a test of MODULE
    1 001     STS 553x0, engineering assistant
    2 001      specialist, dated september 1982
    1 002     1. career field structure within civil
    2 002      engineering
    1 003     1a. civil engineering structural
@eof
0001  123
0003    8
0003   12
0003   12
0002  200
0001  111
@EOF

A new Module Title file named mt000 will be created with the module titles above. Tasks 111 and 123 will be assigned to module 1. Tasks 12 and 8 will be assigned to module 3. Task 200 will be assigned to module 2. Upon completion of this run, a TASKXX run will be started using mt000 as its input file.

While the previous example is perfectly valid, usually the module titles and pointers are extensive and are kept in separate "card" files. A more typical runstream example would look like this:

@codap module p ssss tt001 mts01
module ssss sts001 Tactical Aircraft Maintenance
@add tsts1
@eof
@add psts1
@eof

Back to document index