41.   The only requirement regarding the software itself is that each file should contain a module header.

42.   In such circumstances, the recommended course of action is to mass-produce module headers that contain only the minimum information required.

43.   A stand-alone facility is delivered with the LIFESPAN issue which allows module headers to be mass-produced.

44.   It recommends how to generate modules, and what they and their module headers should contain.

45.   The mnemonics used in the Relationships Listing map onto the text strings used within a module header.

46.   This option is used to update the module header for source, foreign and pmodel modules.

47.   If the module name is accepted by LIFESPAN, then you will be able to update the module header by making entries in the following fields.

48.   The purpose of scanning is to check that all the information in the module header has been correctly formatted, and is in the correct place.

49.   The versions of the module header that LIFESPAN will accept are shown on the Log On page.

50.   This displays the title of the module as contained in the module header.